Key takeaways
- The Google-selected canonical appears in URL Inspection’s indexed data, not its live test.
- Redirects and canonical annotations are strong signals; sitemap inclusion is weaker.
- A parameterized URL should be checked for its final destination before changing canonical tags.
- Consistent canonical declarations, sitemap entries, and internal links help communicate the preferred URL.
To find the URL Google has selected as canonical, inspect the full URL in Search Console and check Page indexing → Google-selected canonical in the indexed data. Then compare it with the URL you intended to represent the page, its redirect destination, declared canonical, sitemap entry, and internal links. A live test can help verify a fix, but it cannot predict Google’s canonical selection. Source: Google URL Inspection tool
Start with Google’s indexed data
- Open the Search Console property that contains the URL and enter the complete URL in URL Inspection.
- Record the page verdict and the Google-selected canonical under Page indexing. Note any crawl, fetch, or indexing problems in the same report.
- Inspect the intended canonical URL separately. If the original URL redirects, inspect the destination too: the original URL’s indexed result does not simply stand in for the destination’s result.
- Record when Google last crawled the page, so you can distinguish the indexed snapshot from changes made since then. Source: Google URL Inspection tool Source: Google’s single-page troubleshooting guide
Keep indexed data and the live test separate in your notes. Indexed data reflects what Google last recorded and is used for search results; the live test checks the current page and is useful after a fix. A successful live test does not guarantee indexing, and “URL is on Google” does not guarantee the page will appear for a search. Source: Google URL Inspection tool Source: Google’s single-page troubleshooting guide
Compare the signals side by side
Choose the preferred URL based on the content users should reach. The paths below are illustrative fields to collect, not findings from a real site.
| Field | What to record | What to investigate |
|---|---|---|
| Intended URL | The preferred address for the content | Whether it actually serves the intended page |
| Redirect destination | Each redirect and the final destination | Whether a duplicate or parameterized URL lands on an unrelated page |
| Declared canonical | The canonical URL in the page response | Whether it points to the intended URL |
| Sitemap | The relevant URL listed in the sitemap | Whether it conflicts with the declared canonical |
| Internal links | The URLs used by relevant navigation and content links | Whether links consistently point to the preferred URL |
| Google-selected canonical | The value from indexed URL Inspection data | Whether Google selected the intended URL or another version |
Google describes redirects and canonical annotations as strong signals, while sitemap inclusion is a weaker signal. Combining consistent signals can increase the chance that Google shows the preferred URL, but it does not make the declaration a guarantee. Google also recommends linking internally to the canonical URL and avoiding conflicting canonicalization methods. Source: Google canonicalization guidance
Worked example: a parameterized URL reaches the wrong page
Illustrative scenario: All paths below belong to the same fictional site. The team intends the product page at /products/green-dress/ to be canonical. A tracking-parameter version is supposed to reach that same product.
| Check | Illustrative finding |
|---|---|
| URL inspected | /products/green-dress/?campaign=spring |
| Redirect destination | /dresses/, a category page |
| Declared canonical on the landing page | /dresses/ |
| Sitemap entry | /products/green-dress/ |
| Internal links | Some product links use the parameterized URL; others use the clean product URL |
| Google-selected canonical for the inspected URL | /dresses/ |
The immediate problem is the redirect: the parameterized product URL reaches a category page instead of the intended product. The category page’s canonical may be appropriate for the category page; changing that declaration alone would not fix the incorrect destination. The example does not establish why Google selected the category URL.
How to debug and repair it
- Trace the request. Open the parameterized URL and use your browser’s network tools or a redirect checker to record every redirect and the final page. Check the redirect separately: Google’s live test follows redirects but does not show the final tested URL. Source: Google URL Inspection tool
- Confirm the intended content. Open the clean product URL and verify that it serves the product, rather than a category or error page. Check the page’s declared canonical and inspect it in Search Console.
- Fix the routing rule. If the parameter only identifies a campaign and does not change the product content, update the rule so the parameterized URL reaches the intended product rather than the category. Use a redirect to the clean product URL if that matches the site’s intended behavior.
- Align the other signals. Make sure the product’s canonical points to the preferred product URL, the sitemap lists that preferred URL, and relevant internal links use it. Google recommends a self-referential canonical on the canonical page and consistent internal links. Source: Google canonicalization guidance
- Retest and revisit indexed data. Trace the redirect again, run URL Inspection’s live test, and optionally request indexing for the corrected URL. Later, inspect the indexed data again to see what Google selected; the live test cannot make that determination. Source: Google URL Inspection tool
Do not assume every parameter is disposable. First check whether it changes the content or represents a page that should remain distinct; canonical guidance concerns duplicate or very similar pages. Source: Google canonicalization guidance
When the signals still disagree
Compare the current response with the indexed snapshot. If the redirect or canonical was recently corrected, Google’s indexed information may still reflect what it saw earlier. Use the live test to check the current page, but review sitemap and referring-page signals separately: the live test does not check them or determine whether the page is a duplicate. Source: Google URL Inspection tool
Also check crawl permission, page fetch, and indexing permission in Page indexing. Avoid using robots.txt as a canonicalization method, and do not use noindex merely to force a canonical choice within one site: Google says it blocks the page from Search rather than serving as the preferred canonical solution. Source: Google’s single-page troubleshooting guide Source: Google canonicalization guidance
Before closing the canonical investigation
- Record the inspected URL, intended URL, Google-selected canonical, and last crawl date.
- Trace the full redirect chain and confirm the final page contains the intended content.
- Correct conflicting routing rules, canonical declarations, sitemap entries, and internal links.
- Run a live test after the fix and request indexing if appropriate.
- Recheck indexed data later to see whether Google’s selection has changed.
FAQs
Where can I find Google’s selected canonical URL?
Enter the complete URL in Search Console’s URL Inspection tool and look under Page indexing for Google-selected canonical. The URL must be in the currently selected property. Source: Google URL Inspection tool
Can a live URL test confirm the canonical Google will select?
No. The live test can help you check the current page after a fix, but it cannot predict whether Google will consider that URL canonical. Check the indexed data for Google’s selection. Source: Google URL Inspection tool
Does a canonical tag guarantee that Google will index the preferred URL?
No. A canonical annotation is a strong preference signal, not a guarantee. Google recommends combining consistent signals, such as redirects, canonical annotations, sitemap inclusion, and internal links. Source: Google canonicalization guidance
Should I use noindex to make Google choose another canonical?
Google does not recommend using noindex to prevent canonical selection within a single site because it blocks the page from Search. Google recommends canonical annotations for that purpose instead. Source: Google canonicalization guidance
Sources
- How to Specify a Canonical with rel="canonical" and Other Methods | Google Search Central | Documentation | Google for DevelopersAccessed
- 网址检查工具Accessed
- URL-inspectietoolAccessed
- Inspect and troubleshoot a single pageAccessed
- URL Inspection toolAccessed
- Google-selected canonical is to a porn or dangerous off-domain siteAccessed
Discussion
Join the discussion