Guide · Practitioner
Content Refresh Playbook for AI Search
Refresh pages by checking every fact and source, updating the direct answer and evidence, merging overlapping pages, and showing an honest "last updated" date only after substantive changes. Google asks whether sites change dates to make pages seem fresh when content hasn't substantially changed (Google), and recommends a visible, clearly labelled date (Google). Stale facts on your own pages can end up repeated in AI answers.
Facts are from Google Search Central, accessed 30 Oct 2026. Recommendations marked "our view" are interpretation.
On this page
- Why does refreshing matter for AI search?
- How do you choose pages to refresh?
- What's the refresh checklist?
- What counts as a substantive update?
- How do you handle merging pages?
- How do you handle discontinued products or features?
- What's a worked example?
- How long until engines reflect changes?
- How do you measure refresh results?
- How do you run refreshes as a programme?
- Which pitfalls should you watch for?
- How do you find every page that repeats a fact?
- Should you delete lots of old content to look fresh?
- Checklist
- From MentionX data: why freshness matters more in some engines
- Worked example: Ledgerline refreshes its invoice-matching guide
- What signals say a page is out of date?
- How do you set a refresh schedule?
- How do you show readers what changed?
- How do you coordinate refreshes with product releases?
- How do you refresh pages you can't fully rewrite?
- What tools help with refreshes?
- How do you report on the programme?
- What should you do with pages that no longer fit?
- Common questions
- Related
- Sources
Checked on 31 October 2026. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.
Why does refreshing matter for AI search?
Our view: engines that ground answers in web pages can repeat whatever your page says, including last year's price, a discontinued feature or a changed regulation. A refresh programme keeps the facts engines retrieve about you accurate. It also keeps pages useful for readers, which is the basis of Google's guidance (Google).
How do you choose pages to refresh?
| Signal | Why it matters |
|---|---|
| Contains prices, plans or limits | Facts change often |
| Covers regulation or standards | Rules change |
| Falling clicks in Search Console (Google) | Possibly outdated or outcompeted |
| Wrong AI answers in prompt tests | Engines may be using stale info |
| High business value | Worth the effort |
| Overlaps another page | Candidate for merging |
Our view: score pages on these and work through the top of the list each month.
What's the refresh checklist?
- Facts: check every claim, price, limit and date against the current source.
- Sources: open every link; replace dead or superseded sources with primary ones.
- Answer: rewrite the opening if the answer has changed.
- Evidence: add new data, examples or screenshots you've gathered.
- Gaps: add answers to new follow-up questions readers ask.
- Structure: convert dense paragraphs to tables or lists where useful.
- Overlap: merge with similar pages if needed.
- Images: update screenshots; check alt text (Google).
- Review: subject expert checks accuracy.
- Date: update "last updated" only if changes are substantive.
What counts as a substantive update?
Our view: new or corrected facts, new sections answering real questions, new evidence, or a rewritten answer. Fixing a typo or swapping a stock image isn't. Google estimates when a page was published or significantly updated from several signals, and recommends labelling dates as "Published" or "Last updated" (Google).
How do you handle merging pages?
When two pages compete for the same question, combine the best of both into one, keep the stronger URL, and permanently redirect the other (Google). Update internal links to point to the surviving page. Our view: merging often helps more than writing a third page on the same topic.
How do you handle discontinued products or features?
Don't silently delete pages that people and engines rely on. Update the page with a clear notice, the end date and the replacement, or redirect to the replacement. Our view: a clear "this plan was retired on [date]" helps engines answer accurately instead of repeating old details.
What's a worked example?
Fictional example: a SaaS company's prompt tests show engines quoting an old €29 price. The pricing guide still lists €29 in a table from 2025. The refresh updates the table with an as-of date, rewrites the opening, adds a section on the new plan, updates screenshots, merges an older "plans compared" post with a redirect, and sets "Last updated" after expert review. Prompt tests are repeated monthly.
How long until engines reflect changes?
There's no fixed time. Pages must be recrawled, and engines refresh their indexes on their own schedules. Our view: request indexing for important pages in Search Console's URL Inspection tool, then re-test over the following weeks, recording dates.
How do you measure refresh results?
| Metric | Source |
|---|---|
| Clicks and impressions | Search Console (Google) |
| Answer accuracy | Monthly prompt tests |
| Citations of the page | Prompt tests |
| Conversions | Analytics |
Compare periods of similar length and note other changes that could explain differences.
How do you run refreshes as a programme?
Our view: give each important page an owner and a review date, keep a refresh log (what changed, when, who reviewed), and review the backlog monthly. Small, regular refreshes beat occasional large rewrites.
Which pitfalls should you watch for?
- Updating dates without content changes
- Changing URLs without redirects
- Removing useful historical context
- Refreshing low-value pages while high-value ones go stale
- Forgetting related pages that repeat the old fact
How do you find every page that repeats a fact?
Our view: keep a single source of truth for key facts such as prices, limits and plan names, and search your site for the old value whenever it changes. A site search or crawl export makes it easy to find blog posts, FAQs and docs that still quote the outdated number.
Should you delete lots of old content to look fresh?
No. Google's helpful content guidance asks whether you're adding or removing a lot of content primarily because you believe it will make your site seem "fresh", and answers that it won't help (Google). Our view: remove or merge pages because they're unhelpful or duplicated for readers, not as a ranking tactic, and redirect where there's a relevant replacement.
Checklist
- Pages scored and prioritised
- Facts and sources checked
- Opening answer updated
- Overlaps merged with redirects
- Expert review done
- Honest "last updated" date
- Results logged
From MentionX data: why freshness matters more in some engines
Method. Read-only aggregate queries over MentionX scans from 22 August to 29 October 2026 (UTC): 2,217 engine runs (2,154 completed) across 18 anonymised projects and six engines.
Engines differ in how often they cite sources at all. Engines that cite often rely heavily on live retrieval, which means current pages matter:
| Engine | Brand mentioned | Answers with no citations |
|---|---|---|
| Gemini | 47.3% | 50.7% |
| OpenAI | 42.9% | 30.2% |
| Perplexity | 31.5% | 4.1% |
| AI Mode | 31.3% | 12.6% |
| Copilot | 26.0% | 47.0% |
| DeepSeek | 24.0% | 99.0% |
Articles are the URL type cited most often in the sample, so they are a natural focus for refreshes:
| Cited URL type | Share of 9,750 citations |
|---|---|
| Blog or article | 19.6% |
| Homepage | 10.0% |
| Review page | 2.7% |
| Docs | 2.6% |
| Pricing | 1.9% |
| Wikipedia | 1.6% |
Our view: prioritise refreshes for pages targeted at engines that cite often, and for articles and commercial pages that appear in answers. Engines that rarely cite rely more on what they already know, and refreshes take longer to show there.
Limits. A convenience sample of mostly B2B software projects, run through engine APIs, which can behave differently from the consumer apps. Perplexity, Copilot and DeepSeek figures come from a single day (26 October 2026), so treat them as a snapshot, not a trend.
Worked example: Ledgerline refreshes its invoice-matching guide
Ledgerline is a fictional accounts-payable tool. Figures are illustrative.
Ledgerline's guide to three-way invoice matching was written two years ago. Screenshots show an old interface, one feature has been renamed and the pricing section mentions a plan that no longer exists.
The content team updates screenshots, corrects the feature name throughout, removes the old plan and adds a short section on a matching option released this year. They check every page that repeats the old feature name and fix those too. The visible "last updated" date changes only because the content changed. A short note at the top of the page explains what was updated.
The team adds the guide to a quarterly review list, with the product manager for invoice matching as the owner of its facts.
What signals say a page is out of date?
Look for old screenshots, renamed features, removed plans, broken links, references to past years and advice that no longer matches your product. Check support tickets and sales notes for questions the page fails to answer. Run the page's target prompts and note whether AI answers repeat old facts that came from it. Each of these is a reason to put the page on the refresh list.
How do you set a refresh schedule?
Group pages by how quickly their facts change. Pricing, feature and comparison pages change often and need checking every quarter or after each release. Guides and explainers usually need checking twice a year. Evergreen definitions may need only a yearly check. Put the schedule in a shared calendar with a named owner for each page.
How do you show readers what changed?
Add a short update note near the top, stating what changed and when. Keep the published date and the updated date separate where your CMS allows. Don't change the date without changing the content, because readers and engines can see that nothing new was added.
How do you coordinate refreshes with product releases?
Ask product and marketing teams to share release notes before launch. Build a list of pages affected by each release and update them on launch day or soon after. Assign each release a content owner who checks the list is complete.
How do you refresh pages you can't fully rewrite?
Sometimes there isn't time for a full rewrite. Fix the facts first: names, prices, screenshots and links. Then update the opening so it gives a current direct answer. Add the page to the full-rewrite list if the structure also needs work.
What tools help with refreshes?
A spreadsheet of pages, owners, last checked dates and next check dates is enough for most teams. Site crawlers can find broken links and old terms. Your CMS may support scheduled reminders. Keep the tooling simple so the programme keeps running.
How do you report on the programme?
Report the number of pages refreshed, the pages overdue and any changes in citations for refreshed pages' target prompts. Note big fixes, such as wrong prices removed. Our view: a short monthly update keeps the programme visible and protects time for it.
What should you do with pages that no longer fit?
Some pages cover products, features or advice you no longer support. If a newer page covers the topic, merge the useful parts and redirect. If nothing replaces it, update the page to explain what changed and point readers to the current option, or remove it and redirect to the closest relevant page. Don't leave outdated pages live without a note, because engines may keep citing them.
Common questions
Does changing the date help? Not on its own; engines and readers look for real changes.
How often should I refresh? It depends on how quickly the facts change; quarterly for fast-changing pages is a common starting point.
Should I refresh or rewrite? Refresh when the structure works but the facts are old; rewrite when the page doesn't answer the right questions.
Related
Sources
- Google, Creating helpful content; Influence your byline dates; Redirects; Image SEO; Performance report
All accessed 30 Oct 2026.
Questions
How often should content be refreshed?
It depends on how fast the topic changes. Pricing, product and regulatory pages may need checks monthly or quarterly; stable explainers maybe yearly. Set a review date per page.
Can I just update the date?
No. Google's helpful content guidance asks whether you're changing dates to make pages seem fresh when content hasn't substantially changed. Update the date only after a real update.
Should I merge or delete old pages?
Merge overlapping pages into the strongest one and redirect the others. Delete only pages with no value, and redirect where there's a relevant replacement.