A 301 redirect strategy maps permanently moved URLs to their most relevant current destinations. It is part of content planning as well as server configuration: the replacement must make sense for someone who requested the original page. A documented map helps preserve useful journeys when a website is reorganised.
Communicate a permanent move
A server-side 301 is a permanent redirect signal. Search engines can use it when deciding which URL should represent moved content, but the change still needs processing. A redirect cannot make an unrelated destination answer the original query. Retain the original purpose where possible, update internal links and align the sitemap with the new preferred URLs. Redirect planning is especially important when names, domains or category structures change together and many existing references still point to older addresses.
Build and validate a migration map
Inventory existing URLs using a site crawl, sitemap, search performance data and useful external references. Give each one an explicit outcome: retain, move to a relevant replacement, consolidate with closely related content, or remove. Test mappings before launch for status codes, loops and final page content. After release, sample high-value URLs and check that redirect rules survive hostname and trailing-slash variations. Keep the mapping accessible to editors so subsequent page changes do not quietly add another redirect chain.
Include downloadable files in the migration inventory when people link to them directly. An important brochure or guide can retain external references even though it does not appear in the normal page-navigation crawl.
Choose relevance over blanket redirects
Suppose a hypothetical Perth training business combines two introductory courses into one current course. A permanent redirect can be appropriate when the new page clearly serves the old audience and explains the current offer. A discontinued specialist qualification with no replacement is a different case. Sending all such pages to the homepage may frustrate users and be interpreted as a soft 404. Monitor old-to-new traffic and index coverage, and allow time for search systems to recognise a legitimate migration.
A technical SEO migration review can connect the URL map with launch checks.
Common questions
Should every deleted URL return a 301?
No. Use a relevant replacement when one exists. A genuinely removed page without a suitable successor can return a proper 404 or 410 response.
Can permanent redirects be removed immediately?
Google recommends keeping migration redirects for at least one year. Retain them longer where useful external links, bookmarks or customer traffic still rely on the old addresses.
Terms in this guide
- Redirect — A server or browser instruction that sends a request to another URL. Permanent URL migrations should avoid unnecessary chains and link directly to the intended destination.
- Internal link — A hyperlink between pages on the same website. Useful internal links connect related subjects, explain the site structure and give readers a relevant next step.
- Sitemap — A structured list of relevant site URLs. XML sitemaps support discovery by search engines; an HTML sitemap helps people navigate the site.
- HTTP status code — A response code communicating the result of a request. Examples include 200 for a successful response, 301 for a permanent redirect and 404 for a resource not found.
Related SEO guides
Apply this to your website
Explore Technical SEO, SEO Audits for help planning and implementing the relevant changes, or discuss your website with Refined IT.