SEO & Performance

Canonical URL vs 301 redirect: choose the right SEO implementation

Understand when to use a canonical tag, a permanent redirect or neither. Review duplicate URLs, page moves, sitemap consistency and deployment checks.

A campaign URL, an old service-page address and a duplicate product page can all appear to need “an SEO fix.” They do not necessarily need the same implementation.

First decide what should happen to a visitor. Should the old address remain available, or should the visitor move to another page? That question helps separate canonicalisation from redirection.

A canonical expresses a preferred version

For duplicate or very similar content that remains available at multiple URLs, a canonical declaration identifies the preferred version for search engines:

<link rel="canonical" href="https://example.com/services/consulting/">

The browser does not navigate away because of this tag. The alternate page can still load normally. Google treats canonical declarations as signals and can select a different canonical; see its canonicalisation guidance.

Do not point unrelated articles at one generic page merely because you want that page to rank. Canonicalisation is not a mechanism for promoting a preferred topic.

A permanent redirect moves the request

If a service page has permanently moved and the old address should no longer serve its own content, a server-side permanent redirect can send visitors to the replacement.

An illustrative response is:

HTTP/1.1 301 Moved Permanently
Location: https://example.com/services/consulting/

This is a response example, not configuration to paste into every web server. Implement the rule in the layer that owns routing for your project. Google’s redirect documentation distinguishes permanent and temporary moves, including supported status codes.

A temporary campaign change may need a temporary redirect instead. Choose the status according to the intended duration and request behavior, not because a generic checklist says every redirect should be 301.

Choose by the URL’s purpose

Situation Starting point
Old service page permanently replaced by an equivalent page Permanent redirect to that replacement
Tracking parameters show substantially the same content Review a canonical to the clean URL while preserving necessary tracking behavior
Two pages answer different questions Keep distinct URLs and relevant self-canonicals
Page removed with no suitable replacement Consider an appropriate not-found or gone response
Temporary move Use the appropriate temporary redirect behavior

A redirect to an unrelated homepage may frustrate visitors and fail to communicate a useful replacement. Match old URLs to destinations based on their purpose.

Keep supporting signals consistent

Once you choose the preferred URL, update relevant internal links and sitemap entries to use it. Check that the preferred destination is publicly accessible and intended for indexing.

Avoid declaring one canonical in HTML while a different layer supplies another in the response headers. Review CMS output, plugins and CDN rules together if multiple systems can influence the response.

For pagination or filtered catalogues, do not assume every URL is a duplicate of page one. The right strategy depends on whether the content and intended search purpose are actually equivalent.

Verify the deployed behavior

Test a small mapping sheet containing the old address, expected behavior and destination. For example:

curl -sS -D - -o /dev/null \
  'https://example.com/old-consulting/'

Inspect the first response, then inspect the destination. Confirm that there are no loops, accidental cross-domain moves or unnecessary chains. Check both the final content and its canonical declaration.

For a canonical-only alternate, confirm that the page remains accessible and that its canonical points at the intended equivalent page. A successful HTTP status alone does not verify the head markup.

Check normal user journeys too

Test navigation, enquiry links and forms after URL changes. Check whether campaign parameters survive where required. A redirect that satisfies a status-code test can still break a business workflow.

Record the change and monitor relevant Search Console information after recrawling. Do not promise immediate consolidation or rankings from a technically correct declaration.

If a page is missing from search, follow the indexing diagnostic checklist. Before a larger URL restructure, use the WordPress content audit guide to inventory existing pages and assign suitable destinations.