Ttooleras
🔗

Canonical URL Checker

SEO Tools

Check canonical URL tags on any page and detect missing, wrong, or conflicting canonicals that cause SEO duplicate content issues.. Free, private — all processing in your browser.

Google Search Preview

Page Title
https://example.com › page
Your meta description will appear here. Write a compelling description to improve click-through rates.

Mobile Preview

Page Title
https://example.com › page
Your meta description...
⚠️ Title is empty
⚠️ Description is empty
Advertisement

The Canonical URL Checker examines any page for canonical tag configuration. A canonical URL tells search engines which is the preferred version of a page when multiple URLs serve similar content. Properly configured canonicals consolidate link signals and prevent duplicate content issues. Missing, wrong, or conflicting canonicals are among the most common SEO mistakes — and the tool helps identify them quickly.

Enter any URL and the tool checks: is there a canonical tag, does it point to an absolute URL, does it match the current URL (self-referencing), does it match the URL structure (https, www, trailing slash), is the canonical page itself indexable, are there conflicts between HTML canonical and HTTP Link header, does the canonical resolve with a 200 (not 4xx or 5xx). Also checks for common canonicalization issues like mixed-case URLs, trailing slash inconsistency, and URLs that canonicalize to non-canonicals (chains). All analysis runs by fetching the URL and parsing the response.

Canonical URL Checker — key features

Canonical tag detection

Finds canonical in HTML and HTTP Link header.

Self-reference check

Flags whether canonical points to current URL (ideal) or elsewhere (intentional?).

URL format validation

Checks absolute URL, HTTPS, trailing slash, and case consistency.

Canonical target accessibility

Fetches the canonical URL to confirm it returns 200 and isn’t blocked.

Chain detection

Detects canonicals pointing to pages with their own canonicals (chains are ignored by Google).

Noindex conflict

Flags when canonical target has noindex (contradictory to intent).

Bulk URL check

Process a list of URLs for site-wide canonical audit.

Client-side fetching

The tool fetches the page for you; no server-side logging.

How to use the Canonical URL Checker

  1. 1

    Enter URL

    Paste the page URL to check.

  2. 2

    Analyze

    Tool fetches the page and extracts canonical from HTML and HTTP headers.

  3. 3

    Review canonical

    See the canonical URL, whether it’s self-referencing or cross-URL, and its validity.

  4. 4

    Check target

    Tool validates the canonical target URL is accessible and indexable.

  5. 5

    Fix if needed

    Specific recommendations for any issues identified.

Common use cases for the Canonical URL Checker

SEO audit

  • Site-wide canonical audit: Verify every important page has correct self-referencing canonical.
  • Duplicate content prevention: Check that filter, sort, and tracking URL variants canonical back to the main page.
  • Migration verification: After URL structure changes, confirm canonicals updated correctly.

Debugging

  • Lost rankings investigation: When a page loses visibility, check if canonicals consolidated signals to a different page by mistake.
  • Template issue detection: Identify CMS or template bugs that generate wrong canonicals across many pages.
  • Cross-domain canonical check: Verify syndicated content has correct canonical pointing to original.

Ongoing maintenance

  • Weekly spot checks: Quick canonical check of high-value pages as part of regular SEO monitoring.
  • Before link-building: Confirm target page has correct canonical before investing in backlinks.
  • Post-deployment verification: Verify CMS updates didn’t break canonical tags.

Canonical URL Checker — examples

Good self-canonical

Typical correct configuration.

Input
https://example.com/article
Output
canonical: https://example.com/article (self-referencing)
status: correct
HTTPS matches, absolute URL, target accessible

Missing canonical

Common issue.

Input
https://example.com/page-without-canonical
Output
canonical: missing
recommendation: add <link rel=canonical href=\"https://example.com/page\"> to head
without canonical, Google may index variants separately

Wrong canonical

Points to unrelated page.

Input
product page canonicals to /
Output
issue: canonical points to homepage
impact: all product pages consolidate to homepage (signals lost)
fix: change canonical to point to the product page itself

HTTP in HTTPS page

Protocol mismatch.

Input
HTTPS page with canonical to HTTP version
Output
warning: HTTPS page canonicals to HTTP
impact: confusing — Google may not consolidate correctly
fix: update canonical to use HTTPS

Canonical to noindex

Contradictory configuration.

Input
page A canonicals to B; B has noindex
Output
conflict: canonical target has noindex
impact: Google ignores canonical, indexes A directly
fix: either remove noindex from B or change canonical

Technical details

Canonical tag is <link rel=\"canonical\" href=\"https://example.com/canonical-url\"> in the <head>. Can also be sent as HTTP Link header: Link: <https://example.com/canonical-url>; rel=\"canonical\".

Self-referencing canonical: the most common pattern. Page at URL X has canonical to X. Explicitly declares \"this is the canonical version\". Recommended for every indexable page.

Cross-URL canonical: page at URL X has canonical to URL Y. Tells Google to consolidate signals onto Y. Use when:
- URL X is a variant (tracking parameters, print version, sorting/filtering)
- URL X is a duplicate of Y (syndicated content)
- Y is the canonical version across the site

