When a permanent redirect is appropriate

A 301 indicates that a resource has permanently moved. Use it when an old address should lead to the corresponding new page after a URL change, content consolidation or site migration. A 308 can also be appropriate, depending on request handling and implementation.

A redirect does not make every destination a suitable replacement. If a removed article has no relevant equivalent, sending visitors to the homepage simply to avoid a 404 usually fails their original task.

One direct, relevant redirect: Old URL; 301; Relevant new page; HTTP 200; Updated internal links
One direct, relevant redirect

Map addresses before changing them

Collect old URLs from sitemaps, analytics, Search Console and known external links. Assign each a new destination or an intentional removal decision. Prioritise pages with customers, links and useful information.

An illustrative mapping is /old-service/ to /services/new-service/. The new page must genuinely serve the earlier need. For translated material, verify the destination language as well.

Keep the rule set understandable

Redirects may be implemented on the server, in the CMS or through a plugin. Problems arise when several layers add rules independently, creating chains, loops or unexpected changes between HTTPS, www and path variants.

Back up the configuration first. Do not paste an arbitrary .htaccess snippet without checking the server type and existing rules. A configuration error can affect the entire site.

Test more than whether a page opens

  1. The old URL returns the intended redirect status.
  2. It reaches the right destination without a loop or avoidable intermediate hops.
  3. The final page returns a successful response and relevant content.
  4. Its canonical agrees with the new URL.
  5. Navigation, body links and the sitemap use the final address.

A browser displaying the destination can conceal a long chain. Inspect network responses or use a suitable crawling tool.

Include useful files

PDFs, images and other downloads can have incoming links too. Check important file URLs and embedded references rather than treating the migration as a list of HTML pages only.

For a full site move, use the migration plan. Redirects are one component alongside content, indexing permissions and working business functions.

Monitor after launch

Keep the mapping and implementation date. Watch for errors, unexpected destinations and recrawl outcomes. Do not remove redirects merely because the new URL has appeared in search: old links and bookmarks may still be used. Retention depends on the situation and migration requirements; redirects are not a launch-day-only task.

Need a plan for your website?
Explore our services: SEO Services, pricing or discuss your project.