Canonical URL Checker

Enter any URL to check its canonical tag — from both the HTTP response header and the HTML <link rel="canonical"> tag. See whether the canonical is self-referencing, points to another URL, or is missing entirely.

How to Use the Canonical Tag Checker

Five steps from entering a URL to understanding your canonical setup.

1

Enter a URL

Paste any full URL into the input field — include the https:// prefix. The tool accepts any publicly accessible page URL.

2

Run the Check

Click the check button. The tool fetches the page and inspects both the HTTP response headers and the HTML source simultaneously.

3

Review HTTP Header Result

See whether the server is sending a Link: <url>; rel="canonical" HTTP header, and what URL it points to.

4

Review HTML Tag Result

See whether the page’s <head> section contains a <link rel="canonical" href="..."> tag and what URL it specifies.

5

Interpret and Act

Each result is colour-coded green, orange, or red. Use the status labels to decide whether the canonical is correctly configured or needs attention.

HTTP Header Canonical vs HTML Canonical Tag

There are two places a canonical URL can be declared, and this checker reads both. Understanding the difference matters — search engines process each one slightly differently.

HTTP Header Canonical

The HTTP header method sends a Link: <https://example.com/page/>; rel="canonical" directive in the server response. This method is useful for non-HTML files such as PDFs, and for pages where you cannot edit the HTML directly. Some CMSs and CDNs set this automatically.

HTML Link Tag Canonical

The HTML method places a <link rel="canonical" href="https://example.com/page/"> element inside the <head> section of the page. This is the most widely used method and is fully supported by all major search engines.

When Both Are Present

If both methods are present and agree on the same URL, there is no problem. If they conflict — pointing to different URLs — search engines must decide which to honour, and they may ignore both as a conflicting signal. The tool flags this condition so you can resolve it.

  • Checks both detection methods in one request
  • Shows the exact canonical URL returned by each method
  • Flags conflicts between HTTP header and HTML tag
  • Works on any publicly accessible URL

Understanding Your Canonical Checker Results

Every result is colour-coded to help you act quickly. Here is what each status means and what to do about it.

Self-Referencing Canonical

The canonical URL matches the page URL you checked. This is the expected state for a primary page. It tells search engines: “This is the preferred version of this content.”

Points to a Different URL

The canonical tag points to a URL that is different from the page you checked. This may be intentional — for example, a paginated page canonicalising to the root page — or it may indicate a misconfiguration. Verify that the target URL is correct and intentional.

Canonical Tag Missing

No canonical tag was found in either the HTTP header or the HTML. Missing canonicals leave search engines to guess the preferred URL, which can lead to duplicate content issues and diluted ranking signals across URL variations (with/without trailing slash, HTTP vs HTTPS, www vs non-www).

Conflicting Canonical Signals

The HTTP header canonical and the HTML canonical tag point to different URLs. Search engines treat conflicting canonical signals as an unreliable hint and may disregard both. Resolve the conflict by ensuring both methods point to the same URL, or by removing one of them.

When to Use a Canonical Link Checker

The tool fits into several common SEO and development workflows.

🔍

Technical SEO Audits

During a site audit, use the checker to verify that key pages — homepage, category pages, product pages — all carry the correct self-referencing canonical. Spot pages that are accidentally canonicalised to a staging domain or old URL structure.

🔁

Site Migrations

After migrating a site to a new domain, CMS, or URL structure, check that canonicals have been updated. A common migration mistake is leaving canonicals pointing to the old domain, which can signal to search engines that the old site is still the preferred source.

📋

Duplicate Content Investigation

If you suspect content is being indexed at multiple URLs (e.g., with and without trailing slash, or with URL parameters), check each variant to confirm which URL holds the canonical. This helps you trace where duplicate signals are originating from.

⚙️

CMS and Plugin Verification

After installing or updating an SEO plugin (such as Yoast, Rank Math, or All in One SEO), verify that canonical tags are being generated correctly. Plugin updates sometimes change canonical behaviour unexpectedly.

🌐

Cross-Domain Canonical Checks

When syndicating content to another domain with a canonical pointing back to the original, use the checker to confirm the cross-domain canonical is in place on the syndicated copy. This ensures the original page retains its ranking signals.

🛠️

Staging to Production Checks

Before launching a new page or redesign, check the staging URL to confirm the canonical is already set correctly for production. This prevents staging canonicals from slipping into the live environment unnoticed.

Canonical Tag Best Practices

Common mistakes and how to avoid them when implementing canonical URLs.

01

Always Use Absolute URLs in Canonical Tags

A canonical tag should contain the full absolute URL including the protocol and domain — for example, https://example.com/page/ rather than just /page/. Search engines accept relative canonical URLs, but absolute URLs are unambiguous and less likely to be misinterpreted. This is especially important during migrations where the domain itself is changing.

02

Be Consistent with Trailing Slashes and Protocol

Pick a canonical URL format — with or without a trailing slash, always HTTPS — and stick to it across the entire site. If https://example.com/page/ is your canonical, do not have some pages referencing https://example.com/page (without slash). Even small inconsistencies create duplicate URL variants that search engines must reconcile, wasting crawl budget and diluting link equity.

03

