Refresh
Correct stale facts, repair links, improve examples, tighten the answer, and fill meaningful gaps while preserving the core structure.
Guide
Content Refresh vs. Rewrite: What to Change and What to Preserve
Decide whether an underperforming page needs a light refresh, a substantial rewrite, consolidation, or a new URL without erasing what still works.
Practitioner guidance reviewed for accuracy, usefulness, and alignment with current search documentation.
Refresh when the page still serves the right audience and intent but needs current facts, clearer structure, stronger evidence, or missing subtopics. Rewrite when the answer is fundamentally weak or the intent has changed. The scope of the edit and the decision to change the URL are separate choices.
What to remember
- Preserve the URL when the page still owns the same purpose; a large rewrite does not require a new address.
- Protect sections, links, examples, and query coverage that continue to earn results.
- Create a separate page when one URL would otherwise have to satisfy incompatible intents.
- Measure the same page-query pairs before and after the change.
Separate four decisions that teams often collapse into one
Rewrite
Rebuild most of the argument or instruction because the current page is incomplete, confusing, generic, or aimed at the wrong version of the intent.
Consolidate
Merge genuinely overlapping pages into the strongest destination and redirect retired URLs when they no longer need to exist.
Create
Build a distinct URL when the opportunity serves a different audience, intent, funnel stage, or page type.
Score the page before choosing the scope
| Question | Refresh signal | Rewrite or new-page signal |
|---|---|---|
| Does the page satisfy the same search intent? | Yes; the job is still correct. | No; the audience or task changed. |
| Is useful material still present? | Most important sections remain accurate and helpful. | Very little is worth preserving beyond the topic. |
| Does the current URL have relevant history? | It earns impressions, links, conversions, or recurring visits. | It has no meaningful fit or points at a different purpose. |
| Are the gaps local or structural? | A few missing answers, examples, or updates. | The argument, hierarchy, or format is fundamentally wrong. |
| Would one page become internally contradictory? | No; the same reader benefits from the update. | Yes; distinct intents need distinct destinations. |
Use Search Console page and query filters to mark what the page currently earns. Search performance does not tell you whether a paragraph is good, but it helps reveal which query relationships you should avoid disrupting without a reason.
Build a preserve list before the edit list
- Purpose: the primary audience, problem, and intent the URL should own.
- Winning query coverage: terms and questions for which the page already earns qualified impressions or clicks.
- Useful evidence: original examples, screenshots, data, expert commentary, and explanations that remain correct.
- Link equity and navigation: valuable backlinks and internal links pointing to the URL.
- Conversion path: calls to action that match the reader’s next reasonable step.
Google says helpful content should add original information, complete treatment, clear sourcing, and first-hand expertise. Use its people-first content questions as an editorial test, not a box-ticking ranking formula.
Write an evidence-based change plan
- 01
State the current job
Write one sentence describing who the page is for, what question it answers, and what the reader should be able to do afterward.
- 02
List the evidence
Record the page-query data, declining or stable sections, outdated facts, competing-result patterns, user feedback, and conversion behavior that led to the change.
- 03
Label every section
Keep, update, expand, combine, remove, or create. “Rewrite everything” is not a useful instruction.
- 04
Protect the URL decision
If URLs are combined, use a redirect and consistent canonical signals. Google describes redirects and rel=canonical as strong canonicalization signals.
- 05
Create the measurement annotation
Record the publish date, changed elements, affected queries, and next review date before the new version goes live.
Quality-check the finished page
| Layer | Check |
|---|---|
| Answer | The first screen makes the page’s purpose and answer clear. |
| Accuracy | Every changed fact, link, example, and claim is verified. |
| Coverage | The page resolves the core task without padding or duplicating adjacent pages. |
| Search appearance | Title, H1, description, and visible copy describe the same page. |
| Technical | Canonical, status code, structured data, sitemap entry, and internal links point to the intended URL. |
| Measurement | Baseline, publication date, primary page-query pairs, and conversion event are recorded. |
Common questions
Frequently asked questions
What is the difference between a content refresh and a rewrite?
A refresh improves an existing answer while preserving most of its purpose and useful material. A rewrite rebuilds much of the answer because the current structure, coverage, or intent is fundamentally weak. Both can remain on the same URL.
Should I change the URL when I rewrite a page?
Usually not if the page still serves the same purpose. Change the URL only when the current address is misleading, the site structure requires a move, or content is being consolidated. Use a permanent redirect and update internal links when a URL changes.
Can changing too much hurt an existing ranking?
Any substantial change can alter how a page is understood and which queries it serves. That does not mean pages should never change. Preserve useful material and proven intent, make changes for documented reasons, and measure the same page-query pairs afterward.
When should two articles be consolidated?
Consolidate when they substantially overlap in audience and intent, compete for the same internal links or search demand, and one stronger page can satisfy the task. Similar keywords alone are not enough.
Continue with Perennial
Refresh without erasing what already works
Perennial helps teams research, draft, review, and measure content updates in one workflow.