When an article that ranked well years ago loses traffic, teams often replace the year and add a few paragraphs. If user questions and competing pages have changed, this kind of surface-level update rarely restores value.
Diagnose why the page stopped working before editing: outdated facts, an incomplete answer, changed search intent, a mismatched title, internal duplication, or weaker sitewide signals. Each cause requires a different action.
01 Review the Queries the Page Covers Today
Use Search Console to analyze changes in impressions, clicks, position, and queries. Separate a primary-keyword decline, lost long-tail demand, and a click-through issue. The page may still receive traffic while users have shifted from introductory questions to comparison or execution.
Do not decide to rewrite the entire article based on one target keyword.

02 Research the Current Search Results Again
Review ranking-page types, titles, structures, freshness, and common user questions. If the SERP has shifted from tutorials toward tools or product pages, the old article may need a different format.
The goal is to find gaps, not to combine the headings of the top ten pages into an outline.
03 Mark Outdated Facts and Broken Content
Technology versions, platform policies, pricing, laws, screenshots, links, and product features can all change. Verify each section and remove advice that no longer holds.
Evergreen content that has not materially changed does not need to be rewritten merely to look “fresh.”

04 Add Information Gain and First-Hand Evidence
Add real cases, processes, tables, calculation methods, before-and-after comparisons, or measured results so the revised page offers value other pages do not.
More generic explanation makes the article longer, not more useful.
05 Resolve Internal Duplication and Keyword Cannibalization
Related search topics may be scattered across several old articles. Compare their queries and intent, choose one primary page, merge valuable material, and redirect retired URLs appropriately.
Do not keep three “how to choose” articles that differ only in their titles.

06 Update Publication Information and Internal Links
After a substantive revision, update the modified date and reflect the new conclusions in the body. Review the title, description, images, structured data, inbound and outbound links, and CTAs.
Continue monitoring crawling, indexing, queries, and conversions after publication. A changed date is not the definition of completion.
Decision Framework for Old Content
Status | Recommended Action | Typical Situation |
|---|---|---|
Accurate and still performing | Minor maintenance | Update links, screenshots, or a few facts |
Same intent, outdated content | Rewrite while keeping the URL | The page has links, history, and relevance |
Several pages compete | Consolidate and redirect | Topics and SERPs overlap heavily |
The topic no longer has value | Retire or archive | No traffic, links, or business value |
Old and new intent differ | Create a separate page | The ideal answer and page type have changed |
Frequently Asked Questions
How often should old articles be updated?
There is no fixed schedule. Time-sensitive topics need regular verification; evergreen content should be updated when performance or facts change.
Should the original URL be retained?
If the topic and intent remain the same and the URL has value, retaining it is usually safer. Create a new page when the topic changes completely.
Can we delete underperforming articles?
Yes, but first check backlinks, queries, internal links, and consolidation potential instead of relying only on current traffic.
Should we request indexing again after an update?
You can request recrawling through URL Inspection, but submission does not guarantee immediate processing or higher rankings.
Does adding an FAQ count as a meaningful update?
Only when the FAQ addresses real user questions. Mechanically adding one does not replace improvements to the main content.
Service | View |
|---|---|
Related service | |
Related article | Read the article |
Design work | |
Project inquiry |