First decide whether the pages genuinely serve the same purpose. Merge and redirect when one page can replace another. Consider a canonical when duplicate versions must remain accessible but you want to identify a preferred URL. Keep separate pages when they answer different needs, and make that distinction clear in their content.
Check the purpose before the wording
Two pages can use similar terms and still be useful separately. A service page about office refurbishment and a guide to preparing staff for the work answer different questions.
Compare the reader, the task and the information. If someone could use either page interchangeably and learn nothing different, consolidation may help. If one explains the offer and the other helps with a practical decision, they may belong together through links.
Do not decide from titles alone. Read the pages, check where they are linked and ask whether customers or colleagues use either URL for a specific reason.
Merge when one stronger page can do the job
Choose a destination with the right purpose and a stable URL. Preserve useful material from both pages, remove repetition and edit the result into one coherent answer.
For an illustrative business, separate articles called “Preparing for your office move” and “Office move preparation checklist” might be combined if their content is effectively the same. An article about managing the move on the day could remain separate.
Before retiring the old page, note its incoming links, downloads and references in email templates or documents. The content decision and the URL decision should be made together.
Use a redirect when the old page is being replaced
A redirect sends a visitor from one URL to another. It suits a page that has moved or been replaced by an equivalent destination. The developer should choose the correct implementation for the change.
Google’s canonicalisation guidance describes redirects as a strong signal of the preferred URL. It also distinguishes them from canonical annotations, which can leave duplicate versions accessible.
Test the old address after the change. It should arrive at the intended page without an unnecessary sequence of stops. Update internal links to point directly to the replacement.
Use a canonical for genuine duplicate versions
A canonical annotation identifies a preferred URL for duplicate or very similar content. It can be relevant where a page remains available through variations such as tracking parameters.
It is a signal rather than an absolute instruction to a search engine. The page content, links and other signals should support the same choice.
A canonical is not a way to turn unrelated pages into one. Pointing a distinct service page at the homepage does not make the service information interchangeable with it. If you are unsure, establish the intended page relationship before adding the tag.
Keep the surrounding signals consistent
Check the preferred URL in the page’s canonical, internal links and sitemap. Google advises avoiding contradictory canonical signals and linking to the preferred version internally.
Do not block duplicate URLs in robots.txt and assume that has solved canonicalisation. Likewise, a noindex instruction and a canonical serve different purposes. Ask the developer to explain which outcome the proposed change is meant to achieve.
Keep a short change record with the old URL, chosen destination, reason and implementation. It makes future investigation much easier than trying to remember why a page disappeared.
Verify the result as a visitor and a site owner
Open the affected URLs and read the resulting page. Does it still answer what the old link promised? Have useful images or downloads survived the merge?
- The preferred page loads correctly.
- The old URL behaves as planned.
- The canonical names the intended page.
- Important internal links use the current destination.
- The merged content does not contain repeated introductions or conflicting facts.
Where Search Console is available, inspect the relevant URLs after Google has had an opportunity to process the changes. Do not assume a tag change produces an immediate search result change.
Duplicate decisions are easier with a content inventory and a clear internal linking plan. Our SEO service can help review the technical handling alongside the content, rather than treating either in isolation.