indexing.io

Check & monitor · Canonical tags

Canonical Tag: How Canonical URLs and Rel Canonical Decide What Google Indexes

Canonicalization is the quietest way to lose pages. Nothing errors, nothing 404s, the page loads fine for visitors, and yet Search Console keeps reporting it as a duplicate of some other URL you never meant to promote. Somewhere a canonical tag is pointing at the wrong place, or several signals are arguing with each other and Google is picking the winner on its own.

Submit · monitor coverage · official methods only

Coverage Console
White-hat · official methods
Presets

Ready to check coverage

Paste a sitemap to sweep every URL for index status, then submit the missing ones through the official Google Indexing API and Bing IndexNow.

Not indexed Discovered, not indexed Indexed ✓

Coverage

indexed

Submitting via

Avg time to index

URLs submitted

Now eligible

Live, interactive · sample data · official methods only

Official Google Indexing API · Bing IndexNow · verified sitemaps · no spam, no PBNs

In short

A canonical tag is a link rel="canonical" element in a page's head that tells Google which URL is the preferred version of duplicate or near-duplicate content. Google treats it as a strong signal, not a command: it can still choose a different canonical if your redirects, internal links and sitemaps point somewhere else. Use one absolute URL per page, keep the target crawlable and indexable, and make every duplicate point at the same address. When Google overrides you, Search Console labels the page "Duplicate, Google chose different canonical" and the URL you wanted ranked never enters the index.

Last updated July 2026

Indexing does not rewrite your markup, and any tool that claims it can override Google's canonical choice is selling you something. What it does is show you the outcome. Every URL on your site gets a status, and pages that were canonicalized away or dropped as duplicates come back with a plain-English reason, so you know exactly which canonical decisions cost you an indexed page. Once you have fixed the tag, the corrected URL is resubmitted through the official Google Indexing API, Bing IndexNow and your sitemaps, and watched until the status flips.

GOOGLE API INDEXNOW SITEMAPS COVERAGE RE-CRAWL

Official methods only

White hat · no spam, no PBNs

Why it works

What your team gets with canonical tags

See which pages Google canonicalized away

Duplicate and canonical exclusions are reported per URL, not as a sampled example list, so you find every money page Google folded into another address.

A cause you can act on

Each excluded URL comes with the likely reason: a canonical pointing at the home page, a conflicting internal link pattern, a near-duplicate template, a canonical target that is blocked or noindexed.

Fix, resubmit, confirm

Once the canonical is corrected, the URL is resubmitted through official channels and monitored until it is indexed, so you see the fix land instead of guessing.

What it handles

Submitted, monitored and fixed, automatically

Indexing submits your URLs through the official Google Indexing API, Bing IndexNow and clean XML sitemaps, watches coverage across both engines, and flags any page that drops out with a plain-English reason so you can resubmit and get it back.

  • Reports every URL Google excluded as a duplicate or alternate canonical
  • Explains the likely canonical conflict in plain English
  • Resubmits corrected URLs through the official Indexing API and IndexNow
  • Watches the status until the page you wanted is the one indexed
  • Stays white-hat: official methods only, no spam, no forced-index tricks
COVERAGE Live

Not indexed yet

/blog/seo-guide-2026 is discovered but not indexed

crawled, not indexed resubmit

thin content signal, queued for re-crawl via the Indexing API

1 Submitted to Google Indexing API OK
2 Pinged Bing via IndexNow OK
Google + Bing · one status Official · white hat

Why Indexing

One place to submit, monitor and fix coverage

Not a black-hat indexer that risks your site, not a free checker that only tells you the bad news. Indexing unifies official submission and live coverage monitoring, the white-hat way, across Google and Bing.

Submits the official way

Bulk-submit through the Google Indexing API, Bing IndexNow and clean XML sitemaps. We speed discovery and re-crawl using methods the engines support, never spam, PBNs or black-hat tricks.

Monitors coverage live

You do not refresh a search bar one URL at a time. Indexing watches which pages are in Google and Bing, catches anything that drops out, and tracks time-to-index across your whole site.

Diagnoses and resubmits

Every non-indexed page comes with a plain-English reason, then auto-resubmits through the official API so it gets another shot. Google still decides, but nothing waits in the dark.

At a glance

Six canonical tag mistakes, and what Google actually does

Each of these is common, silent, and costs you indexed pages. The fix column is what Google's own canonicalization documentation recommends.

Mistake What Google does The fix
Canonical points at the home page Every page declares itself a duplicate of the home page. Google either ignores the tag or takes you at your word and drops the page from the index. Point each page's canonical at its own URL unless the content really is a duplicate of another page.
Relative path instead of an absolute URL Google supports relative paths, but a missing or wrong base URL resolves to an address that does not exist, so the signal is thrown away. Always write the full absolute URL including the protocol and host. Google explicitly recommends absolute paths.
Two canonical tags on one page Google sees contradictory signals, discards both, and picks a canonical itself using redirects, links and sitemaps. Ship exactly one rel=canonical per page. Check what your CMS, theme and SEO plugin each inject.
Canonical placed in the body The element is only read inside the head. In the body it is invisible to Google and the page has no canonical at all. Move it into the head, before any markup that could close the head early.
Canonical combined with noindex You are asking Google to index the target and drop this page in the same breath. Google lists this as a mistake because the two directives contradict each other. Choose one. Canonical for genuine duplicates, noindex for pages that should never rank.
Canonical target blocked in robots.txt Google cannot crawl the target to confirm it is the better version, so the consolidation never happens and both URLs suffer. Keep the canonical target crawlable. Google says not to use robots.txt for canonicalization at all.

