Skip to Content
URL Parameter AuditIssue 112

Faceted navigation URLs left indexable

What Is This Issue

This issue checks whether URLs with multiple filter and sort parameters (faceted navigation combination pages) have proper SEO directives to prevent them from being indexed as separate pages.

A URL passes this check if it has at least one of the following:

  • A canonical tag pointing to a URL with fewer parameters (preferably the base URL)
  • A noindex directive in the HTML meta tags
  • A noindex directive in the HTTP response headers (X-Robots-Tag)

A URL fails if it:

  • Contains two or more filter/sort parameters without proper handling
  • Has a self-referencing canonical that includes all the same parameters
  • Has more than five query parameters without any handling directive

Example:

  • Base URL: https://example.com/shoes
  • Combination URL: https://example.com/shoes?color=red&size=42&brand=nike&sort=price
  • Passing: The page has <meta name="robots" content="noindex, follow">
  • Failing: The page has no canonical or noindex directive, or has a self-referencing canonical

Why Is This Important

Faceted navigation creates severe SEO problems when left unhandled:

  • Crawlability: Faceted navigation can generate thousands or even millions of URL combinations from a single base page. Search engine crawlers waste their entire crawl budget on these low-value pages, leaving important pages uncrawled.

  • Indexability: Near-duplicate combination pages enter the search index, causing index bloat and reducing the overall quality signal of the site.

  • Rankings: Link equity and ranking signals are diluted across hundreds of near-duplicate faceted URLs instead of consolidating on the canonical page.

  • Duplicate content: Multiple faceted URLs with substantially similar content confuse search engines about which version to rank, potentially causing all versions to be suppressed.

  • Crawl budget waste: Googlebot and other crawlers allocate a finite number of requests per site. Unhandled faceted navigation causes crawlers to spend their budget on low-value combination pages.

Resolving this issue improves the overall SEO health score by preventing index bloat, optimizing crawl budget usage, and ensuring search engines focus on indexing valuable pages.

How XeoPix Detects This

XeoPix follows a logical detection process to identify unhandled faceted navigation pages:

  1. URL parameter analysis: The system extracts all query parameters from each crawled URL and counts the total number of distinct parameter keys.

  2. Faceted combination identification: A URL is classified as a faceted combination page when it meets either condition:

    • Contains two or more parameter keys from known facet patterns (filter parameters like color, size, brand; or sort parameters like sort, order)
    • Contains one filter key and one sort key simultaneously (e.g., ?color=red&sort=price_asc)

  3. Parameter depth check: The system checks whether the URL contains more than five distinct query parameter keys, which is considered excessive and high-risk regardless of pattern matching.

  4. Header inspection: The crawler checks the HTTP X-Robots-Tag response header for the presence of noindex (case-insensitive).

  5. HTML parsing: The raw HTML <head> section is parsed to:

    • Locate the first <link rel="canonical"> tag and extract its href attribute
    • Check for <meta name="robots"> tags containing the noindex token
    • Detect if multiple canonical tags are present (a misconfiguration)

  6. Canonical evaluation: If a canonical URL is found:

    • It is normalized (relative URLs are resolved against the page’s base URL)
    • The system checks whether the canonical URL contains fewer parameter keys than the page URL
    • It verifies whether the canonical is self-referencing (identical to the page URL including all parameters)

  7. Handling determination: A faceted combination page is considered “handled” if at least one condition is met:

    • Noindex header is present
    • Noindex meta tag is present
    • Canonical is present, is not self-referencing, and points to a URL with fewer parameters

  8. Issue triggering: An issue is raised when a faceted combination page lacks proper handling (no valid canonical or noindex directive).

How To Fix

  1. Audit all faceted URL combinations. Use server access logs or a full site crawl to collect all URLs containing two or more query parameter keys. Group them by parameter count and combination type to understand the scope.

  2. Define an indexability policy for faceted URLs. Decide which facet combinations have unique SEO value and should be indexed. In most cases, only these are worth indexing:

    • Single-facet pages that correspond to queries users actually search for (e.g., /shoes?brand=nike if “nike shoes” has significant search demand)
    • The base category page without parameters

  3. Apply noindex to all non-valuable combination pages. For every combination page that doesn’t meet your indexability policy, add to the <head>:

    <meta name="robots" content="noindex, follow" />

    Use follow so links on the page are still crawled even if the page itself is excluded from the index.

  4. Add canonical tags pointing to cleaner URLs. For combination pages that should consolidate to a simpler version:

    • Point to the base URL (no parameters) for maximum consolidation
    • Or point to a single-facet URL if that has SEO value
    • Ensure the canonical URL has fewer parameters than the page URL

  5. Avoid self-referencing canonicals on combination pages. A canonical that includes all the same parameters as the page URL provides no deduplication benefit.

  6. Handle excessive parameter depth. If a URL has more than five query parameters, it requires immediate noindex or canonical handling regardless of the specific parameters used.

  7. Normalize parameter order. Ensure faceted navigation generates consistent URL formats regardless of which filter the user selects first (e.g., /shoes?color=red&size=42 should always appear in the same order).

  8. Verify the fix via re-crawl. After implementing directives, re-crawl the affected faceted URLs to confirm the tags are present and correctly formed.

What We Store

Storage Level

Page Level

Database Table / Prisma Model

PageUrlParameterAudit

Fields Used

FieldTypeDescription
queryParamKeysString[]List of query parameter keys detected in the URL
validNoIndexPresentBooleanWhether a valid noindex directive is present on URLs with query parameters

