Skip to content
Chalk Labs / AI SEO
How-to guide

How to Refresh Old Blog Posts for AI Search Freshness

By Rahil Jain, founder of Chalk LabsUpdated How we research

The short answer

To refresh old posts for AI search, pick pages whose facts have changed, make real improvements (new sourced numbers, a worked example, an answer-first intro), then update the visible date, the dateModified markup and the sitemap lastmod to match. Never change dates without changing the content, which Google warns against 52.

  • An Ahrefs study of about 17 million cited URLs found AI assistants cite content 25.7% newer by publication age than Google's organic results 1.
  • The same study found the average AI-cited page is still about 2.9 years old, so old pages can win 1.
  • Google warns against changing page dates to make content seem fresh when it has not substantially changed 5.
  • Keep the URL and your best answer passages when you update. Changing them can remove what was earning citations.

What does fresh mean for AI search?

Fresh means the page is accurate today, and visibly so. It has three parts: the content is current, the date a reader sees is honest, and the machine-readable dates (markup and sitemap) say the same. Microsoft describes the content that does well in AI answers as fresh, authoritative, structured and semantically clear 7.

It does not mean newly dated. A page with a 2026 date and 2023 facts is stale and slightly deceptive. A page with a 2023 date and facts that are still right is fine.

Do it step by step

0 of 8 done0%

  1. Export your posts into a sheet with URL, publication date, last meaningful update, impressions and enquiries. Add a column for whether AI tools cite it.

  2. Mark each post as update now, expand, merge, remove or leave alone. Choose the first five from the update-now group.

    Tip: Start with posts that contain prices, laws, product features or statistics. They go stale fastest.

  3. Open each statistic and claim and confirm it against a named, dated source. Replace the weak ones. Remove anything you cannot source.

  4. Put the direct answer in the first two sentences. Add a worked example, a table or a decision rule that other pages lack.

    Tip: Keep the original URL and any heading that already earns traffic.

  5. Show Published and Last updated dates plus a one-line note on what changed. Set dateModified in markup to match the visible date.

  6. Set lastmod for the URL to the real update time. Do not touch lastmod for pages you did not change.

  7. If you want faster recrawling in Bing and other IndexNow engines, submit the changed URLs with the IndexNow template. Resubmit the sitemap in your search tools.

  8. Re-run your tracking prompts in fresh chats and record citations, impressions and enquiries against the starting state.

Your ticks are saved in this browser only.

Copy-ready templates

Visible dates and update note

html
<p class="byline">By <a href="/about/priya-sharma">Priya Sharma</a>.
  Published <time datetime="2024-02-12">12 February 2024</time>.
  Last updated <time datetime="2026-10-20">20 October 2026</time>.</p>
<aside class="update-note">
  <strong>What changed on 20 October 2026:</strong> replaced the 2023 fee table
  with current prices, added a worked example and removed a provider that has closed.
</aside>

Placeholder name and dates. Write the note in plain words about what is different, not 'updated for freshness'.

Article JSON-LD with matching dates

json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to choose a payroll provider",
  "datePublished": "2024-02-12",
  "dateModified": "2026-10-20",
  "author": [
    {
      "@type": "Person",
      "name": "Priya Sharma",
      "url": "https://www.example.com/about/priya-sharma"
    }
  ]
}

datePublished and dateModified must match the dates readers can see. Change dateModified only when the content really changes.

Sitemap entry with an accurate lastmod

text
<url>
  <loc>https://www.example.com/guides/choose-a-payroll-provider</loc>
  <lastmod>2026-10-20T09:30:00+05:30</lastmod>
</url>

Use ISO 8601. Set lastmod to when the page last changed, not to when the sitemap was built.

IndexNow submission (Bing and other participating engines)

bash
# Replace ENGINE_HOST with the endpoint host of a participating search engine
# (see indexnow.org/documentation), and KEY with your own key.
ENGINE_HOST="engine.example"
KEY="your-key-here"
curl -X POST "https://$ENGINE_HOST/indexnow" \
  -H "Content-Type: application/json; charset=utf-8" \
  -d '{
    "host": "www.example.com",
    "key": "'"$KEY"'",
    "keyLocation": "https://www.example.com/'"$KEY"'.txt",
    "urlList": [
      "https://www.example.com/guides/choose-a-payroll-provider"
    ]
  }'

Host a text file named after your key at your site root first. Get the real endpoint from the IndexNow documentation. A 200 response means received, not indexed. Google is not listed as a participant in the IndexNow documentation.

