When to update an old article: 4 signs in Search Console, and 3 to ignore

One of your articles slipped a few positions in Search Console. Should you rewrite it, refresh it, or leave it alone? Often the right answer is to leave it alone. An update can't fix a problem the page doesn't have, and it can break what already works.

This post lists the Search Console signs that tell you when to update, and the ones to ignore. They come from SEOs who test this for a living, like David Quaid and Charles Floate. You'll also see how long to wait before you judge an update.

3 signs to ignore

1. A drop that's only days old

Google tests pages. For one search, it moves a few pages up and down for a while, sometimes for weeks, and watches which one people click. If your page went from 4 to 7 on Tuesday, it may be in the middle of such a test.

Rankings also move more than they used to. In one study of 8.1 million local search results, nearly half got more volatile during the May 2026 core update and stayed that way. So wait until a drop has lasted several weeks before you do anything.

2. The article is old

Age alone isn't a reason to update. A two-year-old page that still gets clicks is doing its job.

Bumping the date doesn't help either. Google checks whether a page really changed. If your sitemap keeps marking unchanged pages as updated (the lastmod date), Google stops trusting those dates. On mid-authority sites, David Quaid says, it can also slow down how fast your new pages get indexed.

3. Your whole site is down

Average CTR and average position for a whole site tell you very little. One page that loses a big search can pull the total down while every other page is fine. Check one page at a time, with the searches it ranks for. Otherwise you'll rewrite pages that were never the problem.

4 signs to update

1. Same position, fewer clicks: change the title

If the page ranks where it did but fewer people click, start with the title. Searchers see it before they ever see your article.

Compare the click rate of each search the page shows up for. If one gets 0.2% and a similar search gets 40%, the title promises that searcher something the page doesn't give. Change the title and leave the article as it is. Google often moves a retitled page higher for a while to test it, so you'll know soon whether the new title works.

2. It ranks for searches it doesn't answer

Filter Search Console to the page and read its searches. If the biggest ones ask something the page barely covers, people want something other than what you wrote.

Then search the main keyword yourself. Were the results guides, and are they now product pages or tools? Then new wording won't fix it. The page has to become that kind of page.

Charles Floate says this is the most common cause of lost traffic he finds in audits. In one case he shared, a services page got a refresh of two paragraphs, its images and its metadata. It went from 22 to about 5,000 visits a month, by Ahrefs' estimate.

3. The facts changed

Did a price, an API or a Google policy on the page change? Then update it, whatever the traffic does. Readers who find old information go back to Google and click something else, and Google counts that.

4. Two of your pages compete for one search

Filter Search Console on a search and see which of your pages get its impressions. Two URLs that take turns are competing. So is a page whose position chart has gaps where the other page took over.

Google usually shows one page per site for a search. The other page drops out, without a penalty you'd notice. Pick the stronger page, merge the other one into it, and 301 redirect the old URL.

When a rewrite won't help

Some pages never take off. Before you rewrite one, look up the best position it ever reached for its keyword.

Did it reach page one or two, but nobody clicked? Then the content doesn't match what people want, and a rewrite can fix that. Did it never get past position 50? Then your site doesn't have the authority for that keyword yet. Pick an easier keyword instead.

If you update, change as little as you can

A light refresh usually beats a full rewrite. Keep the URL and the parts that work. Fix what's out of date, add what's missing, and leave the rest alone.

Even small edits can move rankings. Putting the headings in a different order can change which searches Google shows the page for.

How long to wait, and what to compare

Give it several weeks, not days. Google has to crawl the page again, and it usually tests it in a few positions before it settles. It mostly recrawls pages that people click in its own results. So a page with little search traffic takes longer, and sharing it on social media won't speed that up.

Then compare equal periods. Search Console can put the 28 days after the update next to the 28 days before. That's fine for a first look, but seasons can make a bad update look good.

The fair test compares the months after the update with the same months a year earlier. Later, you compare the full year after with the full year before. That takes 24 months of data, and Search Console only keeps 16. Save a page's history before you change it. Otherwise the "before" is gone by the time you want to judge the result.

If your Search Console data is connected to Claude over MCP, each of these checks takes one prompt per page. And if the title turns out to be the problem, start with the four places a keyword has to appear.