FAQ Schema in WordPress Blocks: What Search Engines Receive

A WordPress FAQ block can render visible questions, answers, disclosure controls, and FAQPage markup.

Google stopped showing FAQ rich results on May 7, 2026.

Inspect actual output before maintaining markup. No block label proves what search systems receive.

Understand the current Google status

FAQ rich results no longer appear in Google Search. This applies across site categories.

Google removed its FAQ feature documentation during June 2026. Earlier eligibility guidance is obsolete.

The Google Search documentation updates record both deprecation and removal.

Treat older advice carefully

Older tutorials promise expanded FAQ listings. Some mention government and health eligibility.

That restricted phase also ended. Current Google Search shows no FAQ rich results.

Check source dates before following schema advice. Search features can disappear entirely.

Understand what FAQPage still means

FAQPage remains a Schema.org type. It describes pages presenting frequently asked questions.

The Schema.org FAQPage definition connects a WebPage with its primary questions.

Vocabulary existence does not guarantee a Google feature. Consumer support must be checked separately.

Separate vocabulary from search features

Schema.org publishes shared vocabulary. Search engines choose which types support special displays.

A valid FAQPage graph can remain understandable. Google may simply ignore it.

Never translate validity into promised visibility. Those are different claims.

Separate FAQPage from QAPage

FAQPage suits publisher-authored questions with authoritative answers. Editors control every answer.

QAPage describes one question receiving answers from users. Community voting can matter there.

Do not mark a forum thread as FAQPage. Its authorship model is different.

Separate FAQs from help articles

A help article may answer one broad question through sections. That is not automatically FAQPage.

FAQ content presents distinct questions with direct answers. Ordinary headings can organise explanations instead.

Choose structure for readers first. Do not rewrite every heading as a question.

Understand the visible output

An FAQ block usually renders headings, buttons, or disclosure summaries. Answers sit nearby.

Some blocks keep every answer expanded. Others use accordions or native Details elements.

That user interface exists independently from schema. Evaluate it on its own merits.

Understand the machine-readable output

A schema-enabled block may generate JSON-LD. Another may embed microdata around visible content.

Some plugins generate nothing until one setting changes. Others enable markup by default.

Inspect the public page. The editor interface cannot prove final output.

Know the basic FAQPage graph

The page becomes an FAQPage entity. Its `mainEntity` property references Question entities.

Each Question carries a name. Its `acceptedAnswer` references an Answer entity.

Each Answer carries text. That text should match the accessible visible answer.

Keep every question visible

Users should encounter every marked question on the page. Hidden schema-only questions lack evidence.

Do not add popular queries only inside JSON-LD. Publish useful answers visibly.

The visible wording can be concise. It should still express the same question.

Keep every answer accessible

Collapsed answers can remain visible to users through accessible disclosure controls.

The answer should exist in rendered HTML. Do not require unavailable scripts.

Test with keyboard and assistive technology. Schema cannot rescue an inaccessible accordion.

Match answer text accurately

Machine-readable answers should not exaggerate visible claims. Keep meaning and important qualifications aligned.

Exact HTML need not match formatting. The actual information must remain equivalent.

Update both outputs from one field where possible. Parallel copies drift.

Do not mark user answers

FAQPage implies authoritative publisher answers. Community replies can conflict and change.

Use an appropriate Q&A model when users submit alternatives. Follow that consumer’s rules.

Do not choose FAQPage merely because its plugin interface looks easier.

Do not mark promotional slogans

A fake question can disguise advertising. Readers recognise that manoeuvre immediately.

Use questions people genuinely ask. Answer limitations alongside benefits.

Schema should describe content, not manufacture credibility. Accuracy remains the boundary.

Do not duplicate every answer

Repeating identical FAQs across many pages creates thin repeated content. It also increases maintenance.

Place shared policy answers on an authoritative page. Link there when context permits.

Keep page-specific FAQs genuinely specific. Avoid automatic boilerplate.

Prevent duplicate schema generators

