Google Search Console has a talent for making ordinary website behaviour sound like a production emergency.
You open your inbox.
There's an indexing notification.
You see the words:
"Alternate page with proper canonical tag."
And suddenly you're wondering whether Google has decided your website shouldn't exist.
Before changing your redirects, rewriting your sitemap or adding another SEO plugin, take a breath.
Sometimes Google is simply telling you that it found duplicate URLs and selected a preferred version.
That was the situation I investigated on Pocket PDF.
What does the message actually mean?
A website can expose multiple URLs that lead to essentially the same content.
For example:
https://example.com/merge-pdf
https://example.com/merge-pdf.html
Both URLs might represent the same tool page.
From Google's perspective, these are separate URLs, even if they eventually display the same content.
A canonical tag tells search engines which URL should be treated as the preferred version.
For example:
<link rel="canonical" href="https://example.com/merge-pdf">
If Google finds the .html version but sees that it redirects to the clean URL, it can identify the clean version as the preferred destination.
The Search Console notification can simply reflect that duplicate-handling process.
It doesn't automatically mean there's something broken.
What happened on my website
Pocket PDF uses clean URLs for its tool pages.
The older .html versions redirect to the clean versions using HTTP 308 redirects.
For example:
/merge-pdf.html
redirects to:
/merge-pdf
The clean destination returns a successful response.
I also checked the sitemap.
It contained 200 URLs, and those URLs used the clean versions.
Each of those pages had a self-referencing canonical tag.
That was important because I didn't want to assume that the Search Console message was correct without checking the actual implementation.
There are several separate things to verify:
What happens when the old URL is requested?
What status code does the server return?
Where does the redirect lead?
Does the destination have the correct canonical?
Is the sitemap listing the preferred URL?
Looking at only one of these can give you an incomplete picture.
Why I didn't change anything
After checking the redirects, sitemap and canonical tags, I found no issue that required an origin-side change.
The website was already doing what I intended.
The old URL redirected to the clean URL.
The clean URL returned successfully.
The canonical pointed to itself.
The sitemap contained the preferred URLs.
There was no reason to remove the redirects or start changing canonical tags just to make a Search Console notification disappear.
In fact, making unnecessary changes could create the problem you were trying to avoid.
For example, removing a redirect could leave duplicate URLs accessible. Changing a canonical incorrectly could tell Google to prefer a different page entirely.
Neither is an improvement.
The file-by-file canonical audit
One thing I would recommend to anyone managing a static website is a small automated canonical audit.
Instead of checking random pages manually, inspect every HTML file.
For each page, verify:
It contains a canonical tag.
It points to the intended clean URL.
It's absolute and uses HTTPS.
It isn't accidentally pointing to another tool.
The sitemap contains the preferred URL rather than the duplicate.
You can also test redirect behaviour separately with curl:
curl -I https://example.com/merge-pdf.html
Check the response status and the Location header.
Then inspect the destination:
curl -I https://example.com/merge-pdf
This tells you much more than repeatedly clicking URLs in a browser.
For a larger static website, automate the audit rather than doing it by hand once.
The URL count grows. So does the number of ways the same page can be reached.
The honest takeaway
The email looked scary enough to trigger a debugging session.
Most of the session was confirmation, not repair.
That's still a valid outcome. A Search Console notification means something deserves a look, not that something is broken.
Sometimes the right fix is no fix.
When was the last time you sat down to fix an issue and found out it was already working the way Google wanted?
Top comments (0)