A page group ties a set of entities from your Knowledge Graph to a layout. Yext Pages generates one page per entity in the group, and all those pages share the same layout. One site can have multiple page groups — useful for segmenting pages by location type, region, or any other entity characteristic.

Create a Page Group

After you create a site, you'll be prompted to set up your first page group. You can also add more page groups at any time from the Page Groups screen.

To create a page group:

1. Navigate to Pages > [Your Site] > Page Groups.
2. Click + Add Page Group.
3. Name your page group.
4. Select an entity type. This determines which entities will have pages generated. See Supported Entity Types below.
5. Optionally, select a saved filter to refine which entities within that type are included. For example, you might filter to only locations in a specific region, or only stores currently marked as open. See Configure Page Group Scope below.
6. Select one or more locales. A page will be generated for each entity in each selected locale.
7. Set a URL template. The default template is recommended for most sites. If you need a custom path structure (for example, to avoid conflicts across multiple page groups), select Custom and define your template. See URL Templates below.
8. Choose whether to Generate a Directory and/or Generate a Locator. Both are checked by default and recommended — directories improve SEO and site navigation, and locators help visitors find nearby locations. You can always add or remove these later.
9. Click Next.

Once you click Next, the site deploys in the background. Expect this to take a few minutes. After the deployment completes, you'll see your page group on the Page Groups screen. If you enabled a directory, you'll also see four additional page groups created by the directory manager — one for each level of the directory hierarchy.

Note: If your site is already live on a production domain, use a staging environment before creating new page groups. Creating a page group triggers a deployment, which would publish unfinished pages to production. See Staging Environment for details.

Tip: If you're creating a page group based on an existing one — such as intent pages or coming soon pages — duplicate an existing page group instead of starting from scratch. Duplication carries over the entity scope and full layout. See Create Intent Pages and Create Coming Soon Pages for step-by-step workflows.

Supported Entity Types

Each page group is tied to a single entity type. Any entity type with an address field is supported, including:

Note: Only built-in entity types with an address field are currently supported. Support for additional entity types is planned for future releases.

Configure Page Group Scope

By default, a page group includes every entity of the selected type. Use a saved filter to narrow the scope — for example, to only show open locations, or only locations in a specific region.

Saved filters are created and managed in the Knowledge Graph. A few examples of how to use them:

Important: Make sure no entity is included in more than one page group on the same site. Each entity should generate exactly one page. If your saved filters overlap, you'll end up with duplicate pages for some entities.

To edit an existing page group's name, locales, URL template, or saved filter: from the Page Groups screen, click the ellipsis menu next to the page group and select Configure Page Group. Note: you can edit the saved filter, but not the entity type, after creation.

URL Templates

Every page in a page group uses a URL template to define its path. The template is set when you create the page group.

Default URL templates

The default template is recommended for most sites. It builds URLs from each entity's address fields:

Custom URL Templates

Select Custom during page group setup to define your own path structure. Custom templates support:

• Static strings (for example, /locations/stores/)
• Any string field from the entity (for example, {name}, {address.city})

Custom URL templates are most useful when you have multiple page groups built on the same entity type — for example, standard location pages and intent pages. Without distinct URL templates, page groups on the same entities will produce conflicting paths.

Locale Code in URLs

When configuring the URL template, you must select a Primary Locale. This determines which locale is treated as the canonical language for your pages.

The Include locale code setting controls whether a locale prefix appears in the URL:

Note: The default setting keeps primary locale URLs clean and prevents breaking changes if you add additional locales later. If you switch to For primary and additional locales after your site is live, your primary locale URLs will change, which can break existing links and affect SEO.

Note: Directory and locator page groups automatically inherit the locale code setting from their parent location page group.

Keep URLs in Sync with Listings

When you create a page group, Yext automatically creates a custom URL field on the entity type and keeps it synchronized with your live page URLs. If you use Yext Listings, you can map this field to the websiteUrl field in Listings so your publisher listings always reflect the correct, brand-verified URL — even as your site evolves.

For steps on finding the auto-generated field, mapping it to Listings, and verifying it's working, see Sync Pages with Listings.