Faro AI Signals·August 6, 2026

FAQ Rich Results Dead; Schema Adds No AI Citation Lift

Two converging findings reshape the structured-data playbook: Google has killed FAQ rich results as of August 2026, and a controlled Ahrefs study of 1,885 pages found adding JSON-LD schema produced no meaningful AI citation gain — and actually cut Google AI Overviews citations. Meanwhile, brands with active review profiles are cited in AI answers at a rate 75 times higher than brands without them.

ShareShare

This Week's Signals

1

Ahrefs Controlled Study: JSON-LD Schema on 1,885 Pages Cut AI Overviews Citations 4.6%

Source: Dotinacademy (citing Ahrefs researchers Louise Linehan & Xibeijia Guan) ↗

Why it matters for your score

The study used before-and-after matched controls against 4,000 pages specifically to isolate schema's causal effect — making this harder to dismiss than a correlation report. Google AI Overviews citations fell 4.6% (statistically significant) after schema addition, while gains in AI Mode (+2.4%) and ChatGPT (+2.2%) were indistinguishable from noise. If you have been treating schema as a primary AI-visibility lever, this evidence says it is not — redirect that effort toward content and authority signals instead.

2

Google Ends FAQ Rich Results; Review Profile Presence Now Drives 75x Citation Gap

Source: AuthorityTech ↗

Why it matters for your score

Google announced on May 7, 2026 that FAQ rich results will no longer appear in Search, with FAQ structured data support removed from Search Console, the Rich Results Test, and the API by August 2026. At the same time, a Trustpilot analysis of 800,000+ AI responses found brands with active review profiles cited in 75.3% of answers versus 1% for brands with no review profile, with review and trust sites accounting for 14% of all AI citations in the sample. The practical shift: time spent maintaining FAQ schema is better redirected to building and maintaining third-party review presence.

3

500 Million AI Bot Visits Logged: Only 408 Fetched /llms.txt Directly

Source: Limy.ai ↗

Why it matters for your score

Limy monitored over 500 million AI bot visits across a 90-day window and found only 408 targeted /llms.txt directly — GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, and Google-Extended overwhelmingly skip the file and crawl HTML directly. A separate SE Ranking XGBoost model found that removing the llms.txt variable actually improved citation-frequency prediction accuracy, meaning the file added noise rather than signal. No major LLM provider has publicly committed to using llms.txt as a production signal, so crawlability of your core HTML pages remains the critical factor.

What to do this week

  1. 1

    Audit your current schema investment using Faro's AI Readiness Scan (/tools/ai-readiness-scan) — given the Ahrefs finding that schema addition produced no meaningful AI citation lift and cut AI Overviews citations 4.6%, confirm whether schema is consuming build time that could go toward content authority or review acquisition instead.

  2. 2

    Check whether any FAQ structured data is still deployed on your site and remove or deprioritize it — Google ended FAQ rich results support in Search Console and the API by August 2026, so maintaining that markup now serves no confirmed purpose in either traditional or AI search.

  3. 3

    Use Faro's llms.txt generator (/tools/llms-txt) to confirm your file exists, then shift primary attention to ensuring your HTML pages are fully crawlable — the Limy.ai data showing only 408 direct llms.txt fetches out of 500 million bot visits confirms that crawlers read your HTML, not your llms.txt file.

Sources

← All editionsScan your site now →