Should you separate opinions from facts on pages meant for citation
Usually yes, but do it with restraint

Why does separating facts from opinions help AI citation?

AI assistants do not read like careful human editors. They often retrieve short passages, compress them, and restate them in answer form. When a paragraph mixes a hard fact, a strategic recommendation, a caveat, and a rhetorical aside, the model has to infer which part is source truth and which part is your framing. That is where misquotes start.

A cleaner structure gives the model fewer judgment calls. You are not trying to game the system. You are reducing ambiguity. Stable facts should look stable. Opinions should look interpretive. That sounds obvious, but most marketing pages still blend both into one stream of copy.

This matters even more because AI crawlers do not execute JavaScript. The verified server log finding is simple: they fetch JavaScript files and never run them. So if your fact section depends on client rendering, tabs that hydrate late, or toggles that hide the key sentence until a script runs, separation on its own will not save you. The factual block must also be present in the HTML the crawler receives.

What should count as a fact block?

A fact block is the smallest unit on the page that can stand alone without your commentary. It should answer one retrieval need cleanly. Definitions, eligibility criteria, process steps, product capabilities, exclusions, source-backed statements, and dates of change all fit here.

Good fact blocks are boring in a useful way. They are explicit. They use concrete nouns. They avoid throat clearing. They avoid opinion verbs like believe, prefer, or recommend unless the point is explicitly advisory.

• One claim per paragraph or bullet cluster
• Clear subject first, then the assertion
• Visible labels when needed, such as Definition, Requirement, Limitation, or Source note
• No dependency on surrounding paragraphs to understand the sentence
• No hidden key clause buried after an analogy or anecdote

For this site, an example would be stating that Google says llms.txt is not used by Search. That is a fact claim. Another is that a study across about 300,000 domains found 10.13% adoption, zero adoption among the top 1,000 sites, and no citation lift after controls. Those statements belong in a factual section if the page is about llms.txt. Your take on whether it is still worth publishing belongs in the opinion section that follows.

Where should the opinion go?

Near the fact, not miles away. Separation does not mean splitting your site into a sterile database on one side and a thought leadership essay on the other. In practice, the best pattern is factual core first, interpretation second, trade off third.

That keeps the model anchored in the extractable statement while still giving human readers a reason to care. It also protects your voice. Founder pages that sound like legal disclaimers are technically extractable, but strategically weak. Operators want judgment, not just inventory.

If you have to choose, put the burden on the opinion, not the fact. The fact should survive extraction without the opinion attached. The opinion can reference the fact and add your conclusion.

When does this advice fail?

It fails when site authority, originality, or crawl access are the real bottlenecks. I see teams obsess over content formatting when the page is thin, derivative, blocked, or invisible in the first place. Better paragraph hygiene cannot compensate for weak source value.

It also fails when people turn separation into a template religion. If every page starts with a fact matrix, then a note, then a caveat, then a take, the site becomes repetitive and less useful. Models do like consistency, but humans still decide whether your source deserves trust and links.

Another failure case is when the facts themselves are unstable. If your claim changes often, or depends on context not carried in the excerpt, a cleanly extractable sentence can still become a bad citation. In that case, add scope and update cues directly inside the factual statement.

And if your page is mostly opinion by design, do not pretend otherwise. Strategy essays, market commentary, and founder memos are valid page types. They just should not be your main citation targets for factual retrieval.

How should you structure a page without killing the founder voice?

Use a layered structure. Start with the plain answer. Follow with the factual basis. Then add your operator interpretation, limits, and what you would do in the reader's position. This keeps the page quotable without flattening it into encyclopedia prose.

• Open with a direct answer paragraph
• Place one clearly scoped factual section near the top
• Use subheads that signal whether the section is evidence, interpretation, or exception
• Keep caveats close to the claim they qualify
• Reserve stronger opinion language for recommendation sections

This is also where visible copy beats schema folklore. Structured data can help clarify entities and page meaning, but it cannot rescue muddy writing. And after FAQ rich results were fully deprecated on 2026-05-07, a lot of teams lost one of their favorite shortcuts. The practical move now is to make the visible page itself more quote ready.

Who should not follow this advice?

Do not lead with this if your site has obvious crawl and rendering problems, or if your pages are just saying the same thing as ten stronger domains. Fix access, uniqueness, and source quality first. Formatting is a multiplier on substance, not a substitute for it.

You also should not over-separate if your sales process depends on nuanced argument. Some categories need the reasoning attached tightly to the claim because the claim is meaningless without context. In those cases, focus on making each section internally coherent rather than trying to force a hard fact versus opinion split.

If your core problem is outbound execution, this is the wrong site to solve it. We handle managed outbound under Outbound Pros. That work is useful context because we see how demand capture and demand creation interact, but execution detail belongs there, not here.

What is the practical page pattern I would use?

For most citation-targeted pages, I would use a short answer intro, then a factual section with direct language, then a section called what this means or my take, then an explicit limitations section. That last part matters. Honest trade offs are not decoration. They help both trust and retrieval because they define the boundary of the claim.

If you only remember one rule, use this one: make it impossible to confuse what happened, what the source says, and what you think about it. When those are collapsed into one paragraph, assistants paraphrase badly. When they are separated with discipline, citation quality usually improves.