A canonical tag is a strong signal, not a command

This is the part most people get wrong. Google does not obey rel=canonical; it weighs it. In its own canonicalization documentation Google ranks the signals it uses, and redirects sit above the canonical link element, which in turn sits above simple inclusion in an XML sitemap. Internal linking patterns and hreflang clusters feed in too. If your canonical says one thing and every internal link, redirect and sitemap entry on the site says another, Google follows the crowd, not the tag.

That is why canonical problems are so often really consistency problems. A product available at three URLs with a correct canonical on each will consolidate cleanly. The same product where the canonical points to the clean URL but every category link, every sitemap row and the site search all point to the parameter version will get canonicalized to the parameter version, and Search Console will tell you Google chose a different canonical. Fix the surrounding signals and the tag starts working.

  • Redirects are the strongest canonicalization signal Google uses.
  • The rel=canonical link element is strong, but still a preference Google can overrule.
  • Sitemap inclusion is a weak signal that nudges a URL toward being canonical.
  • Internal links are the tie-breaker people forget: link only to the canonical version.
  • With hreflang, Google prefers canonicals that stay inside the same language cluster.

How canonical problems show up as missing pages

Canonicalization rarely announces itself. It surfaces in the Page Indexing report as one of two labels. "Duplicate without user-selected canonical" means Google found duplicates, you never declared a preference, and it picked one for you. "Duplicate, Google chose different canonical" means you did declare a preference and Google disagreed. Both end the same way: one URL is indexed, the others are not, and if the indexed one is not the version you optimized, your traffic goes to the wrong page or nowhere at all.

Search Console will show you a sample of affected URLs, which is fine on a 200-page site and useless on a 40,000-page one. That is the gap this tool fills. It reports the status of every URL you submit, flags the ones excluded as duplicates or alternates, and gives you the likely cause so you can tell a deliberate consolidation from an accident. When the markup is corrected, the URL is pushed back through the official Indexing API, IndexNow and your sitemaps, and watched until the right page is the one in the index. What no tool can do is force Google to accept your canonical choice, and you should distrust anyone who says otherwise.

  • Duplicate without user-selected canonical: you set no preference, so Google chose.
  • Duplicate, Google chose different canonical: you set one and Google overruled it.
  • Alternate page with proper canonical tag: working as intended, nothing to fix.
  • Check the indexed URL, not just the count: the wrong winner is still a loss.

Good questions

Questions about canonical tags

A canonical tag is a link element with rel="canonical" placed in a page's head that names the URL you want treated as the master version of that content. It is how you tell Google which address to index and rank when the same or near-identical content is reachable at several URLs. Google treats it as a strong signal rather than an absolute instruction.
A canonical URL is the single address you want search engines to index and show for a piece of content, out of all the URLs where that content is reachable. Parameters, tracking codes, session IDs, print views and trailing-slash variants all create alternate URLs for one page. The canonical URL is the clean one you nominate to represent them all.
They consolidate duplicate and near-duplicate URLs into one indexed page, so ranking signals such as links are not split across copies. They also stop Google from wasting crawls on variants and from picking the wrong version to show in search results. On ecommerce and faceted sites, where one product can sit at dozens of URLs, they are essential rather than optional.
A 301 redirect removes the duplicate: visitors and crawlers are sent to the target URL and the old one stops being reachable. A canonical tag keeps both URLs live and working for users while telling Google which one to index. Use a redirect when nobody needs the duplicate, and a canonical when the alternate URL still has a job, such as a filtered or tracked version.
View the page source and search for rel="canonical" in the head, or open the URL Inspection tool in Search Console, which shows both your declared canonical and the one Google actually selected. Those two lines disagreeing is the fastest way to spot a canonical problem. At scale, check indexed status across every URL rather than inspecting pages one at a time.
Yes, a self-referencing canonical is standard practice and safe. It states plainly that this URL is the preferred version, which helps when the page is later reached with tracking parameters or a variant slug appended. It is not required by Google, but it removes ambiguity at effectively zero cost, so most CMS platforms output one automatically.

Explore more

More ways teams get every page indexed

Stop guessing. Get every page indexed and keep it that way.

Bulk-submit your URLs through the official Google and Bing channels, monitor coverage, and resubmit anything that drops out, automatically. White hat only, so we speed discovery without ever guaranteeing what Google chooses to index.

See pricing

Google Indexing API · Bing IndexNow · sitemaps · coverage monitoring · official methods only