Duplicate without user-selected canonical: fix the URL family

Read the selection before changing the tag

Inspect the excluded URL and record its Google-selected canonical. Inspect that destination too. Compare the actual content and the intended purpose of both pages. The indexed report reflects Google's last observation; the live test checks present accessibility and does not settle canonical selection. URL Inspection

If the selected destination is the page you want people to find, the exclusion may be serving its purpose. If an important product, article or category has been grouped with a materially different page, diagnose that grouping before applying a site-wide rule. A category full of useful products should not be collapsed into an empty category merely because their templates match.

Compare that outcome with a correctly canonicalized alternate, where keeping the duplicate out of the index can be the intended result.

A four-URL example

Consider an illustrative shop that sells the same blue mug through the addresses below. The product, price and description are identical. The clean product URL is the address the shop wants indexed. The tracking and sort parameters add no independent product information.

Give each address a job. Remove obsolete routes with a permanent redirect. Keep a useful parameterized experience accessible while declaring the representative product page. The point is to resolve intentional differences, rather than force every address through the same response.

Align the signals around one destination

Publish an absolute canonical URL in the HTML head of the chosen page and any accessible duplicate that should consolidate into it. Use permanent redirects for addresses you are retiring. Update ordinary navigation, product cards and editorial links to the preferred URL; list that address in the sitemap. Google treats redirects and canonical annotations as strong signals and sitemap inclusion as a weaker one. Canonical methods

Trace one real entry path through the fixture. A category card should open the clean product address. The email link can retain its campaign parameter for attribution, but the resulting document should identify the clean product as its canonical. An old bookmarked route should land there through a direct redirect. Those outcomes are coherent even though the three entry paths differ.

Keep unrelated choices separate. A Spanish translation needs a language strategy. A distinct product variant may deserve its own page. A filtered category that solves a useful search task is not equivalent to a tracking parameter. Decide what the pages mean before deciding which URL survives.

Check the response and the rendered document

Capture the HTML response, response headers and rendered head. A framework or plugin can append a second canonical after the server has emitted the first. Google recommends specifying the canonical in source HTML where possible and keeping JavaScript from changing it to a different URL. JavaScript SEO

Write down the resulting destination, not merely the presence of a canonical element. A tag pointing at a redirect, a second hostname or an unavailable route does not establish the intended representative. Follow the target and confirm it serves the expected content with a self-consistent identity.

Use the existing canonical audit when the disagreement crosses templates, headers or rendering. The individual Search Console label is the entry point; the delivered responses are the material you can repair.

Verify the family after the repair

Recheck the clean URL, one parameterized duplicate and each retired address. Confirm the expected status, final destination, canonical and internal-link path. This small family check catches a common partial fix: the preferred page looks correct while the old route still publishes conflicting signals.

Then compare Google's next indexed observations with that intended state. Keep the crawl date beside the report. A successful live fetch is useful evidence about accessibility, and a later Google-selected canonical answers the separate selection question. There is no dependable countdown from a tag edit to a changed report.

If the page instead has an alternate with a proper canonical, use the narrower question: is that alternate supposed to remain available while another URL represents it? A correct exclusion is an outcome to retain.