Canonical Points to Homepage: How to Fix It

TL;DR: Your inner pages carry a canonical pointing at the homepage. That tells Google every one of those pages is a duplicate of the homepage and should not be indexed on its own. This is the single most destructive canonical misconfiguration there is, because one bad template line can deindex an entire site's worth of content overnight. The fix is a self-referencing canonical on every URL. Treat this as urgent.

What "canonical points to homepage" means

The canonical element names the master copy of a piece of content. This flag fires when an inner page — a blog post, a service page, a product — declares the homepage as that master. The page is announcing "I am not the original; the homepage is the real version of me." For a handful of near-homepage landing variants that might be true. For an entire site of unique pages, it is a catastrophe: you are asking Google to collapse hundreds or thousands of distinct URLs into a single one.

Why this deindexes the whole site

Google reads the canonical as a strong instruction. When every page nominates / as canonical, Google consolidates all of them onto the homepage and stops indexing the rest. Your blog stops ranking, your service pages disappear, your product pages vanish from results — and the homepage cannot rank for all those specific queries either. Traffic does not dip; it falls off a cliff. Because the cause is usually one shared template, the blast radius is site-wide, which is what makes it more severe than the internal-URL or external-URL variants of this problem.

A real failing tag, and the fix

<!-- On every inner page: /services/seo-audit/, /blog/whatever/, etc. -->
<link rel="canonical" href="https://example.com/" />

That is the whole disaster, repeated in the site header on every page. The correct output is a canonical that echoes each page's own address:

<!-- On https://example.com/services/seo-audit/ -->
<link rel="canonical" href="https://example.com/services/seo-audit/" />

In practice the bug is one hardcoded line — often <link rel="canonical" href="<?php echo home_url(); ?>" /> or a plugin default — sitting in a shared header. You fix one file, not a thousand pages.

Severity next to its sibling checks

How to detect it

1. Screaming Frog: crawl, open Canonicals, and filter Canonicalised. If the Canonical Link Element 1 column shows the homepage URL on rows that are clearly not the homepage, you have caught it. A fast tell: the count of "Canonicalised" pages roughly equals your total page count.
2. GSC URL Inspection: inspect any deep page. If "User-declared canonical" is your homepage while you inspected an inner URL, it is confirmed. In the Pages report, watch for a spike in "Duplicate, Google chose different canonical than user" or "Alternate page with proper canonical tag" across many URLs.
3. curl: curl -s https://example.com/any-inner-page/ | grep -i canonical. If the returned href is the bare domain root instead of the page you fetched, the template is broken. Loop it over a few sampled URLs to confirm it is site-wide.

How to fix it

1. Locate the shared source — the header template or SEO plugin setting that hardcodes the homepage. That one place is generating every bad tag.
2. Replace it with dynamic self-referencing output that emits each page's own absolute URL.
3. Deploy, then spot-check a range of page types (post, product, service, archive) with curl to confirm each now self-canonicals.
4. Re-crawl the whole site; the "Canonicalised" filter should return only the pages you genuinely intend to consolidate.
5. In GSC, use the canonical tag inspection and Validate Fix on the affected pages, then request indexing for your top URLs to accelerate recovery. Expect re-inclusion over days to weeks, not hours.

FAQ

How fast will my pages come back after I fix it?

Once Google recrawls and sees correct self-canonicals, pages start returning to the index over days to a few weeks depending on crawl frequency. Requesting indexing for priority URLs and having a healthy sitemap speeds it up.

Could a canonical-to-homepage ever be correct?

Only for URLs that are genuinely duplicates of the homepage — say /?utm_source=x or /index.html resolving to the same content. A unique inner page pointing at the homepage is never correct.

Why is this rated more severe than pointing at a different internal URL?

Scope. A wrong internal-URL canonical usually hits one page or one section. Canonical-to-homepage is almost always template-wide, so it takes out the entire site at once.

My homepage ranks fine but nothing else does — is this the cause?

It is a prime suspect. When every page consolidates onto the homepage, the homepage survives while deeper content silently disappears. Inspect a few inner pages to confirm before assuming it is content quality.

Does a missing canonical cause the same damage?

No. A missing canonical just lets Google guess, which is usually harmless for unique pages. A wrong canonical actively instructs Google to deindex. If some pages have none, see Missing Canonical Tag; if fixed pages are slow to return, see Crawled: Currently Not Indexed.

Related canonical checks: Canonical Points to a Different Internal URL · Canonical Points to External URL · Canonical Loop