How to check and fix canonical URL signals
One product page can declare several URLs
A product page can be requested at one URL, redirect to another, declare a canonical URL, publish an Open Graph URL, identify itself inside JSON-LD, and appear in an XML sitemap. Those values often differ after a domain move, framework migration, staging copy, or change to trailing-slash rules.
The checker follows the public response and places those declarations beside one reference URL. It does not produce a made-up authority score or claim to know which URL Google indexed.
- The final response URL shows where the submitted address resolves.
- The canonical tag is a strong hint about the preferred search URL.
- Open Graph and structured data URLs describe the entity shared with other systems.
- Sitemap inclusion is another canonicalization hint, not proof of indexing.
Fix pages that name different URLs
First decide which public URL should permanently represent the product page. Make redirects, internal links, canonical annotations, structured data, social metadata, and sitemap entries point to that choice when they describe the same page.
Do not force unrelated or materially different pages onto one canonical. Search engines can ignore a declared canonical when page content, linking, redirects, or other signals suggest another URL.
Know what this URL check cannot prove
Mydentify reads the submitted page and a bounded sitemap sample. Very large indexes, compressed sitemap files, blocked resources, personalized responses, or JavaScript-injected tags may require a deeper crawl.
Use Search Console URL Inspection to see Google's selected canonical and indexing state. This result is a reproducible view of public page declarations, not access to a search engine index.