Page type methodology
Page types make it possible to compare AI traffic and benchmarks without mixing blog posts, product pages, documentation, pricing pages, and other content.
How page types are assigned
Page classification uses reusable URL patterns rather than treating each URL independently. It groups paths such as /blog/, /docs/, /products/*, and /pricing for each host, saves page types for those patterns, and deterministically matches future URLs against active host and path mappings.
Ambiguous paths receive a second pass using titles, meta descriptions, headings, and visible text, rather than relying on URL shape alone.
Page type definitions
| Page type | Definition |
|---|---|
blog_editorial | Informational or editorial content such as articles, guides, thought leadership, news, press releases, case studies, glossary pages, research pages, media posts, and SEO content. |
product_page | Pages where a user evaluates, discovers, compares, or selects an offering. This includes product, feature, solution, ecommerce product detail, category, marketplace, catalog, listing, inventory, integration, and template pages. |
docs_support | Help, support, and documentation pages. This includes technical docs, help center articles, API references, manuals, troubleshooting pages, warranty pages, and support content. |
landing_page | Campaign-specific or conversion-focused pages, such as promotional pages, seasonal pages, partner campaigns, paid acquisition pages, product launch pages, event or webinar registration pages, trial pages, sign up pages, and lead-capture pages. |
brand_about | Pages about the company, brand, organization, or physical presence. This includes about pages, company pages, mission, team, leadership, careers, contact, locations, store locators, and investor pages. Home, security, and trust pages may classify here when supported by host-specific mappings or page evidence. |
pricing | Pricing, plans, subscription tiers, packages, and plan comparison pages. |
ugc_page | Public pages created or owned by users, customers, members, creators, vendors, or community participants rather than the brand itself. Examples include public profiles, creator pages, storefronts, vendor profiles, forum threads, community questions, reviews, and donation or tip pages. |
technical_infra | Machine-readable or infrastructure URLs used for crawling, indexing, AEO/SEO, APIs, tracking, or site operation. Examples include robots.txt, llms.txt, sitemaps, manifests, service workers, XML/JSON feeds, API endpoints, tracking endpoints, metrics endpoints, CDN/proxy URLs, and similar infrastructure files. |
file_asset | Direct downloadable or static file URLs, such as PDFs, images, videos, ZIP files, spreadsheets, presentations, documents, calendar files, catalogs, reports, and other file-extension-based assets. |
other | Utility, legal, transactional, or unmatched pages that should not be forced into another page type. Includes privacy, terms, login, sign up, account, cart, checkout, and internal search pages. Also used as the fallback when no mapping confidently classifies the page. |
Fallback behavior
Every page used in benchmarking resolves to a type. Host-specific mappings take precedence; otherwise generic rules handle common blog, docs, pricing, file, infrastructure, login, and legal patterns. If neither confidently classifies the URL, it resolves to other.
How page types are used in benchmarking
Compare product pages with product pages and documentation with docs/support. Views may include all types or filter to one type. Keep other in reporting, but interpret it as a utility or fallback bucket rather than a strategic content category.
Limitations
Ambiguous URL structures, reused paths, and template changes can require review. Update page evidence and mappings when these change.