Refresh, merge, or retire content with a defensible reason

1. State the page’s current job

For each candidate, write who uses it, what they should understand or complete, and which business process depends on it. A support instruction, sales reference, event announcement, and general article have different jobs. Ask the relevant owner whether colleagues still send the link or rely on its attachments. Check important facts against the current service. Record a clear problem, such as an obsolete requirement, overlapping answer, or discontinued offer. If you cannot identify a problem or an unmet need, keeping a sound page unchanged can be a valid decision. Age alone does not describe usefulness.

2. Check whether the evidence can answer your question

Collect authorized data that matches the page’s job: search impressions and clicks, relevant website events, customer questions, internal references, or known links. Google describes Search Console’s performance report as a view of Google Search metrics. That is a narrower scope than total business usefulness. Record dates, filters, tracking changes, and unavailable information before comparing periods. A page with few search visits may still be used in customer onboarding. An untracked form cannot establish an absence of enquiries. Where evidence is weak, document uncertainty and choose a smaller reversible change rather than treating missing data as a deletion instruction.

3. Refresh when the job remains useful

Refresh a page when its audience and purpose still make sense but its answer needs repair. Specify the affected claims, missing steps, unclear conditions, or broken customer route. Preserve accurate material rather than rewriting every paragraph for novelty. Update the substantive content and record what changed; a new date should reflect real editorial work. Keep the URL when it still describes the same task and no broader change requires moving it. Review connected FAQs, downloads, and translations so the corrected answer does not conflict with adjacent material. Give the owner a concrete acceptance test tied to the original problem.

4. Merge only when one page can serve the combined task

Two pages discussing the same subject may serve different decisions. Compare their audience, scope, and next action before merging. When the overlap is genuine, select a destination that preserves the strongest accurate material and any useful unique details. Draft the combined page before changing the old URLs. Google’s migration guidance advises against sending unrelated old pages to a generic destination and allows relevant consolidation into one page. Plan the old-to-new mapping with the person responsible for implementation. Update internal references and language equivalents. A shorter inventory is not sufficient evidence that readers will be better served.

5. Separate three choices in a hypothetical library

Imagine a hypothetical service company reviewing three resources. Its still-used onboarding guide needs a corrected preparation step, so it is a refresh candidate. Two articles answering the same package-eligibility question contain compatible details, making them possible merge candidates after review. An expired workshop announcement has no current booking purpose, but may still need a clearly labeled archive if people refer to it. This example contains no real performance results. Retirement might mean removing misleading promotion while retaining historical context, or removing the page with an appropriate technical response when no useful replacement exists. Check retention obligations and obtain the owner’s approval first.

6. Verify the decision without inventing its impact

Before release, preserve the original page, the reason for the decision, the approved destination or removal behavior, and a recovery plan where available. Afterward, test the reader’s route, internal links, attachments, and both language versions. Review outcomes over a period appropriate to the page’s use and the available data. Keep implementation success separate from a claimed increase in leads or rankings. If a merged page no longer answers an important question, repair that gap instead of defending the original decision. Use Suprara’s resources to document the change and its remaining uncertainty, with further study in the related indexing guides.

Frequently asked questions