Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Practical guides

    Prepare and test a URL redirect plan

    An old address may still have visitors, backlinks and documents referring to it. A redirect plan records what each address becomes during a rebuild, domain change or content consolidation, preserving useful journeys.

    Go to the method

    Page layouts and journey arrows on paper
    AI-generated illustration

    Inventory addresses with a purpose

    Combine sitemaps, a crawl, internal links, campaign pages and available traffic evidence. Include downloads and addresses distributed in emails or printed material. A page without recent traffic can still be referenced elsewhere.

    Record the old URL, subject, proposed destination, decision, owner and test result. Similar addresses do not establish equivalent content. Identify parameters needed by the journey separately from those used only for measurement.

    Choose an equivalent destination

    A replacement with genuinely equivalent content can receive a permanent redirect. A removed resource without a relevant replacement should retain a real absence status. Sending every old page to the homepage loses the context of a visitor seeking a specific service.

    A canonical indicates a preferred representation; it does not move the visitor. A temporary redirect suits a temporary move. Record the reason for each decision and confirm that the destination answers the original need.

    Preserve methods and avoid chains

    For GET navigation, 301 and 308 indicate a permanent move. A client receiving 301 may change POST to GET; 308 preserves the method. Temporary codes 302 and 307 have a comparable distinction. Forms and APIs therefore require tests beyond reading the destination page.

    Point old addresses directly to the final destination. Check HTTP/HTTPS, hostnames, trailing slashes and previously redirected addresses. Detect loops, missing targets and unwanted language changes. Use synthetic data and a test environment when exercising POST routes, never a real order simply to prove a redirect.

    A fictional reading-page test compares two chains: A returns 301 to B, B returns 301 to C, and C returns 200. This is two redirects and three sequential HTTP exchanges for navigation, excluding page assets. A direct A-to-C rule reduces this example to one redirect and two exchanges; that alone does not measure time saved.

    For a submission, record the method, test body and application outcome after each hop. Preserving POST with 307 or 308 does not make the operation idempotent or guarantee no duplicates. These tests use a demonstration handler without a real order, payment or message; an HTTP status alone does not prove correct processing.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Fictional exercise: four redirects tested by request method
    Request and responseBehaviour to examineExpected evidence in the test environment
    GET · permanent 301Navigation to the final destinationThe correct page arrives without another chain.
    POST · permanent 301A client may change POST to GETThe test does not assume the body is forwarded.
    POST · temporary 307The method is retained when followedThe test destination receives the expected method and data.
    POST · permanent 308The method is retained when followedThe test separates receipt, application effect and possible duplication.
    • RFC 9110 · HTTP Semantics

      RFC 9110 and MDN distinguish permanence from method preservation. Sources consulted on 22 October 2026; this table is not a ready-to-deploy redirect rule for a live service.

    • MDN · 308 Permanent Redirect

      Read the mechanism and its limits in this primary reference.

    Align the website’s signals

    Update internal links, the sitemap, canonical references, language versions and document links. Redirects support old references; current navigation should use the new addresses directly.

    After release, check examples from every page family and observe errors and indexing. Google recommends retaining migration redirects as long as possible, generally at least a year. Visitors can use old links beyond that period, so also consider references still in circulation.

    An example of a documented decision

    Educational example: an old shop-maintenance page is merged into a page that still describes that service. The mapping uses a permanent redirect and updates internal links. An expired event offer either becomes a useful archive or returns an absence status when removed. Available content determines the choice, rather than URL similarity alone.

    Decision case: merge two pages without losing their purpose

    Synthetic example: a service introduction and its conditions page are combined. Before sending both old URLs to the new page, confirm that it actually contains the offer and expected conditions. Test a link from a document with its useful fragment or parameters. Reaching the right section may still be insufficient when the precise information has disappeared.

    Keep a separate justification for each old address in the migration table. Update links you control to reach the final content directly. If an old URL receives form data, assess its method and processing separately; do not submit a real request to validate an editorial rule. Prepare rollback for the affected rules and content.

    Reference documents

    Content updated on

    Documented reference points for this topic

    Documented reference points for this topic
    ReferenceValue or syntaxScope
    HTTP · 308
    308 · LocationPermanent relocation: the request method and body are preserved.

    Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.

    Acceptance matrix to adapt to your project

    These proposed checks use synthetic cases. Decide the required behaviour with the team, record the result and assign unresolved gaps before release.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Test cases, expected outcomes and useful evidence
    CaseExpected outcomeEvidence to retain
    Merged service pageThe destination still answers the service need and returns 200Initial URL, status at every hop, final destination and passage answering the original need.
    Previously redirected addressThe rule reaches the final destination directlyHop list and loop check
    Synthetic POST routeMethod and behaviour match the intended contractTrace without personal data in a test environment
    Removed content without equivalentA real absence status remains and recovery links are usefulHTTP status and onward links

    Frequently asked questions

    Should every 404 be redirected?

    A redirect needs a relevant destination. An unknown address or removed content without a replacement may remain 404 or 410 depending on context. Review intent and existing references first.

    Does a canonical replace a redirect?

    No. It indicates a preferred URL to search engines; the browser stays on the requested address. A redirect moves the request.

    Is testing the destination enough?

    Also test the old address: status, Location header, hops, parameters, language and method for action routes. A correct destination can still be reached through an incorrect rule.