A listed page names another page as the main one
In the reportSitemap URL canonicalized away
sitemap_url_canonicalized_away · Review item
This appears when a page listed in your sitemap loads normally but names a different address as its canonical, the main version. The sitemap and the page then suggest different preferred addresses. Check which one you want in search, list it, and let the page's canonical agree with it.
Severity: Medium. Review it in your next round of site changes; the two signals conflict, but it can be intended for duplicate addresses.
Why it matters
Google suggests every page listed in a sitemap as a canonical, and advises against naming one address in a sitemap and another for the same page with rel="canonical".
What to do
- Look at the finding: it shows the sitemap entry, the canonical the page declares, and up to ten links to the page.
- If the canonical is right, list that address in the sitemap instead of this one.
- If the listed address is the one you want, correct the page's canonical to point to itself.
When to leave it as it is: if both addresses are intended for a while, for example during a move, you can leave it until the move is settled; Google decides which address to show.
What we read
We check the pages listed in your sitemap that our crawl requested and whose final address is the listed one, answering 200 with HTML; a redirect that comes back to the same address still counts. The crawl starts at your homepage and follows links, reserving every tenth page it fetches, up to 20, for sitemap addresses by default, within the audit's page limit. We read <link rel="canonical"> in the page's head and any canonical in its Link header.
A page is reported when it declares exactly one canonical and it differs from the listed address. The comparison ignores letter case in the host and similar details, but a trailing slash, www., http against https and the query all count as differences. Pages with two different canonicals are left to their own check.
Example & evidence
Illustrative example — one listed page, not a live audit.
https://bakery.example/sitemap.xml lists:
<url><loc>https://bakery.example/cakes/chocolate?size=large</loc></url>The page answers 200, and its head contains:
<link rel="canonical" href="https://bakery.example/cakes/chocolate">The page names a different address as its main version, so it is reported with the sitemap entry and the canonical.
A possible correction: if https://bakery.example/cakes/chocolate is the version you want and it works, list it in the sitemap instead.
Confirm & check again
Check for yourself: open the listed page's source, search for rel="canonical", and compare the address with the entry in your sitemap: letter case in the host does not matter, but a trailing slash, www., http against https and the query do.
Check again: Full audit — run a new audit of the site. A canonical corrected to match the listed address can be confirmed when every sitemap is read in full, every page it lists is reached and either redirects or answers 200 with complete HTML that is not only a frame for scripts, and none has two canonicals. Listing the canonical address instead is confirmed only if the crawl still reaches the old one, or it now permanently redirects within your site.
Limits & sources
The check reports the conflict, not which address Google chooses, and it does not request the canonical address. Canonicals added by JavaScript or placed outside the page's head are not seen, and listed pages the crawl does not reach are not checked.
Confidence: High because the sitemap entry and the canonical are both read directly.
Sources
- Google, Build and submit a sitemap — says Google generally shows canonical URLs in its results, which you can influence with sitemaps. Checked 25 September 2026.
- Google, How to specify a canonical URL with rel="canonical" and other methods — advises against naming one URL in a sitemap and a different one for the same page with rel="canonical". Checked 25 September 2026.
Editorial review: 29 September 2026