How a Wrong Canonical Tag Created an Indexing Risk for Key Pages
How a Wrong Canonical Tag Kept Our Key Pages Out of Google (And How I Fixed It)
An SEO case study from a real project — explained simply, for anyone learning technical SEO.
A Quick Backstory
While auditing the website assistly.care in Google Search Console, I noticed something odd: a few important service pages simply weren’t showing up in Google’s index. Not “ranking low” — literally not indexed at all. No impressions, no clicks, nothing.
After digging in, I traced it back to one small but very costly mistake: a wrong canonical tag. In this post, I’ll break down what happened, why it matters, and exactly how I fixed it — in plain English, so even if you’re new to SEO, you’ll walk away understanding what a canonical tag is and why it deserves your attention.
First, What Is a Canonical Tag?
Think of a canonical tag as a little note in a webpage’s code that tells Google:
“Hey Google, if you find multiple versions of this content, this is the one URL you should treat as the ‘original’ and show in search results.”
It looks like this in the HTML <head> of a page:
It’s normally used to avoid duplicate content problems — for example, if the same product page is accessible through two different URLs. You tell Google “this one is the master copy,” and Google consolidates everything (rankings, indexing signals) to that one URL.
The catch: if you point the canonical tag to the wrong page by mistake, you’re basically telling Google, “Please don’t treat this page as worth indexing — go index that other page instead.” That’s exactly what happened here.
The Problem I Found
Assistly Care has several solution pages, each meant to target a different service:
/solutions/home-care//solutions/senior-care//solutions/adult-day-care//solutions/assisted-living/
Each of these pages is unique — different content, different keywords, different search intent. They were never supposed to be treated as duplicates of each other.
But when I opened Google Search Console → Page Indexing, several of these pages were missing from the “Indexed” list entirely.
 |
| Page Indexing report showing missing pages |
So I ran each URL through the URL Inspection tool, and that’s where the issue became obvious.
What URL Inspection Revealed
For the Home Care page, the “User-declared canonical” field showed this:
Inspected URL: https://assistly.care/solutions/home-care/
User-declared canonical: https://assistly.care/solutions/assisted-living/
 |
| URL Inspection showing wrong canonical |
In other words, the Home Care page itself was telling Google, “I’m not the real page - go index the Assisted Living page instead.” Google listened, and simply didn’t bother indexing Home Care.
I checked the Adult Day Care page’s raw source code (view-source:) to confirm it directly, and found the same pattern baked right into the HTML:
<link rel="canonical" href="https://assistly.care/solutions/assisted-living/" />
 |
| HTML source showing wrong canonical |
Every one of these solution pages — Home Care, Senior Care, Adult Day Care — had been pointed to the same wrong destination: the Assisted Living page.
How Did This Happen?
The site runs on WordPress. At some point, the site’s URLs were restructured/updated. When a developer updates a page’s URL or duplicates a page as a template for a new one, many SEO plugins carry over the old canonical setting by default unless it’s manually corrected.
In this case, it looks like the developer built out these solution pages using the Assisted Living page as a starting template, updated the content and title, but never updated the canonical field to point back to the page itself. So instead of each page saying “I am the original,” they were all quietly pointing to one single page — Assisted Living.
The takeaway: canonical tags don’t fix themselves when you duplicate a page or change a URL. They need to be manually verified every time.
Why This Is a Big Deal for SEO
This is a sneaky problem because:
The pages loaded fine. Visitors browsing the site wouldn’t notice a thing.
There was no error message or broken link. Everything technically “worked.”
Google was actively being told to ignore these pages. This isn’t a crawl budget issue or a minor ranking dip — it’s Google being explicitly instructed not to index them.
It’s invisible unless you check Search Console. Most site owners never look at “User-declared canonical” values unless something already feels wrong.
The practical result: three service pages that should have been driving organic traffic for terms like “home care,” “senior care,” and “adult day care” were essentially invisible in Google Search.
The Fix
The fix itself is simple once you’ve found the cause — the challenge is finding it in the first place. Here’s what I did:
Identified every affected URL using the Page Indexing report in Search Console.
Corrected the canonical tag on each page so it pointed to itself instead of the Assisted Living page.
CodeUser-declared canonical: https://assistly.care/solutions/senior-care/
Corrected canonical tag Requested re-indexing for each corrected URL using the “Request Indexing” option.
Verified via the sitemap-based indexing report that Google had picked up the corrected pages.
Indexed pages list after fix Monitored the Page Indexing report over the following days to confirm all pages moved from “Not indexed” to “Indexed.”
The Result
Within about a week of the fix and re-indexing request, all three pages - Home Care, Senior Care, and Adult Day Care — showed up correctly in the Indexed Pages report in Search Console, alongside the site’s other pages.
Indexed pages after fix
That’s a full recovery: content that had effectively been hidden from Google for who knows how long was now eligible to rank and appear in search results.
Key Lessons for Anyone Doing SEO or Managing a Website
Always check the “User-declared canonical” field in URL Inspection, especially after a redesign or when new pages are built from templates.
A page can look perfectly fine to a visitor and still be invisible to Google. Canonical issues don’t throw errors, they just quietly redirect indexing signals elsewhere.
Every unique page should canonicalize to itself, unless you have a deliberate reason to point it somewhere else.
Audit canonical tags regularly. Developers duplicating pages as templates is one of the most common ways this issue creeps back in.
Search Console’s Page Indexing report is your early warning system. If pages you expect to see indexed aren’t there, that’s the first place to look.
Final Thoughts
It’s easy to assume indexing issues are always about big technical problems — broken robots.txt files, server errors, or noindex tags left on by accident. But sometimes it’s something as small as one misconfigured <link rel="canonical"> tag, silently telling Google to ignore perfectly good content.
If you manage a website, it’s worth a five-minute check right now: open a few of your key pages in Search Console’s URL Inspection tool and confirm the “User-declared canonical” actually points to the page itself. It could be quietly costing you traffic without you ever knowing.
Comments
Post a Comment