Canonicalization Checker
Free, no signup. Check the canonical Google can see, the HTTP Link header, and whether the chosen target is actually a clean, live URL.
Checks run from our server; we fetch the URL you enter and don't keep the results. The URL and its canonical target are fetched to build this report. The full URL is not stored; after a successful check, only its domain may be remembered in this browser. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
Example result
Illustrative example — fixed signals, not a live URL claim
Page checked: https://example.com/product?color=blue
This example assumes the canonical target returns a direct 200. If it redirected or failed, the same engine would add a high-risk finding instead of hiding that evidence.
How to use it
- Enter the exact URL variant you want to audit, including parameters when they are part of the question.
- Choose Audit canonical. The report shows every HTML and HTTP Link-header canonical observed.
- Read the override-risk explanations and fixes, then confirm that the target resolves directly to a live page.
- Use Search Console URL Inspection to compare the user-declared and Google-selected canonical for a verified property.
+ saves the current site or page. Use ☆ beside any saved site, page, or list to favorite it. Recent check history appears below.
Create a named list
Target filled from your local choices.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Observed canonical signals
Google override-risk predictor
This is a deterministic signal check, not a claim about Google’s indexed canonical.
Why these verdicts and how to verify them
Portable baseline
Download this result as JSON, then import it after a later run of the exact same URL. The baseline stays in your files and is not uploaded.
Rate this tool
What the results mean
The report checks the observable signals involved in CanonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. and estimates when conflicts may lead Google to select another URL.
- High marks a direct conflict such as disagreeing canonicals, noindex plus canonical, an unreachable target, or a target that redirects.
- Medium marks a meaningful consistency risk, including cross-domain targets or hreflang that omits the canonical URL.
- Low means the observed signals are internally consistent or describe a normal parameter cleanup. It is not a promise that Google agrees.
How it works
One bounded server request collects the final URL, response headers, and HTML body. A deterministic parser reads canonical and hreflang links from the head plus canonical Link headers, resolves relative URLs, records duplicates and noindex, and then checks each unique canonical target through the status endpoint. The predictor maps those observed signals to explicit risk reasons and fixes.
Features
- HTML and HTTP Link-header canonical discovery.
- Relative, missing, multiple, and conflicting canonical checks.
- Noindex, hreflang, cross-host, protocol, and parameter consistency signals.
- Bounded canonical-target status and redirect verification.
- Plain-language likelihood labels without claiming Google's selection.
Limitations
The checker reads the server response and does not render JavaScript. It cannot compare page content across duplicate URLs, inspect all internal links or sitemap signals, access Search Console, or observe Google's selected canonical. A low-risk result only describes the evidence fetched in this run.
Frequently asked questions
Can this tell me Google’s selected canonical?
No. Google’s selected canonical is only observable through Search Console URL Inspection for a verified property. This tool predicts override risk from observable HTTP and HTML signals.
Does it fetch rendered JavaScript canonicals?
No. It reads the server response. A canonical injected only after JavaScript runs is discouraged and should be verified in URL Inspection.
Should every indexable page have a self-referencing canonical?
A self-referencing canonical is generally useful because it makes the preferred URL explicit and helps keep parameters or alternate URL forms from becoming ambiguous. It is still a hint, not a directive.
Can a canonical point to a redirect?
It can, but it creates a conflicting and inefficient signal path. Point the canonical directly to the final live 200 URL and align internal links, redirects, and sitemap entries with it.
Why might Google ignore a canonical tag?
Google may choose another URL when content, redirects, internal links, sitemaps, hreflang, protocol or host signals disagree, or when the declared target is unavailable. This checker tests several observable conflicts but cannot see Google’s full index-level evidence.
Feature requests for Canonical Checker
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Tentang alat
Audit sinyal canonical HTML dan HTTP, periksa target canonical, dan dapatkan penjelasan berbasis bukti tentang sinyal yang dapat membuat Google memilih URL canonical lain.
Fitur
- Penemuan canonical dari HTML dan header Link HTTP. Pemeriksaan canonical relatif, hilang, ganda, dan berkonflik. Sinyal noindex, hreflang, lintas-host, protokol, dan konsistensi parameter. Verifikasi status dan pengalihan target canonical secara terbatas. Label kemungkinan dengan bahasa jelas tanpa mengklaim pilihan Google.
Cara kerja
Satu permintaan server terbatas mengumpulkan URL akhir, header respons, dan isi HTML. Parser deterministik membaca tautan canonical dan hreflang dari head serta header Link canonical, menyelesaikan URL relatif, mencatat duplikat dan noindex, lalu memeriksa setiap target canonical unik melalui endpoint status. Predictor memetakan sinyal teramati menjadi alasan risiko dan perbaikan yang eksplisit.
Batasan
- Keterbatasan: pemeriksa membaca respons server dan tidak merender JavaScript. Pemeriksa tidak dapat membandingkan isi halaman di antara URL duplikat, memeriksa semua tautan internal atau sinyal sitemap, mengakses Search Console, atau mengamati canonical pilihan Google. Hasil berisiko rendah hanya menjelaskan bukti yang diambil pada proses ini.
Pertanyaan umum
Mengapa Google mungkin mengabaikan tag canonical?
Google mungkin memilih URL lain ketika sinyal konten, pengalihan, tautan internal, sitemap, hreflang, protokol, atau host tidak selaras, atau ketika target yang dinyatakan tidak tersedia. Pemeriksa ini menguji beberapa konflik yang dapat diamati, tetapi tidak dapat melihat seluruh bukti tingkat indeks Google.
Apakah pemeriksa mengambil canonical JavaScript yang dirender?
Tidak. Pemeriksa membaca respons server. Canonical yang hanya disisipkan setelah JavaScript berjalan tidak disarankan dan harus diverifikasi di URL Inspection.
Bisakah alat ini memberi tahu canonical yang dipilih Google?
Tidak. Canonical pilihan Google hanya dapat diamati melalui URL Inspection Search Console untuk properti terverifikasi. Alat ini memprediksi risiko override dari sinyal HTTP dan HTML yang dapat diamati.
Haruskah setiap halaman yang dapat diindeks memiliki canonical yang merujuk ke dirinya sendiri?
Canonical yang merujuk ke diri sendiri umumnya berguna karena membuat URL pilihan menjadi eksplisit dan membantu menjaga parameter atau bentuk URL alternatif agar tidak ambigu. Namun, canonical tetap merupakan petunjuk, bukan direktif.
Bisakah canonical menunjuk ke pengalihan?
Bisa, tetapi hal itu menciptakan jalur sinyal yang berkonflik dan tidak efisien. Arahkan canonical langsung ke URL akhir yang aktif dan mengembalikan 200, lalu selaraskan tautan internal, pengalihan, dan entri sitemap.