Quick answer
Compare the final page’s declared canonical with its intended representative URL and Google’s last selected canonical. Correct an erroneous template or header, then align links and sitemap entries. A canonical is a preference, not a redirect or a guarantee that Google will select the same URL.
Start with a final page that actually loads
Use this guide for a reachable page whose canonical points to an unintended old or temporary URL. Agree the representative URL with the content owner. Diagnose wrong redirects separately, and allow for delay in Search Console’s processed canonical.
You need site-owner access to the application or CMS that supplies the signal and verified Search Console access to compare Google’s view. A host move that kept public URLs unchanged may not need any canonical change. Deliberate duplicate pages may correctly point to another representative page, so decide with the content owner which URL should represent this particular content before editing.
Separate the declared URL from Google’s selection
Inspect the final page’s HTML head for a rel="canonical" link and, where applicable, its HTTP Link header. Record every declared destination and whether it uses the intended scheme, host and path. A template or SEO plugin can continue emitting the previous domain after files move. Check both the original source and rendered page when application code may alter the head. Multiple conflicting declarations deserve owner review, not another tag added on top.
In Search Console URL Inspection, compare the user-declared and Google-selected canonical for the same URL. The indexed result reflects Google’s last processing and can lag behind a live fix. Google may choose differently even when your tag is technically correct, because canonicalisation considers duplicate content and other signals. A declaration is a strong hint, not a command. Do not infer an indexing defect merely because two genuinely duplicate URLs consolidate under one representative.
Find the signal owner before editing
Compare the final page’s declared canonical with its sitemap entry, current internal links and any HTTP redirect chain. Google lists redirects and canonical annotations as strong signals and sitemap inclusion as weaker. Contradictory destinations can make diagnosis harder. Check whether the old or staging destination is still public and has matching content; a temporary copy should be retired or properly restricted through its own access plan, not made public by casually removing a protective rule.
Locate the actual owner of the wrong annotation: page metadata, a CMS or SEO setting, template code, or a server-controlled HTTP header. Do not assume a specific plugin exists on a Novasean-hosted site. Save the prior value and test one representative page before changing a site-wide template. If the Google-selected URL differs despite coherent technical signals, review whether the pages are truly distinct and follow Google’s canonical troubleshooting rather than forcing repeated edits.
Make the smallest justified correction
If the declared canonical is plainly a carry-over from the old deployment, the authorised application owner can replace that one erroneous value with the agreed representative URL, using the CMS or template actually installed. For a non-HTML resource that uses an HTTP canonical header, ask the responsible response owner to correct that header. Keep deliberate canonical relationships for duplicate variants; do not force every URL to self-reference or redirect pages that visitors still need.
Check that the changed final page still serves content and the canonical now names an accessible representative URL. Sample related templates, a query-parameter variant and both preferred hostnames if the change was global. If the new value points to an unrelated page or breaks a legitimate variant, restore the saved value and narrow the edit.
Monitor the selected canonical as Google reprocesses
Recheck the live HTML or header, sitemap and internal links, then use Search Console URL Inspection to monitor Google’s later selected canonical. Request indexing for a representative important URL if the tool offers it, but allow for reprocessing. A corrected hint does not guarantee Google will select it, include the page, recover traffic or meet a deadline. If selection remains unexpected, preserve the before-and-after URLs and exact response evidence for the application owner or Search Console specialist.
Example: a staging hostname remains in the canonical
On the intended public page https://www.example.com/help/, an inherited canonical to https://preview.example.com/help/ is wrong if the public URL is the agreed representative. Update the responsible setting to the public URL. Do not add a second canonical tag or change deliberate duplicate-page relationships.
If the declared canonical is correct but Google selects another URL, compare duplicate content and conflicting links, redirects or sitemap entries before rewriting the tag again. Record the last processed crawl separately from the live response.
Frequently asked questions
Is a canonical tag the same as a redirect? No. The tag expresses a preference while the page may remain visitable; a redirect sends visitors elsewhere.
Must every page be self-canonical? Google recommends a self-reference on a chosen canonical page, but a page may deliberately point to another representative and a canonical declaration is not mandatory on every URL.
Why did Google select another URL? Check content similarity and conflicting technical signals; Google makes the final selection.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.