Yes, Google Just Killed FAQ Snippets: What It Means for Your Small Business

By Cap Puckhaber, Reno, Nevada

Updated: 11/4/26

Yes, Google killed FAQ snippets. The expandable question dropdowns that used to sit under some search listings stopped appearing on May 7, 2026. A few clients emailed me that week asking if their rankings were about to crash. They weren’t, and yours probably won’t either. But the change does say a lot about where search is heading, and it’s worth adjusting how you spend your SEO time.

I’ve managed SEO for small businesses for years, and I watched FAQ snippets go from a cheap trick to a dead feature. This post covers what happened, what I saw in real client accounts and what I’m telling owners to do next. I’ll also explain why I still put FAQ sections and FAQ schema on posts like this one.

What actually happened to FAQ snippets

FAQ snippets were a type of rich result. If a page had FAQ structured data, Google could show a few of its questions as dropdowns right in the search results. That made a listing taller and pushed competitors further down the page. For a while, it was one of the easiest visibility wins in SEO. So everyone used it, and that’s exactly what ruined it.

The shutdown happened in two stages, about three years apart. First Google cut the feature down to a small group of sites. Then it removed the feature entirely, even for that group. Knowing both stages helps explain why most small businesses felt almost nothing this spring.

The first cutback

In August 2023, Google announced that FAQ rich results would only show for well-known, authoritative government and health websites. Everyone else lost them almost overnight. Search Engine Land reported a Portent study showing how fast the change hit. FAQ rich results in Google search appeared on 53.94% of the results pages Portent tracked in February. By mid-August, that share had fallen to 17.04%.

That was the moment most small business sites lost their FAQ dropdowns for good. If you’re a plumber, a dentist or a boutique, you haven’t had them since then. The recent change just closed the door the rest of the way.

The final shutdown

Search Engine Journal reported that Google dropped FAQ rich results from search completely on May 7, 2026. Google updated its FAQ structured data documentation with a short notice instead of a full announcement. The FAQ report and the Rich Results Test support were scheduled to come out of Search Console in June. Support in the Search Console API was set to end in August.

Google didn’t publish a detailed explanation. Still, the reasoning isn’t hard to guess. AI Overviews and AI Mode now answer many questions directly at the top of the page. A dropdown of website questions underneath competes with Google’s own answers.

What I saw in client accounts

When the first cutback hit, I pulled Search Console data for every client using FAQ schema. Impressions on a few pages dipped, mostly on informational blog posts. Clicks barely moved. That told me the dropdowns had been inflating how often a listing got seen without adding much real traffic.

The final shutdown was even quieter. Almost none of my clients still had FAQ rich results by then, because none of them were government or health sites. Rankings held steady across the board. The only practical change was cleaning up a Search Console report that had been empty for years.

A Reno HVAC client’s numbers

One heating and cooling client had FAQ dropdowns on a handful of service pages before the first cutback. Those pages lost about 20% of their impressions in the following month. Clicks from those pages stayed within a few percent of where they’d been. Calls from organic search didn’t change at all. The dropdowns made the listing look bigger, but people still clicked the same result for the same reasons.

What I check in Search Console now

With the FAQ report gone, I lean on the regular performance report. I filter by page and compare clicks and click-through rate month over month. A page losing clicks while holding its position usually means the listing itself needs work. Pages that lose position need better content or links. Splitting problems that way keeps me from blaming Google for issues we can fix ourselves.

The mistake I made with FAQ schema

Back when FAQ snippets still worked for everyone, I got greedy with them. I added FAQ sections to nearly every service page for a few clients, sometimes with questions nobody actually asked. The snippets showed up, and the listings looked great. But the pages got longer and harder to read, and a couple of them saw time on page drop. I’d written for a search feature instead of for customers, and I’ve avoided that habit ever since.

Why this change can help small businesses

Big brands had the budgets to mark up thousands of pages with FAQ schema. They used it to take up extra space on the results page, and local businesses often got pushed down. Losing the feature removes one of those advantages. Every listing now gets roughly the same footprint, and the content decides who earns the click.

It also saves owners money. I’ve seen small businesses pay developers to add and maintain FAQ markup that hadn’t produced a visible result in years. That money is better spent on photos, reviews or a faster website. Nobody has to chase a moving technical target for this feature anymore.

A trail sign comparison

FAQ snippets remind me of the old wooden trail signs around Tahoe that got covered in stickers. At first, a few stickers helped hikers find a shop or a guide service. Then everyone added one, and the sign got so cluttered nobody could read the trail name. Eventually the forest service scraped them all off. The trail didn’t change. It just became easier to see what was actually there, and that’s roughly what Google did here.

Other rich results that went away

FAQ snippets weren’t the only casualty. Google pulled HowTo rich results around the same time as the first FAQ cutback, so step-by-step dropdowns vanished too. Over the years, Google has trimmed several other rich result types that sites overused. The pattern is consistent. Once a feature gets abused at scale, Google shrinks it or shuts it off.

