Canonical Checker: Preferred URL and Target Check
Free individual check · without registration
Check which canonical URL names a page and whether the destination is reachable. The check detects conflicting information, redirects and noindex rules at the canonical destination.
Result of test
Ready
- Checked final URL
- —
- HTTP status
- —
Canonical and Tested Goal
- Declared Target URL
- —
- Final Target URL
- —
- HTTP status at the destination
- —
- noindex at the destination for Googlebot
- —
| Source | Declared value | Resolved URL |
|---|
What should you do next?
Robots Rules and Their Sources
The assignment refers to Googlebot for web search. The result proves no inclusion in the Google index; robots.txt and JavaScript are not checked here.
| Source | Scope of application | Rule found | Google web search |
|---|
snapshot of the retrieved response. No JavaScript rendering, no access to Google index data.
Fixing Canonical Errors: Choosing the Right Target
A canonical names the preferred URL for the same or very similar content. The check reads HTML link tags and HTTP link headers, resolves relative URLs, and checks a unique target for HTTP status and robots rules.
The target delivers 404, 5xx or noindex
First, check which page should be the preferred content. Correct an incorrect destination address or fix the error on the desired destination. If the target is to appear as a search result, it must not be excluded by noindex at the same time.
The goal continues
Enter the final preferred URL directly. Also check these in internal links and sitemap. A redirect from the entered test link is viewed separately from a redirect at the canonical destination.
HTML and HTTP headers name different targets
Match template, SEO extension, and server configuration to a target URL. For conflicting goals, this check does not arbitrarily select one for further retrieval.
There is no canonical
This is not automatically a mistake. For identical URL variants, a unique signal helps. For different contents, you must first decide whether a common canonical makes sense at all.
Example: Bundling tracking parameters
Delivery /leistung and /leistung?utm_source=newsletter The same content, both can point to the preferred URL:
<link rel="canonical" href="https://example.com/leistung">The URL is an example. Replace them with your own preferred address. Meaningful parameters, for example for independent content, should not be removed in general.
Canonical, noindex or forwarding?
- Canonical: Variants should remain achievable, but name a preferred version.
- 301/308: An old URL should permanently lead to the new address. Visitors come directly there.
- noindex: A page should not appear as a search result. It does not replace a canonical for bundling duplicates.
Basis: Google to set canonical URLs.
Frequent Questions about Canonicals
Does each side have to point to itself?
A self-referencing canonical can clarify the preferred URL. However, its absence is not automatically a mistake. Crucial are matching content and consistent signals for existing URL variants.
Is a canonical on another domain wrong?
Not mandatory. It may be intended for the same or very similar content. Check the target domain and content carefully. The checker assesses technical signals, not the full substantive equivalence.
Does the check recognize the canonical selected by Google?
No. It shows the information provided by the website. Google can choose a different canonical URL. You can see the selection of Google for your website in the URL check of the Search Console.
How many destinations does the check call?
It loads the entered page and at most an additional unique canonical destination; HTTP redirects are tracked. For a canonical to the final page URL, the same answer is reused. Further canonical chains are not called up.