The diagnostic test is straightforward: pull the pages that overtook yours in the SERP, check whether they show a recently changed publish or modified date, and then actually read the content that changed rather than stopping at the date. If competitors display a new date but the substance of the page (claims, data, structure, depth) is materially the same as before, freshness is very unlikely to be the explanation for their gain, no matter how convenient that explanation might be, and the decline needs to be attributed to something else, most often link changes, broader relevance/quality shifts, or a change in how Google is interpreting the query’s intent. Google has said directly, including in comments from John Mueller in Search Central discussions and office-hours contexts, that changing a displayed date without making genuine content updates doesn’t earn a freshness benefit, and that its systems attempt to assess whether the actual content has meaningfully changed rather than just trusting a timestamp. This means the diagnostic can’t stop at “did the date change,” it has to continue to “did the content change enough to plausibly explain why a freshness-sensitive query would now prefer this page.”
Building the actual diagnostic
Start by confirming the query genuinely behaves as freshness-sensitive in the first place. Not every evergreen-seeming query has a freshness component to its intent; Google’s systems apply what’s often described as query deserves freshness weighting selectively, more strongly for queries tied to recurring events, rapidly evolving topics, or things users implicitly expect to be current (best practices that change, pricing, statistics, product comparisons, anything with a “current year” framing). A query that’s evergreen in the sense of stable, unchanging information (how a mechanism works, a definitional question, a historical fact) is much less likely to have freshness acting as a meaningful ranking factor at all, so if the query is in that category, freshness is probably not the right hypothesis regardless of what competitors did to their dates.
Assuming the query does plausibly carry a freshness component, pull the current top-ranking pages that displaced yours and check three things in order. First, the visible date: is there a publish date, modified date, or both, and does either fall in a window that plausibly correlates with the ranking change (use a rank tracker’s historical data or manual SERP checks to establish roughly when the shift happened, then compare). Second, use a page-diff tool (the Wayback Machine’s snapshot comparison, a change-detection service, or your own historical crawl data if you have it) to see what actually changed in the competitor’s content between the old and new version. Third, assess whether what changed is substantive: new data, expanded coverage, updated recommendations that reflect something that’s genuinely different now, restructured content that better serves the query, added examples or specificity, versus cosmetic changes like a changed date stamp, a reworded introduction, or a copyright year bump with no other edits.
If the diff shows real substance changes, freshness combined with quality improvement is a reasonable explanation, though even then it’s more accurate to say the competitor made a genuine content update that happened to also refresh the date, rather than attributing the gain to the date change itself. If the diff shows the date changed with little or nothing else different, rule freshness out as the explanation and move the investigation elsewhere. This is the step most audits skip, because checking a date is fast and reading a full page diff is slow, but skipping it produces false positives constantly: teams conclude “they beat us by republishing” when the actual cause was a links gain, a technical improvement on the competitor’s side, or your own page losing something (a broken element, a content section removed in a prior edit, an internal link that stopped pointing to the page).
A hypothetical case showing why the diff step matters
Imagine a hypothetical site, “Example Fitness Guide,” that loses its top ranking for an evergreen query to a competitor, and the team notices the competitor’s page now shows a “last updated” date from the previous week. Hypothetically, if the team stopped there and concluded “they beat us by refreshing their date,” they might respond by simply bumping their own page’s timestamp without changing anything else, expecting that alone to restore the ranking. Now imagine they instead ran a page-diff against an archived snapshot of the competitor’s page from a month earlier and found, hypothetically, that the competitor had actually added a new section addressing a common follow-up question, updated an outdated recommendation, and restructured the introduction to answer the query more directly, real substantive work, not a cosmetic date bump. In that hypothetical, the honest conclusion would be that a genuine content improvement drove the gain, and the actual fix would require comparably substantive work on their own page, not a timestamp change, which is exactly the kind of do-nothing “fix” that predictably fails when the diagnosis skips the diff step.
What else to check once freshness is ruled out
Once the date-and-diff check comes back negative for genuine freshness signal, the more common actual causes for an evergreen-query decline are worth checking in roughly this order. Check your own page for unintended regressions first: has anything been removed or changed in a recent edit, has a canonical tag or noindex been introduced accidentally, has page speed or Core Web Vitals performance degraded, has an internal link that used to point to this page from a high-authority page on your site been removed or changed. Then check the competitive link profile: did the pages that overtook yours gain a meaningful number of new referring domains around the time of the shift, which is available from most third-party link index tools and is a far more common explanation for sustained ranking gains than a content refresh alone. Then reassess relevance and depth independent of dates: has the competing page always been more comprehensive or better structured for the query’s actual intent, and the gap simply became visible once some other factor (an algorithm update, a link change) shifted weighting. And check for intent or SERP-feature shifts unrelated to any single competitor: sometimes the query itself is being interpreted differently by Google (a shift toward a different dominant intent, a new SERP feature absorbing clicks), which shows up as multiple established pages losing ground simultaneously rather than one specific competitor gaining at your specific expense.
The overarching principle for the diagnosis is to treat a changed date as a hypothesis to test, not evidence in itself. Since Google has been explicit that timestamp changes without real content updates don’t produce a ranking benefit, any diagnosis that stops at “they changed their date” without confirming the content actually changed is very likely misattributing the cause, and any recovery plan built on that misdiagnosis (simply changing your own date without a substantive rewrite) is unlikely to work.
