Skip to main content
You can create page groups to represent sections of your website, business units, or projects and use them as a filter on the Pages report. Here are some frequently asked questions related to page groups.
Page groups show you aggregated page data relevant to your business. Page groups are the page-level equivalent of your keyword groups. Each group should contain pages that are similar and closely related or have something in common.Page groups come in two flavors: smart and custom:
  • Smart page groups are rule-based. They can be topical, based off page templates from your content management system, divisions of business units, or any theme your rules can capture.
  • Custom page groups are made from specific pages that you want to track in a single page group. They can represent any set of pages from your integrated web analytics profile.
You can create and manage your page groups in the Page Groups activity in the Settings area of Conductor. For instructions, refer to the Page Groups Setup article.
How many page groups can you create? How many rules can I add to a smart page group? And how many URLs can I add to a custom page group?By default, each web property has 25 or 50 page groups depending on your Conductor account configuration. If you need more page groups to accommodate your platform usage, you may be able to increase this number. Contact your Conductor representative to request more.Smart page groups can have up to 25 rules per page group and custom page groups can include up to 10,000 URLs.
Not sure how to group your pages? Below are some basic considerations for creating page groups.Customer PersonasDo you use personas to aim your content at specific types of customers with similar consumer habits and values? Create page groups to see your content’s performance for different personas.Topical page groups
  • E-commerce sites: Do you have different sections or departments set aside for different product lines or categories? Those different sections or departments can make useful page groups.
  • Publishers: Does your site have different sections with articles and posts on different topics or content types? Consider tracking that content together in a page group.
Consumer Buyer’s Journey
  • If you publish different content to buyers in different stages of the buyer’s journey, track and manage how each piece of content in each stage is performing with a page group.
  • If you break down the goals of your content based on Informational versus Transactional pages, use page groups to see how those goals are being met.
Templates and IdentifiersDoes your Content Management System (CMS) have unique ways of identifying pages that were created in the system? Check for patterns in the URL, Title Tag, and Meta Description, and use these identifiers to group your content in the same way as your CMS.Marketing Campaigns and Business InitiativesIf you are running marketing campaigns, you can use page groups to track the performance of content under different initiatives.Business UnitsA great way to group your content if you want to keep track of how different departments or business units are performing.Get ideas from keyword groupsAnother good place to start thinking about page groups is to look at how your keywords are currently organized.
You can create rules based only on a page’s:
  • URL
  • Title tag
  • <h> tags
  • Meta Description
Custom variables or other tags cannot be used to determine the constituent pages of a page group.
Yes. Analytics providers take case into account when reporting on your site, so URLs must be case sensitive when you add them to page groups in Conductor.
URLs in a custom page group can have one of three statuses:MatchedThis status means that Conductor has already discovered the page and will report on the URL when the page group is created.InvalidA URL is invalid if it is:
  • Missing the protocol.
  • Not part of the web property you have integrated from your web analytics.
  • Not part of the web property you track in Conductor.
  • Not structured like a URL.
Not MatchedThis status means that the URL is not currently tracked in Conductor and there is no data to report. Not Matched URLs will be reported on when Conductor discovers them either from the SERP or as a preferred URL, or from your analytics provider. Note that these URLs are case sensitive.
To appear as a matched URL, a page must:
  • Have received at least one session attributed to organic search during the last reporting period.
  • Be in the top 10,000 pages (or the top 100,000 pages, if you have upgraded) of pages receiving at least one session from organic traffic.
  • Match the URL recorded by your web analytics provider exactly. For example:
    • The URL you enter in a page group must include a trailing slash ( / ) if that is what your web analytics provider sends through your Conductor integration.
    • The URL you enter in a page group must match the exact case your web analytics provider sends through your Conductor integration.
You can still add pages to a page group that Conductor says are Not Matched. If they receive traffic from organic search, the page will appear in Conductor as Matched after the next publish period.
This is an indication you might have an issue with your web analytics integration. Previews for smart page groups are based on the latest weekly publication of analytics data. If Conductor did not receive data from your analytics provider, for the most recent week, the preview will not include any pages.If this occurs for you, contact Conductor Support to help troubleshoot your integration.
Regex—or “Regular Expression”—is a simple way to write a rule that finds and groups all the pages that share a specific URL pattern. Think of it like a “Find” feature, but for patterns instead of just exact text.For smart page groups, you can use regex as the “language” you use to write a rule based on the page’s URL. It lets you find all pages that look similar, without having to list them one by one with a custom group.

​
Example

Imagine you run an e-commerce site. You want a smart page group for all your individual Product Detail Pages, but you want to exclude your main Category pages. Your URLs look like this:The Problem: If you use a Contains: /products/ rule, Conductor will incorrectly select all four of those pages, mixing your category and product pages together.The Regex Solution: You need a rule that tells Conductor: “Only find pages that start with /products/ AND end with a dash followed by some numbers (like a product ID).”You would use a regex rule like this: /products/.*-\d+$. What this rule tells Conductor:
  • /products/ : “Find any URL that starts with the exact text /products/.”
  • .* : This is a wildcard for “followed by any text” (like green-widget).
  • -\d+$ : This breaks down as follows:
    • - : It must have a dash.
    • \d+ : It must then have one or more digits (0-9).
    • $ : And this pattern must be at the very end of the URL.
With this single regex rule, Conductor will group all your product pages while ignoring your category pages.Regex101 is a useful site for learning about and building your regex. AI tools like ChatGPT or Claude are also great for explaining your desired outcome, and having them return the necessary regex to input.