An FAQ block and SEO plugin can both generate FAQPage graphs.

Two FAQ blocks can also create separate graphs. Their question sets may overlap.

Choose one generator. Disable redundant markup while preserving visible content.

Inspect JSON-LD output

1. Open the public page.
2. View the original source.
3. Search for `FAQPage`.
4. Count every FAQPage graph.
5. Compare each visible question.
6. Compare every visible answer.
7. Check duplicate questions.
8. Record the generating plugin.

Repeat this inspection after plugin updates. Output defaults can change.

Inspect embedded markup

Search rendered HTML for FAQPage vocabulary attributes. Microdata may surround the accordion wrappers.

Follow each `itemprop` relationship. Confirm questions and answers belong to the correct scope.

DOM changes can break embedded relationships. Retest after frontend refactors.

Validate syntax appropriately

Google removed its FAQ feature documentation and rich-result support. Expect no FAQ eligibility there.

Schema.org Validator can still inspect vocabulary syntax. It cannot promise consumer use.

Separate syntax checks from product eligibility. Record both results clearly.

Do not promise AI citations

FAQPage markup does not guarantee citation by AI models. No such dependable contract exists.

Google requires no special schema for generative search. Useful accessible answers matter more.

Use direct answer-first writing because readers benefit. Avoid invented model-access claims.

Write answer-first FAQs

Begin each answer with its conclusion. Add conditions and context afterwards.

Use the same nouns from the question. Pronouns can become ambiguous outside surrounding context.

Keep each answer focused. Link toward deeper guidance instead of copying whole articles.

Choose useful question wording

Use natural questions that match reader decisions. Avoid keyword lists with question marks.

Distinguish close questions by intent. Price, compatibility, and process need separate answers.

Do not repeat the heading unnecessarily. Let each question add new value.

Keep answer scope controlled

A concise FAQ answer should resolve one uncertainty. It need not become another article.

State exceptions when they change the decision. Remove unrelated background.

Long answers can remain useful. Consider ordinary headings when several sections become necessary.

Use accessible disclosure controls

Question controls need meaningful names and exposed expanded states. Keyboard activation must work.

Focus should remain visible. Opening one panel should not move focus unexpectedly.

Native Details elements provide useful semantics. Custom accordions require careful interaction engineering.

Avoid accordion overload

Dozens of closed answers hide page substance. Scanning becomes slower for many readers.

Group related questions under visible headings. Keep essential information outside collapsed panels.

Use ordinary paragraphs when hiding adds no benefit. Simpler content often performs better.

Provide deep links carefully

Useful FAQ answers can receive stable anchors. Shared links then reach exact questions.

Check whether opening a fragment expands its panel. Some accordions keep targets hidden.

Preserve published identifiers. Renaming a question need not rename its anchor.

Handle translations deliberately

Translated questions need translated answers and matching schema text. Do not reuse English graphs.

Keep each language page internally consistent. Validate language-specific output independently.

Shared identifiers can help ownership. Visible text must follow the page language.

Handle conditional answers

Personalised answers may differ across sessions. Static FAQPage markup can then misrepresent content.

Mark only stable universally visible answers. Avoid account-specific values inside shared graphs.

Test logged-out output. Search crawlers generally receive the public version.

Handle changing policy answers

Refunds, support, pricing, and availability can change. FAQ copies become stale quietly.

Link toward authoritative policy pages where possible. Assign review dates for duplicated summaries.

Update visible and machine-readable copies together. Purge caches afterwards.

Measure value without rich results

FAQs can reduce confusion and support demand. They can improve internal navigation and task completion.

Measure page engagement, conversions, and support patterns. Do not credit invisible markup automatically.

The useful content may deserve upkeep. The schema layer may not.

Decide whether markup deserves upkeep

1. Identify every consuming system.
2. Confirm current documented support.
3. Estimate validation and update work.
4. Check duplicate generator risk.
5. Preserve valuable visible FAQs.
6. Disable needless markup safely.
7. Retest the rendered page.

