B2B content fails to earn AI citations for 18 specific, fixable reasons -- not because the writing is bad, but because the page is structured in ways that AI engines can't extract from. ChatGPT, Perplexity, and Google AI Overviews lift answers in 40-60 word chunks from the first paragraph after each heading. If your answer is buried, hidden in JavaScript, missing schema, or stale beyond 13 weeks, you're invisible. This piece names every common mistake, shows you how to detect each one in under five minutes, and gives you the fix.
Why is my B2B content not being cited by ChatGPT or Perplexity?
Your content isn't being cited because of structural mistakes that block extraction, not because of writing quality. AI engines don't read pages the way humans do -- they retrieve, then extract specific 40-60 word answers under each heading. According to the Princeton GEO study, adding statistics boosts citation rate ~30%, expert quotes ~41%, and inline citations ~30%. None of that helps if the answer is below word 400, hidden in a tab, or missing schema.
The 18 mistakes below come from three buckets: content structure (how the answer is presented), technical extraction (whether AI crawlers can access it), and authority signals (whether the page looks trustworthy enough to cite).
Fix mistakes 1-6 first -- they're the highest-leverage and lowest-effort. Then move to the technical layer. Each section includes a one-line detect step and a one-line fix.
Mistake 1: Burying the answer past word 100
The problem: AI engines extract the first 40-60 words after each H2. If you open a section with context-setting ("Before we discuss X, let's review the history of Y..."), the model lifts the wrong sentence and skips you for a competitor who answered first.
90% of top-cited sources answer the page's core question within the first 100 words, per Stridec's 2026 AEO content structure analysis. AI Overviews specifically prefer pages that match search intent in the opening lines.
| Detect | Fix |
|---|---|
| Read your first paragraph aloud. Did you answer the H1 question? | Rewrite paragraph 1 so sentence 1 = subject + verb + direct answer. |
Apply the same rule to every H2 section. Each section opens with a 40-60 word answer, then expands. Treat the first sentence after every heading as a standalone, extractable unit.
Mistake 2: No TL;DR or summary box at the top
The problem: Pages without a structured TL;DR force AI engines to construct one. They often build a worse version than you would have, or they cite a competitor whose summary is cleaner.
The TL;DR is the single highest-leverage AEO element. ChatGPT and Perplexity preferentially extract from clearly-bounded summary blocks because they look like ground truth: short, declarative, no hedging. According to Frase.io's 2026 AEO analysis, a structured summary in the first viewport is one of the strongest extraction signals an AI engine sees.
| Detect | Fix |
|---|---|
| Open your page. Is there a visible TL;DR / Key Takeaways box above the fold? | Add a 50-70 word summary + 3-5 bullets (≤25 words each) directly under the H1. |
Don't bury it under an image. Don't put it inside a collapsed accordion. Plain HTML, top of page, marked up with semantic structure.
Mistake 3: Cute or clever H2s instead of question-shaped headings
The problem: "The Hidden Truth Behind X" doesn't match how anyone queries an AI engine. "What is X?" and "How does X work?" do. AI engines weight H2 text heavily when matching content to queries.
Question-shaped H2s are how users actually phrase prompts to ChatGPT, Perplexity, and Gemini. When your H2 mirrors the prompt verbatim, the model treats your section as a high-confidence answer candidate. Clever copywriter headings actively harm AEO -- they force the model to do semantic translation, and competitors with literal headings win.
| Detect | Fix |
|---|---|
| Read each H2. Could a person literally type it into ChatGPT? | Rewrite every H2 as a question: "What is...", "How do I...", "When should I...", "Why does..." |
Look at People Also Ask, Reddit thread titles, and Quora to find the exact phrasing real humans use. Match it. The slight loss in editorial flair is worth a multiple in citation rate.
Mistake 4: Walls of text with no bullets, tables, or short paragraphs
The problem: Long, dense paragraphs are hard for LLMs to chunk into extractable units. Bullets, numbered lists, and tables parse cleanly. According to GenOptima's 2026 listicle research, AI search engines cite listicle-formatted pages at 5x the rate of standard blog posts.
AI engines prefer content that's pre-segmented for them. A 6-row markdown table beats three paragraphs of comparison prose every time. A numbered 5-step list beats a flowing how-to narrative.
| Detect | Fix |
|---|---|
| Scroll the page. Are there paragraphs longer than 4 lines? Lists fewer than 1 per H2? | Break paragraphs to 2-3 lines. Add at least one list or table per major section. |
Where comparison data exists, use a table. Where steps exist, use a numbered list. Where features or items exist, use bullets. Prose should connect structured elements, not replace them.
Mistake 5: Hedged, indirect language
The problem: "X may potentially sometimes help with Y" is invisible to AI engines. They prefer confident, declarative sentences because those are easier to extract as factual claims without inheriting your hedging.
LLMs are trained to output high-confidence answers. When they see hedged source content, they either skip it or strip the hedges, which can hallucinate certainty you didn't intend. The fix is to write declarative claims and let the citation handle qualification ("X works in 73% of cases" not "X may sometimes work").
| Detect | Fix |
|---|---|
| Search your page for: "may", "might", "could potentially", "sometimes", "often". Count them. | Rewrite half. Replace hedges with specific numbers, conditions, or named exceptions. |
Subject + verb + object. "AEO requires schema markup." Not "AEO can sometimes benefit from schema markup implementation." The first version gets cited. The second one doesn't.
Mistake 6: "Studies show" with no source, no number, no year
The problem: Generic claims without citations look like content-farm spam to AI engines. They cite pages that cite their sources, because grounding chains build trust.
The Princeton GEO study (Aggarwal et al., 2024) tested this directly: adding inline citations to research, statistics with named sources, and quotes from named experts increased citation visibility 30-41%. "Research shows" with no source is worse than no claim at all -- it's a negative signal.
| Detect | Fix |
|---|---|
| Ctrl-F for "studies show", "research suggests", "experts agree". Each is a leak. | Replace with: "According to Source Name (Year), X is Y." Hyperlink the source. |
Name the company. Name the study. Name the year. Hyperlink to the original. If you can't, delete the claim. AI engines parse linked citations as confidence multipliers.
Mistake 7: Why does content behind tabs and accordions not get cited?
Content inside JavaScript-rendered tabs, accordions, or click-to-expand FAQs is often invisible to AI crawlers because most LLM crawlers don't execute JavaScript. According to Search Engine Journal's analysis of AI rendering, ChatGPT, Perplexity, and Claude rely on static HTML and plain-text visibility -- they don't click anything.
If your FAQ section is a React accordion that injects answers into the DOM only after a user clicks, AI engines see your questions but never your answers. You're publishing the worst possible content from an AEO perspective: a teaser without the substance.
| Detect | Fix |
|---|---|
| View page source (not DevTools). Search for your FAQ answer text. Missing? It's hidden. | Render FAQs as static HTML. Use <details>/<summary> if you want collapsibility. |
The <details> element is fully rendered in source HTML and parses cleanly for both AI crawlers and screen readers. Avoid React/Vue accordions that inject content via JS for any text you want cited.
Mistake 8: How does pagination affect AI citation extraction?
Pagination splits a single article across multiple URLs (page 1, page 2, page 3), which fragments AI extraction. The model retrieves one page at a time and rarely follows pagination links, so the answer on page 2 is effectively orphaned from the question on page 1.
According to INSIDEA's 2026 AEO pagination analysis, paginated articles consistently underperform single-URL equivalents in AI citation tests because LLMs treat each page as an isolated document. The same applies to infinite scroll where content loads only after scroll events fire.
| Detect | Fix |
|---|---|
| Does your article use ?page=2 or /part-2/? Does content load on scroll? | Consolidate to a single URL with anchor links. Render lazy-loaded content in initial HTML. |
Use a table of contents with in-page anchors instead of splitting pages. If you must paginate (large product catalogs),use rel="canonical" to consolidate, and ensure each paginated URL has unique self-contained value.
Mistake 9: Does blocking GPTBot in robots.txt hurt AI citations?
Blocking GPTBot rarely stops AI citations but reliably costs you traffic -- the worst possible trade. According to BuzzStream's March 2026 study of 4 million citations across 3,600 prompts, CNBC blocks ChatGPT-User, GPTBot, and OAI-SearchBot but still appeared 1,298 times in the citation dataset. Roughly 95% of cited pages blocked GPTBot or Google-Extended.
Why? AI retrieval often pulls SERP-level snippets and titles directly without fetching the underlying page. Blocking the crawler doesn't block the citation. Meanwhile, Adobe's LLM Optimizer data shows publishers blocking AI crawlers experienced a 23.1% total traffic decline and 13.9% drop in human-only browsing.
| Detect | Fix |
|---|---|
| Check yoursite.com/robots.txt for GPTBot, ClaudeBot, OAI-SearchBot, PerplexityBot disallows. | Allow them unless you have a specific licensing strategy. Remove blanket blocks. |
See our deeper guide on robots.txt configuration for AI crawlers for the full bot allowlist.
Mistake 10: Image-only data with no text equivalent
The problem: Charts, infographics, and screenshots without text alternatives are invisible to AI engines. They can't extract pixels. If your unique data lives only in a PNG, your competitors who transcribed similar data into a table will outrank you for it.
AI engines specifically reward original statistics with named numbers, but only if those numbers are in extractable text. According to Quoleady's 2026 study of 10,000 LLM citations, pages with proprietary data presented in HTML tables were cited dramatically more often than pages with the same data in image form.
| Detect | Fix |
|---|---|
| For each image with data, is the same data also in HTML text on the page? | Add a markdown table or bullet list reproducing every key number from each chart. |
Use alt text for accessibility, but don't rely on it for AEO -- alt text isn't where extraction happens. Put the actual numbers in the body, then use the image for visual reinforcement.
Mistake 11: Missing or shallow schema markup
The problem: Pages without proper structured data forfeit a major citation advantage. According to Metrics Rule's 2026 RAG citation analysis, pages with complete author markup, datePublished, dateModified, and comprehensive schema achieve 54.2% citation rates vs 31.8% for generic or minimal schema.
FAQPage schema specifically increases AI Overview citation probability by over 20% according to Frase.io's 2026 schema research. FAQPage matches AI's question-answer format perfectly. Article + ItemList + FAQPage stacking is the strongest combination for content like this article.
| Detect | Fix |
|---|---|
| Run your URL through Google's Rich Results Test. What's flagged? | Add Article + FAQPage + (ItemList for listicles) + Organization site-wide. |
See our schema markup for AI search guide for ready-to-paste JSON-LD templates. Don't ship a content page without these three schemas.
Mistake 12: Stale or missing dateModified
The problem: AI engines weight recency heavily, and a missing or stale dateModified makes your page look abandoned. According to the 13-Week Rule analysis (Rank & Convert, 2026), 50% of AI citations come from content less than 13 weeks old.
ChatGPT shows the most aggressive recency bias: 76.4% of its most-cited pages were updated within the last 30 days. Perplexity is similar -- roughly 50% of its citations come from current-year content. A page updated within 30 days receives 3.2x more AI citations than identical content from six months ago.
| Detect | Fix |
|---|---|
View page source. Is there a <meta> or schema dateModified field? Is it within 90 days? |
Add dateModified to schema. Set up a 13-week refresh calendar for priority pages. |
Warning: Don't bump the date without changing the content. Google explicitly identifies artificially inflated modification dates as manipulation. Refresh statistics, add new sections, update for the current year -- then update the date.
Mistake 13: Does AI-generated content rank in AI search?
AI-generated content with zero original data, examples, or expert input rarely earns citations -- AI engines filter approximately 95% of retrieved content before answer generation, and generic AI prose is the first thing filtered. According to Search Engine Journal's 2026 AEO analysis, AI cites content that's "unique enough to be uncopyable": original research, proprietary data, specific numbers no one else has, and experience-backed POV.
Generated content paraphrased from competitors fails on every dimension. It has no proprietary data, no novel POV, and often hallucinated statistics with no source. AI engines deliberately downweight content that looks generated to avoid feedback loops.
| Detect | Fix |
|---|---|
| Does the page contain any original number, quote, screenshot, or framework not on 5+ other sites? | Add proprietary data: customer interviews, internal benchmarks, original survey results, or expert quotes. |
Use AI for first drafts, but every published page needs at least one element a human had to create: original research, named expert input, proprietary screenshots, or genuinely novel synthesis. Generic AI prose gets filtered.
Mistake 14: No author markup or expert credentials
The problem: Pages with no named author, no bio, and no E-E-A-T signals look like content-farm output. AI engines explicitly downweight unattributed content, especially for YMYL topics (finance, health, legal, B2B SaaS where decisions matter).
According to Metrics Rule's RAG confidence weighting research, pages with full author markup (name, role, credentials, sameAs links to LinkedIn) achieve significantly higher citation probability than anonymous content. The author becomes part of the trust chain the model uses to rank citations.
| Detect | Fix |
|---|---|
Does your page show a real author name with a credentialed bio? Does schema include author? |
Add Person schema with name, jobTitle, sameAs LinkedIn/X, knowsAbout topics. Show a visible bio. |
Ghost-bylines ("Editorial Team") work for news but actively hurt B2B SaaS content. AI engines reward Person > Organization > Anonymous. Make your subject-matter experts the bylined authors.
Mistake 15: No third-party co-mentions or Reddit presence
The problem: AI engines weight "co-mentions" -- pages on other sites that reference both your brand and the topic. Pages with strong third-party mentions get cited far more than equally good content with none. Perplexity specifically pulls 46.7% of its citations from Reddit, per tryProfound's platform citation patterns analysis.
Social and Reddit content earns 2.5x more AI citations than owned brand pages. If your AEO strategy is publish-and-pray on your own blog, you're missing more than half the citation surface.
| Detect | Fix |
|---|---|
| Search Reddit, Hacker News, Indie Hackers for your brand + topic. Count results. | Earn 5-10 third-party mentions per priority page: substantive Reddit comments, podcast mentions, guest posts, doc references. |
Don't link-drop. Post substantive answers in r/SaaS, r/SEO, r/marketing where the question is genuinely being asked. ChatGPT and Perplexity both index these threads aggressively. Wikipedia and Wikidata entries for your company also materially improve grounding.
Mistake 16: Moving URLs and breaking canonical stability
The problem: When you move a page, AI training data freezes the old URL. Citations from existing model snapshots point to a 404 or redirect, and your authority resets. Stable canonical URLs are an AEO requirement, not a nice-to-have.
LLMs are retrained on rolling crawls, but citation memory persists between training cycles. A page that's been at the same URL for two years carries cumulative citation weight that a freshly-moved equivalent doesn't. Frequent slug changes during "SEO migrations" can wipe AEO authority overnight.
| Detect | Fix |
|---|---|
| Has the URL of your top content page changed in the last 12 months? Multiple times? | Lock canonical URLs. Use 301s only when absolutely necessary. Never restructure for cosmetic reasons. |
If you must migrate, do it once, do it cleanly, and maintain 301 redirects forever. Don't iterate on URL structures. The citation cost compounds.
Mistake 17: Letting content go stale beyond 13 weeks
The problem: Half of all AI citations come from content less than 13 weeks old. If your top pages haven't been touched in six months, you're losing citation share to fresher competitors regardless of content quality.
The 13-Week Rule research (Rank & Convert, 2026) found that 50% of AI citations come from content under 13 weeks old, and ChatGPT specifically pulls 76.4% of its top citations from pages updated in the last 30 days. Static "evergreen" strategy is now an AEO liability.
| Detect | Fix |
|---|---|
| List your top 20 pages by importance. When was each last meaningfully updated? | Build a 13-week refresh calendar. Update statistics, add new sections, refresh the dateModified. |
Meaningful updates only -- new data, new examples, new sections. Don't bump the date with cosmetic edits. Plan refresh as a recurring workstream, not a one-time project. The pages you neglect today are the citations you'll lose next quarter.
Mistake 18: Optimizing for keywords instead of question intent
The problem: Targeting "AEO best practices" (a keyword) misses how users actually ask AI engines ("why am I not cited by ChatGPT?"). AEO traffic is largely invisible in keyword tools because users phrase prompts as full natural-language questions, not 2-word fragments.
According to HubSpot's AEO metrics analysis (2026), 70.6% of AEO-driven traffic arrives as "Direct" in analytics because AI referrers strip query parameters. Optimizing for keyword volume catches none of this. You have to optimize for the question itself.
| Detect | Fix |
|---|---|
| Are your H2s keyword fragments or full questions? | Convert every H2 into the literal question a buyer would type into ChatGPT. |
Use Reddit, AnswerThePublic, and ChatGPT itself to find the exact question phrasings. Then make each H2 a verbatim match. The keyword research tools you've used for a decade are the wrong instrument here. Watch how real humans phrase prompts and mirror them.
How do I audit my pages for these AEO mistakes?
Run a 30-minute audit using this checklist on your top 10 pages:
- Above the fold: Is there a TL;DR + visible direct answer in first 100 words?
- H2 audit: Is every H2 a literal question a person would ask ChatGPT?
- View source: Search for your FAQ answers in raw HTML. Are they there?
- robots.txt check: Does it block GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot?
- Schema check: Run Google Rich Results Test. Article + FAQPage + ItemList present?
- dateModified: Is it within 90 days? Has the content actually been updated?
- Citations: Does every "studies show" claim have a hyperlinked source?
- Author markup: Named author with credentials and sameAs LinkedIn?
- Co-mentions: 5+ third-party references on Reddit, podcasts, or guest posts?
- URL stability: Has this URL been stable for 12+ months?
Score each page out of 10. Anything below 7 is bleeding citations. Use our full AEO audit checklist for the 50-point version with priority weighting.
| Mistake | Category | Detect in <5 min | Fix difficulty |
|---|---|---|---|
| 1. Buried answer past word 100 | Structure | Read paragraph 1 aloud | Easy |
| 2. No TL;DR box | Structure | Check above the fold | Easy |
| 3. Cute H2s instead of questions | Structure | Could a user type each H2 into ChatGPT? | Easy |
| 4. Walls of text, no lists or tables | Structure | Count lists per section | Easy |
| 5. Hedged language | Structure | Ctrl-F: may, might, sometimes | Easy |
| 6. Studies show with no source | Structure | Ctrl-F: studies show, research suggests | Easy |
| 7. FAQs in JS tabs/accordions | Technical | View source, search for answer text | Medium |
| 8. Paginated articles | Technical | Check for ?page= URLs | Medium |
| 9. Blocking GPTBot in robots.txt | Technical | Check /robots.txt | Easy |
| 10. Image-only data | Technical | Are numbers in HTML text? | Easy |
| 11. Missing schema markup | Technical | Run Rich Results Test | Medium |
| 12. Stale or missing dateModified | Technical | Check schema dateModified field | Easy |
| 13. AI content with no original data | Authority | Find one number unique to your page | Hard |
| 14. No author markup | Authority | Is there a named author + bio? | Easy |
| 15. No third-party co-mentions | Authority | Search Reddit + HN for brand + topic | Hard |
| 16. URL instability | Authority | Has URL changed in 12 months? | Easy |
| 17. Stale content beyond 13 weeks | Authority | When was last meaningful update? | Medium |
| 18. Keyword instead of question intent | Authority | Are H2s questions or fragments? | Easy |