Refresh checklist

markdown
- [ ] Every number has a named, dated source
- [ ] Dead links fixed, old screenshots replaced
- [ ] First two sentences answer the question
- [ ] One new original element added (example, table or rule)
- [ ] Visible 'Last updated' date and change note added
- [ ] dateModified in markup matches the visible date
- [ ] Sitemap lastmod updated for this URL only
- [ ] URL unchanged, best headings kept
- [ ] Tracking prompts logged before and after

Tick every line before you change a date.

Do AI assistants really prefer newer content?

A little, and not equally. Ahrefs analysed about 16.975 million URLs cited in its Brand Radar data. Pages cited by AI assistants averaged 1,064 days since publication against 1,432 days for Google's organic results, which is 25.7% newer. On days since last update the gap was smaller, 13.1% 1.

The caveats matter more than the headline. The average AI-cited page was still about 2.9 years old, and Ahrefs says Google is the least influenced by freshness. It also says frequent updates to low-quality content will not help much, and that Google's John Mueller warned against changing dates without changing content 1. This is a correlation from one vendor's data, not proof that updating causes citations. Ahrefs's own tables show slightly different organic averages in places, so treat the exact percentage as approximate.

25.7%newer by publication age: pages cited by AI assistants versus Google organic results, in an Ahrefs study of about 17 million cited URLs1

What do you need, and how long does it take?

You need a list of your posts with publication dates, your traffic or impression data, access to edit pages and the sitemap, and one person who knows the subject. A thorough refresh of one post takes one to three hours; that is our estimate. Plan a batch of five to ten posts a month, not a mass update.

Which old posts are worth refreshing?

Refresh the posts where an update changes the answer. Rank them by value: pages that still earn impressions or enquiries, pages that cover a topic where facts, prices or rules change, and pages that AI tools already cite for your brand. The Generative AI performance report in Google Search Console shows impressions in AI Overviews and AI Mode by page, which helps you spot those 9.

Then apply this decision rule to each post.

Triage rule for an old post
What you findWhat to do
Facts, prices or rules are now wrongUpdate first. Highest priority.
Facts are right but the page is thin or buries the answerExpand it and rewrite the intro to answer first.
Two posts answer the same questionMerge into the stronger one and 301 redirect the other.
Topic is obsolete and gets no trafficRemove or redirect it to the closest useful page.
Facts are still right and the page performsLeave it alone.

What counts as a real update?

A real update changes what a reader learns. Replace old numbers with current ones from a named source. Delete claims you can no longer back up. Add a worked example, a table or a decision rule. Rewrite the first two sentences so the answer comes first, as in how to write answer-first intros. Fix dead links and outdated screenshots.

Google's helpful content guidance lists changing page dates to seem fresh when content has not substantially changed as a warning sign. It lists adding or removing content mainly to look fresh in the same way 5. So tell the reader what changed, as in the template below.

How should you handle dates on the page?

Show a clear, labelled date. Google advises a user-visible date such as 'Published' or 'Last updated', dateModified in Article markup, and consistency between the two. It also says dates should reflect when the page was published or updated, not events it describes, and should never be in the future 2.

Change the modified date only when the content meaningfully changes. Fixing a typo is not a reason. Keep the original publication date visible too, because it tells readers how long you have covered the topic.

How do you get the update noticed?

Update the lastmod value in your sitemap for that URL. Google says it uses lastmod when it is consistently and verifiably accurate and ignores priority and changefreq 3. Bing calls lastmod a key signal for prioritising recrawls and warns against setting it to the time the sitemap was generated unless the page changed 4.

For Bing and other participating engines, IndexNow lets you ping them when a URL is updated, and one post can carry up to 10,000 URLs 6. The IndexNow documentation does not list Google as a participant, so do not rely on it for Google; use your sitemap and Search Console there 6. A 200 response means received, not indexed 6. No tool can promise when or how content appears in AI answers 4.

What can go wrong when you refresh?

The main risk is damaging a page that works. Do not change the URL. Keep the headings and the answer passages that earn citations unless they are wrong. Do not stuff in new keywords or bulk-edit dozens of pages with the same sentence.

Also avoid creating near-copies. Bing says models group near-duplicate URLs and pick one to represent the set, which may be an outdated version 8. If you rewrite a post heavily, redirect the old copy rather than leaving both live.

How do you check the refresh worked?

Record the date and the starting state before you edit: impressions, enquiries, and whether the page is cited when you ask your ten tracking prompts. Re-run the same prompts four and eight weeks later in fresh chats, and compare. Answers vary between runs, so look for a pattern across several prompts.

