Skip to main content
NewNMC’s advertising guidelines for doctors are in force from 6 Oct 2026. See what to change, and get a free compliance auditNew NMC advertising rules for doctors: what to change
SEO

FAQ and HowTo Rich Results Are Gone: What Healthcare Sites Should Keep, Rewrite or Remove

Google ended FAQ rich results in May 2026 and HowTo in 2023. Here is how to audit legacy markup on hospital pages and decide what to keep, rewrite or remove.

FAQ and HowTo Rich Results Are Gone: What Healthcare Sites Should Keep, Rewrite or Remove

This post is for marketing leads and web managers at hospitals and clinics whose site still carries FAQPage or HowTo markup added years ago, often by a plugin, on the promise of expandable answers in Google results. Those results are gone. The question now is what to do with the markup, and with the FAQ blocks it describes.

It answers three things: what changed and when, why "gone" does not automatically mean "delete everything", and how to audit a sample of pages and decide, page by page, whether to keep, rewrite or remove. We describe the audit method. We have not published findings from any hospital site here, and nothing below should be read as a result. Where an example appears, it is invented and says so.

What actually changed

The dates are worth getting right, because they are often misquoted.

  • HowTo. In August 2023 Google announced it was changing how FAQ and HowTo rich results appear. How-To results were first limited to desktop and then dropped. Google's Search Central changelog records the documentation removal on 14 September 2023, saying the result is no longer shown on desktop or mobile.
  • FAQ, 2023. The same announcement said FAQ rich results would be shown only for well-known, authoritative government and health websites. Hospitals were, in principle, in the group still eligible.
  • FAQ, 2026. The changelog records a deprecation notice on 8 May 2026 saying the feature would no longer appear in Google Search from 7 May 2026, and the documentation was removed on 15 June 2026.

So the FAQ result that health sites alone kept after 2023 has now gone too. No site, whatever its sector, gets the expandable question-and-answer result from FAQPage markup.

"Gone" does not mean "harmful"

Google's 2023 announcement made a point that still holds: you can drop the structured data, but there is no need to proactively remove it, because unused structured data does not cause problems for Search and has no visible effect.

That should shape the audit. The reason to touch legacy markup is not penalty risk. It is one of these.

  1. Accuracy. Markup that no longer matches the visible page is a liability. Google's structured data guidelines say not to mark up content that is not visible to readers.
  2. Maintenance weight. A template that emits twenty identical questions on every page is code and data someone must keep correct.
  3. Clinical risk. Every answer in a health FAQ is a clinical statement. A block that nobody has reviewed since 2021 is an editorial risk whether or not it carries markup.
  4. Focus. Time spent on dead markup is time not spent on content readers use.

The FAQ block that readers see is a different asset from the markup. A good set of questions with direct answers helps a patient who is deciding whether to book, and nothing in Google's change touches that. Our FAQ and People Also Ask optimisation service is about the content, and it is why the question is "what should the block say?", not "is the schema still valid?".

One caution on the other side. Do not assume FAQ markup now helps AI answer tools. We have not seen documentation from any major search or AI provider that says it does, so treat that as unproven and do not use it as a reason to keep boilerplate.

The audit method

The aim is a defensible decision for each template and each page, using a sample.

Step 1: Sample

For a hospital group, take a stratified sample of 100 pages: specialty hubs, treatment pages, condition pages, doctor pages and blog posts, in proportion to how many of each exist, with extra weight on pages that earn clicks. If you are studying several sites, sample the same page types from each so results are comparable. A sample of 100 does not give you statistics about the whole site; it gives you enough to see which templates are the problem.

Step 2: Extract

Crawl the sample and extract, for each page:

  • every JSON-LD, Microdata or RDFa node of type FAQPage, Question, Answer and HowTo;
  • the number of questions in the markup and the number of questions visible in the rendered page;
  • the answer text in the markup and the answer text on the page;
  • whether the FAQ is in the raw HTML, or only after JavaScript runs;
  • the template name and the CMS or plugin that emits it.

Step 3: Classify each page

Apply the rules in order.

ObservationClassificationAction
Markup contains questions not visible on the pageMismatchRemove the markup now, or add the content if it is valuable
Same question set appears on many pagesBoilerplateRemove from pages where it does not apply
Answers are promotional or make unreviewed clinical claimsEditorial riskRewrite with clinical review, or delete
Answers are short, specific, accurate and visibleSoundKeep the content; keeping the markup is optional
HowTo markup on a page that is not step-by-step instructionsMisuseRemove
HowTo markup on genuine instructions, such as a preparation guideDead featureRemove or keep, but the result will not appear
FAQ only appears after a click that loads from a scriptFragileMove into the page body if the answers matter

