“Alternate page with proper canonical tag” can describe an intentional equivalent URL. Begin by deciding which version you want selected. This guide separates an expected alternate from a duplicate that needs investigation.
01Record the two URLs and the intended outcome
Write down the inspected URL, your preferred URL and why the versions exist. Product filters, tracking parameters and slash variants can create different cases. An intentionally equivalent alternate needs a different response from a useful standalone page incorrectly pointing elsewhere.
- Capture exact URLs and checked date
- Identify the intended owner page
- Separate equivalent variants from distinct content
02Read the live canonical signal
Inspect the canonical in the served HTML or applicable HTTP header and resolve its target. Then inspect the destination response. A target that redirects repeatedly, returns an error or points to unrelated content is a configuration question to investigate, not a reason to copy the same tag everywhere.
- Check source and destination responses
- Compare initial and rendered HTML where relevant
- Look for conflicting canonical declarations
03Interpret an intentional alternate
If the page is an equivalent version and its preferred destination is correct, the alternate may be behaving as intended. For example, an illustrative tracking URL can point to the clean page. Do not force both equivalent URLs into the sitemap merely to make each appear as an independent indexed page.
- Confirm the destination answers the same task
- Link internally to the preferred version
- Keep intent separate from the status label
04Investigate an unselected duplicate
For a duplicate-without-user-selected-canonical case, compare content, redirect behavior and existing hints. Choose a preferred version based on the actual information architecture. Canonical hints, redirects and sitemap inclusion are different signals; align them deliberately instead of using noindex as a substitute for choosing a canonical.
- Check template defaults and URL variants
- Verify whether distinct pages were accidentally duplicated
- Assign the configuration fix to the correct system owner
05Keep the technical fix bounded
Write a reproducible ticket: affected template, observed output, intended URL, change and test cases. Include a page that should remain self-canonical as a control. A global replacement without controls can fix one variant while incorrectly consolidating useful pages.
- Test one alternate and one distinct page
- Check internal links and sitemap consistency
- Preserve a rollback path
06Verify the change at the right layer
Recheck the live response and HTML after deployment and caching. Search Console can later show Google’s selected canonical and crawl observations where access is available. A corrected tag is evidence of implementation; it is not immediate proof that selection or rankings have changed.
- Save before-and-after evidence
- Record deployment and verification dates
- Keep unresolved index-selection questions separate