Alternate page with proper canonical tag: when to leave it alone

A healthy alternate does not need its own search result

Imagine a product page at /products/blue-mug and a campaign link at /products/blue-mug?campaign=email. The visitor sees the same mug, price and description. The campaign address exists to preserve attribution, while the clean address is the search destination. Keeping the duplicate accessible can be intentional.

In that fixture, a canonical from the campaign URL to the clean product expresses the intended relationship. Canonicalization selects a representative of duplicate or very similar material. It does not require every address that a visitor can open to receive a separate search listing. Google's explanation

Check that the target is the real product page. A correctly formatted tag can still point to the wrong product, an old hostname or a route left over from a migration. The label tells you what Google understood about a relationship; your product and publishing decisions determine whether that relationship is useful.

If Google chose a representative without a clear declaration, the duplicate URL-family repair supplies the next diagnostic sequence.

The same label can describe two different decisions

Compare these authored examples. In the first, the alternate adds a tracking attribute without changing the offer. In the second, a template points a large mug at a smaller mug even though capacity, pricing and customer intent differ. A blanket instruction to remove all alternate statuses would mishandle the first; a blanket instruction to ignore them would miss the second.

Inspect the alternate and its target together

Open URL Inspection for the alternate. Compare the user-declared and Google-selected canonical, then inspect the target itself. Use the indexed report for Google's observed choice. The live test does not test every duplicate or canonical condition, so its success cannot settle the selection. Inspection documentation

Look at the two pages side by side. Match the main subject, product identifier, language, availability and other material details. A shared header and navigation are weak reasons to conclude that the main content is equivalent. Conversely, different campaign parameters do not by themselves create distinct editorial value.

Record a clear intended outcome: retain an accessible duplicate, retire an obsolete route, or maintain two independently useful pages. That sentence should explain the change you make to the template. It is more useful than a goal of driving an exclusion counter to zero.

Choose the smallest change that matches the content

For a retained duplicate, keep the canonical preference and align ordinary internal links and the sitemap with the preferred URL. For a permanently retired address, use an appropriate permanent redirect. For an independently useful page, give it its own coherent identity and substantive content. Google recommends consistent canonical signals and does not treat a canonical declaration as an unconditional command. Canonical methods

Check the final target directly. A page can be reachable to a logged-in editor while ordinary visitors receive an error or an empty response. Test the public response and the actual body, not merely a green plugin indicator. If rendering injects or changes a tag, compare raw HTML with the rendered DOM.

Avoid adding noindex merely to tidy the report. Exclusion from search and consolidation into another URL are different publishing decisions. Start with the intended reader destination and let that choice determine the implementation.

Watch the preferred page, not the alternate count

After a change, verify the response family and keep the dates of your observation and Google's crawl distinct. If the preferred product or article is correctly selected and discoverable, an excluded duplicate can remain exactly where it belongs.

The pattern worth investigating is a lost destination: a valuable page selected away from itself, a target that fails publicly, or navigation that keeps advertising obsolete addresses. Those are concrete problems with reader and search consequences.

When Google has selected a representative without a clear declaration, use the companion duplicate without user-selected canonical repair. Both cases benefit from one URL-family decision, while requiring different amounts of work.