FAQs on the Page

What This Page Covers

AIO Radar generates a set of questions and answers for each of your pages. This page is about

getting them onto the page itself: where they come from, the two ways to place them, and what

placing them changes about the structured data your page emits.

Why This Matters

An FAQ that only exists in your machine-readable files is invisible to the assistants that

matter most, because the ones that cite sites fetch the live page. Placing the FAQ is what

turns a generated answer into a citable one.

FAQs Are Never Placed For You

Summaries have an auto-display setting. FAQs do not, and that is deliberate — a block of

questions inserted automatically at the bottom of every page is rarely where you want it, and

it changes the shape of the page far more than a summary paragraph does.

So FAQs appear only where you put them, with the block or the shortcode.

The Block

In the editor, add the AI FAQ block where you want the questions to sit.

The block reads the FAQs already generated for that page, so it shows a placeholder until the

page has some. Generate them from AIO Radar → Content → FAQs, then refresh the editor.

The block's sidebar has one control, Show "FAQ" label, which turns the heading above the

list on and off. It is on by default. Everything else — colours, open or collapsed — comes

from your Appearance settings.

The Shortcode

For the classic editor, page builders, or a template:

[aio_faqs]

[aio_faqs id="42" class="my-faq-section"]

In a theme template:

echo do_shortcode( '[aio_faqs]' );

Placing FAQs From the Admin

The FAQ table at AIO Radar → Content → FAQs → Generated has an On page column. For any

page whose FAQs are not yet placed, Show on page appends the block to that page's content

for you. Pages already carrying the block or the shortcode read Yes.

Where To Put Them

Below the main content, above the footer, is the usual answer. The questions are a supplement

to the page, not its opening.

For a service or product page, placing them directly after the description works well, because

the questions people ask are usually the objections that stop them buying.

Classes and Markup

Whether you use the block or the shortcode, and whichever display mode is set, the markup is

the same skeleton:

<div class="aio-faqs aio-faqs--open">
  <h2 class="aio-faqs-label">FAQ</h2>
  <div class="aio-faq-item">
    <h3 class="aio-faq-question">Do you offer hotel pickup?</h3>
    <div class="aio-faq-answer"><p>Yes…</p></div>
  </div>
</div>

In collapsed mode each .aio-faq-item becomes a <details> and each .aio-faq-question its

<summary>. The block adds a .wp-block-aio-optimiser-faq wrapper around the whole thing.

The full class list, with what each one is for, is in

Appearance.

FAQs and Schema

Placing FAQs on the page is what allows AIO Radar to emit FAQPage structured data for it.

Google's guidelines require the questions and answers to be visible to the visitor, so the

schema follows the placement rather than the generation:

Collapsed mode is fine here. The answers are in the HTML either way; a <details> element is

visible content that happens to start closed.

Troubleshooting

The block shows a placeholder

That page has no FAQs yet. Generate them at AIO Radar → Content → FAQs, then refresh the

editor.

The block renders nothing on the front end

Check the page's serving destination. A page set to machine-only serves its enrichments through

llms.txt and its .md file alone, and the block deliberately renders nothing. See

Serving Destination.

The FAQs look wrong on my theme

Set the colours and the display mode in

Appearance, or target the classes above with Custom CSS.

Related