“Alternate page with proper canonical tag” is not automatically an SEO problem. It can be the expected result when an alternate URL points to the version you want Google to use. The important question is whether the selected relationship matches your intended site structure.
Google describes this status in the Page indexing report documentation. This guide turns that explanation into an investigation process. The examples are illustrative, and the documentation was reviewed on 3 October 2026.
What does the status mean?
The reported URL is treated as an alternate of another page, and its canonical relationship is recognised. The alternate itself does not need to appear as a separate indexed result. A tracking variant of a useful landing page is one example of a URL you may not want indexed independently.
When can you leave it alone?
Consider these two illustrative addresses:
Preferred: https://example.com/services/
Alternate: https://example.com/services/?utm_source=newsletterIf both show the same service content and the alternate declares the clean URL, that relationship may be intentional. Do not remove a sensible declaration simply to reduce the count of excluded URLs in a report.
Keep a record of the purpose of important variants. A campaign URL can still be useful for tracking even when the clean landing page is the version intended for search. The goal is a coherent site, not an empty list of alternate URLs.
When should you investigate?
- A distinct product or service page points to an unrelated URL.
- The preferred address belongs to a staging site or an old domain.
- The canonical target no longer opens the expected content.
- Your navigation and sitemap consistently promote a different version.
- A recent template or plugin change affected many pages at once.
For example, imagine that a newly published website-development page points to a generic services page because a shared template contains a fixed canonical. If the pages have distinct purposes, the template is worth investigating. This is a diagnostic example, not evidence that every consolidated service page is incorrect.
A six-step investigation
1. Identify the affected URL precisely
Copy the complete URL, including parameters, protocol, hostname and trailing slash. Record the report date and the last crawl information available. Without the exact address, two people can unknowingly inspect different variants.
2. Inspect the declared canonical
Run the address through our canonical tag checker, then inspect the returned source where necessary. The tool reports the first HTML canonical; it does not inspect every possible declaration or reveal Google’s decision.
3. Compare the indexed information
Use Search Console URL Inspection to review the available user-declared and Google-selected canonical information. The official URL Inspection guide distinguishes indexed information from a live test. A change visible today may not yet be reflected in the indexed result.
4. Open the preferred page
Check that the target is the intended page and review its response, content and indexing instructions. If it redirects, use our redirect checker to understand the route. A target that reaches an error page is a different problem from an intentional duplicate.
5. Find conflicting signals
Compare the page source, internal links, redirect rules and sitemap. Google’s canonical guidance recommends consistency across these signals. Record the disagreement before deciding which implementation to change.
6. Fix the cause and verify again
Correct the relevant template, plugin setting or URL rule. Clear applicable caches and inspect the public output again. Where appropriate, request indexing for the intended preferred page after the change; submission does not guarantee inclusion or an immediate update.
A decision table for common situations
| What you find | Practical next action |
|---|---|
| A tracking variant points to the intended clean page | Verify the clean page and retain the intentional relationship. |
| A distinct page points to another topic | Review the content purpose and remove an accidental template-level override. |
| The target is an old or staging address | Correct the environment or migration configuration and inspect affected page types. |
| The HTML is corrected but indexed information is older | Record the change date and monitor recrawling; avoid repeated speculative edits. |
| Google chooses a different canonical | Investigate the separate canonical-selection issue and compare the content and signals. |
WordPress and redesign checks
For WordPress, identify which component owns canonical output before adding code. The page may already be controlled by an SEO plugin. Follow our WordPress canonical implementation guide for the Yoast and Rank Math routes.
During a redesign, sample more than the homepage: a service page, an article, a category and a parameterised URL can use different templates. Compare staging and production output, and keep a URL change map. Our website redesign guide covers the broader launch process.
What not to do
Do not add noindex everywhere, block all variants indiscriminately or redirect unrelated content merely to change a report label. These actions change how a site works and should follow a defined URL strategy. Fix one representative issue, verify it, and then apply the same confirmed rule to genuinely similar cases.
A useful investigation log contains the affected URL, intended preferred URL, observed declaration, indexed information, change made and date checked. This makes it possible to distinguish a deployment problem from a report that has not caught up.
Frequently asked questions
Is this a duplicate-content penalty?
The status itself is not a statement that a penalty has been applied. It describes how an alternate URL is handled in indexing.
Must every URL in the report be indexed?
No. Some alternate URLs intentionally represent the same content. Focus on whether the pages you want people to find are eligible and useful.
How long will a corrected report take?
There is no fixed update time you can rely on. Keep evidence of the deployed change and monitor the indexed information instead of assuming the live test updates the report immediately.
Get help with an unintended canonical
Our technical SEO services can help inspect the signals, while website redesign services can address template and migration causes. Send the affected URL and the URL you believe should be preferred so the investigation starts with a clear comparison.