That history shapes how I plan SEO work for clients. I treat any special search feature as a bonus that could disappear next quarter. The page underneath has to work without it. If a strategy only pays off because of a temporary display feature, it’s a short-term bet at best.

Structured data that still matters

Plenty of structured data still earns its keep. LocalBusiness markup helps Google confirm your name, address, phone number and hours. Product markup can show price and availability for stores that sell online. Review snippets still appear for certain types of pages, and Event markup helps venues and organizers. Those types describe real facts about a business, which is why I keep them on every client site where they apply.

Should you delete your FAQ schema?

No, you don’t need to delete anything. John Mueller from Google said there’s no need to change anything, though sites can remove the markup if they added it only for search. Leftover FAQ schema won’t hurt your rankings. It simply won’t produce a dropdown in Google anymore. I tell clients to leave existing markup alone and stop spending time adding new markup for Google’s sake.

There’s one exception. If your FAQ schema contains questions that don’t appear on the visible page, clean that up. Hidden or mismatched structured data was never a good idea, and it still isn’t. Your markup should always describe what a visitor can actually read.

Removing markup is fine too, if your developer is already working on those pages. I wouldn’t pay for a separate project just to strip it out. The time is better spent on something that brings in customers. For most sites, leaving it alone is the cheapest and safest choice.

Why I still add FAQ schema to my own posts

You might notice this post has FAQ schema attached to it. I keep adding it because it costs me a few minutes and describes the page clearly to any system reading it. Google won’t show a dropdown, and I don’t expect one. But other search tools and AI assistants still read structured data when they try to understand a page. I’d rather give them a clean summary than make them guess.

Yoast and Rank Math users

Most WordPress sites I work on use Yoast or Rank Math, and both handle FAQ blocks automatically. Those blocks still display your questions and answers on the page for visitors. The schema they generate still validates as normal structured data. You don’t need to swap out the blocks or rebuild those pages. If a plugin update changes how the blocks behave, the plugin will handle it.

FAQ content still earns its spot on the page

Losing the snippet doesn’t make the FAQ section useless. Visitors still have questions before they buy, call or book. A clear answer on the page can stop someone from bouncing back to the results to find it elsewhere. I’ve watched good FAQ sections cut down on repeat phone calls asking the same three things.

Those questions also help Google understand what the page covers. A service page that answers pricing, timing and service area questions plainly is easier to match with real searches. That matters even without a special result type. It matters even more as AI answers pull facts from pages like yours.

Write answers for people first

The best FAQ questions come from your phone, your inbox and your front counter. I ask every client to list the questions customers ask most often in a typical week. Those go on the page in the customer’s own wording. Answers should be short, direct and specific, with real prices or time frames when possible. A vague answer wastes everyone’s time, including Google’s.

How many questions to include

I usually aim for four to eight questions on a service page. Fewer than that often misses common concerns, and more than that starts to bury the important answers. Blog posts can carry a few more if the topic invites them. Each answer should stand on its own, since many visitors skim straight to the one question they care about. If two questions have nearly the same answer, I merge them.

Where to put the effort instead

If you spent time on FAQ markup before, that time has better uses now. For local businesses, I’d shift it toward the parts of search that still decide who gets the call. Most of these are simple, and they don’t require a developer. They just require consistency.

Title tags and meta descriptions

Without dropdowns, your title and description do all the work in a standard listing. I rewrite those for every important page with the service, the city and a reason to click. A title like Furnace Repair in Reno with Same-Day Service tells searchers exactly what they’ll get. Small changes like that have lifted click-through rates on client pages more than FAQ snippets ever did. They’re also free to test.

Google Business Profile

For local searches, the map pack usually sits above the regular listings. That makes your Google Business Profile the most valuable piece of search real estate a local business owns. I post updates and fresh photos on client profiles every week. Services, hours and service areas get checked every month. Profiles that look active and complete tend to earn more calls and direction requests.

Reviews and replies

Reviews feed both rankings and trust. I set up a simple process for every client to request a review after each completed job, usually by text. Replying to every review, good or bad, shows searchers that someone is paying attention. A Reno landscaping client went from 31 reviews to over 120 in a year with that process alone. Their calls from the map pack rose steadily through the same stretch.

Service area pages that say something real

Many local businesses serve several towns, and each one deserves its own page. A Reno contractor might work in Sparks, Carson City and Truckee, with different permits and travel times for each. I build those pages around real local details, like neighborhoods served and typical jobs in that area. Thin pages that just swap the city name tend to fail. Pages with genuine local detail earn rankings and calls.

Page speed and mobile layout

Most local searches happen on phones, often when someone needs help fast. A slow or cluttered mobile page sends those people right back to the results. I test every client’s main pages on a phone over a normal cellular connection, not office Wi-Fi. If the phone number and the main call to action aren’t visible without scrolling, we fix that first. Those fixes usually move calls faster than any content change.

Link your FAQ answers to your service pages

An FAQ answer is a great place for an internal link. If someone asks whether you service Sparks, link the answer to your Sparks service page. When they ask about pricing, link to the page that explains your packages. Those links help visitors take the next step and help Google see how your pages connect. I add them to every FAQ section I write.

