Does Elementor Have FAQ Schema? Yes. Here’s the Problem

Everyone in marketing right now is talking about FAQ schema. Add it to your site. Structure your content. Make it easy for AI engines to find you.

They’re. FAQ schema does matter for AI visibility. But if you built your site on Elementor and you toggled on the FAQ schema option thinking you had it covered, there is something worth knowing.

Does Elementor support FAQ schema?

Yes. Elementor has a built-in FAQ widget with a schema toggle. You enable it and it generates structured data in the background, and on paper your FAQ content is marked up and readable by search engines and AI engines.

That is the theory.

So what’s the problem?

There is a known bug in how Elementor renders FAQ schema. When crawlers read the structured data, the field that should contain your actual answer text is often empty. The accordion looks perfect to anyone visiting your page. The structured data that AI engines read has a blank where your answer should be.

Elementor’s support team has acknowledged the issue. It is tracked on GitHub. There is no confirmed fix date. It has been ongoing since early 2025.

There is a wrinkle worth knowing about. Elementor now enables element caching by default in its Performance settings. That caching interferes with how FAQ schema renders. So the closest thing to a workaround Elementor currently offers is: turn off the thing we turned on. That is where the bug stands as of 2026.

How would I know if I’m affected?

Check Google Search Console under Enhancements. If you have FAQ schema errors listed, specifically anything referencing a missing field in acceptedAnswer, that is the bug.

If you have not checked, and you have an Elementor FAQ widget on any page with the schema toggle enabled, there is a reasonable chance the error is there.

Is there a second problem with Elementor FAQ?

Yes – and I’m glad you asked! 😁 If you have more than one FAQ accordion on a page and you have enabled schema on each one, Elementor generates a separate schema block for each widget. Search engines expect one FAQ schema block per page. Multiple blocks trigger a duplicate error, and duplicate errors mean the schema is disregarded entirely.

So you can have the bug, the duplicate problem, or both. None of them are visible to a human visitor. All of them are visible to crawlers.

Does FAQ schema actually matter for AI search?

More than it used to. When someone asks ChatGPT or Gemini to recommend a coach, or asks what to look for when hiring one, those are FAQ-shaped questions. If your FAQ schema is working correctly, you have structured, citable answers already in place. AI engines can extract them directly and use them in responses.

If your schema is broken, you have a page that looks thorough to a human visitor and says almost nothing to an AI engine.

The coaches showing up in AI responses are not always the ones with the most content. They are often the ones whose content is structured in a way AI engines can actually read and use.

Should I add FAQ schema manually?

You can. Properly written FAQ schema in JSON-LD format, added independently of Elementor’s widget, bypasses the bug entirely. It requires a little technical confidence but it is not complicated once you understand the structure.

The other option is to use a tool that handles FAQ schema as part of your overall business structured data, outside of Elementor’s implementation. StructuredAF does this: your FAQ schema is delivered independently of your page builder, which means Elementor’s bug is not your bug.

We are, obviously, not a neutral party in that recommendation.

What should I do right now to fix my FAQ schema?

Three things, in order.

Check Google Search Console for FAQ schema errors. If they are there, you will see them clearly under Enhancements.

If you find errors, disable the schema toggle on your Elementor FAQ widgets. You can also try disabling element caching in Elementor’s Performance settings, which is the workaround Elementor currently points to. Whether that resolves it depends on your setup. A widget with no schema claim is less harmful than a widget generating broken schema claims.

Then decide how you want to replace it: manual JSON-LD added independently of Elementor, or a tool that handles schema outside of your page builder entirely.

If you want to see what AI engines currently understand about your business overall, the free tool at structuredaf.com/free takes about two minutes and does not require any technical knowledge.

Elementor is excellent at what it does. Layout, design, visual structure: it handles all of that well. Schema is a different job. It is infrastructure, not design. Mixing the two is how coaches end up wondering why AI engines have never heard of them.

The FAQ schema conversation is worth having. Just make sure yours is actually working before you tick the box.