All posts
Guide

Should you keep citation worthy facts out of expandable FAQs?

By Janis Plume, Founder, Outbound Pros · 8 min read · 2026-10-17

Quick answer

Yes, usually. Do not hide citation worthy facts only inside expandable FAQs. Put the fact in normal body copy, close to its qualifier, on the canonical page you want cited. Then use the FAQ as reinforcement, not as the only location. This matters because extractability beats clever UI. If the accordion fails to load cleanly, is buried under boilerplate, or separates caveats from claims, assistants can quote the wrong thing or skip it entirely.

Why are expandable FAQs risky for citation worthy facts?

Expandable FAQs are a presentation pattern, not a retrieval strategy. They can work, but they add failure points between your fact and the model trying to extract it. If the statement you want cited lives only behind a collapsed interface, you are betting that every crawler, parser, summarizer, and answer composer interprets that interface cleanly and keeps the qualifiers attached.

That is not a bet I would make for high value facts. If a claim affects buying decisions, compliance, product expectations, implementation effort, or competitive positioning, put it in plain visible copy first. Use the FAQ to restate it in question form for humans who scan.

This is even more important on JavaScript heavy builds. We have one verified anchor here that matters a lot: AI crawlers do not execute JavaScript, they fetch JS files and never run them. So if your accordion content depends on client side rendering to appear, the crawler may fetch the assets and still never see the final expanded content.

If your site still leans on client side disclosure patterns for important content, read Do AI crawlers execute JavaScript or only fetch files.

When do FAQs help instead of hurt?

FAQs help when they are a second copy of an already clear fact, not the first or only copy. They are good for reducing friction after the core statement is already present in the page intro, comparison table, specification block, policy section, or definition paragraph.

  • Use FAQs to restate a fact in customer language after the formal statement appears elsewhere.
  • Use FAQs to capture adjacent intent, where the answer repeats the canonical fact without changing wording.
  • Use FAQs when the accordion content is server rendered and present in the HTML source.
  • Use FAQs for nuance and exceptions, if the main claim is already stated plainly above.

The mistake is treating the FAQ as the content layer instead of the interface layer. Operators do this because FAQs feel tidy. They let teams hide complexity, legal caveats, and awkward exceptions. That is fine for design. It is not fine for retrieval.

There is another reason not to over invest in FAQ packaging. FAQ rich results were fully deprecated and stopped appearing on 2026-05-07. So the old search playbook of shoving every important statement into an FAQ because the SERP might reward it is gone. Today the value of an FAQ is mostly usability and intent matching, not search decoration.

What should live in visible body copy first?

Anything you would be unhappy to see misquoted should live in visible body copy first. That includes definitions, limitations, prerequisites, exclusions, supported integrations, geographic availability, implementation dependencies, and the current version of a policy or process.

My rule is simple. If a sales rep would read the sentence out loud on a call, it deserves a stable home outside an accordion. AI assistants prefer clean, direct extraction targets. A normal paragraph or list item is easier to parse than content hidden behind interaction patterns, repeated across many templates, or separated from its context.

Content typeBest placement
Canonical product or policy factVisible paragraph near the top of the page
Qualifier or exceptionIn the same sentence or immediately after the claim
DefinitionVisible body copy or definition block
Comparison pointVisible table plus short explanatory copy
Repeated customer phrasingFAQ after the canonical statement
Edge case exampleFAQ or supporting section below the main answer

Notice the pattern. The more important and quote sensitive the statement, the closer it should sit to the main body copy. The FAQ can still exist, but it should not be carrying the whole factual burden by itself.

What breaks when a fact lives only inside an accordion?

Several things break. Sometimes nothing technically breaks, but enough ambiguity is introduced that the assistant pulls a shorter, worse version from somewhere else. That is the operator problem. You do not need a total failure for performance to degrade. You only need a competing source that is easier to quote.

  • The accordion content may be injected client side, which some AI crawlers will not execute.
  • The claim may be visible only after interaction, which creates extraction inconsistency.
  • The qualifier may sit in a different FAQ item from the main claim, so the model detaches them.
  • The same FAQ template may repeat across many pages, diluting which URL is truly canonical.
  • A third party page may summarize your fact more cleanly than you do, and get cited instead.

