Reading what a live page declares
The canonical tag checker is the starting point for any single URL. It requests the page from this site's server, follows redirects to the final response, and reports every hop with its status code, then the canonical declared in the HTML head, any canonical sent in an HTTP Link header, and the robots directives. The Link header matters because it never appears in View Source, and it is the only way a PDF or other non-HTML file can declare a canonical at all.
Two limits follow from fetching server-side. First, the checker does not run JavaScript, so a canonical injected or rewritten by a script will not appear, and "no canonical found" on a JavaScript site may only mean the tag exists in the rendered page. Second, the checker is not Googlebot. A site that varies its response by user agent, verifies crawlers by IP address, or has been compromised with cloaked tags can show it a different page than it shows Google.
The bulk canonical checker runs the same server-side fetch across up to 25 URLs and lays the results side by side, with the same blind spot for JavaScript. Its value is comparison. Paste the variants of one page, a sample from one template, a paginated series or a set of language versions, and the pattern across rows shows whether a template prints a fixed URL on every page or drops the tag where it should not. Consistency is not correctness, so pair it with a crawler for indexability and link data.
Writing and validating markup
The canonical tag generator runs in the browser and sends the URL nowhere. It normalizes what you enter, lowercasing the host, using HTTPS, removing tracking parameters and optionally adding a trailing slash, then writes the result as an HTML link element, an HTTP header, or a PHP example. What it cannot know matters as much: whether the URL returns a 200, whether your site uses www, and whether a color or size parameter should consolidate.
The canonical tag validator also runs entirely in the browser, with no network request, which makes it the tool for markup a URL-based check cannot reach: a staging template behind a login, or the rendered head copied from browser developer tools after JavaScript has run. It checks for exactly one canonical, placement in the head, an absolute HTTPS URL, a usable href, and a noindex sitting beside a canonical that points elsewhere. A clean result confirms the form of the tag, not that the target is the right page.
The hreflang tag generator builds the alternate link set for international sites, again in the browser. It checks language codes against ISO 639-1 and region codes against ISO 3166-1, flags common errors such as a UK region code where the standard code is GB, and outputs both HTML links and a sitemap block, so you can maintain whichever method the site already uses. Every version in a set must list itself and all the others, and a generator cannot confirm that the other pages link back, so the return links still need checking. Each page in the set should also carry a self-referencing canonical, never one pointing at another language.
Choosing the right tool
- To see what one live URL declares after redirects, use the canonical tag checker.
- To compare a template's output across many pages, use the bulk canonical checker.
- To test markup before deployment or after rendering, paste it into the canonical tag validator.
- To write a normalized element from scratch, use the canonical tag generator.
- To build language and region alternates, use the hreflang tag generator.
What none of them can show
No tool on this site reports the canonical Google selected, how it clustered the duplicates, or how sitemaps and internal links shaped that decision. That answer lives only in the indexed data of URL Inspection, and Google notes that even its own live test cannot predict which version will be treated as canonical. Use the tools to make the declaration clean and consistent, then let Search Console confirm the outcome. Nothing entered into any of the five is stored: URLs are fetched to produce a report, and pasted HTML never leaves the browser.