Step 4: Record, count and report

For each template, report the number of pages sampled, how many fall into each class, and the proposed action. Keep the counts as plain numbers and say they are for the sample. A report that says "template X emits twelve generic questions on every service page" is far more useful to a developer than a percentage.

Want this applied to your practice? Get a free seo audit.

Book my free audit

Keep, rewrite or remove

Convert the classification into three decisions.

Keep. The questions are real, the answers are accurate and approved, and the content sits on the page where a reader will see it. Keep the visible block. If the markup is accurate and cheap to maintain, there is no urgency to remove it, and removing a correct node gains nothing. If it is hard to maintain, drop the markup and keep the content.

Rewrite. The questions are good but the answers are thin, salesy or unreviewed. Rewrite for a patient with a decision to make: what is the procedure for, who it may suit, what the first visit involves, how to contact the team. Keep each answer to what the provider is willing to stand behind, and have the clinical team review anything that is medical. Avoid outcome promises and comparative claims. For doctors in India, remember that NMC rules constrain how medical practitioners advertise, so a doctor's FAQ is not a place for claims about being the best; our NMC compliance handbook sets out the working rules.

Remove. The block is boilerplate, the questions are invented to carry keywords, the answers contradict other pages, or the markup describes text that is not shown. Delete the markup. Delete the block too if it does not help a reader.

A hypothetical example of the decision

Suppose a template on an imagined 150-bed hospital site in Lucknow prints the same eight questions at the foot of every specialty page: "Which is the best hospital?", "Is treatment safe?", "What is the cost?" and so on, each with the same two-line answer. The markup mirrors the block.

By the table, that is boilerplate with editorial risk. The cost answer cannot be right for every specialty, and the safety answer is an unreviewed clinical claim. The decision is to delete the block from the template, then reintroduce a short, specialty-specific set of questions on the pages where the enquiry team hears the same questions every week. Those answers come from the call log, are written by the team who answer the phone, and are checked by the department. Whether to add markup to the new block is a minor choice; it does not change what Google shows.

Practical removal notes

  • Remove at the template level, then spot-check pages. Do not strip markup page by page.
  • Check where the markup is injected. It may come from a plugin, a tag manager or a theme. Disabling it in one place while another still emits it leaves duplicates.
  • Do not remove the content you want readers to see just because the markup is going. Keep the visible block and its anchor links.
  • Keep a record of what was removed and the date, so a later drop in traffic is not blamed on schema by default. Google's documentation says the feature is no longer shown, so a change in impressions from FAQ appearances after the dates above is expected rather than a fault.
  • Search Console reporting changed as features were retired. We have not checked how every report currently behaves, so look at your own property for the details.

Where to start

This week, run the extraction on twenty pages. Count how many have FAQ or HowTo markup, how many questions it carries, and whether those questions match the visible text. Read ten answers aloud and ask whether you would be comfortable with the provider's clinicians seeing them under the hospital's name.

Then decide at template level: keep the content, rewrite the weak answers, delete the boilerplate and the HowTo markup. Revisit your structured data scope while you are there, because the types that still change search appearance are listed in Google's gallery and the medical ones are not. If you want the wider vocabulary refreshed, the glossary entry on schema markup is a short briefing for the stakeholders who approve changes.

Filed underFAQ schema deprecatedFAQPage markup removedHowTo rich results removedFAQ schema hospital websiteremove FAQ schemaFAQ rich results 2026

About the author

Co-Founder & CTO · Gurugram, India

Arush builds the systems the rest of the company runs on — the patient-acquisition pipelines, the AI chatbots, the analytics that tie a single click to a booked appointment. If a campaign reports a number, it's because something his team built is tracking it.

Free guide · 15 pages

The Patient Acquisition Blueprint

A 90-day plan from first search to booked appointment.

The Pioneers Brief — one essay, three benchmarks, one teardown, every Thursday. Subscribe free →

Free seo audit

Your next chapter starts with a conversation.

Three quick questions. We come prepared with a plan for your specialty and city.

  • A 30-minute call with a healthcare specialist
  • Your top three growth opportunities, in writing
  • Honest advice — even if that means not hiring us
  • No obligation and no hard sell
You’ll speak with a senior strategist
Consultations are hosted by Arush Thapar’s team.
Step 1 of 3Takes 30 seconds

What do you want to improve first?

Details stay privateNo obligationReply within 1 working day

Client portfolio · Healthcare websites

Work relevant to faq and howto rich results are gone what healthcare sites should.

Explore client work →