That last point matters more than most teams realize. Vendor sites often lose citations not because their information is wrong, but because it is harder to extract cleanly than an aggregator, reviewer, or implementation guide. If your own source hides the best facts in UI patterns while a third party writes them plainly, you are helping the middleman win.

That dynamic is worth understanding in more depth. See why AI assistants cite aggregators over original sources.

Should you ever leave important facts in an FAQ anyway?

Yes, sometimes. There are two reasonable cases. First, when the page intent is genuinely question led and the FAQ is the natural reading flow, but the answers are still rendered in the initial HTML. Second, when the fact is secondary support, not the primary canonical statement.

For example, a product page can state the core integration requirement in visible copy, then answer a practical follow up in an FAQ. A policy page can state the current rule in body copy, then use the FAQ to explain how archived versions differ. That is a good split between canonical fact and support detail.

What you should not do is tuck the main truth into a collapsed widget because design wants a cleaner page. Clean for humans can become invisible for machines.

A simple operating rule

If removing the FAQ would remove the only precise version of the claim, your content structure is wrong.

How should you rewrite pages that already hide key facts in FAQs?

Do not start by deleting the FAQs. Start by promoting the best facts out of them. Pull the canonical statement into the body copy, then keep the FAQ if it still serves readers. This is usually a content surgery job, not a redesign job.

  • Find every FAQ answer that contains a claim you want repeated accurately.
  • Choose the one URL that should own that fact.
  • Move the cleanest version of the statement into visible body copy on that URL.
  • Keep the qualifier in the same sentence or immediately after it.
  • Leave the FAQ version only if it repeats the same meaning without drift.
  • Check that the answer exists in the server rendered HTML, not only after interaction.

This also helps with governance. Once the canonical sentence exists in body copy, updates become easier. Teams can revise the source statement first, then decide whether the FAQ still needs a matching restatement. That is much safer than maintaining several accordion answers that drift over time.

If you are tempted to solve this with llms.txt, do not. Google states llms.txt is not used by Search, and a large study found low adoption and no citation lift after controls. Publish it if you have a narrow operational reason, but do not use it as a substitute for better on page fact placement.

We covered that trade off directly in Should you publish llms.txt or ignore it.

Who should not follow this advice too literally?

Teams with very dense technical documentation should not flatten every FAQ into always open body copy. That can make pages harder to scan and worse for users. The goal is not maximum visible text. The goal is making the citation worthy sentence easy to extract in its canonical location.

You also should not force every edge case into the top of the page. If a rare exception interrupts the main answer, keep the main claim clear and place the exception immediately after or in a nearby support section. Over optimizing for machine extraction can make writing stiff and unnatural. That backfires too.

And if your issue is not accordion structure but weak authority, this advice will not save you by itself. Clean extractability helps, but it does not override poor sourcing, inconsistent claims across the site, or low trust compared with stronger third party sources.

One more boundary. This site focuses on demand capture and AI visibility. If your real problem is outbound execution, list building, or multichannel prospecting, that belongs on the sibling properties, especially Outbound Pros. Different motion, different playbook.

My operator conclusion is straightforward. Keep your best facts in the open. Let FAQs support, not carry. If a statement deserves to be cited, give it a stable visible home, keep its caveat attached, and make sure the page can be read without running JavaScript.

Common questions

Can AI assistants read content inside accordions?

Sometimes, yes. But you should not rely on that for critical facts. If the content depends on client side rendering or if the claim and caveat are separated across items, retrieval quality drops.

Should I delete all FAQs from important pages?

No. Keep FAQs when they help users scan, answer adjacent questions, or restate a fact already made clear in visible copy. The problem is facts living only there.

Does FAQ schema fix this problem?

No. FAQ rich results were deprecated, and schema does not replace clear visible copy. Use visible text as the source of truth.

What is the safest placement for a citation worthy fact?

Put it in normal body copy on the canonical URL you want cited, with the qualifier in the same sentence or immediately after it.

What if my design team wants a cleaner page with more collapsed sections?

Compromise by keeping the key sentence visible and collapsing only supporting detail. You do not need to expose every paragraph, only the facts you most need quoted accurately.

Last updated: 2026-10-17

Talk through your AI visibility with people who measure it

30 minutes. We will look at what assistants can actually retrieve from your site and tell you plainly what is worth fixing first.

Book a strategy call

30 minutes, no obligation. The calendar shows real availability.

Or start with the free GTM audit from Outbound Pros