How to Update Old Content to Rank and Get Cited in AI Search

Updating old content works when you pick pages that already show a signal in Search Console, replace what is genuinely outdated and only then record the new date. That holds for Google and for AI search (this guide covers the difference between SEO, AEO and GEO). Changing only the date does not help, and it can backfire.

Quick summary

• Prioritize with Search Console: pages with many impressions and a middling position, a recent drop in clicks or expired facts. Pages with zero impressions call for a different decision (merge, redirect or delete).
• The change that counts is the one that changes the answer the reader gets: a direct answer up top, new numbers and sources, current examples, missing questions and internal links.
• AI assistants tend to cite newer content than Google shows, but that is a correlation, and the cited content is still almost 3 years old on average.
• Record the date only when the change is substantial, and use the same value on screen, in structured data and in the sitemap.
• Measure with equal time windows before and after, changing one thing at a time on each page.

How to read this guide

If you are just starting, read the why, what to change and the step-by-step, and save the "For SEO professionals" blocks for later. If you already work in SEO, jump to data-driven selection, technical dates and measurement. GEO and AEO are defined in the glossary.

Does updating old content really help you rank and get cited in AI?

It can help, but the public evidence is correlation, not causation. Two large studies suggest newer content shows up more often as an AI source. Neither proves that updating a page makes AI cite it, and Google asks you not to fake freshness.

The first is from Ahrefs, published on July 28, 2025. It compared the age of nearly 17 million URLs cited by seven sources, including ChatGPT, Perplexity, Gemini, Copilot, AI Overviews and Google organic results. According to the Ahrefs study on freshness and AI citations, content cited by assistants averaged 1,064 days old, versus 1,432 days in Google's organic results (about 25.7% newer). AI Overviews (1,432 days) came out almost identical to organic (1,416 days), with no visible freshness bias.

The second is from SE Ranking. In its study of 129,000 domains, published on November 24, 2025, content updated within the last 3 months was associated with an average of 6.0 ChatGPT citations, versus 3.6 for outdated content. The authors warn that the factors are interdependent and that optimizing one while ignoring the others weakens the effect.

In plain English: think of a restaurant menu. If the prices and dishes are wrong, anyone reading it doubts everything else, whether that is a person or an AI assistant deciding which source is safe to repeat. Updating is fixing the menu, not repainting the front door.

For SEO professionals: both studies are observational. Sites that update content tend to invest more in everything (links, brand, traffic), which muddies the reading. SE Ranking counts citations per domain, not per page, and does not say which ChatGPT version it used. Treat the result as a hypothesis to test on your own pages. Ahrefs itself points out that cited content is still 2.9 years old on average.

Which pages should you update first?

Start with pages that already have proven demand on Google and are close to earning more. Updating a page with no impressions is rewriting in the dark. Search Console gives you these signals in the Performance report.

Signal in Search Console	How to find it	What it usually means	Likely action
Many impressions and low CTR	Performance, Pages tab, sort by impressions and compare CTR	A title or opening that does not persuade	Rewrite the title, description and first paragraph
Average position between 8 and 30	Filter by the page and open the Queries tab	"Almost there" content	Cover missing subtopics and strengthen internal links
Drop in clicks	Compare the last 3 months with the previous period	Outdated information, a better competitor or a shifted intent	Review the Google results and update
Several pages for the same query	Filter by the query and look at the pages	Cannibalization	Merge or differentiate (see keyword cannibalization)
No impressions for months	Pages that do not appear in the report	No demand or not in the index	Decide between indexing, merging, redirecting or deleting
Expired facts	Search the text for years, prices, tool names, laws	Risk of wrong information	Fix before anything else

The 8 to 30 range is a market heuristic, not a Google rule. And the "position" in the report is an average across all of the page's queries, so look at the Queries tab too.

To decide the order, use this score (a suggested method, not an official metric). Give 1 point for each "yes": the page is in the top 20% by impressions; average position is between 8 and 30; clicks have dropped; there is an expired fact; it leads to a sale, signup or contact. Update the 4 and 5 point pages first.

What should you change on an old page?

Change what alters the answer the reader gets, and leave the packaging for last. A good update usually has 4 to 7 of the items below, and it does not need to rewrite the whole text.

1. A direct answer at the top. The first paragraph, at 40 to 70 words, answers the question in the title. It is the easiest passage to cite. The guide to LLM-citable content structure explains how.
2. Facts, numbers and dates. Replace old data with current data and state the verification date ("as of October 2026").
3. Examples and screenshots. A 2023 screenshot on a 2026 page tells the reader the rest may be old too.
4. Missing questions. If Google's results answer something you ignore, add it. AI systems break one question into several searches, which query fan-out explains.
5. An FAQ with real questions, taken from your Search Console queries. The guide to FAQs that AI cites shows the format.
6. Internal links from new posts to the old one and vice versa, plus cleanup of duplicated passages and broken links.

In plain English: renovating a house starts with the leaks and the wiring, not the wall color. Fix what is wrong or missing first, then think about formatting.

For SEO professionals: keep the URL. Changing the address throws away the page's history, and if it is unavoidable, use a 301 redirect and update internal links. Preserve section headings that already rank for real queries, and add sections instead of deleting. The same SE Ranking study found no advantage for FAQ sections (3.8 versus 4.1 citations) or for FAQ schema (3.6 versus 4.2), so use an FAQ because it answers real questions, not as a trick.

How do you record the update date without fooling Google or the reader?

Show the date visibly and use the same value in structured data and in the sitemap, but only update it when the change is substantial. In its helpful content guide, Google asks whether you change page dates to "make them seem fresh" without changing the content, and treats that as a sign of content made for search engines.

Three places need to agree:

