What AI Crawlers See – and What They Don't
Much of what is considered standard in everyday SEO is invisible to LLMs in conversation mode. The new Writesonic Study 2026 analyzed six major LLM crawlers (ChatGPT, Claude, Gemini-Conversation, Perplexity, Bing Copilot, Google AI Overviews) and confirms: all content must be delivered in a way that remains understandable without JavaScript, without extensive scrolling, and without metadata in the head.
The Three Crawler Tiers (HTML-only / Headless / Full-Browser)
A simple grid helps with classification, where today's LLM crawlers mostly fall into Tier 1–2:- Tier 1: HTML-only Parser – read static HTML, follow links to a limited extent, do not execute JavaScript, do not scroll.
- Tier 2: Headless Light – can parse HTML more robustly, take individual fallbacks (e.g.,
- Tier 3: Full-Browser – execute JavaScript and complex rendering and scroll. However, behaviors from Tiers 1–2 dominate in the study.
What All 6 LLMs Reliably See — and What Not
The Writesonic tests reveal clear patterns:- 3 out of 6 LLMs do not execute JavaScript. JS-only content (SPAs, client-side injected reviews, lazy-load content) remains invisible.
- 0 out of 6 LLMs read JSON-LD in live conversation mode. Important: JSON-LD remains relevant for the Google search index – two different worlds.
- 0 out of 6 LLMs read meta descriptions or OG tags in conversation mode.
- 5 out of 6 LLMs reliably read the
tag. It is thus the most important head element for LLM-read.</li> <li>0 out of 6 LLMs scroll. Content "below the fold" and lazy-loaded images/text blocks are ignored.</li> <li>4 out of 6 LLMs read <noscript> fallbacks.</li> <li>CSS-hidden content (e.g., display:none, accordions) is visible; ::before/::after pseudo-content is invisible.</li> <li>Microdata in the body is read better than JSON-LD in the head.</li> </ul> <h2>Title Tag is the New Gold — Practical Recommendation</h2> If 5 out of 6 crawlers reliably read the title, it becomes the central lever. Recommendations: <ul><li>Precise, information-dense, under 60 characters; avoid empty phrases.</li> <li>Structural suggestion: Primary topic | specific benefit | brand.</li> <li>Vary by page type (category, product, guide), but keep terminology consistent.</li> <li>Place the strongest terms first; brand name at the end, unless there is strong brand demand.</li> <li>Synchronize H1 and title semantically without blind copying: The title condenses, the H1 explains.</li> </ul> <h2>JSON-LD is Not Dead, but Microdata Wins in LLM-Read</h2> The study shows: In conversation mode, JSON-LD is not read, whereas Microdata in the body tends to be. Action recommendation: <ul><li>Keep JSON-LD for the search index (products, FAQs, organization, breadcrumbs).</li> <li>Mirror critical facts as Microdata directly in the visible body (prices, availability, ratings), content-identical to the JSON-LD.</li> <li>Avoid contradictions between structured data and visible text.</li> <li>Use semantic HTML elements (article, header, nav, main, footer) to cleanly structure the body content for parsers.</li> </ul> <h2>Lazy Loading & Below-the-fold — The Underestimated Killers</h2> Since 0 out of 6 LLMs scroll, lazy-load mechanisms cut off core content from perception. Consequences: <ul><li>Place the core message, product USPs, prices, and primary calls-to-action above the first viewport height.</li> <li>Load hero-relevant images/text content without lazy-load (or with server-side inline fallback). Do not use purely client-side injection for main content.</li> <li>Provide <noscript> fallbacks for critical assets (e.g., static product images, text snippets).</li> <li>Check SPAs and review widgets: without server-side rendering, they remain invisible.</li> </ul> <h2>What Our Audit Makes of This</h2> We are expanding technical audits to include four targeted checks and moderately adjusting weightings: <ul><li>title_tag_present: Checks existence, length, and precision of the title tag per URL.</li> <li>lazy_loaded_main_content: Warning if essential content is exclusively lazy-loaded or only becomes visible after interaction.</li> <li>noscript_fallback_present: Records whether a <noscript> fallback exists for critical images/text modules.</li> <li>css_generated_critical_content: Reports risk if relevant copy is generated via CSS pseudo-elements (::before/::after).</li> </ul>The weighting of individual on-page signals is moderately shifted in favor of above-the-fold HTML and semantic markup quality. <h2>Conclusion & 5 Concrete Measures for Shop Operators</h2> The study separates classic SEO signals from what LLMs actually capture in dialogue mode. Rely on robust, HTML-first delivered content and secure critical information against rendering limitations. Five prioritized measures: 1) Sharpen title strategy: Every category page and every product gets a precise, short, benefit-oriented title. 2) Harden above-the-fold: USP, price, availability, primary CTA, and a descriptive paragraph directly in the server-rendered HTML. 3) Progressive enhancement instead of JS-only: Run SPAs and widgets with SSR/ISR or static fallbacks; do not inject critical copy via JavaScript. 4) Double up structured data: Keep JSON-LD, but also mark up key information as Microdata in the body. 5) Fallback and CSS check: <noscript> fallbacks for core modules; do not output business-critical texts in ::before/::after. <p>The Writesonic results thus provide clear guardrails: what is not in the initial HTML and above the fold effectively does not exist for many LLMs. Align your templates accordingly and validate regularly with real crawler checks.</p> </article> <footer> <p>© 2026 Trusted Shops SE — <a href="https://ai-trust-audit.trustedshops.com">AI Trust Audit</a></p> <p> <a href="https://uyeqrrnoelyciqvpzhur.supabase.co/functions/v1/blog/en">Blog</a> · <a href="https://uyeqrrnoelyciqvpzhur.supabase.co/functions/v1/site/en/about">How it works</a> · <a href="https://uyeqrrnoelyciqvpzhur.supabase.co/functions/v1/site/en/faq">FAQ</a> · <a href="https://uyeqrrnoelyciqvpzhur.supabase.co/functions/v1/site/en/contact">Contact</a> · <a href="https://uyeqrrnoelyciqvpzhur.supabase.co/functions/v1/site/en/impressum">Impressum</a> · <a href="https://uyeqrrnoelyciqvpzhur.supabase.co/functions/v1/site/en/nutzungsbedingungen">Terms</a> · <a href="https://uyeqrrnoelyciqvpzhur.supabase.co/functions/v1/site/en/datenschutz">Privacy</a> </p> </footer> </body> </html>