Choose redirects according to the move a visitor needs

Start with the decision, not the metric.

A migration changes the routes by which people and search engines reach your content. Protect that journey with a URL-by-URL plan, appropriate redirects, updated discovery signals, and post-launch monitoring. A successful deployment means that important old links reach useful new destinations, not merely that the new homepage loads.

A redesign can accidentally remove popular guides, product URLs, images, or regional pages. Redirecting everything to the homepage hides the loss rather than preserving the visitor's intent. Treat a migration as a coordinated release across content, server configuration, analytics, search ownership, and customer-facing links.

Your focus: Choose redirects according to the move a visitor needs

Explain temporary and permanent redirects through real page changes, including equivalent destinations, chains, and verification. Distinguish a redirect from a canonical signal or an error response, and show why preserving a useful journey matters more than hiding every missing URL behind the homepage.

Turn the idea into a repeatable workflow.

Collect old URLs from the CMS, sitemaps, analytics, Search Console, and known inbound links. Map each important URL to the closest legitimate new destination. Explicitly identify content being retained, merged, replaced, or removed.
Use server-side 301 or 308 redirects for permanent moves when suitable. Point each old address directly to the final new page, avoid loops, and test both host variants, HTTP-to-HTTPS behavior, and meaningful query parameters.
Before launch, update internal links, canonicals, language annotations, images, and sitemaps to the new URLs. Verify access settings and search ownership. Keep a configuration backup and a practical rollback procedure for deployment defects.
After launch, test the mapping in bulk and monitor error responses, important landing pages, and search visibility. For domain moves use the applicable Search Console process. Maintain redirects for the documented long-term migration period, not only the launch week.

A practical example

Map an old service URL to its actual replacement and test the response chain from start to finish. Confirm the final page answers the original need, update internal links to the new destination, and test unrelated missing URLs still return appropriate errors.

Make the next step specific.

Choose one commercially important page or a small, related group of URLs. Record its current state, the user need, the proposed change and the person responsible. Separate evidence from assumptions so you can tell whether the work solved the original problem.

Use the Gavek planning workspace to turn these checks into assigned priorities. The free website snapshot can help inspect initial HTML signals; it does not replace a site-wide crawl, a live ranking data source or an index coverage review in Search Console.

Create your SEO action plan ↗

Avoid the work that creates more work.

Sending unrelated removed pages to the homepage as a universal fix.
Leaving long redirect chains after several successive migrations.
Deleting the old routing configuration before important links are verified.

Measure useful progress.

Important old URLs reaching the intended final destination.

Redirect loops, chains, and new error responses.

Search clicks and conversions for mapped landing-page groups.

Keep the comparison period, location, device and data source consistent. Search results and AI answers vary; a single observation is a diagnostic clue, not proof of long-term growth or causation. Connect visibility changes to relevant enquiries, qualified leads or sales wherever reliable first-party data is available.

Questions worth asking.

Which redirect is appropriate for a permanent move?

Server-side 301 and 308 responses are permanent redirect options Google recognizes. Select an implementation that also respects your application's request behavior, and test the final destination rather than relying on the status label alone.

Can migration cause temporary search fluctuations?

Yes. Search engines need to reprocess changed URLs and signals. Monitor the affected groups and diagnose specific failures; do not immediately reverse a technically sound migration because of a single day's movement.

Go to the source.

These independent guides are grounded in primary documentation. Platform behavior and search systems can change; consult the linked documentation when implementing a change.

Editorial guidance from Gavek. No ranking guarantees, customer-result claims or endorsement by the referenced platforms.