A page needs an SEO update when evidence shows it has become less visible, less accurate, or less useful than the results it competes with. Age alone is not that evidence.
Some old pages keep ranking for years. Others decay within months. The hard part is knowing which pages need attention and what actually needs to change, because a traffic drop can come from falling search demand, a core algorithm update, an AI Overview, a canonical error, or a competing page on your own site. Only some of those are content problems.
This guide uses a four-phase process: detect a performance signal, diagnose the cause, decide on the smallest fix, and measure the result against a baseline.
Phase 1: Detect a meaningful performance signal
Start in the Google Search Console Performance report, filtered to a single page, and compare at least the last 3 months against the same 3 months a year earlier. Year over year comparison is the default because it cancels out seasonality.
A page is worth investigating when you see one of these patterns:
- Organic clicks down 20% or more year over year, sustained for 4 or more weeks
- A page that was stable for months starts a steady decline
- Several pages in the same topic cluster decline together
- A keyword that held page one slips to page two
- Impressions fall before clicks do, which is often the earliest warning
Rule out demand and algorithm changes first
Before blaming the page, check two external causes. Open Google Trends for the main query: if search interest fell by a similar amount, the page lost demand, not rankings. Then line up the date the decline started with confirmed core updates and spam updates (see how the September 2026 update affected rankings). A drop that begins within days of a core update points to a sitewide quality or relevance reassessment, which a single rewrite rarely fixes.
Read the metrics together
Impressions, clicks, CTR, and average position each tell you something different. Switch the Search Console view from page level to query level to see which queries moved.
| Signal | Likely cause |
|---|---|
| Impressions down, position down | Relevance or competition problem |
| Impressions stable, CTR down, position stable | SERP feature or AI Overview taking clicks, or a weak snippet |
| Impressions up, clicks flat | Ranking for broader queries the page doesn't fully serve |
| Position down across many queries | Page level or topic level problem |
| One query down, others stable | Query specific intent shift or competitor |
| Impressions down, Google Trends down | Falling search demand, not a page problem |
Phase 2: Diagnose the cause
Work through the causes from cheapest to fix to most expensive. A technical error or a cannibalization conflict will undermine any rewrite, so check them before touching the copy.
- Technical SEOIs the page indexable, with the right canonical and status code?
- Keyword cannibalizationDo two of your URLs swap positions for the same query?
- Internal linksDo strong, related pages link to it?
- SERP features and AI OverviewsIs something above the organic results taking the clicks?
- Outdated informationAre facts, screenshots, and recommendations still correct?
- Content gapsDoes it answer what searchers now expect?
- Search intent shiftHas the dominant page format changed?
1. Technical SEO
Confirm the page can be crawled, rendered, and indexed. Use the URL Inspection tool in Search Console and a site crawler to check for:
noindexdirectives or robots.txt blocks- Canonical tags pointing to another URL
- Redirect chains, 4xx, or 5xx status codes
- Missing or duplicate title tags and H1s
- JavaScript rendering that hides main content
- Incorrect hreflang on multilingual sites
A page that isn't indexed doesn't need a better article. It needs the technical problem fixed.
2. Keyword cannibalization
Filter Search Console by the page's main query and check whether two or more of your URLs swap positions for it. Similar titles, overlapping intent, and alternating ranking URLs are the giveaway. Decide whether to consolidate with a 301 redirect, differentiate the intent of each page, or leave both alone before updating either one.
3. Internal links
A strong page with few relevant internal links can underperform. Check how many pages link to it, whether any are high authority pages, what anchor text they use, and whether it is orphaned. Adding three contextual links from related, well performing pages is often cheaper and faster than a rewrite. Our guide to auditing internal links covers the process.
4. SERP features and AI Overviews
Search the main query yourself. If an AI Overview, featured snippet, People Also Ask box, or video carousel now sits above the organic results, stable rankings can still lose clicks.
Last year: position 3
This year: still position 3
This is a zero click problem, not a title problem. The realistic responses are earning a citation in the AI Overview with a clear, direct answer near the top of the page, targeting the featured snippet format, or shifting effort toward queries where users still click through.
Also check whether Google is rewriting your title tag in the results. If it is, your carefully edited title may not be what searchers see.
5. Outdated information
Check for stale statistics, old screenshots, changed software interfaces, deprecated techniques, discontinued products, wrong pricing, and features that no longer exist. Fast moving topics like analytics, search, and SaaS decay fastest. A page can keep ranking while recommending something that no longer works, which erodes trust and E-E-A-T signals over time.
6. Content gaps against current results
Compare your page with the top 5 results on intent, format, coverage, freshness, examples, and original value. Look at the questions appearing in People Also Ask and the queries in Search Console that bring impressions but few clicks. The goal is not a longer page. It is a page that answers what searchers now expect, with something competitors don't offer, such as original data, a worked example, or first hand testing.
7. Search intent shift
Look at what currently ranks for the main query. Are the top results guides, comparisons, tools, product pages, or definitions? An overview article cannot win a query that now returns step by step tutorials, no matter how many keywords you add. If the dominant format changed, the page needs to change format.
Phase 3: Decide on the fix and prioritize
Match each finding to the smallest change that addresses it. This is the difference between updating content and randomly rewriting it.
| Finding | Action |
|---|---|
| Page not indexable or wrong canonical | Fix the technical issue, no content change |
| Two pages competing for one query | Consolidate, redirect, or differentiate |
| Demand fell (Google Trends) | Leave the page alone or broaden the topic |
| AI Overview or SERP feature absorbing clicks | Add a direct answer near the top, target the snippet format |
| CTR low, position stable, no SERP feature | Rewrite title tag and meta description |
| Search intent changed | Rework the page format around the current intent |
| Information outdated | Update only the affected sections |
| Subtopics missing | Add coverage searchers now expect |
| Weak internal linking | Add contextual links from related pages |
| Competitors give better answers | Add original data, examples, or testing |
| Performance stable and accurate | Leave it alone |
Prioritize pages on the edge of page one
On large sites, rank candidates by combining traffic decline, business value, and current position. Pages ranking in positions 5 to 15 for valuable queries usually deliver the best return, because they already have visibility and a focused fix can move them into the top results.
A page with strong historical traffic and a recent decline deserves attention before an old page that never ranked.
Avoid fake freshness
Don't change the published date, dateModified schema, or sitemap lastmod without a substantive update. Search engines can compare page versions, and cosmetic date changes don't earn freshness credit. They also make your own change history harder to trust.
Phase 4: Record a baseline and measure the result
Without a baseline, you can't tell whether an update helped. Before changing anything, record the following, and write each item down so you can compare against it later.
Search performance
Pull the last 3 months from Search Console, filtered to the page.
Record: Clicks, impressions, CTR, average positionKey queries
The 5 to 10 queries that drive most of the page's value.
Record: Position and ranking URL per queryTechnical state
A crawl captures this in one pass.
Record: Title, meta description, H1, canonical, indexabilityContent and links
So you can see exactly what changed later.
Record: Saved copy, internal links in, last meaningful update
A crawl with SiteAuditLint captures the technical side of this baseline in one pass: status codes, indexability, canonicals, headings, metadata, and links.
Change one thing at a time where possible
If you rewrite the title, restructure the content, and add internal links in the same week, you won't know which change worked. When the diagnosis points to several fixes, ship the technical and linking fixes first, then the content changes. This is the discipline behind SEO change management.
Wait before judging
After publishing, request indexing through the URL Inspection tool, then crawl the page again to confirm nothing broke: no new noindex, no changed canonical, no broken links introduced in the edit. Comparing the before and after crawls in SiteAuditLint gives you an evidence trail and catches technical regressions early.
Give rankings 4 to 8 weeks to settle before drawing conclusions. Compare the same metrics you recorded in the baseline, and check year over year again so seasonality doesn't flatter or punish the result. If a core update lands during the measurement window, note it, because it can mask the effect of your change. Tracking this on a schedule is the core of SEO monitoring.
Worked example: a decline that wasn't a content problem
Illustrative example. Replace with a real case and real numbers from your own site before publishing.
A guide to setting up GA4 conversion tracking lost 38% of its clicks year over year. The team's first instinct was a full rewrite.
Detect. Search Console showed impressions down 41% and average position slipping from 4.2 to 9.8 across most queries. Google Trends showed stable demand, and the decline started 3 weeks after a site migration, not after a core update.
Diagnose. A crawl found the guide's canonical tag pointed to an old staging URL left over from the migration. The search engine was treating a different URL as the primary version. A secondary finding: two screenshots showed a GA4 interface that had since changed.
Decide. Fix the canonical first. Replace the two screenshots. No rewrite.
Measure. Six weeks after the fix, position recovered to 4.6 and clicks returned to within 5% of the previous year.
A rewrite would have cost days of work and changed nothing, because the problem was invisible in the content itself. It only appeared when the performance signal was matched against technical evidence from the same time window. For a fuller process, see our guide to SEO debugging.
SEO content update checklist
Before updating a page, confirm the following:
- Clicks or impressions are down 20% or more year over year for 4+ weeks
- Search demand is stable in Google Trends
- The decline doesn't line up with a confirmed core update
- The page is indexable with a correct canonical (use the indexability checklist)
- No other page on the site competes for the same query
- AI Overviews and SERP features are checked for the main query
- Ranking pages still match the page's format and intent
- Facts, screenshots, and recommendations are current
- The page covers the questions searchers now expect
- The page has relevant internal links from strong pages
- A baseline is recorded before any change
If several items point to a real problem, the page is a strong update candidate. If it still performs well, stays accurate, and matches current intent, changing it just because it is old adds risk without benefit.
Frequently asked questions
- How often should I update old content?
- On a signal, not a schedule. Review performance monthly or quarterly, and update a page when the data shows a sustained decline, outdated information, or a change in search intent.
- Does updating the published date help rankings?
- Not on its own. Changing the date without a substantive update doesn't earn freshness credit and makes your change history harder to trust.
- How long until an SEO update shows results?
- Expect 4 to 8 weeks for rankings to settle after the page is recrawled. Technical fixes like a corrected canonical can show effects sooner.
- Should I rewrite a page or create a new one?
- Update the existing URL when it targets the same intent, since it keeps its history and backlinks. Create a new page only when the intent is genuinely different, and avoid creating a second page that competes with the first.
Key takeaway
Start with the signal. Find the cause. Make the smallest change that fixes it. Then measure against the baseline. That turns content updating from a recurring rewriting exercise into a measurable SEO process.
The useful question isn't "is this page old?" It's "what changed, what caused it, and what evidence shows the fix worked?"