Detection Dependencies

  • HTML Document
  • HTTP Response Headers

Examples

Example 1: Basic Faceted Navigation with Noindex

Scenario: An e-commerce category page with multiple filter combinations.

Problematic state (failing):

URL: https://example.com/shoes?color=red&size=42&brand=nike
Canonical: None
Noindex: None

Corrected state (passing):

URL: https://example.com/shoes?color=red&size=42&brand=nike
Noindex: <meta name="robots" content="noindex, follow" />

Example 2: Faceted Navigation with Canonical to Base URL

Scenario: A product listing page with sort and filter parameters.

Problematic state (failing):

URL: https://example.com/shoes?sort=price_asc&color=blue
Canonical: <link rel="canonical" href="https://example.com/shoes?sort=price_asc&color=blue" />

Corrected state (passing):

URL: https://example.com/shoes?sort=price_asc&color=blue
Canonical: <link rel="canonical" href="https://example.com/shoes" />

Example 3: Excessive Parameter Depth

Scenario: A URL with more than five query parameters creating combinatorial risk.

Problematic state (failing):

URL: https://example.com/products?color=red&size=42&brand=nike&sort=price&material=leather&style=casual
Canonical: None
Noindex: None

Corrected state (passing):

URL: https://example.com/products?color=red&size=42&brand=nike&sort=price&material=leather&style=casual
Noindex: <meta name="robots" content="noindex, follow" />

Unit Test

Test File

__tests__/seo-audit-checks/urlParameterAudit/issue-215-faceted-navigation-handled.test.js

Purpose

Validates that faceted navigation URLs (with multiple faceted parameters like filter, sort, color, size, etc.) are properly handled with either a noindex directive or a clean canonical URL.

Tested Function

runUrlParameterAudit from toggleGroups/urlParameterAudit.js

Issue Information

  • Issue Number: 215
  • Issue Code: faceted_navigation_handled
  • Toggle Group: urlParameterAudit

Test Scenarios

Positive Test Cases

  1. Less than 2 faceted parameters — the page URL has only one faceted parameter (filter=red), which is below the threshold of 2.
  2. 2+ faceted parameters with valid noindex — the page URL has 3 faceted parameters (filter, sort, color) and a <meta name="robots" content="noindex"> directive is present.
  3. 2+ faceted parameters with clean canonical — the page URL has 3 faceted parameters and a <link rel="canonical"> pointing to a clean URL (without query parameters) is present.
  4. Non-faceted parameters with 2+ params should not trigger issue — the page URL has 2+ query parameters (utm_source, utm_medium) but none are faceted parameters, so the issue is not reported.

Negative Test Cases

  1. 2+ faceted parameters but no noindex and no clean canonical — the page URL has 3 faceted parameters but neither a noindex directive nor a clean canonical is present.
  2. 2+ faceted parameters and canonical has parameters — the page URL has 3 faceted parameters and the canonical URL also contains query parameters (filter=red), meaning it is not clean.

Boundary Cases

  1. Exactly 2 faceted parameters — the page URL has exactly 2 faceted parameters (filter, sort), which meets the minimum threshold and triggers the issue when no handling is present.

Edge Cases

  1. Identify all 8 faceted parameters correctly — the page URL contains all known faceted parameters (filter, sort, color, size, brand, price, rating, category) and the test verifies all are reported.
  2. Case-insensitive faceted parameter matching — faceted parameters in uppercase (FILTER, SORT, COLOR) are still correctly identified.
  3. Empty HTML — passing an empty HTML string does not throw an error.
  4. Malformed HTML — passing unclosed or broken HTML tags does not throw an error.
  5. Cache validation — calling runUrlParameterAudit multiple times with the same context does not duplicate issues; results are correctly cached.

Expected Outcome

Fail

The issue should be reported when a page URL has 2 or more faceted parameters and does not have either:

  • A noindex directive in the robots meta tag, or
  • A clean canonical URL (without query parameters).

When reported, the issue includes:

  • A message of "Faceted navigation handling validation failed"
  • The list of facetedKeys detected
  • The canonicalUrl (if present)
  • A validationErrors array describing what is missing

Pass

The issue should not be reported when:

  • The page URL has fewer than 2 faceted parameters, or
  • A valid noindex directive is present, or
  • A clean canonical URL is present, or
  • The query parameters are not faceted parameters (e.g., only tracking parameters).

Validation

  • Correct issue detection for 2+ faceted parameters without proper handling
  • No issue detection when noindex or a clean canonical is provided
  • No issue detection for fewer than 2 faceted parameters
  • No issue detection for non-faceted parameters (e.g., tracking parameters)
  • Accurate identification of all known faceted parameter keys
  • Case-insensitive matching of faceted parameter names
  • Graceful handling of empty and malformed HTML
  • Cache behaviour prevents duplicate issue entries on repeated calls
  • toggleGroups/urlParameterAudit.js
  • issueCodes.js
  • utils/issues.js

Coverage Summary

  • Covers all positive scenarios: below threshold, noindex present, clean canonical present, non-faceted params only
  • Covers all negative scenarios: missing handling, non-clean canonical
  • Covers boundary condition: exactly 2 faceted parameters
  • Covers key identification with all known faceted parameter keys
  • Covers case-insensitive matching for faceted parameters
  • Covers error resilience: empty HTML, malformed HTML
  • Covers cache deduplication behaviour

References

Last updated on
Issue 111Issue 113