The idea, in plain English
Start here.
A canonical annotation identifies a preferred URL for duplicate or very similar content. It does not move the visitor, and Google can select a different canonical. A redirect changes the request destination. For a permanent move, Google recommends a permanent server-side redirect where possible, such as 301 or 308.
Two addresses can lead to essentially the same information for a good reason, or because an old page was never retired. Before changing a tag, open both pages. Find out what each version does for the reader and whether one truly replaces the other.
A few words you’ll meet.
OPEN WHAT YOU NEED ↙Canonical URL
The representative URL selected for a group of duplicate or very similar pages. Your declared preference and Google’s selection are separate observations.
Canonical annotation
A declaration such as a rel=canonical link element in an HTML head, naming a preferred URL without navigating the browser.
Redirect
A response or mechanism that directs a request to another address. Its implementation and intended duration matter.
Redirect chain
A route through intermediate redirects before the final destination. Each step needs checking; a final successful response alone does not prove the destination is appropriate.
Compare what the pages actually offer
List the two addresses, their main information and why someone might need each version. A large-type reading view may deliberately repeat a guide in a more usable presentation. A retired address may instead need to take an old bookmark to its replacement. Two different guides can share a topic without being duplicates.
Use the content relationship and visitor requirement together. If a proposed destination omits the answer the original visitor needed, investigate before consolidating. A matching keyword, similar title or common template does not establish that the pages are equivalent.
Keep an alternate view when it serves a purpose
For duplicate or very similar content that needs to remain available, a canonical annotation can express the preferred representative. On an HTML alternate, it belongs in the head; Google recommends an absolute destination URL. The browser can still display the requested version.
Keep the preference coherent. The main page should name its own canonical URL, ordinary links should use the preferred address, and sitemap choices should agree. A useful alternate can still have a clearly labeled access link. Learn how to choose helpful internal links rather than removing a needed reader route merely to reduce URL counts.
- Check that the preferred page actually represents the alternate’s main content.
- Inspect the delivered declaration and any conflicting canonical header.
- Keep the alternate’s useful reader function working.
Same guide, two different URL jobs
Move a request when the address has moved
If an old address has permanently moved to a genuine replacement, investigate a permanent server-side redirect. Google documents 301 and 308 for permanent moves. A temporary situation calls for a suitable temporary behavior instead. Choose the implementation supported by the hosting platform; a response rule is not an HTML canonical tag.
Check the old address, every intermediate destination and the final content. Update the originating links and sitemap rather than relying on an unnecessary detour. Do not automatically send every removed page to the homepage: first establish whether a relevant replacement exists. An unrelated destination can leave the original task unresolved.
Keep declaration, route and selection separate
Record three checks independently: what the current page declares, where a real request goes, and which canonical Google reports in indexed URL Inspection information when available. Inspecting HTML alone cannot prove a redirect route or Google’s selection. A live accessibility test cannot predict the canonical Google will eventually choose.
If those observations disagree, compare dates, responses, content and signals before changing another setting. Noindex concerns excluding a page from search; it is not Google’s recommended way to choose among same-site duplicates. A technically coherent implementation does not guarantee a ranking increase or a particular processing date.
A reading view and a retired address
Fictional paths for a repair-instructions guide. These are proposed behaviors for an exercise, not captured responses.
| Address | Reader requirement | Proposed check |
|---|---|---|
| /guides/repair/large-type/ | Keep the equivalent large-type guide usable. | It remains open and declares /guides/repair/ as preferred. |
| /repair-instructions-old/ | Take an old bookmark to its verified permanent replacement. | The response redirects to /guides/repair/ and that guide still answers the task. |
| /guides/replace-a-part/ | Explain a separate replacement task. | Keep its own role; shared repair vocabulary is not a reason to consolidate. |
Put it into practice
Prepare a URL treatment record
The fictional repair guide has a useful equivalent large-type view, a retired old address and a separate replacement guide. You can inspect their content but have no Search Console access.
- Record the role and content relationship for each path.
- Choose which version should remain accessible and which request should move.
- Specify the current HTML and response checks needed.
- Include one distinct page that must stay independent.
- Mark Google’s selected canonical as unavailable rather than inventing it.
Keep your working notes in your own document. This page saves only your completion check, not your answers or customer data.
Check your understanding
Make the call.
Choose an answer for each question. Then compare the reasoning.
You have a useful next step.
- Compare the main content and reader requirement before treating URLs as duplicates.
- A canonical preference can retain an alternate; a redirect moves the request.
- Verify declarations, real routes and Google’s reported selection separately.
Completion is your own learning record. Quiz scores and practice checks are saved separately, on this browser.
Sources & context
The sources below explain the factual foundations and editorial methods used in this lesson. Worked examples, planning models and exercises are illustrative teaching material.
- Google: Canonical URL methods
Primary guidance on duplicate relationships, declarations, consistent signals and why noindex is not the recommended same-site canonical selection method.
- Google: Redirects and Search
Primary guidance on permanent versus temporary behavior and permanent server-side moves. The URL cases are original teaching examples.