Do not remove visible answers merely because one search feature ended.

Remove markup without removing content

Many blocks separate FAQ schema from the visual accordion. Disable only the schema setting. We cover the method in HowTo schema in WordPress.

Verify questions and answers remain accessible. Confirm no orphaned script persists.

Test caches and minified assets. Old JSON-LD can remain after configuration changes.

Keep markup when another consumer needs it

Another documented consumer may still process FAQPage. Verify that claim through its current documentation.

Record the consumer, required fields, and validation method. Avoid vague “AI visibility” justifications.

Retest when that consumer changes. Vocabulary support is not permanent.

Check block serialization

Questions and answers may live inside block attributes. Others live in nested paragraph blocks.

That storage choice affects migration and search. Exported HTML may not preserve every setting.

Test copying, converting, and deactivating the block. Record what visible content survives.

Check block conversion

Converting an FAQ block can remove schema while retaining text. It may also flatten disclosures.

Preview the converted result before saving. Confirm headings and answer relationships remain understandable.

Keep a revision until migration finishes. Bulk conversion deserves a staged sample.

Check frontend performance

Custom accordions can load scripts and styles. FAQPage JSON-LD itself is usually small.

Measure real pages containing many panels. Do not infer cost from the editor.

Native Details elements may need less JavaScript. Their simpler behaviour can be sufficient.

Check print and no-script views

Important answers should remain available when scripts fail. Printing should not omit closed panels.

Disable JavaScript on a test page. Confirm readable content and sensible order.

Add print rules when disclosure styling hides content. Test actual printed output.

Check mobile interaction

Long questions can wrap across several lines. Their complete clickable area should remain clear.

Icons must not cover text. Touch targets need usable spacing and predictable activation.

Test narrow screens and enlarged text. Desktop accordion screenshots prove little.

Check search snippets separately

Ordinary search snippets can quote visible FAQ answers. FAQ rich results are different.

Write accurate visible answers for readers. Do not treat snippet selection as guaranteed.

Metadata and page content can influence presentation. FAQPage no longer enables its former feature.

Check indexing controls

A noindexed support page may still help users. Search enhancements remain irrelevant there.

Do not enable FAQ markup to overcome indexing restrictions. Resolve the indexing decision first.

Schema does not override robots controls. It only describes the received page.

Check answer ownership

Every answer should have a responsible subject owner. Legal and billing claims need careful review.

Record review dates for volatile topics. Assign escalation when facts become uncertain.

Content ownership matters without schema. The markup simply adds another copy to verify.

Check analytics carefully

Accordion clicks can reveal reader uncertainty. They do not prove schema performance.

Track question expansion without blocking ordinary interaction. Respect consent and privacy choices.

Use repeated support requests as stronger editorial signals. Improve answers when confusion persists.

Check removal after caching

Disabling schema may leave cached JSON-LD. Page caches and edge caches expire separately.

Purge every relevant layer. Fetch the anonymous public response afterwards.

Search for FAQPage again. Confirm the intended generator truly disappeared.

Know when FAQ schema adds little

Google now provides no FAQ rich-result benefit. Many sites have no other documented consumer.

Ordinary headings or Details blocks can still answer readers. They carry less schema maintenance.

This is the honest weak case. Keep helpful content and remove needless machinery.

Use the FAQ output checklist

1. Confirm FAQ content fits.
2. Separate FAQPage from QAPage.
3. Check current consumer support.
4. Inspect visible questions.
5. Inspect accessible answers.
6. Search for FAQPage markup.
7. Count every generator.
8. Remove conflicting duplicates.
9. Match visible wording accurately.
10. Test keyboard interaction.
11. Test direct answer links.
12. Validate vocabulary syntax.
13. Review translations and caches.
14. Assign policy update ownership.
15. Measure reader outcomes.

Frequently asked questions

The verdict

Core Details blocks can handle simple disclosures. Try free FAQ blocks before paying. Then compare the $299 lifetime suite when several Pro blocks fit maintained sites.