Short answer
Most Google changes remove or restrict a presentation feature — a rich result, a badge, a panel — without changing what makes a page rank or get quoted. So the correct default reaction is to check whether the change touches a surface you actually appear in, look at Search Console dated around the rollout, and change nothing until the data says otherwise. Two exceptions deserve same-day attention: anything that blocks machine access to your pages, and anything that changes eligibility rather than appearance.
The pattern behind the announcements
Read a few years of Google's documentation changelog and the shape becomes obvious. The features that get removed are almost always the ones that decorated a result. The things that decide whether you appear at all — indexing, crawlability, snippet eligibility, content quality — get clarified far more often than they get changed.
That distinction is the whole article. A presentation change moves your click-through rate. An eligibility change moves whether you exist on the surface. The industry reacts to both with the same volume of noise, which is why teams end up spending a quarter on something that was worth an afternoon.
One question sorts nearly every announcement: does this change what qualifies a page, or only how a qualifying page is displayed? Display changes are worth knowing and rarely worth reorganizing around. Eligibility changes are worth dropping other work for.
Three changes worth learning from
Rather than list everything, three documented examples show the pattern and the correct response to each. All three are recorded with their dates in Google's documentation changelog, which is the primary source worth watching — read it directly rather than the write-ups of it.
- The HowTo rich result was removed entirely (September 2023). Google removed the HowTo structured data documentation, noting that the rich result "is no longer shown in search results, on both desktop and mobile devices". The pages themselves were unaffected — only the decoration disappeared.
- The FAQ rich result was narrowed, then withdrawn altogether (September 2023, then May 2026). Google first restricted the feature "to well-known, authoritative government and health websites", which already ended it for ordinary businesses. It then deprecated it outright: the changelog states the feature "will no longer appear in Google Search starting May 7, 2026", and the documentation page was removed the following month. Two announcements, three years apart, on a feature many sites had built page templates around.
- AI surfaces arrived with no new requirements (2025 onward). Google's guidance on its AI features states that to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown with a snippet, and that "there are no additional technical requirements". A major new surface, and the eligibility rules were the existing ones.
The middle example is the instructive one, and it is why every dated claim in this article carries its date in the sentence rather than in a link. A page that stated the 2023 restriction as a permanent rule became wrong in May 2026 without a single word of it changing — which is how content about announcements quietly rots.
Two removals and one addition, and none of them required a new tactic. The correct response to all three was the same: understand it, adjust expectations about click-through, and keep publishing pages that answer questions. What the third one does change is where the competition happens — that is covered in how to appear in AI Overviews and AI Mode.
What to do with your structured data
The FAQ case creates a specific decision that a lot of sites got wrong in both directions, so it is worth separating three different things that people collapse into one.
- The rich result — the expanded accordion in the search listing. Gone for everyone since May 2026, and no amount of markup brings it back.
- The markup — the FAQPage structured data in your page. Still valid, still accurately describes your content to machines, and costs nothing to leave in place. Do not rip it out in a panic; do not expect it to earn you anything on its own either.
- The visible FAQ section — the questions and answers a human reads. This is the part that matters most now, and removing it because the rich result disappeared would be the genuinely expensive mistake. A short, self-contained answer under a clear question is exactly the shape a retrieval engine can lift into an AI answer.
Which is the general lesson about markup: structured data helps a machine understand what a page is claiming. It has never forced a result and it does not force a citation. When a rich result is withdrawn, what you lose is the display, not the understanding.
A procedure for the next announcement
Announcements arrive faster than anyone can absorb them. A fixed procedure keeps the response proportionate, and it takes about an hour.
- Read the primary source. Google's own blog post or documentation page, not a summary of it. Most of the panic in any given week comes from a second-hand paraphrase that dropped a qualifier.
- Classify it. Eligibility or presentation? Write the answer down in one sentence. If it is presentation, the rest of this list is short.
- Check whether it touches you. A change to a rich result you never earned, or a surface you do not appear in, is not your event.
- Look at Search Console around the rollout date. Compare a window before and after. If your curve moved before the date, something else caused it.
- Wait for enough days to distinguish signal from noise before changing anything structural. Weekly seasonality alone can produce a swing that looks like a penalty on day three.
- Fix only what the evidence points at, and record what you did and when, so the next drop can be compared against a known change rather than guesswork.
The one category that skips the waiting is access. If an announcement concerns crawlers, directives or indexing rules, check your own configuration the same day — a page that cannot be fetched or shown with a snippet is out of every surface at once, and that failure is silent from the browser. The first step of a visibility audit covers exactly what to check.
What has never moved
Against a decade of feature churn, the durable requirements are strikingly short — and they are the ones that also govern whether an AI assistant can use your page.
- A page a machine can fetch, render and read without executing your application.
- Content that answers a real question, written for the person asking it.
- Honest structure: one question per heading, the answer under it, dates that mean what they say.
- A site that is technically stable — working status codes, stable URLs, an accurate sitemap.
- A reputation that exists off your own domain, because a claim only you make is weaker than one others corroborate.
Every announcement is worth reading against that list. If a change does not affect any of the five, it does not warrant a project. If your content plan is built on them, most weeks you will read the news and do nothing — which is the correct outcome, and the point of having a strategy that does not depend on a feature staying available.
Frequently asked questions
Should I remove FAQ structured data from my pages?
The rich result is gone for everyone, so stop counting on it for visibility: Google restricted it to well-known, authoritative government and health websites in September 2023, then deprecated it entirely — its changelog states the feature stopped appearing in Google Search on May 7, 2026, and the documentation page was removed the following month. Leaving valid FAQPage markup in place is harmless and still describes your content accurately to machines. Removing the visible FAQ section would be the real mistake — those short, self-contained answers are prime material for extraction into AI answers.
How do I know whether a Google change affected my site?
Compare the date of the change to the shape of your traffic, not to your feelings about it. Search Console gives you impressions and clicks by day and by page. If the drop starts before the change was rolled out, the change is not your cause. This sounds obvious and is skipped constantly, which is how teams end up rewriting a site in response to something that never touched them.
Do AI Overviews require anything special from my site?
No — eligibility runs on the ordinary indexing and snippet rules, and Google states there are no additional technical requirements. The full rule, including the control whose name misleads people into blocking themselves, is covered in our article on appearing in AI Overviews and AI Mode.
How quickly should we react to an announcement?
Slower than the industry does. Read the primary documentation rather than the summaries, check whether the change touches surfaces you actually appear in, and wait for enough days of data to distinguish a change from noise. The exception is anything that blocks access — a directive or a robots rule that would remove you from a surface. Those get checked the same day.
If you are looking at a traffic drop right now and cannot tell whether an announcement caused it, that is a diagnosis before it is a project. Book a call and we will look at the dates with you.
