URL Parameters
URL parameters pass data in the query string and multiply crawlable addresses. Learn the types and how to stop them fragmenting your site.
TL;DR
URL parameters are the key and value pairs that follow a question mark in a web address. They pass information to the server or the page: which filter is active, which campaign sent the visitor, which page of results to display. Every distinct parameter combination is a distinct URL as far as a crawler is concerned.
Why URL parameters matter
Parameters are useful and they fragment your site, and both facts have to be managed at once.
- Duplicate content: The same content at many addresses splits ranking signals across versions.
- Crawl waste: Crawlers fetch parameter variants instead of pages you actually publish.
- Analytics fragmentation: One page traffic scattered across dozens of URLs in reporting.
- Signal dilution: Links pointing at different variants divide authority that should consolidate.
How to handle URL parameters
Inventory what your site generates
Server logs and analytics reveal parameters nobody remembers adding, often from long-dead integrations.
Classify by function
Tracking, filtering, sorting, pagination and session parameters each need different treatment.
Self-canonical to the clean URL
Tracking parameters should not create new indexable pages, so canonical them to the base address.
Block worthless patterns
Session identifiers and sort orders can be disallowed in robots.txt, since no combination deserves crawling.
Keep ordering consistent
Generate parameters in a fixed sequence so the same state always produces the same URL.
Prefer paths for real pages
Content that deserves indexing is better served by a clean path than a parameter, which reads as configuration.
URL parameters vs. clean URLs
URL parameters: State encoded in a query string. Flexible, easy to generate, and treated as a variant of a base page.
Clean URLs: State encoded in the path. Harder to generate dynamically, and read as distinct pages with their own standing.
The rule of thumb is that anything you want indexed and linked deserves a path. Anything that configures a view without changing what the page fundamentally is belongs in a parameter.
Parameter sprawl is invisible in a site map and obvious in server logs. Findrix checks crawler access and technical health across 31 points, then tracks whether seven AI engines cite your pages against named competitors. Every gap comes with the fix already written: technical, content and off-site. The audit is free, takes about a minute, and requires no signup.
Types of URL parameter
- Tracking: UTM tags and click identifiers, which should never create indexable pages.
- Filtering: Facet selections, where a few combinations deserve indexing and most do not.
- Sorting: Reordering the same content, which never deserves a separate indexed page.
- Pagination: Page numbers through a result set, which need distinct URLs that self-canonical.
- Session: Per-visitor identifiers, which should be blocked entirely.
- Localisation: Language and region, which are usually better expressed as paths or subdomains.
Why the parameter tool disappearing mattered
Google retired the URL parameter handling tool in Search Console, which had let sites declare how each parameter should be treated. The reasoning was that Google own handling had improved enough to make manual configuration unnecessary.
For most sites that is true. For large catalogues with heavy faceted navigation it removed a lever that was doing real work, and the replacement is doing the job properly at the site level instead.
Consistent canonicals, deliberate robots rules, and not generating variants that never needed to exist. That is more durable than a setting in someone else dashboard.
Frequently asked questions
Do URL parameters hurt SEO?
Unmanaged, yes. They create duplicate content, waste crawl budget and split ranking signals. Handled with canonicals and sensible crawl rules they are harmless and often necessary.
Should UTM parameters be blocked in robots.txt?
Usually not necessary if pages self-canonical correctly, since the canonical consolidates them. Blocking can help on sites where campaign URLs are heavily linked and crawlers spend real time on them.
How do I stop parameters creating duplicate pages?
Self-referencing canonicals pointing at the clean URL handle most cases. Add robots.txt rules for parameter patterns that should never be crawled, such as session identifiers and sort orders.