Do not expect an overnight change. We found no reliable data on how quickly a refresh shows up in AI answers. Use how to test whether your changes worked to set up a fair before-and-after.

When should you not touch an old page?

Leave a page alone if its facts are still right, it ranks and converts, and nobody has asked a question it does not answer. Ahrefs suggests new, high-quality content may often beat frequent updating of the same resources 1. Put your time into the page that does not exist yet.

Frequently asked questions

How often should I update my blog posts for AI search?

Update when the facts change, not on a calendar. Review pages with prices, laws or statistics every six to twelve months, and leave stable explainers alone. For example, re-check pricing and law pages when the underlying fees or rules change, and at least once a year. That schedule is our judgement, because no source gives a correct interval. Ahrefs found AI-cited pages average about 2.9 years old 1.

Is it okay to just change the date to look recent?

No. Google's guidance names changing the date of pages to make them seem fresh, without substantial change, as a warning sign 5. It can also mislead readers. Change the date only after you have improved the content, and show what changed.

Does updating old content make ChatGPT cite it?

We found no study showing that an update causes a citation. Ahrefs found AI assistants cite newer pages more often on average, but it is a correlation, and frequent updates to weak content will not help much 1. Update to make the page right, then measure.

Should I update the sitemap lastmod for every refresh?

Yes, but only for pages that really changed. Google uses lastmod when it is consistently and verifiably accurate 3, and Bing warns against setting it to the sitemap build time unless the page changed 4. A wrong lastmod teaches crawlers to ignore it.

About the author

Rahil Jain

Rahil Jain is an AI SEO (answer engine and generative engine optimisation) consultant and co-founder of Chalk Labs.

LinkedIn · Method and credentials

Sources

  1. AI assistants and content freshness: a study of cited URLs (Ahrefs Brand Radar data) · AhrefsOpened October 20, 2026. Supports: About 16.975 million cited URLs; AI assistants average 1,064 days since publication vs 1,432 for organic results (25.7% fresher) and 13.1% fresher by last update; average cited page about 2.9 years old; caveats on Google, low-quality updates and changed dates. Published 28 July 2025.
  2. Influence your byline date in Google Search · Google Search CentralOpened October 20, 2026. Supports: Show a labelled visible date; use datePublished and dateModified; keep them consistent; dates reflect publish or update time, not future dates. Page last updated 2025-12-10.
  3. Build and submit a sitemap · Google Search CentralOpened October 20, 2026. Supports: Google uses lastmod if consistently and verifiably accurate; ignores priority and changefreq. Page last updated 2026-07-08.
  4. Keeping Content Discoverable with Sitemaps in AI Powered Search · Microsoft Bing Webmaster BlogOpened October 20, 2026. Supports: lastmod is a key signal for recrawls; do not set it to sitemap generation time unless the page changed; no tool can guarantee when content appears in AI answers. Post dated 31 July 2025.
  5. Creating helpful, reliable, people-first content · Google Search CentralOpened October 20, 2026. Supports: Warning signs: changing page dates to seem fresh without substantial change; adding or removing content mainly to seem fresh. Page last updated 2026-10-05.
  6. IndexNow documentation · IndexNow.orgOpened October 20, 2026. Supports: Protocol to notify engines when URLs are added, updated or deleted; up to 10,000 URLs per POST; key file at site root; HTTP 200 means received, not indexed; Google is not mentioned as a participant.
  7. Optimizing Your Content for Inclusion in AI Search Answers · Microsoft Advertising (Bing)Opened October 20, 2026. Supports: Success depends on content that is fresh, authoritative, structured and semantically clear. Post dated 8 October 2025.
  8. Does Duplicate Content Hurt SEO and AI Search Visibility? · Microsoft Bing Webmaster BlogOpened October 20, 2026. Supports: LLMs group near-duplicate URLs into a cluster and choose one page, possibly an outdated version. Post dated 19 December 2025.
  9. Generative AI performance report · Google Search Console HelpOpened October 20, 2026. Supports: Report shows impressions in AI Overviews and AI Mode by page, country, date and device; rolled out to all websites as of 31 August 2026.
How this page was made. Built on Rahil Jain's AI SEO method and drafted with AI research assistance. Every statistic links to the page we read it on (opened October 20, 2026 or nearby). Published October 20, 2026; last updated October 20, 2026. Chalk Labs sells AI SEO services, so we have a commercial interest in this topic. Spotted an error? Tell us and we will fix it.