What AI search means for local content

AI answers are the real reason FAQ snippets disappeared, so they deserve some attention. When someone asks a simple question, Google can now answer it at the top of the page without sending a click anywhere. That’s bad news for sites built on generic how-to articles. It’s much less of a problem for a local business with real services, real prices and real reviews.

AI tools still need sources, and they favor pages that state facts clearly. A page that says exactly what you charge, where you work and how fast you respond is easy to summarize. Vague marketing copy gives those systems nothing to work with. I’ve started rewriting client service pages with that in mind, and the pages read better for humans too.

Experience is the hardest thing to copy

Anyone can publish a generic answer to a common question. Very few businesses can publish photos of their own work, stories about real jobs and specific numbers from their own customers. That first-hand material is hard for AI to fake and easy for customers to trust. I push every client to add at least one real example to each service page. A single before-and-after photo with a short story often beats a thousand words of generic advice.

A quick audit you can run this week

You don’t need an agency to make sense of this change. Start by opening your five most important pages on your phone and reading them like a customer would. Check whether the title, the main service and the phone number are obvious within a few seconds. Then look at any FAQ section on those pages and ask whether real customers ask those questions. Cut the filler and add the questions you actually hear.

Next, open your Google Business Profile and confirm your hours, services and photos are current. Look at your last ten reviews and reply to any you skipped. Last, compare clicks for your top pages in Search Console against the same period last year. That hour of work will tell you more about your search health than any FAQ report ever did.

How I measure search success now

FAQ snippets taught a lot of marketers to celebrate impressions. Impressions are easy to inflate and easy to lose. I build client reports around clicks, calls, form fills and booked jobs instead. Those numbers connect directly to revenue, and they don’t swing every time Google redesigns a results page.

I also keep an eye on how AI features change click patterns. Some informational searches now get answered on the results page, so fewer people click through for simple facts. Pages that serve buyers, like service pages and pricing pages, still get the clicks that matter. That’s where I put most of the content effort now.

Track calls, not just clicks

For most local businesses, the phone still rings more than the contact form gets filled out. I set up call tracking on every client site so we can tie calls back to the page that produced them. Without it, organic search looks weaker than it really is. One client thought SEO wasn’t working until call tracking showed it drove nearly half of their booked jobs. That single setup changed how they budgeted for the next year.

What to tell your web developer

If you have a developer or a web host who manages your site, send them a short note. Tell them to leave existing FAQ markup in place and not spend billable hours removing it. Ask them to stop adding new FAQ markup purely for Google’s benefit. Then point their time toward page speed, mobile layout and accurate LocalBusiness markup. Those requests take five minutes to write and can save you real money.

Developers sometimes push big technical projects whenever Google changes something. Most of the time, this change doesn’t justify one. Ask what problem a proposed fix solves and how you’ll measure the result. If the answer involves FAQ snippets coming back, it’s not worth paying for.

Frequently Asked Questions

Did Google remove FAQ snippets for every website?

Yes, it did. Google stopped showing FAQ rich results in search on May 7, 2026, including for the government and health sites that kept them after the August 2023 cutback. Most other sites had already lost them years earlier. The change applies across all search results.

Does leaving FAQ schema on my site hurt SEO?

No, it doesn’t. Google said there’s no need to change anything, and leftover FAQ markup won’t hurt rankings. It just won’t create a dropdown in search results. Make sure any markup matches the questions visible on the page.

Should I keep FAQ sections on my web pages?

Yes, as long as they answer real customer questions. FAQ sections help visitors find answers quickly and help search engines understand the page. They can also feed People Also Ask boxes and AI answers. Use questions your customers actually ask, written in their words.

What replaced FAQ snippets in Google search?

Google didn’t announce a direct replacement. AI Overviews and AI Mode now answer many questions at the top of the results page. People Also Ask boxes still appear for many searches. For local businesses, the map pack and Google Business Profile matter more than any rich result.

What should small businesses focus on after this change?

Focus on title tags, meta descriptions, Google Business Profile activity and reviews. Keep useful FAQ content on your pages for visitors. Track clicks, calls and booked jobs instead of impressions. Those steps protect your search traffic no matter how Google changes the results page.

Check out my latest blog on the Rise of Agentic Ai

New on Black Diamond is my take on Will AI Replace Me? A Marketer’s Perspective by Cap Puckhaber

If you haven’t read it yet, check out our blog on the decline of strip malls

About the Author

Cap Puckhaber is a marketing strategist, finance writer, and outdoor enthusiast. He writes across CapPuckhaber.com, TheHikingAdventures.com, SimpleFinanceBlog.com, and BlackDiamondMarketingSolutions.com. Follow him for honest, real-world advice backed by 20+ years of experience.

If you want to connect with Cap Puckhaber and see more of his insights on marketing, check out his LinkedIn profile where he shares regular updates and professional tips.

Home

Blog

About Cap Puckhaber

Did Google Kill FAQ Snippets? What to Do Now