A redirect can move a visitor to a new address, but an API request needs a separate check of its method and body. DEFINE THE SCENARIO FIRST List old and new addresses: homepage, language pages, articles, sign-in form and API routes. For each, record whether the move is temporary and whether the route receives a request body. A GET navigation between pages and moving a POST request are different tests. Do not impose one global redirect pattern just because it fixed the homepage. THE METHOD MATTERS MDN describes 307 as temporary and 308 as permanent redirects that preserve the request method and body. POST behavior with 301 and 302 can differ for historical reasons. A transition to a results page after successful form processing may call for 303. Choose according to the route's contract rather than an administrator's preferred status code. BUILD A TEST MATRIX In a test environment, check each route in a browser and with the actual API client intended for the integration. Record the initial response, Location header, final address and method received at the destination. Use harmless fixtures, not a real payment to exercise a route. Check query parameters, language paths, loops and unnecessary redirect chains. CONTROL THE RELEASE Do not enable a permanent redirect before verifying the destination and rollback plan. Update internal links so new navigation goes straight to the target. Review sitemap and canonical addresses separately: an HTTP response is not the entire SEO migration process. For authenticated requests, do not assume credentials or sessions transfer safely to another host; check the client's behavior and the service's rules. When shortlisting a new domain for a rebrand, budget for an address map and integration tests. An attractive name alone cannot provide a correct website migration. Give one person responsibility for the route inventory and retain the test results alongside the change record. Image: AI photoillustration created for this article; a conceptual scene, not a documentary photograph. Domain catalogue: https://domainevery.com/en/domains Primary sources: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/307 https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/308 https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Redirections
