Google Just Explained Why Fake Content Refreshes Don't Work Anymore
Google Just Explained Why Fake Content Refreshes Don't Work Anymore
Google's Gary Illyes said this month that if your lastmod dates are wrong, you're better off removing them entirely. Around the same week, John Mueller explained on Google's own podcast that thin, generic content is a top reason pages get crawled but never indexed. Two different topics, one shared lesson: Google checks your freshness claims instead of taking them at face value.
If you've ever bumped a publish date without changing much on the page, this is worth reading closely.
What Google Said About Lastmod Dates
A site owner asked Illyes a fair question on Bluesky: what if your lastmod dates are wrong because of a bug, not because anyone's trying to game anything?
His answer was blunt. Remove them. "Probably better off without the lastmods," he wrote. "At least you save a few bytes."
Google has said versions of this for years. Lastmod is a binary trust signal. Prove your dates are accurate and Google uses them.
Get caught faking or fumbling them and Google ignores the field entirely, including the honest updates buried in there.
An inaccurate freshness signal isn't neutral. It's worse than having no signal at all.
What Google Said About Thin AI Content
That same week, John Mueller and Martin Splitt talked through the "crawled - currently not indexed" status on Google's Search Off the Record podcast.
Mueller's explanation was simple. When Google's systems have real concerns about a site's overall quality, they crawl less of it and index less of it. Pages sit visited but untrusted, parked in limbo indefinitely.
He named AI-generated content as one driver of that pattern. His framing mattered more than the label did.
Generic pages were the real problem, not the tool that made them easy to produce. Anyone could have written them, and they said nothing a reader couldn't already find on ten other results.
"Anyone could have written this. This tells me nothing," is how he put it.
The Pattern Behind Both Statements
Line these two stories up and the connection is hard to miss.
A publish date is a promise: this page changed, come check it again. Lastmod fails when the promise doesn't match reality.
A refreshed article makes the same promise at a bigger scale. Update the date without updating the substance and you've made the exact same mistake Illyes described, just one level up from the sitemap.
Google is auditing both promises now, and saying so in public.
What This Means for Your Refresh Process
Only touch lastmod when something actually changed
If your CMS bumps the modified date on every save, including a comma fix, turn that off. A date that moves for cosmetic edits is precisely the pattern Google said it stops trusting.
Save date changes for updates a returning reader would notice. New data, a rewritten section, an updated recommendation.
Run the stranger test before you republish
Read the refreshed page as someone who's never seen your site. Does it say anything the last five competing results didn't already say?
If not, you added a date and nothing else. That's the same failure Mueller flagged, just dressed up as a refresh.
Add something only you could add
The fastest way to pass that test is specificity. A number pulled from your own traffic, a mistake you made and how you fixed it, a screenshot of your actual process.
Generic advice makes a page interchangeable with a thousand others. Specific experience is what makes it worth an index slot.
Rebuild trust in a pattern, not a single post
One strong refresh won't flip Google's read on a site that's been coasting on cosmetic updates. Trust here builds the same way lastmod trust builds, through a consistent pattern over time.
Keep doing real refreshes on a schedule. The signal breaks fast and recovers slow.
Audit Your Last Five "Refreshed" Posts Today
Pull up the five most recent posts you refreshed. For each one, ask what specifically changed besides the date.
If you can't answer that in one sentence, the post has the lastmod problem. It's making a claim the page itself can't back up.
This costs nothing and takes twenty minutes, and it predicts ranking recovery better than most tools do.
FAQ
Should I remove lastmod dates from my sitemap? Only if you can't guarantee they're accurate. If your CMS updates them correctly, and only for meaningful changes, keep them. An honest lastmod date is a real trust signal.
Does Google penalize AI-generated content specifically? No. Google has repeatedly said it doesn't penalize content based on how it was produced. The problem is generic, interchangeable writing, which AI tools make easy to produce at scale but isn't unique to them.
How do I know if a refresh was substantive enough? Ask whether a returning reader would notice a real difference from the old version. New data, a corrected error, or an added section counts. A reworded intro doesn't.
How long does it take to rebuild trust after a run of cosmetic updates? Google hasn't given a number, and it likely varies by site. Treat it like E-E-A-T generally. Consistent, real improvements over months, not one fix.
Stop Guessing Which Refreshes Are Actually Working
Telling a real refresh apart from a cosmetic date bump gets hard to track by hand once your archive grows past a few dozen posts. SEORefresher flags that gap directly and helps you prioritize which pages still need substantive work instead of another date change. Start finding out at seorefresher.com.