Serving Destination

What Serving Destination Controls

AIO Radar can publish generated summaries and FAQs in two places: on the page itself

(visible to a human visitor) and in your machine channels (llms-full.txt and each

page's .md file). Serving destination decides which of those a given summary or FAQ set

actually appears in.

Set the site-wide default at AIO Radar → Settings → Content, and override it per page

in the post editor.

The Three Options

Why This Matters

Answer engines fetch your live page, FAQ rich results need visible text, and no major AI

provider has confirmed it reads llms.txt — so keep summaries and FAQs on the page, not just

in your machine files. Machine-only isn't cloaking (the same content sits at its own

disclosed URL), but it leaves that reach on the table.

The Three Reasons, in Full

Overviews read your actual HTML page when they answer a question about you — not just

your llms.txt or llms-full.txt. Content that exists only in a machine file is

invisible to them.

from FAQ content a visitor can actually see on the page. An FAQ that's machine-channel

only can never earn that placement.

it reads llms.txt or llms-full.txt at all. It's a disclosed, good-faith channel — not

a guaranteed one.

Put together: on-page is where the guaranteed reach is. Machine channels are a genuine

addition on top of that, not a substitute for it.

Why Machine-Only Isn't Cloaking

Cloaking is showing search engines or bots different content than you show a human at the

same URL. Serving a summary only through llms-full.txt or a page's .md file isn't

that: the same content is published at its own disclosed URL, openly, to anyone who

requests it — a browser, a script, a bot, or a curious visitor who types /llms-full.txt

into their address bar. Nothing is swapped at the human-facing URL, ever. See

ADR 0005

for the full no-cloaking rule this product follows.

Machine-only is a legitimate, disclosed choice — for content you deliberately don't want

cluttering the page, for instance. It's just weaker for AI visibility than putting the same

content on the page too, for the three reasons above.

Changing the Default

AIO Radar → Settings → Content → Serving destination sets the site-wide default for

new summaries and FAQs. Existing content keeps whatever destination it was generated with

until you change it.

Overriding a Single Page

Open the page in the editor and use the Serving destination field in the AIO Radar

metabox. Choose Inherit site default to fall back to the site-wide setting, or pick one

of the three destinations to override it for that page only.

Troubleshooting

A Summary Isn't Showing on the Page

Check that page's serving destination override isn't set to Machine channels only —

that's working as configured, not a bug.

FAQ Rich Results Aren't Appearing

Rich results depend on the search engine choosing to show them, not just eligibility — but

first confirm the FAQ is set to a destination that includes on page; a machine-only FAQ

is never eligible.