FAQ and HowTo Schema After Google's Changes: Still Worth It for AI?

The short answer: the rich result is gone, the structure is still useful, and the value depends on whether the markup matches real content on the page.

What changed and what did not

Google changed what it displays. It did not change what it parses. FAQPage and HowTo remain valid schema.org types. The markup is read; it just no longer earns the expanded result in a standard search listing.

AI engines are a separate question. None of them has published a statement that FAQPage markup is a ranking or citation signal. What we can say from testing is that pages with clearly delimited question-and-answer pairs tend to be quoted more cleanly, and that the markup is one way to make those pairs unambiguous to a parser.

Why the structure still helps

An answer engine is looking for a chunk of text that directly answers a query. A question as a heading followed by a two-sentence answer is the ideal chunk. FAQPage schema is a machine-readable copy of that same structure: Question objects, each with an acceptedAnswer.

If the visible page already has that structure, the schema is a cheap duplicate that removes any doubt about where one answer ends and the next begins. If the visible page does not have that structure, the schema is describing content that does not exist, and that is where the problems start.

The rule: markup must mirror the page

Every Question in your FAQPage block should correspond to a visible heading or bold question on the page, and every acceptedAnswer should be the text below it. Not a summary, not a longer version, the same text.

If an engine reads the schema and the page and finds two different answers, it has to choose, and the choice is unlikely to favor you. Hidden FAQ markup was a spam pattern before the Google change and remains one after.

HowTo: keep it for real procedures

HowTo markup makes sense when the page is a numbered procedure with discrete steps, each with its own heading and text. Setup guides, recipes, repair instructions. The HowToStep objects give a parser the step boundaries, and tool and supply fields give it the prerequisites.

It does not make sense for a listicle, a conceptual explainer, or a page where the "steps" are marketing stages. If you cannot write the page as "Step 1, Step 2, Step 3" with a clear action in each, do not mark it up as a HowTo.

When to remove it

Remove FAQPage or HowTo markup when any of these is true:

• The questions in the markup do not appear on the page.
• The answers in the markup differ from the visible text.
• The page has more than eight or ten questions and is really a glossary or a support index.
• The markup was generated by a plugin and nobody has reviewed it.

In each case the markup is adding risk and no information.

When to keep or add it

Keep it when the page is a short, focused set of questions a real customer asks, each with a direct answer, and the markup is a faithful copy. Add it to pricing pages, product pages, and comparison pages where three to six specific questions come up repeatedly. Those are the pages most likely to be pulled into an answer, and the ones where a clean question-and-answer chunk pays off.

How we handle it

At AEO GEO Labs we treat FAQ markup as a byproduct of writing answer-ready pages, not a separate task. We write the question headings and answers first, so they read well and are quotable on their own, then generate the schema from that text. The markup cannot drift from the page because it is built from the page.

Check one page

Pick a page with FAQ or HowTo markup. Open the schema and the visible text side by side. If every question and answer matches exactly, you are fine. If not, either fix the page or remove the block. The free answer-ready checker at AEO GEO Labs will show you whether the questions on the page are phrased the way people actually ask them, which matters more than the markup around them.