Do Not Canonicalise Paginated Pages to the Root Page

A common mistake is to set the canonical on all paginated versions (page 2, page 3, etc.) to point back to page 1. This tells search engines the paginated pages are duplicates of page 1, which causes them to drop the paginated content from the index. Instead, each paginated page should carry a self-referencing canonical, and you should use rel="next" and rel="prev" if needed — or simply ensure pagination is discoverable through internal links.

04

Resolve Conflicts Between HTTP Header and HTML Canonical

If your server sends an HTTP header canonical and your CMS also outputs an HTML canonical tag, make sure both point to the same URL. Conflicting signals — where the HTTP header says one URL and the HTML tag says another — tell search engines the canonicalisation is unreliable. In most cases, the easiest resolution is to disable the HTTP header canonical if your CMS handles canonicals correctly through the HTML tag.

05

How to Add a Canonical Tag to Your Pages

If you find a missing canonical, here is how to add one depending on your setup:

  • HTML/Static sites: Add <link rel="canonical" href="https://yourdomain.com/page-url/"> inside the <head> section of the page.
  • WordPress (Yoast SEO): The canonical is set automatically. Override it in the Advanced tab of the Yoast metabox on each page.
  • WordPress (Rank Math): Go to the Advanced tab in the Rank Math metabox and set the canonical URL field.
  • Shopify: Shopify sets self-referencing canonicals automatically on product and collection pages.
  • Custom CMS / Server: Set the canonical in your template’s <head> block or configure your server to send the Link HTTP response header.

Related SEO Tools

Other free tools for checking your site’s technical SEO setup.

📜

Robots.txt Checker

Check your robots.txt file for syntax errors and crawl directives that may be blocking search engines.

Check Robots.txt
🔗

Broken Link Checker

Find broken links on any webpage. Identify 404 errors and dead links that affect crawlability and user experience.

Check Broken Links
📄

Title and Description Checker

Check your meta title and description tags for length, format, and whether they are present and correctly formed.

Check Meta Tags
⚙️

Robots.txt Generator

Generate a correctly formatted robots.txt file for your site. Configure crawl rules for all major search engine bots.

Generate Robots.txt

Frequently Asked Questions

What is a canonical URL?

A canonical URL is the preferred version of a webpage when multiple URLs serve the same or very similar content. Declaring a canonical URL tells search engines which version to index and assign ranking signals to. Without a canonical, search engines must choose for themselves, which can result in the wrong URL being indexed or ranking signals being split across duplicates.

How does the canonical URL checker work?

The tool makes an HTTP request to the URL you enter and inspects two locations: the HTTP response headers (looking for a Link: ; rel="canonical" header) and the HTML source (looking for a element in the ). Results from both sources are displayed and compared. If both are present and agree, that is shown. If they conflict or one is missing, that is flagged.

What is the difference between an HTTP header canonical and an HTML canonical tag?

Both methods declare the same thing — the preferred URL — but through different channels. The HTML canonical tag is placed inside the section of the page HTML. The HTTP header canonical is sent as part of the server's HTTP response before the HTML is delivered. The HTML tag method is more common and universally supported. The HTTP header method is useful for non-HTML resources like PDFs, where there is no HTML to modify. If you are using a CMS, the HTML tag is the correct approach.

What happens if the canonical tag is missing?

If no canonical tag is present, search engines will attempt to identify the preferred version on their own. This is generally fine for straightforward sites, but it creates risk when the same content is accessible at multiple URLs — for example, /page and /page/, or http:// and https://. In those cases, Google may index the wrong variant and distribute link equity across multiple URLs instead of consolidating it. Adding a self-referencing canonical removes the ambiguity.

What does a self-referencing canonical mean?

A self-referencing canonical is when the canonical tag on a page points back to the page itself. For example, if you check https://example.com/blog/post/ and the canonical is https://example.com/blog/post/, that is self-referencing. This is the correct and expected state for any page you want indexed. It confirms: "This URL is the authoritative version of this content."

What do conflicting canonical tags mean and how do I fix them?

Conflicting canonical signals occur when the HTTP header canonical and the HTML canonical tag point to different URLs. This usually happens when a CMS or SEO plugin sets the HTML canonical while the server or CDN is also setting an HTTP header canonical independently. To fix it: first, identify which source is setting each canonical (check server config, CDN settings, and CMS/plugin settings). Then either align both to the same URL, or disable one of them — typically the HTTP header — to leave a single, unambiguous canonical signal.

Can I use a canonical tag to consolidate duplicate content?

Yes, this is one of the canonical tag's primary use cases. If you have multiple pages with substantially similar content — such as product pages with minor variations, or the same article syndicated in multiple categories — you can add a canonical on each duplicate pointing to the original preferred URL. Search engines will treat the duplicates as secondary and focus indexing and ranking signals on the canonical URL. Note that this is a hint rather than a directive; search engines may not always follow it, but it is the standard recommended approach.

Does the free canonical checker work on any website?

The tool works on any publicly accessible URL. It does not require login credentials or authentication. Pages behind a login, paywalls, or IP-restricted environments will not return a canonical result since the tool cannot fetch the page content. For those cases, you would need to inspect the canonical manually by viewing the page source directly in a browser.