You check Google and see parameter URLs indexed: URLs with ?sort=, ?filter=, ?utm= or other parameters. These URLs create duplicate content and waste crawl budget. This guide explains why Google indexes parameter URLs and how to fix it.
What parameter URLs are
Parameter URLs include query parameters after the question mark:
— example.com/page?sort=price;
— example.com/page?color=red;
— example.com/page?utm_source=newsletter.
These URLs often show the same content as the main URL, creating duplicates.
Why parameter URLs matter
Indexed parameter URLs cause:
— duplicate content;
— split signals;
— wasted crawl budget;
— unstable rankings;
— wrong pages in search results.
They should be controlled to avoid these issues.
Reason 1: no canonical
The most common cause. Parameter URLs do not have canonical pointing to the main URL.
What to check:
— does the parameter URL have canonical;
— does it point to the main URL;
— is it consistent.
The fix: add canonical to parameter URLs pointing to the main URL.
Use canonical tag checker to verify canonical.
Reason 2: internal links to parameter URLs
If internal links point to parameter URLs, Google may index them.
What to check:
— do internal links use parameters;
— are they necessary;
— can they point to the main URL.
The fix: use clean URLs for internal links. Avoid parameters unless necessary.
Reason 3: sitemap includes parameter URLs
If the sitemap includes parameter URLs, Google may treat them as important.
What to check:
— are parameter URLs in the sitemap;
— can they be removed;
— are they necessary.
The fix: remove parameter URLs from the sitemap.
Reason 4: robots.txt does not block parameters
If robots.txt does not block parameter URLs, Google may crawl them.
What to check:
— are parameter URLs blocked;
— are the rules correct;
— are important parameters excluded.
The fix: block unnecessary parameters in robots.txt. Be careful not to block important ones.
Reason 5: external links to parameter URLs
If external sites link to parameter URLs, Google may index them.
What to check:
— are there external links to parameter URLs;
— can they be updated;
— are they intentional.
The fix: use canonical to consolidate signals. External links may still exist, but canonical helps.
How to diagnose parameter URL indexing
A practical sequence:
— search for site:yourdomain.com inurl:?;
— check which parameter URLs are indexed;
— check canonical;
— check internal links;
— check sitemap;
— check robots.txt.
If parameter URLs are indexed, add canonical and fix internal links. For a broader audit, SEO audit can help verify canonical, indexing and crawl issues in one place.
How to fix parameter URL indexing
Fix steps:
— add canonical to parameter URLs;
— use clean URLs for internal links;
— remove parameter URLs from sitemap;
— block unnecessary parameters in robots.txt;
— request removal in Search Console;
— monitor indexing.
FAQ
Why does Google index parameter URLs?
Because they are linked, not canonicalized, or included in sitemap. Google can crawl and index them.
Are parameter URLs bad for SEO?
They can be. They create duplicate content and waste crawl budget. Control them with canonical and robots.txt.
Should I block all parameters in robots.txt?
No. Block only unnecessary parameters. Blocking important ones can hurt functionality.
Does canonical fix parameter URLs?
It helps consolidate signals. But internal links and sitemap should also be clean.
Can parameter URLs outrank main URLs?
Yes, if they have more links or content. Canonical helps prevent this.
How do I find indexed parameter URLs?
Search for site:yourdomain.com inurl:? or use Search Console.
Should parameter URLs be in the sitemap?
No. Sitemap should include clean, canonical URLs.
How do I remove parameter URLs from Google?
Add canonical, block in robots.txt if needed, and request removal in Search Console.
Can external links cause parameter URLs to be indexed?
Yes. Canonical helps consolidate signals, but external links may still exist.
How often should I check parameter URLs?
After site changes and periodically as part of an SEO audit.
