Blog Tools is a WordPress plugin that assembles a toolkit for blogs and company websites from separate modules. It is made by BeeClear, a developer of WordPress plugins and smartphone apps. FAQ schema is one of its modules: it turns the questions a post already contains into structured data. You do not need a separate plugin or a dedicated FAQ block for this. Headings that end with a question mark, each with an answering paragraph below, are all it takes.
Table of contents
- What is FAQ structured data after Google’s changes?
- How does Blog Tools turn question headings into FAQPage?
- How does a definition list become a question and answer?
- What about headings that do not end with a question mark?
- How do you exclude a question, a paragraph or part of an answer?
- How do you switch FAQ data off for a post or a post type?
- Where does the JSON-LD go, and when is it missing?
- Why do you not need a separate FAQ plugin?
- How do you switch on and test FAQ data on your blog?
What is FAQ structured data after Google’s changes?
FAQ structured data describes a page as a set of questions and answers, using the schema.org vocabulary. Its type, FAQPage, holds Question objects with the question text and Answer objects with the reply. The whole thing goes into the page code as JSON-LD, a block of data written in JSON. Google stopped showing expandable FAQ results on 7 May 2026 and removed their documentation on 15 June 2026. The module’s screen says so in a warning.
FAQPage markup is still valid schema.org. Search engines and language models read it when they try to understand a page. What you get is a tidy list of questions and answers for machines, not extra space in the search results. So it pays when this description builds itself, with no copying into a separate field.
How does Blog Tools turn question headings into FAQPage?
Blog Tools turns question headings into FAQPage with one simple rule. A heading of a selected level becomes a question when its text ends with a question mark. The answer is the first paragraph after it, within the same section. By default the module scans H2 and H3, and you can add H4–H6 under “Heading levels”. It reads the content as rendered, so questions coming from blocks and shortcodes count too.
The search for an answer stops at the next heading. A question with no paragraph beneath it therefore never borrows the next one’s text. The paragraph may sit inside a group or a column, unless that container opens a new section with a heading of its own. Anchor links, icons and screen-reader text inside the heading are ignored. An ordinary link in the question keeps its text, including one added by an internal linking tool.
This layout matches good practice for writing for search engines and AI models. The subheading asks a question, and the first sentence of the paragraph answers it straight away. A post written this way yields a complete FAQPage description with no extra work.
How does a definition list become a question and answer?
A definition list becomes a question and answer through the “Definition lists” option, which is on from the start. Each dt element turns into a question, and the dd that follows it becomes the answer. A term without a description is skipped. A question already collected from a heading is not repeated, even if the same text shows up again in the list.
What about headings that do not end with a question mark?
Headings that do not end with a question mark are skipped by default. The “Headings without a question mark” option changes that. Every scanned heading then becomes a question, and a trailing full stop, exclamation mark or colon is replaced with a question mark. The panel advises leaving it off, because Google expects FAQPage entries to be genuine questions and answers. Even in this mode, a heading that is nothing but a link, such as a post card title, is never turned into a question.
The option makes sense on a page that is a list of questions from top to bottom. On an ordinary blog it is better to phrase subheadings as questions wherever a section really answers something.
How do you exclude a question, a paragraph or part of an answer?
You exclude a question, a paragraph or part of an answer with one of three CSS classes placed in the content. In the block editor, add them in the “Additional CSS class(es)” field of the block’s Advanced settings. Each class works at a different level:
| Class | Where to add it | Effect on FAQPage |
|---|---|---|
| faq-question-exclude | a heading | the heading is never treated as a question |
| faq-answer-exclude | a paragraph | the paragraph is skipped and the next one is used |
| faq-answer-part-exclude | any element inside a paragraph | that fragment is dropped from the answer text |
The second class helps when a short lead-in sits under the question and the real answer starts further down. The third removes a remark that only makes sense on the page, such as a pointer to a table. The visible post stays exactly as it was, because the classes affect the structured data only.
How do you switch FAQ data off for a post or a post type?
You switch FAQ data off for a single post in the “FAQ schema” box in the editor. Ticking “Exclude this entry from FAQ structured data” means no FAQPage block is printed on that page. Whole post types are ticked under “Excluded post types”. Those types get no markup at all, and their editor loses the exclusion box.
The “Current state” card sums up the module in one place. It shows the heading levels being scanned, the number of excluded post types and the number of posts excluded one by one. Per-post exclusions survive even when all plugin data is deleted. They are an editorial decision, not configuration.
Where does the JSON-LD go, and when is it missing?
The JSON-LD goes into the page head or the footer, depending on the “Injection position” setting. The footer is the default because it is cheaper. By then the post content has already been rendered once, so the plugin reuses it. In the head the module has to render the content itself, and search engines read both positions equally.
The module runs only on single posts and pages and skips archives. The script appears only when the plugin finds at least one complete question and answer. Nothing is written to the post, because the data is built while the page renders. The exception is a page cache, which you need to clear after changing the module’s settings.
The plugin also keeps the script safe. Slashes in the JSON-LD stay escaped, so a code snippet inside an answer cannot close the block early.
Why do you not need a separate FAQ plugin?
You do not need a separate FAQ plugin because Blog Tools reads the questions straight from the content you write anyway. There is no FAQ block to build, no answers to retype into fields and no two versions of the text to keep in sync. The module outputs structured data only, nothing visible. If you build a visual FAQ yourself, the .beeclear-faq-container, -item, -question and -answer classes listed in the Design panel are there for your CSS.
The module replaced the standalone BeeClear FAQ Schema Generator plugin. While that plugin is still active, Blog Tools stands down, so a page never carries two FAQPage blocks. Per-post exclusions are shared, and the settings move over to Blog Tools once. You can also take the configuration to another site. In “Blog Tools → Import/Export”, tick only the “FAQ schema” group and choose “Export selected”.
How do you switch on and test FAQ data on your blog?
You switch on and test FAQ data on your blog in a few steps, without touching the theme. The module is off after installation. The order is:
- in “Blog Tools → Settings”, switch on the “FAQ schema” feature,
- on the module’s screen, choose the heading levels and where the script is printed,
- under “Excluded post types”, tick the types that should carry no FAQ markup,
- open a post with a question heading and look for a script of type FAQPage in the page source,
- clear the page cache if the script does not show up.
If the script is still missing, check the four things the plugin’s own notes list. The feature must be on, and the post type must not be excluded. The post’s own exclusion box must be clear. And a question heading needs a real paragraph under it, not just an image or a list.
The other modules, from the table of contents to redirects, are described on the Blog Tools plugin page. Each one is switched on separately, just like FAQ schema. If you would like to tidy up the structured data of your whole blog, get in touch.
