**URL parameters — tracking, filters, sorting, session IDs — can multiply one page into countless duplicate URLs and trap crawlers.** This check looks at whether your parameterised URLs are handled correctly: canonicalised to a clean version or disallowed where appropriate, so they don't create duplicate content or a crawl trap that wastes crawl budget on near-identical pages.
It looks at how your site handles URL parameters that don't change the core content. Specifically:
- Tracking parameters — utm_ and similar that shouldn't create indexable duplicates.
- Filter / sort parameters — faceted-navigation combinations that can multiply into many near-duplicate URLs.
- Session IDs — per-visitor parameters that create endless duplicate URLs if indexable.
- Handling — whether these are canonicalised to a clean URL or disallowed, versus left indexable.
Parameters canonicalised or disallowed appropriately passes; some param URLs indexable without a canonical is a warning; a parameter explosion creating duplicate or crawl-trap URLs is a fail.
GEObubbly inspects how parameterised URLs resolve — whether they canonicalise to a clean version, are disallowed, or are left indexable — and looks for signs of parameter-driven duplication. It's an extended Crawlability & Indexability check that runs partially, since assessing parameter handling depends on how the live site responds.
Parameters that don't change a page's core content — tracking tags, filters, sort orders, session IDs — can quietly multiply a single page into countless URL variations. If those are all indexable, you get two problems: duplicate content (the same page under many URLs, splitting ranking signals) and a crawl trap (engines spend crawl budget grinding through endless near-identical combinations instead of your real pages).
Faceted navigation on e-commerce sites is the classic culprit — a handful of filters can generate millions of URL permutations.
For GEO, a clean URL structure means engines spend their limited crawl on your genuine content and have an unambiguous canonical version to trust.
Parameters that don't change a page's core content — tracking tags, filters, sort orders, session IDs — can turn one page into many URL variations. If those variants are indexable, search engines see duplicate content (the same page under multiple URLs, splitting ranking signals) and can fall into a crawl trap, spending limited crawl budget on endless near-identical combinations instead of your real pages. On filter-heavy sites a few facets can generate millions of permutations.
A crawl trap is a part of a site that generates a near-infinite number of low-value URLs for crawlers to follow — most often faceted navigation, where combining filters and sort orders produces endless parameter combinations, or calendars and session IDs that never end. Crawlers waste budget grinding through these instead of your important pages. To avoid it, canonicalise filter/sort variants to a clean URL, disallow parameters that shouldn't be crawled in robots.txt, and don't create indexable links to every possible combination.
Sometimes — it depends on the parameter. For parameters that produce purely duplicate or low-value URLs (certain sort orders, session IDs, some tracking tags), disallowing them in robots.txt stops crawlers wasting budget on them. But be careful: blocking a parameter in robots.txt prevents crawling, so the engine can't see a canonical on those URLs, and you don't want to block parameters that lead to genuinely useful, indexable content. Often the better tool is a canonical tag pointing parameterised variants to the clean URL.
A canonical tag on a parameterised URL points to the clean, canonical version of the page, telling engines to consolidate ranking signals there while keeping the parameterised URL accessible for users. This is ideal for filter, sort and tracking variants that must remain reachable but shouldn't each be indexed separately — the canonical prevents the duplication without blocking the page. Combine it with a consistent URL structure and selective robots rules for true crawl-trap parameters, and you keep engines focused on your real, unique content.
They can if left unmanaged. utm_ tags are great for analytics, but each tagged URL is technically a separate address for the same page, so if those URLs get indexed they create duplicate content and split signals. The usual safeguard is a self-referencing canonical on the clean URL, so any utm-tagged variant consolidates back to it, plus consistent internal linking to untagged URLs. Used that way, tracking parameters serve their analytics purpose without fragmenting your pages in search.