Choose a canonical URL by grouping pages with the same or very similar main content, then picking the version you want people to find and share. If another URL still needs to load the same page, point its canonical tag to the preferred version. If an old duplicate has been retired, use a permanent redirect. Give pages that serve distinct purposes their own URLs and canonical tags. Google Search Central’s guide to specifying a canonical URL
Google uses canonicalization to choose a representative URL from a group of duplicates. A canonical tag expresses your preference, and Google can select a different URL. That distinction matters when you check the result after a change. Google Search Central’s explanation of canonicalization
Compare what people can do on each page

Open the URLs side by side. Read the main content and try the action each page offers. If swapping one URL for the other would change what a visitor can learn, find, or buy, investigate that difference before grouping them.
A tracking parameter can leave the page unchanged. A filter can change the collection of items available to browse. Both URLs may look alike, so the parameter name alone is a poor basis for a sitewide rule. Check what the parameter does and decide whether the filtered page deserves to be a search destination.
Look past shared templates as well. Two workshop pages may use the same navigation, photos, and booking layout. If they teach different skills and take bookings for different sessions, each page has a reason to exist independently. For articles with genuinely overlapping purposes, see when to merge overlapping blog posts.
Align the signals around your preferred URL

Choose a stable, accessible URL that delivers the full page. For an HTML page, add a canonical link in its head that points to the full preferred URL. Include the same declaration on the preferred page itself. Update routine internal links and sitemap entries to use the preferred URL. Google describes redirects and canonical tags as strong signals and sitemap inclusion as a weaker one. Google Search Central’s canonical methods and best practices
Check the destination before editing a template. A URL that redirects again, returns an error, or carries a noindex directive calls for investigation before you designate it as the preferred search destination. Check for competing declarations from the CMS, a plugin, and any HTTP header configured at the server.
Make the decision for the group before changing the sitemap. If the page has moved permanently, document where the old URL should go and test the full route. See how to plan a page URL change for that handoff and what belongs in an XML sitemap for the inventory.
Work through a hypothetical workshop site
Imagine a ceramics studio with a wheel throwing class and a handbuilding class. The paths and decisions below are illustrative. The studio confirms that its email tracking parameter leaves the wheel throwing page unchanged and that its old beginner wheel URL has a direct replacement.
| URL | What a visitor gets | Proposed decision |
|---|---|---|
| /classes/wheel-throwing | Current wheel throwing details and booking | Keep as the preferred URL with a canonical tag pointing to itself. |
| /classes/wheel-throwing?utm_source=email | The same page with campaign attribution | Keep it accessible for the campaign. Point its canonical tag to the clean wheel throwing URL. |
| /classes/beginner-wheel | Retired address for the same class | Permanently redirect to the current wheel throwing page. Update links still pointing to the old address. |
| /classes/handbuilding | A separate class with a different syllabus and booking calendar | Keep independently available with its own canonical URL. |
The useful test is what would happen if a visitor followed the proposed target. The campaign link and retired address lead to the right wheel throwing class. Sending a handbuilding visitor to that same target would send them to a different class. The studio can apply this check to each new class before adding it to the sitemap.
Verify the declaration and Google’s selection
First, test what the site serves. Open the preferred and alternate URLs, check the status or redirect destination, and verify the canonical in the delivered page. Confirm the internal links and sitemap name the intended destination. Keep a small record of the URL checked, the expected result, and what you saw.
Then use URL Inspection in Search Console to compare the declared canonical with the one Google selected in the indexed data. The live test can help you inspect the current page, but Google’s canonical selection is available only in the indexed report. Note the last crawl date when the report still reflects a previous version. Google’s URL Inspection documentation
If Google picks an unexpected URL, compare the pages again and check for conflicting signals. Begin with the exact pair involved. A template rule that works for an email tracking URL may be wrong for a separate class, collection, or product page.
For help with SEO and AI search visibility, try HoneyWeRank.
