Canonical vs 301 redirect: when two pages on your site rank for the same search
Two pages appearing for a search is a prompt to investigate, not proof that one should disappear. A canonical identifies a preferred URL for duplicate or very similar content. A 301 sends visitors and crawlers to a permanent replacement. Distinct pages that answer different customer needs can keep their own URLs and self-canonicals.
Start with the content, then choose the signal
Different useful content
Keep each page self-canonical. Explain the distinct customer question and link between the pages.
Duplicate that must stay accessible
Name the preferred equivalent URL with a canonical. The variant remains available to visitors.
Equivalent URL genuinely retired
Redirect directly to the relevant replacement and update links to the final address.
Existing clicks are a reason to investigate carefully, not an automatic choice of canonical or redirect.
A shared keyword is not enough
A pricing guide and a service page can share a subject while doing different jobs. Check the queries, clicks and enquiries each page earns before changing either. If one explains the cost and the other helps a customer hire you, make that difference clear in their titles, introductions and links.
What a canonical actually changes
A rel="canonical" link is a preferred-URL signal, not a setting for one keyword. It is useful for an accessible duplicate, such as a tracking-parameter version. Google decides which URL to treat as canonical. If it accepts a source as a duplicate, do not expect that source to keep an independent set of rankings.
A useful article should not point its canonical at a different service page simply because both mention the same topic. Keep genuinely different content self-canonical and connect it with a relevant ordinary link.
When a permanent redirect fits
Use a 301 when an address has moved or an equivalent duplicate is being retired. Choose a replacement that serves the same need. A discontinued page with no relevant replacement may need an honest not-found response instead of sending everybody to the homepage.
Existing traffic and backlinks deserve review before a move. They are not a blanket reason to avoid redirects: preserving the purpose of the destination, carrying across useful content and testing the mapping matter. A live page is not worth retiring merely to make a site look tidier.
Check the evidence before changing URLs
- Compare the actual content and the customer job of both pages.
- Review query, page, click and enquiry data over comparable periods.
- Check backlinks and the indexed canonical choice in Search Console.
- Test that the proposed destination returns 200 and serves the relevant content.
- Keep canonicals, internal links and sitemap entries consistent with the intended final URLs.
- Monitor recrawling and performance afterwards. Search visibility can move while changes are processed.
Keep the implementation simple
Point a canonical at the final equivalent URL, not at a redirect chain. Send a moved address straight to its destination. Keep each distinct paginated page self-canonical rather than naming page one for the entire sequence. Check language variants separately and keep their language annotations consistent.
Also inspect robots directives. A stray noindex can prevent indexing even when a canonical is otherwise correct. Multiple directives must be consistent; adding an index tag does not cancel a restrictive directive elsewhere.
Common questions
Should a how-to article canonicalise to a service page?
Usually not when the pages answer different needs. Keep useful distinct pages self-canonical, make their purposes clear and link them naturally. A shared keyword alone does not make them duplicates.
Does a canonical guarantee both pages keep ranking?
No. A canonical is a preferred-URL signal for duplicate or very similar content. Google can choose a different URL, and accepting the source as a duplicate does not preserve its independent rankings.
When is a 301 appropriate?
Use a direct permanent redirect when an old URL has genuinely moved or an equivalent duplicate is being retired. Check the destination, query intent and existing traffic first; keep a useful distinct page when it still has a job.
What should I check before changing either signal?
Check content similarity, query and conversion data, backlinks, current canonical choices and the destination response. Keep the canonical, sitemap and internal links consistent, then monitor recrawling.
Primary references
Related: planning a WordPress migration and redirecting a domain for a genuine move.