A canonical change can be live while URL Inspection still shows Google's previous choice. Google needs to recrawl and process the affected pages before its selection can change. The delay can take days or weeks, and the new declaration is still a hint rather than a guarantee.
Start by separating two questions: did the deployment change the public page correctly, and has Google seen that version yet?
Check the live response first
Take a sample from every affected URL pattern. For each duplicate and its intended canonical, check:
- the final status and redirect destination;
- the canonical in the HTML source and rendered
<head>; - whether the preferred page returns
200and a self-referencing canonical; - which URLs appear in navigation, contextual links, and sitemaps;
- whether a template, locale setting, or cached response emits a different value.
Use one consistent canonical method for a page. Repeating the hint in both HTML and HTTP headers creates another place for conflicting values; it does not establish faster processing. HTTP Link canonicals are useful for documents such as PDFs.
Compare the deployment with Google’s last crawl
In URL Inspection, record the last crawl date, user-declared canonical, and Google-selected canonical for the duplicate and preferred page.
If Google's last crawl predates the fix, the old selection does not tell you whether the new version worked. Keep the live checks and revisit the inspection after recrawling. If Google has crawled the corrected page but still chooses another URL, compare that URL's content and signals too.
Remove conflicting signals
Point relevant internal links and sitemap entries to the preferred URL. Keep the canonical declaration stable across raw HTML, rendered output, and cached responses. Retire obsolete duplicates with permanent redirects when they no longer need to remain accessible.
These changes clarify the preference described in Google's canonical guidance. They do not let you set a deadline for Google's choice.
Track a small group of URLs
For each group of duplicates, keep the deployment date, live canonical, last Google crawl, and selected canonical together. Compare like-for-like pages instead of repeatedly changing a whole template because one URL has not updated.
Search performance rows do not show Google's canonical selection. Use URL Inspection for that check, then use performance data to assess whether the preferred pages gain relevant impressions and clicks.