Plan content retirement and consolidation

State why each article is being retired

Consider a site with an old pricing explanation, a current pricing guide and separate cancellation instructions. Record the retirement reason for each URL: outdated facts, substantially repeated guidance or a service that no longer exists. Low traffic can start a review, but it is not a sufficient deletion rule by itself. A customer may need a cancellation procedure only once a year. Define the review scope with the URL, title, current reader task, proposed reason and information owner before changing publication settings.

• Map search intent to articles

Extract material that still serves a reader

Write one sentence describing the decision or action each article supports. Comparing a plan and cancelling a subscription are different tasks even when the product is the same. Separate useful explanations, figures requiring re-verification and guidance that has expired. Open the underlying official sources before moving facts. If an older page contains a valuable exception, understand it before editing. Do not paste entire old sections into a destination to increase its length; rewrite the necessary point where the destination reader will actually need it.

Choose retain, consolidate or remove

Consolidation is a candidate when a current article serves the same purpose and can absorb the useful material. An article supporting an independent task may instead need a clearer title or navigation. Historical documentation can also remain valuable when its past context is explicit. Removal becomes a candidate when neither useful material nor a suitable replacement remains. Read the proposed destination as someone arriving from the old article. Sending every retired URL to the homepage is not a substitute for checking that the original question is answered.

Finish the destination before enabling redirects

Prepare the destination text and its necessary sources before enabling a permanent move. Then map each old URL to the appropriate published destination. Google distinguishes permanent and temporary redirects, so a temporary editing arrangement should not be described as a permanent migration. Assign ownership to the actual redirect layer, whether that is the CMS, hosting configuration or an extension. Where practical, map original addresses directly to their final destinations instead of extending existing chains. The content decision and the delivery configuration should be reviewed together, rather than handled as unrelated tickets.

• Build a URL migration map

Update internal references and discovery paths

Inventory references in related articles, categories, contents lists, downloadable documents and reusable email text. A working redirect is useful, but links under your control should normally point to the final destination. Review sitemap entries and canonical declarations against the URLs intended for publication. If a crawler such as Screaming Frog supplies the link inventory, record its scope and authentication context. Its output describes what that crawl discovered, not a guarantee that every partner link, private document or previously sent email has been found.

Even a working destination may omit the section that an old link promised. Record the transferred heading as well as the URL, and check links containing section fragments. If the destination merely has a similar title but lacks the required explanation, return to the editorial transfer before extending the redirect rollout.

Verify a small, representative URL set

Start with one consolidated article, one retained article and one removed article without a successor. Check the old response, redirect destination, final visible text and mobile presentation. A missing-page message served with a successful HTTP response is not the same as an actual removal response. Also check without an administrator session to confirm the new copy is publicly available. Record expected and observed outcomes in separate columns of the mapping sheet. Correct mismatches before applying the same configuration to the remaining URLs.

Keep a recovery record and realistic budget

Save the original copy and publication settings before making changes, and record where redirect rules were edited. A rollback may require restoring text, publication status and delivery configuration together. Budget separately for editorial review, destination rewriting, configuration and verification. A small set managed through an existing CMS does not automatically require a new audit subscription. At larger volumes, check current crawler and bulk-edit conditions, while keeping software allowances separate from the human time needed to decide where the content belongs.

Review outcomes without promising a ranking gain

Review the affected URLs with consistent date ranges and filters, including queries now associated with the destination and any broken discovery routes. A ranking increase is not the acceptance condition for an editorial retirement. First confirm that readers can reach a page answering their original need. If support enquiries reveal missing reference material, investigate that task and repair the information path. Record implementation dates, review dates and unresolved URLs. Use that history in the next review rather than repeatedly changing destinations without a new editorial reason.

• Audit internal links