FAQ Toggle

In the Feast Plugin can enable a Yoast FAQ Toggle:

Activating our new "​Enable Yoast FAQ Toggle​" setting will automatically enable this on all your Yoast FAQ blocks, no extra work required: 😎

Using the Yoast FAQs on a page is considered good user experience because you can use it to answer common questions users have.

However, we don't always need to show the full answer unless the user clicks the question, because some questions may not be relevant to them.

Google uses similar expanding FAQs in their search results like this:

Jump to:

• Remove other plugins
• Do not copy+paste
• jQuery
• Weird text
• Live example
• Updated FAQ Guidelines

Remove other plugins

If you've been using the "Turn Yoast SEO FAQ Block to Accordion" plugin, we recommend removing this plugin due to unmodifiable styling and an unresponsive developer.

And this plugin must be disabled once the Feast setting is activated.

Do not copy+paste

Do not write questions and answers then copy+paste the text into WordPress, as this can import tags and text that break the FAQ block.

jQuery

This feature relies on jQuery, so removing jQuery will break this.

It's no longer required or recommended to remove jQuery from loading on WordPress due to optimization updates over the years.

The most common place this is done is in the code snippets plugin.

Weird text

If your arrows get turned into something resembling ↓ then this is the result of a third party plugin compatibility issue:

The iubenda Cooking Compliance plugin is one known source of this issue.

This may also be the result of a database character encoding issue, which you'll need to contact your host about.

Live example

This is the Feast site using the FAQ Toggle:

Updated FAQ Guidelines

This is from Casey Markee on February 23, 2026 on whether FAQs are still helpful for content sites.

An FAQ on FAQs for Bloggers - The More You Know!

There’s been a lot of chatter lately about removing FAQ blocks from recipe posts because Google no longer supports FAQ rich results for most sites.

I want to clarify something important for creators.

Google removing FAQ schema visibility does NOT mean FAQs themselves are a bad idea. It just means adding FAQs purely for rich snippets is no longer a strategy.

Before everyone runs out and "removes FAQS from their posts" please stop and read this:

Google’s Quality Rater Guidelines support helpful Q&A content

If you actually read the Quality Rater Guidelines, they emphasize:

• Satisfying user intent
• Providing helpful supplemental content
• Answering questions clearly and completely
• Reducing the need for users to search again

A strong FAQ section does exactly that when it answers real, practical questions.

Google wants content that helps users accomplish their goal. For recipes, that often includes troubleshooting, substitutions, storage, freezing, and technique clarification.

That is not filler. That is helpful. I recommend all of this in my audits!

FAQs support People Also Ask (even without schema)

Google does not require FAQ schema to pull content into People Also Ask accordions. But it also doesn't penalize you either!

Clear question-based headings and concise answers make it easier for Google to understand:

• What question is being answered
• Where the answer is located
• How it satisfies intent

Well-written FAQs can absolutely improve your eligibility for PAA features because they mirror how real users search.

That’s not gaming the system. That’s aligning with search behavior.

FAQs are useful for LLM crawling and AI Overviews

This is the one I see rarely discussed. LLMS extract data through all the following:

• Direct answers
• Clear clarifications
• Concise explanations
• Conditional statements (“If you use frozen blueberries…”)

A clean Q&A format makes that extraction easier for the average blogger.

That doesn’t mean you should write robotic “bite-sized chunks.”

It means clarity helps everywhere: Google, AI Overviews, Gemini, Perplexity, ChatGPT.

Clarity wins, and FAQs help refine that clarity.

Not all FAQs are the same

This is by far where bloggers get confused the most about FAQs. So let's use some examples:

 Filler FAQ:

Q: What is chocolate cake?

A: Chocolate cake is a cake made with chocolate.

That adds nothing to the user or the average recipe.

 Helpful FAQ:

Q: Why did my chocolate cake turn out dry?

A: The most common cause is overbaking. Remove at 200°F internal temp and avoid overmixing the batter.

The 1st FAQ is keyword padding.

The 2nd FAQ prevents a failed recipe and a frustrated reader.

The problem isn’t FAQs.

The problem is low-quality FAQs.

FAQ accordions improve usability

Even without schema:

• Accordions reduce visual overwhelm
• They improve scannability
• They keep long posts cleaner
• They allow users to jump directly to the information they need

That’s a UX improvement, especially for long-form recipe content.

Schema visibility is gone for most. But user experience is not. We always optimize for the user!

So what should bloggers actually do with FAQs in 2026 and beyond?

• Keep FAQs that answer real reader questions
• Focus on troubleshooting, substitutions, storage, technique
• Use accordions as they improve readability
• Remove thin, repetitive, keyword-stuffed fluff
• Stop adding FAQs purely to chase features

Don’t remove helpful content just because a rich result changed.

If it improves clarity, reduces bounce, strengthens intent satisfaction, and helps users succeed with your recipe that FAQ is doing its job.

I will ALWAYS recommend bloggers add FAQs to their content. And I strongly hope all of you do as well.

Good luck out there!