Refresh, Merge, Redirect, or Retire? Content Decision Tool
Answer five evidence questions and generate a review record for refreshing, merging, redirecting, retiring, or investigating one URL.
Content decision worksheet
Choose a defensible next action for one URL
Answer with evidence from analytics, Search Console, a crawl, and a manual page review. The result is a review prompt—not an automatic deletion rule.
Use this worksheet when an existing URL is weak, stale, overlapping, or no longer necessary. It converts five review questions into a provisional action: refresh, merge, redirect, retire, or investigate. The result stays in your browser and should be confirmed with real crawl, Search Console, analytics, backlink, conversion, and content evidence.
How the decision model works
The first question is the reader job. If the job still matters and the page is distinct, weak execution normally points toward a refresh. If a stronger page already serves the same job, consolidation becomes a candidate. When the job no longer matters, retained value and the presence of a genuinely equivalent successor determine whether a redirect is defensible.
| Action | Use when | Primary risk |
|---|---|---|
| Refresh | The job and URL are still useful, but execution or evidence is weak | Changing too much without a baseline |
| Merge | Two pages materially overlap and one can complete the full job | Losing distinct intent or evidence |
| Redirect | An old URL has a true successor that satisfies the same need | Sending users to an irrelevant destination |
| Retire | The job has ended and no retained value or equivalent destination remains | Deleting before checking dependencies |
| Investigate | Evidence is missing or contradictory | Turning uncertainty into a forced decision |
Evidence to collect before acting
- Current reader job, boundary, and business owner.
- Search Console pages and queries for a complete comparison period.
- Analytics visits and configured outcomes.
- Internal links, canonical state, backlinks, bookmarks, campaigns, and external dependencies.
- Competing URLs and whether their jobs truly overlap.
- Content accuracy, source freshness, original value, and maintenance cost.
Apply the result safely
For a merge, preserve the strongest useful material on the surviving page, update internal links and canonicals, and redirect only when the destination is equivalent. Google describes redirects as a strong canonical signal in its canonicalization guidance. Its site-move guidance recommends mapping old URLs to relevant new URLs, avoiding redirect chains, and not sending many unrelated pages to the homepage.
For retirement without a successor, remove internal promotion, update navigation and sitemaps, preserve any required legal or business record, and return the response that accurately represents the resource state. Monitor logs, links, Search Console, conversions, and support reports after release.
Primary documentation
Privacy and limitation: answers are stored locally in this browser. The worksheet does not crawl a URL, inspect backlinks, calculate business value, or guarantee a traffic result.
Community discussion
Discuss: Refresh, Merge, Redirect, or Retire? Content Decision Tool
Have a question, a useful example, or a different perspective? Join the discussion, share evidence, and help other readers reach a better answer.
Be the first to ask a focused question, share a practical example, or add useful evidence.
Ask a question or join the discussion