• On the page: a clear label such as "Updated October 4, 2026". Google's publication dates documentation recommends a visible date and asks that the visible and structured values match, including the time zone.
• In structured data: datePublished and dateModified in a type such as BlogPosting.
• In the sitemap: the <lastmod> field.

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How Much It Costs to Open a Business in 2026",
  "datePublished": "2024-03-12T09:00:00-03:00",
  "dateModified": "2026-10-04T09:00:00-03:00"
}

Never use a future date, or the date of an event described in the text, in place of the page's date.

In plain English: changing the date without changing the content is swapping the expiration label on a yogurt and leaving the yogurt the same. It works once, until someone opens the package.

For SEO professionals: according to the sitemaps documentation, Google uses lastmod if it is consistent and verifiably correct, and ignores priority and changefreq. Plugins and themes that bump lastmod on every save, or site-wide when you change the footer, burn that trust. Configure it to change only when the main content, structured data or links change. A year update in the footer is not a significant change.

Step-by-step: how to update a page

1. Record the baseline. In Search Console, filter by the page and export clicks, impressions, CTR, position and the top 10 queries for the last 28 days. Write down the date.
2. Compare with the top results. Open the top 5 results for the main query and list what they cover that you do not.
3. List the expired facts (years, prices, rules, screenshots) and rewrite the opening with the direct answer.
4. Cover what is missing, build the FAQ from real queries and review internal and external links.
5. Publish and record the date in the visible label, in dateModified and in lastmod. Then request indexing with Search Console's URL Inspection tool.
6. Schedule the measurement for 4 and 8 weeks later, and do not touch the same page in that interval.

Hypothetical example: the "How to Apply for an EIN" guide from an online bookkeeping firm

The numbers are illustrative, made up to show the reasoning. Imagine an online bookkeeping firm with a 2023 post, "How to Apply for an EIN: Step by Step". Over 90 days, it has 9,000 impressions, an average position of 14 and a CTR of 0.7%. The answer only appears in the fourth paragraph, the text cites a form version from a previous year and the screenshots show a portal that has changed.

Problem found	Change	How to measure
Answer in the fourth paragraph	A 55-word opening with the steps summarized	Page CTR
Outdated form version	Current version, with an official source and verification date	Question-type queries start to be answered
Old screenshots	New screenshots, with a dated caption	Time on page, if available
Missing questions	An FAQ with 5 real Search Console queries	Impressions for the new queries
No internal links	Links from 3 new posts to this guide	Average position

Set the criterion before looking at the numbers ("if position does not improve in 8 weeks, we review the search intent"). Deciding afterward is bias. If position improved and CTR did not, the problem is the title and description.

How often should you review content?

It depends on how fast the subject changes, and there is no official frequency. The pace below is a starting point to adjust with your own site's data.

Page type	Suggested pace
Prices, laws, rules, tool versions	Whenever they change, with a monthly check
Evergreen guides	Every 6 to 12 months, or when clicks drop
Highest-revenue pages	Quarterly review
Dated content ("best of 2024")	At the turn of the year, title and body together

Each review should have a reason (expired data, a drop, a new question), not a mechanical schedule. More on the industry in the SEO trends for 2026.

Common mistakes: changing only the date; rewriting everything and losing sections that already rank; changing the URL without a 301; padding with generic text; updating 50 pages at once and not knowing what worked; using AI to draft and not checking every number.

How do you measure whether the update worked?

Compare periods of equal length and equal mix of weekdays, filtering by the page in Search Console. Wait for Google to recrawl before concluding: 4 to 8 weeks is a practical window, not a Google deadline. Account for seasonality and algorithm updates.

For AI search, there are two paths. The first is Search Console's generative AI performance report which, according to Google's documentation checked in October 2026, shows only impressions in features such as AI Overviews and AI Mode and has been released to all sites, though sites with few impressions in those features may not see it. The second is manual: ask ChatGPT 5 to 10 questions before and after, note the date and repeat each one a few times, because answers vary.

To automate part of this, Contentor has the Results page, with Search Console data per project, and AI Visibility, which tracks whether ChatGPT cites your brand for the questions you choose (ChatGPT only).

Frequently asked questions

Does changing the publish date improve rankings?

No. Google advises showing a new date only when the content changed significantly, and it questions anyone who alters dates to look fresh. Changing the date without changing the content also misleads the reader. Update the text first and record the date afterward.

Do I need to keep the same URL when updating a post?

In most cases, yes. The URL accumulates link and performance history, and changing it is a risk with no gain. If you must change it, use a 301 redirect from the old to the new URL, update internal links and monitor Search Console for a few weeks.

How long does it take to see the effect of an update?

It depends on Google's crawling and on how competitive the query is. Evaluate at 4 and 8 weeks, with the same window before and after. On highly contested queries it can take longer, and nothing guarantees the effect. See how long SEO takes.

Is it better to update old posts or write new ones?

If the site already has posts with impressions and a middling position, updating is usually cheaper and faster than writing from scratch. New posts make sense for topics not yet covered. Reserve part of the calendar for reviewing the pages Search Console flags and the rest for new topics with proven demand.

Does updating content guarantee that AI will cite me?

No. The studies show a correlation between recent content and citations, but no one outside the AI companies knows how sources are chosen. Updating keeps the page useful and correct, which is a prerequisite, not a guarantee. Measure with fixed questions, before and after, and treat any gain as an indication, not proof.

Next step

After updating your pages, the next step is making sure each answer is written in a way AI can extract: see the structure of LLM-citable content. Pick 3 pages using the score in the selection section, update them and measure at 8 weeks.

Read also:

• Keyword cannibalization: how to find and fix it
• Google Search Console: a beginner's guide
• SEO trends in 2026