Canonical rules:
1. Should be absolute URL (https://example.com/page, not /page)
2. Should match protocol (HTTPS page canonicaling to HTTP is contradictory)
3. Should match www vs non-www preference consistently
4. Canonical target must be indexable (not noindex)
5. Canonical target must return 200 (not 404, not redirect)
6. Don\u2019t chain canonicals (X → Y where Y has canonical to Z is confusing)

Canonical vs 301 redirect: 301 physically redirects users and signals; canonical consolidates signals while keeping both URLs accessible. Use canonical for duplicates that must stay accessible (filter variants, tracking URLs); use 301 for moved pages.

Common mistakes:
- Missing canonical: Google guesses which is canonical, often wrong
- Wrong canonical: page A points to unrelated page B, losing signals
- Chained canonical: A → B → C, Google may not follow full chain
- Self-canonical with query strings: /page?x=1 canonicals to /page?x=1 not /page, preserving tracking variant
- HTTP/HTTPS mismatch: HTTPS page canonicalling to HTTP version
- Noindex on canonical target: signals Google shouldn\u2019t index the canonical — contradictory

Paginated content: Google deprecated rel=next/prev in 2019. For paginated content, each page canonicalizes to itself; treat each as a distinct canonical page. Page 1 canonicals to page 1, not /category.

Mobile/desktop: separate mobile URL (m.example.com) should canonical to desktop with <link rel=\"canonical\" href=\"https://www.example.com/page\">, and desktop adds <link rel=\"alternate\" media=\"only screen and (max-width: 640px)\" href=\"https://m.example.com/page\">. Responsive design with one URL is simpler.

Multi-regional (hreflang): works alongside canonical. Each locale variant has its own canonical (to itself), plus hreflang links to other language versions.

Common problems and solutions

Relative canonical URL

<link rel=canonical href=\"/page\"> is relative. Browsers resolve it, but sometimes Google doesn’t. Use absolute URL: https://example.com/page.

Canonical on every page to homepage

A template bug that puts the same canonical on every page consolidates ALL pages to the homepage, essentially removing other pages from index. A common catastrophic mistake.

Tracking parameters in canonical

If canonical includes ?utm_source=..., Google treats each UTM variant as canonical. Canonical should be the clean URL without tracking.

Canonical with hash

URL fragments (#section) are never part of the canonical URL — hashes are client-side. Strip # before putting in canonical.

Multiple canonicals

Multiple <link rel=canonical> tags in one page confuse Google. Use exactly one.

HTTP Link header conflict

If HTML canonical and HTTP Link header canonical differ, Google’s behavior is undefined. Use one or make them identical.

Canonical to redirect

Canonical target should return 200. If canonical points to a URL that redirects, Google may treat the redirect target as canonical or ignore the chain entirely.

Canonical URL Checker — comparisons and alternatives

Compared to manual inspection (viewing page source), this tool automates the check and validates target accessibility. Manual inspection works for single pages; bulk checking and validation needs automation.

Compared to paid SEO platforms (Screaming Frog, Sitebulb), this tool is free and handles single-URL checks quickly. Paid tools are better for site-wide crawls with thousands of URLs.

Compared to Google Search Console, this tool works on any URL whether you own it or not. Search Console is ideal for your own sites; this tool for ad-hoc audits.

Frequently asked questions about the Canonical URL Checker

What is a canonical URL?

The preferred URL for a page when multiple URLs could serve similar content. The canonical tag (<link rel=\"canonical\">) tells search engines which URL to treat as authoritative, consolidating ranking signals instead of splitting them across duplicates.

Do I need a canonical tag on every page?

Yes, as a self-referencing canonical. Every indexable page should have <link rel=\"canonical\"> pointing to itself. This explicitly declares the page as canonical, prevents accidental duplicates, and is considered best practice by Google.

What happens if I’m missing a canonical?

Google picks one automatically based on internal signals, which may not be the version you want. For simple sites with no URL variants, this often works fine. For sites with filters, tracking parameters, or similar, missing canonical can cause duplicate content issues.

Can canonical point to a different domain?

Yes. Cross-domain canonicals are valid and are used for syndicated content (original published at site A, syndicated to site B with canonical to A). Ensures Google attributes to the original.

How is canonical different from a 301 redirect?

301 physically redirects users and passes signals to the target URL. Canonical consolidates signals while keeping both URLs accessible. Use 301 when the URL is permanently moved; use canonical when both URLs must work (e.g., tracking variants, filter URLs).

Will Google always respect my canonical?

Canonical is a hint, not a directive. Google can and does pick different canonicals based on internal signals. Trust it more when: canonical points to page with similar content, canonical target is indexable, links and signals support the choice. Conflicting signals (different sitemaps, inconsistent canonicals) can override your preference.

Should canonical include query parameters?

Only if the parameters change the content meaningfully. Include session or tracking params: no (canonical should be clean URL). Include meaningful params (?product_id=123): yes. The canonical should be the single best URL for that content.

Is the URL I check logged?

The tool fetches the URL to analyze it. No persistent logging of URLs or analysis results.

Additional resources

Advertisement

Related tools

All SEO Tools

Learn more

Explore more tools

200+ free tools that run in your browser.

Browse all tools →