Estimated reading time : 5 min · Published
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.
| Request and response | Behaviour to examine | Expected evidence in the test environment |
|---|---|---|
| GET · permanent 301 | Navigation to the final destination | The correct page arrives without another chain. |
| POST · permanent 301 | A client may change POST to GET | The test does not assume the body is forwarded. |
| POST · temporary 307 | The method is retained when followed | The test destination receives the expected method and data. |
| POST · permanent 308 | The method is retained when followed | The 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
- Google Search Central : URL migration · Source consulted
- Google Search Central : redirects · Source consulted
- MDN : 301 status
- MDN : 404 status
- MDN : 308 Permanent Redirect · Source consulted
Content updated on
Documented reference points for this topic
| Reference | Value or syntax | Scope |
|---|---|---|
| HTTP · 308 | 308 · Location | Permanent 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.
