# AI Search Readiness Score - Full Reference > Free audit tool that evaluates how well websites are optimised for citation in AI-powered search engines (ChatGPT, Perplexity, Google AI Overviews, Bing Copilot). ## What This Site Does - Scores websites across 4 dimensions: Machine Readability, Extractability, Trust, Offering Readiness - 26 automated checks including Schema.org validation, content structure, business identity - Citation monitoring via Perplexity API - PDF reports with Executive Root Cause analysis ## Scoring Methodology Score /100 = 0.25·MR + 0.30·EX + 0.25·TR + 0.20·OR ### MR - Machine Readability (weight: 0.25) - MR1: Indexation (robots.txt) - max 3 pts (premium) - MR2: Language & Mobile Optimization - max 4 pts (core) - MR3: Schema.org Structured Data - max 10 pts (core) - MR4: SSL / HTTPS - max 2 pts (premium) - MR5: Open Graph Completeness - max 3 pts (premium) - MR6: Canonical URL - max 2 pts (premium) - MR7: JS Rendering (AI Crawler View) - max 3 pts (premium) - MR14: Page Title & Social Meta Tags - max 11 pts (core) ### EX - Extractability (weight: 0.30) - EX1: Meta Description Quality - max 5 pts (premium) - EX3: FAQ Content - max 10 pts (core) - EX5: Local Market Relevance - max 10 pts (core) - EX6: Heading Hierarchy (H1/H2) - max 5 pts (premium) - EX7: Content Depth - max 5 pts (premium) - EX12: Rich Content & Comparison Tables - max 10 pts (core) - EX_LLM_BLUF: Content Clarity (BLUF/TL;DR) - max 5 pts (LLM) - EX_LLM_FAQ: FAQ Content Richness (LLM) - max 5 pts (LLM) - EX_LLM_LOCAL: Local Relevance (LLM) - max 5 pts (LLM) - EX_LLM_STRUCTURE: Content Structure (LLM) - max 5 pts (LLM) ### TR - Trust (weight: 0.25) - TR1: Business Identity (NAP) - max 15 pts (core) - TR3: Customer Reviews & Ratings - max 10 pts (core) - TR5: Authorship Signals - max 4 pts (premium) - TR6: GTIN/MPN for Products - max 4 pts (premium) - TR7: Contact & Privacy Pages - max 4 pts (premium) ### OR - Offering Readiness (weight: 0.20) - OR1: Product/Content Quality - max 20 pts (core) - OR4: Image Alt Text Coverage - max 4 pts (premium) - OR5: Price & Currency in Offer - max 4 pts (premium) - OR6: Category Breadcrumbs - max 4 pts (premium) ## All Articles (51) ### GPT-4o Passes Your Prompt Verbatim to Web Search: Empirical Evidence on LLM Query Rewriting - URL: /blog/gpt-4o-passes-prompt-verbatim-web-search - Published: 2026-04-29 - TL;DR: When you send GPT-4o a 38-word conversational prompt with web search enabled, the search backend receives the same 38 words. We measured this empirically across 20 paired prompts (10 SEO-shaped, 10 conversational) using OpenAI's Responses API with web_search_preview and tool_choice forced. Across 8 successful pairs (12 calls failed with HTTP 500s during the run window), every single search query GPT-4o issued matched the user input verbatim. Word-for-word, character identical. This rules out internal LLM rewriting as the variable that would collapse the SEO and conversational citation ecosystems into one. The two query styles really do go to retrieval as different strings, and AI citation monitoring tools that generate only keyword queries are measuring the keyword ecosystem only, not a normalized blend. ### Why Your AI Citation Rate Is Half-Truth: An Experiment - URL: /blog/ai-citation-rate-half-truth-experiment - Published: 2026-04-28 - TL;DR: When you ask an LLM "best dive computer 2026" you get one set of citations. When you ask "I'm doing my Open Water cert next month, looking for my first dive computer around 300 EUR" you get a completely different set. Across 8 sites and 320 Perplexity Sonar queries, the URL overlap between SEO-style and conversational queries was 4% (Jaccard 0.04). Sites averaged 38% self-citation under SEO-style and 26% under conversational — a 12.3-point gap. The pattern was bimodal by site type: educational content sites gained citations under conversational queries (Manduka +23pp), while B2B SaaS sites collapsed (Genie Networks −44pp). Tools that monitor only SEO-style queries report half-truths about AI visibility. ### How Google's Query Fan-Out Affects Your AI Visibility - URL: /blog/google-query-fan-out-ai-visibility - Published: 2026-04-08 - TL;DR: Google patent US20240289407A1 describes query fan-out: AI search decomposes a single query into 5-12 sub-queries and routes each to specialized databases (videos, recipes, places, products). Your content must cover these sub-intents, not just the main topic. Schema.org is no longer just a ranking signal - it determines which specialized database can see your content. Cross-page coverage beats single-page depth. Surfer SEO data on 173,902 URLs shows 161% higher citation rates for fan-out-optimized content. Sub-query instability (only 27% consistent) means you should cover intent categories broadly, not target exact sub-queries. ### How Publish Date Affects AI Search Visibility: What datePublished and dateModified Actually Do - URL: /blog/how-publish-date-affects-ai-search-visibility - Published: 2026-04-09 - TL;DR: Date signals (datePublished, dateModified, visible "last updated" lines) are one of the weakest predictors of AI citations in our data. Domain age showed r=0.026 (p=0.593) - not significant. However, date markup matters for three practical reasons: (1) LLMs use dates to resolve conflicting information - newer content wins when two sources disagree, (2) some AI systems filter by recency for time-sensitive queries like "best tools 2026," and (3) missing date signals are a trust negative - pages without any date look less credible. The fix is cheap: add datePublished and dateModified to your Article/BlogPosting schema, show a visible "last updated" line, and actually update your content regularly. Do not fake dates - LLMs can detect when "updated 2026" content references only pre-2024 sources. ### How LLMs Rank Products: A 91% Manipulation Success Rate and What It Means for Your Business - URL: /blog/how-llms-rank-products-core-paper - Published: 2026-04-07 - TL;DR: The CORE paper (arXiv:2602.03608) tested whether product descriptions can be optimized to manipulate LLM rankings. Result: 91.4% success rate for Top-5 placement across GPT-4o, Gemini-2.5, Claude-4, and Grok-3. Three strategies work: string-based patterns, reasoning-based arguments ("why this product"), and review-based social proof. The study also confirms that classical search rankings heavily influence LLM output order. Our position: don't manipulate, but understand what signals matter and make your content genuinely better along those dimensions. ### We Ran a 28-Day AI Skills Manifest Experiment. The Data Says: It Doesn't Work. - URL: /blog/ai-skills-manifest-experiment-results - Published: 2026-04-07 - TL;DR: We deployed llms.txt, a skills manifest (skills.json), and structured content APIs on getaisearchscore.com, then tracked every AI crawler visit for 28 days (14-day baseline + 14-day treatment). Result: zero bots consumed the skills manifest or content APIs. Only GoogleOther fetched llms.txt (2 hits). ChatGPT-User traffic stayed flat (+10%, same 9 pages). Path diversity showed no consistent change across bots. This directly contradicts LightSite AI's published claims of 3x ChatGPT traffic and 5x Q&A visits. Raw data is public at /experiment. ### Why 90% of AI Search Optimization Advice Is Cargo Cult Science - URL: /blog/science-behind-ai-search-optimization - Published: 2026-04-06 - TL;DR: We ran a pre-registered study on 485 domains and found zero correlation (r=0.009) between generic SEO scores and AI citation rates. Instead of ignoring the data, we studied Google patents, RAG research papers, and Olaf Kopp's GEO framework to understand how AI actually selects sources. The key factors: heading-query alignment (AI skims headings first), self-contained paragraphs (RAG systems extract atomic "nuggets"), content clarity over authority signals, and cross-page brand consistency. We rebuilt our tool around these research-backed signals instead of industry guesswork. ### Why AI Crawlers Hate Your JavaScript (And How to Fix It) - URL: /blog/why-ai-crawlers-javascript - Published: 2026-03-03 - TL;DR: AI crawlers (GPTBot, PerplexityBot) are less sophisticated than Googlebot at rendering JavaScript. If your site relies on client-side rendering (CSR), AI engines often see a blank page. To fix this, move to Server-Side Rendering (SSR), ensure JSON-LD is in the initial HTML, and verify your middleware doesn't block AI-specific user agents. ### Free Content Relevance Audit - Check Your Site's AI Search Readiness - URL: /blog/free-ai-search-readiness-tool - Published: 2026-02-10 - TL;DR: The free audit at getaisearchscore.com runs the full Content Relevance Score on any website - five components (Query Coverage, Content Depth, Sub-Intent Coverage, Citation Reality on paid scans, Technical Health), per-query breakdown, sub-intent gap analysis, and the 26 legacy technical checks as one subcomponent. No login, no credit card, up to 50 pages crawled, 20 monitoring queries generated and editable. The free tier gives the full diagnostic - we don't gate core value. The only things reserved for the paid Starter consultation (149 one-time) are Citation Reality via Perplexity and a human expert review. ### How to Audit Your Website for ChatGPT Shopping Visibility - URL: /blog/audit-chatgpt-shopping-visibility - Published: 2026-02-12 - TL;DR: ChatGPT Shopping surfaces products directly inside chat — but only if your site has the right structured data, crawl permissions, and content format. This guide walks you through a 7-step audit: check robots.txt for AI crawler access, validate Product schema markup, verify pricing and availability data, test review aggregation, audit image quality and alt text, check page load performance for crawlers, and test with the actual ChatGPT Shopping interface. Most e-commerce sites fail on steps 1–3. ### AI Search Readiness Checklist for E-Commerce (2026) - URL: /blog/ai-search-readiness-checklist-ecommerce - Published: 2026-02-14 - TL;DR: This checklist has two parts. Part 1 covers content relevance - the dominant predictor of AI citations (AUC 0.915): mapping target queries to existing pages, checking content depth per query, analyzing sub-intent coverage gaps, and building content clusters that cover the full fan-out of user questions. Part 2 covers technical health - the 26 technical checks organized by the four historical dimensions (MR/EX/TR/OR): schema markup, AI crawler access, trust signals, and offering data. Content relevance is the strategy. Technical health is the hygiene. Our study of 441 domains showed the technical checks alone don't predict citations (r=0.009), but they are real prerequisites - broken plumbing blocks everything. ### What Blocks Your Products from Appearing in Perplexity Answers - URL: /blog/products-not-showing-perplexity - Published: 2026-02-16 - TL;DR: If Perplexity never mentions your products, one of these 8 blockers is likely the cause: (1) robots.txt blocking PerplexityBot, (2) missing or incomplete Product schema, (3) no crawlable product descriptions (content behind JS rendering), (4) missing review/rating data, (5) no FAQ or answer-ready content on product pages, (6) thin product descriptions under 100 words, (7) duplicate product pages without canonical tags, (8) no sitemap.xml or broken sitemap. This guide explains how to diagnose and fix each issue with specific code examples. ### Schema.org Markup for AI Search Visibility: E-Commerce Guide - URL: /blog/schema-markup-ai-search-ecommerce - Published: 2026-02-18 - TL;DR: Schema.org markup is the single most important technical factor for AI search visibility. AI engines like ChatGPT, Perplexity, and Google AI Overviews rely on structured data to understand what your pages offer. This guide covers the 6 essential schema types for e-commerce: Product (with offers, reviews, GTIN), FAQPage, BreadcrumbList, Organization, LocalBusiness, and WebSite. Each includes a ready-to-use JSON-LD code example and a validation checklist. Implement all 6 and your Machine Readability score will jump by 15–20 points. ### How to Improve Your Citation Rate in AI Search Engines - URL: /blog/improve-citation-rate-ai-search - Published: 2026-02-20 - TL;DR: Citation rate — the percentage of relevant AI queries where your site is cited as a source — is the key metric for AI search visibility. Most sites have a 0% citation rate because they lack structured data, answer-ready content, and entity trust signals. This guide presents a 10-step action plan to improve your citation rate: add schema markup, write TL;DR blocks, create FAQ sections, build comparison tables, establish authorship, collect reviews, optimize for featured snippets, ensure AI crawler access, monitor citations across platforms, and iterate based on data. Sites that follow all 10 steps typically see citation rates increase from 0% to 15–25% within 30 days. ### Why Your Site Isn't Cited in ChatGPT Answers (and How to Fix It) - URL: /blog/why-not-cited-chatgpt - Published: 2026-02-22 - TL;DR: ChatGPT cites only 3–5 sources per answer, and your site is not one of them. The 6 most common reasons: (1) Your robots.txt blocks OAI-SearchBot or ChatGPT-User — fix by adding explicit Allow rules. (2) Missing or incomplete schema.org markup — add Product, FAQPage, Organization schema. (3) No answer-ready content — add TL;DR blocks, FAQ sections, comparison tables. (4) Weak trust signals — add reviews, authorship, NAP data. (5) Stale content — update key pages at least monthly. (6) Unclear entity identity — ensure consistent brand naming and Organization schema across all pages. ### Perplexity Not Showing Your Products? Here's Why and How to Fix It - URL: /blog/perplexity-not-showing-products - Published: 2026-02-23 - TL;DR: Perplexity ignores products for four distinct reasons — Machine Readability (bots blocked, JS-only rendering), Extractability (incomplete schema, no FAQ content), Trust & Entity (weak brand entity signals), and Offering (thin descriptions, no reviews, unclear use cases). This guide gives you a symptom-to-root-cause table, patterns from real site audits, a week-by-week 30-day fix plan, and a 10-point checklist. The key insight: fixes across all four dimensions compound — patching schema without fixing crawl access rarely moves the needle. ### How to Get Cited in Google AI Overviews (Formerly SGE) - URL: /blog/get-cited-google-ai-overviews - Published: 2026-02-24 - TL;DR: Google AI Overviews (formerly SGE) now appear for 30%+ of searches, displaying AI-generated answers with 3–8 cited sources. Unlike ChatGPT or Perplexity, Google AI Overviews heavily favor sites already in the top 10 organic results — but ranking alone is not enough. To get cited, you need: answer-ready content formatted as concise paragraphs (40–60 words per answer block), FAQ sections with schema markup, comparison tables for "vs" queries, list-format content for "how to" queries, and strong E-E-A-T signals. This guide covers AIO-specific patterns and how they differ from optimizing for ChatGPT or Perplexity. ### Why Mixing Languages on Your Website Kills AI Search Visibility - URL: /blog/mixed-language-content-ai-search - Published: 2026-03-01 - TL;DR: A website with navigation in one language and product descriptions in another creates serious AI Search Readiness problems across all four dimensions. Machine Readability suffers because missing hreflang tags create technical ambiguity AI cannot resolve. Extractability drops because if a user asks a question in Portuguese and your answer is in English, AI engines won't recognize your page as a relevant source. Trust & Entity signals weaken because language inconsistency is interpreted as poor data governance. And schema.org markup loses accuracy when Product fields don't match the visible language of the page. The fix: create separate language versions with hreflang tags, align schema.org markup with page language, and ensure content is answer-ready in the language of your target audience. ### What Is AI-Ready Data and Why It Determines AI Search Visibility - URL: /blog/what-is-ai-ready-data - Published: 2026-03-01 - TL;DR: AI-ready data is data that has been specifically prepared, structured, and enriched with context so AI systems can understand, trust, and cite it. It has five key characteristics: accuracy and completeness, consistent structure and labeling (e.g., Schema.org markup), rich metacontext (business definitions, lineage, usage rules), governance (access controls, privacy), and optimization for specific AI workloads. Research shows that data readiness — not model complexity — separates winners from losers in the AI race. For websites, being AI-ready means AI search engines like ChatGPT, Perplexity, and Google AI Overviews can find, parse, and cite your content. ### What Is a Content Relevance Score? How It Works and Why It Matters - URL: /blog/what-is-ai-search-readiness-score - Published: 2026-03-02 - TL;DR: A Content Relevance Score (0-100) measures how well a website's content answers the questions its audience actually asks AI search engines - ChatGPT, Perplexity, Google AI Overviews. It has five components: Query Coverage (what fraction of queries the site can answer), Content Depth (how deeply pages cover each query), Sub-Intent Coverage (whether the site addresses the full fan-out of information needs behind each query), Citation Reality (whether Perplexity already cites the site), and Technical Health (the 26 legacy technical checks as one subcomponent, 15-20% weight). Content signals carry 80-85% of the weight. We built this after our original 26-check technical score showed r=0.009 correlation with actual citations across 441 domains. The follow-up study found content relevance predicts citations with AUC 0.915. ### What Is LLM SEO and How Does It Work? - URL: /blog/what-is-llm-seo - Published: 2026-03-02 - TL;DR: LLM SEO (also called Generative Engine Optimization or GEO) is the discipline of optimising websites to appear as cited sources in AI-generated answers from ChatGPT, Perplexity, Google AI Overviews, and similar systems. AI engines use a RAG pipeline that chunks your content into 300–800 token segments and retrieves them via semantic similarity. The most citable content patterns are answer blocks (40–60 word definitions under query-matching headings), FAQ sections, and comparison tables. Our analysis of 98 websites reveals the Readiness Paradox: sites scoring 80–100 on AI readiness have only 1.8% citation rate, while established brands scoring 0–19 achieve 38.8% — because technical readiness is necessary but not sufficient without domain authority and original data. The average citation rate across 1,615 checks is 18.1%. ### AI Search Readiness vs Traditional SEO: What Our Data Shows - URL: /blog/ai-search-readiness-vs-traditional-seo - Published: 2026-03-02 - TL;DR: Traditional SEO optimizes for ranking position. AI search readiness optimizes for citation in AI-generated answers. Neither traditional SEO metrics nor our original 26-check technical readiness score predicted which sites get cited (r=0.009 across 441 domains). Content relevance - measured through query coverage, content depth, and sub-intent coverage - is the signal that does predict citations (AUC 0.915). The current model has five components: Query Coverage, Content Depth, Sub-Intent Coverage, Citation Reality, and Technical Health (the old 26 checks as one subcomponent at 15-20% weight). Technical hygiene still matters - if AI crawlers can't reach your pages, nothing else helps. But the strategy is content relevance, not structural optimization. ### How Content Freshness Affects AI Search Visibility - URL: /blog/content-freshness-ai-search-visibility - Published: 2026-03-02 - TL;DR: Content freshness is a trust signal, not a ranking factor — it becomes decisive for time-sensitive queries but carries less weight for evergreen content. Our analysis of 1,120 crawled pages shows 62% have no machine-readable date signal at all. Sites with dateModified present score 35.6 points higher on AI readiness (74.3 vs 38.7, n=100) — but this likely reflects overall structured data maturity, not the isolated effect of dates. By page type: articles 86% coverage, products 50%, category pages 0%. Three freshness signals matter: JSON-LD dateModified (primary for Google AI Overviews), sitemap lastmod (triggers re-crawl), and visible "Last updated" date (primary for ChatGPT/Perplexity which extract text). All three should be aligned. ### Best AI Search Readiness Tools in 2026 [Comparison] - URL: /blog/best-ai-search-readiness-tools-2026 - Published: 2026-03-02 - TL;DR: AI search readiness tools fall into 4 categories: (1) Content relevance diagnostics - LLM SEO Check (free Content Relevance Score, 5 components, AUC 0.915 research), Otterly.ai (GEO audit + Semrush partnership), Peec AI (content analysis). (2) Citation monitors - Profound/ziptie.dev (multi-platform), LLMrefs (referral analytics). (3) Managed services - LightSite AI. (4) Traditional SEO platforms with AI add-ons - Conductor (enterprise), Semrush (via Otterly). The uncomfortable truth: our own study found zero correlation (r=0.009) between structural readiness scores and actual citations. Content relevance predicts citations (AUC 0.915). Most tools in this space have not published equivalent evidence. Best approach: use a content relevance diagnostic for deep diagnosis, add a monitoring tool for ongoing tracking. Disclosure: we build LLM SEO Check. ### UCP: From Mere Citations to Autonomous Purchases in AI Search - URL: /blog/ucp-agentic-commerce-strategy-ecommerce - Published: 2026-02-27 - TL;DR: The Universal Commerce Protocol (UCP) is a new standard that lets AI agents like Google Gemini discover merchants, understand their capabilities, and complete checkout without custom integrations. UCP solves the transaction layer — but it does not replace AI Search Readiness (discovery). Implement UCP as Phase 2 only after you have clean product data, complete schema markup, and strong trust signals (Phase 1). For SMBs on standard CMS platforms, wait for out-of-the-box plugins. For enterprise e-commerce with high checkout friction and Google-primary traffic, joining the UCP rollout is justified now. ### LLM SEO Check vs Conductor: Content Relevance Diagnostic vs Enterprise Monitoring - URL: /blog/ai-search-readiness-score-vs-conductor-monitoring - Published: 2026-03-02 - TL;DR: Conductor is enterprise brand monitoring across search channels with continuous dashboards and competitor tracking. LLM SEO Check (getaisearchscore.com) is a content relevance diagnostic that measures whether your content answers the queries users ask AI engines, using five components: Query Coverage, Content Depth, Sub-Intent Coverage, Citation Reality (paid), and Technical Health. The free tier gives the full four-component audit. The Starter consultation (149 one-time, 4 slots/month) adds Perplexity citation data and human expert analysis. Conductor makes sense for 20-person SEO teams needing ongoing monitoring. Our tool makes sense for teams that need a deep one-off diagnosis with expert-guided fixes. ### LLM SEO Check Pricing Guide: Free Audit and Starter Consultation - URL: /blog/buy-ai-search-readiness-tool-pricing-guide - Published: 2026-03-02 - TL;DR: LLM SEO Check has two tiers. Free: full Content Relevance Score audit with five components (Query Coverage, Content Depth, Sub-Intent Coverage, Technical Health, and score breakdown per query), no login, no credit card, unlimited rescans. Starter (149 one-time): adds Citation Reality via Perplexity API, a 24-48 hour human-verified report with 20-40 prioritized rewrite tasks, platform playbooks (Shopify/WooCommerce/Prestashop), and a follow-up call. Limited to 4 slots/month. We priced it this way because our research showed the automated diagnostic alone (r=0.009 for technical score) is not the hard part - the value is in expert interpretation of content relevance gaps. ### AI Search Audit: diveshop.pt — 19/100 & 18 Critical Blockers - URL: /blog/ai-search-readiness-audit-review-diveshop-pt - Published: 2026-03-03 - TL;DR: Our audit of diveshop.pt revealed a "Visibility Gap": while the shop sells high-end dive gear, it is invisible to AI search engines (0% citation rate). The audit identified 18 specific blockers, including a missing product sitemap, lack of Schema.org markup, and language inconsistency between UI and product data. This case study demonstrates how diagnostic auditing is the first step toward AI search dominance. ### Why Perplexity and ChatGPT Ignore Your Brand (and How to Fix It) - URL: /blog/why-ai-engines-ignore-your-brand - Published: 2026-03-03 - TL;DR: Brand invisibility in AI search often stems from technical blockers (robots.txt, crawlability), semantic ambiguity, or lack of structured entity data. To fix it: audit your AI crawler access, implement complete Schema.org Organization/Brand markup, and ensure your brand identity is consistent across all data sources. ### How to Write Pages That AI Assistants Actually Cite and Recommend - URL: /blog/how-to-write-ai-search-optimized-pages - Published: 2026-03-03 - TL;DR: AI-visible content is objective, structured, and direct. Move away from marketing fluff toward "answer-centric" blocks: TL;DR summaries, clear FAQ sections, comparison tables, and factual product benefit lists. AI engines cite sources that make data extraction easy. ### AI Search Visibility Metrics: Measure What Matters in 2026 - URL: /blog/ai-search-visibility-metrics-guide - Published: 2026-03-03 - TL;DR: Traditional metrics like CTR and Position are failing in AI search. Focus on Citation Rate, Answer Placement (top-of-answer vs inline), and Entity Confidence Score. Use your AI Search Readiness Score as a leading indicator of visibility growth. ### 7-Day AI Visibility Playbook: A Step-by-Step Guide for Marketers - URL: /blog/7-day-ai-visibility-playbook - Published: 2026-03-03 - TL;DR: Day 1: Audit baseline. Day 2: Fix technical blockers. Day 3: Schema implementation. Day 4: FAQ & TL;DR content. Day 5: Trust signals. Day 6: Cross-platform testing. Day 7: Measurement setup. This playbook is the fastest route to AI readiness. ### AI-Ready Data for E-commerce & SaaS: From Raw Feeds to Selling Answers - URL: /blog/ecommerce-ai-ready-data-guide - Published: 2026-03-03 - TL;DR: AI-ready data is accurate, structured, and context-rich. For e-commerce, this means mapping every product attribute to Schema.org properties and ensuring pricing/availability is updated in real-time for AI crawlers. ### From Citations to Sales: How to Convert AI Mentions into Revenue - URL: /blog/convert-ai-citations-to-sales - Published: 2026-03-03 - TL;DR: AI users arrive with specific intent. If they click from a citation, your landing page must confirm the exact information they saw in the AI answer. Use deep links, clear value propositions, and trust-building elements like reviews. ### AI Visibility Ops: Integrating AI Search into Your Marketing Workflow - URL: /blog/ai-visibility-ops-marketing-workflow - Published: 2026-03-03 - TL;DR: AI visibility is not a "one and done" task. Build a monthly "AI Audit" into your marketing cycle, refresh FAQ content based on AI trends, and use automated monitoring to alert you to citation drops. ### How to Write AI-Citable Pages: LLM Visibility Framework - URL: /blog/how-to-write-ai-citable-pages - Published: 2026-03-03 - TL;DR: An AI-citable page is a document structured specifically for LLM extraction. To achieve high citation rates, you must optimize across four dimensions: Machine Readability (logical hierarchy), Extractability (answer-first blocks), Trust & Entity (clear identity signals), and Offering Readiness (structured value propositions). Use our AI Search Readiness Score to audit and iterate on these signals. ### The 26 Factors That Determine Your AI Search Readiness Score - URL: /blog/26-factors-ai-search-readiness-score - Published: 2026-03-04 - TL;DR: Your AI Search Readiness Score is calculated from 26 specific checks grouped into 4 baskets: Machine Readability (25 pts, 7 checks), Extractability (30 pts, 8 checks), Trust & Entity (25 pts, 5 checks), and Organic Reach (20 pts, 6 checks). The formula is Score = 0.25×MR + 0.30×EX + 0.25×TR + 0.20×OR. A JS dependency penalty halves MR if your page renders fewer than 50 words without JavaScript. Fix Extractability first — it carries the most weight and typically has the largest gaps. ### AI Search Readiness Works for Any Language and Market — Here's How - URL: /blog/ai-search-readiness-international-multilingual - Published: 2026-03-04 - TL;DR: AI Search Readiness auditing is language-agnostic by design. The 26 checks evaluate technical signals (structured data, crawl access, entity identity) that work identically in Portuguese, German, Japanese, or any other language. Schema.org vocabulary is universal, robots.txt is language-independent, and Playwright-based crawling renders any content. The only language-sensitive checks are LLM-based evaluations, which use GPT-4o with multilingual capabilities. ### How to Measure AI Search Readiness for Your Website (Step-by-Step) - URL: /blog/how-to-measure-ai-search-readiness - Published: 2026-03-04 - TL;DR: Measuring AI search readiness requires two layers: technical hygiene and content relevance. Technical hygiene (crawl access, schema, rendering) is necessary but our study of 441 domains showed it predicts citations at r=0.009 - essentially zero. Content relevance - measured through Query Coverage, Content Depth, and Sub-Intent Coverage - predicts citations with AUC 0.915. The current score has five components: QC, CD, Sub-Intent Coverage, Citation Reality (paid), and Technical Health (15-20% weight). The free automated scan runs the full four-component audit in a few minutes. The paid Starter consultation (149 one-time) adds Citation Reality via Perplexity and a human expert review. ### Recommended LLM SEO Check Tools in 2026: What Each One Actually Does - URL: /blog/recommended-llm-seo-check-tools - Published: 2026-03-04 - TL;DR: LLM SEO tools fall into 4 categories: (1) Content relevance diagnostics - LLM SEO Check (free Content Relevance Score with 5 components, research-backed at AUC 0.915), Otterly.ai, Peec AI. (2) Citation monitors - Conductor, LLMrefs, Profound/ziptie.dev. (3) Content optimization - Surfer, Clearscope, MarketMuse. (4) Traditional SEO with AI features - Semrush, Ahrefs. The elephant in the room: our study of 441 domains found zero correlation (r=0.009) between structural readiness scores and actual citations. Content relevance predicts citations. Most tools in this space haven't published equivalent evidence. Start with a content relevance diagnostic to identify gaps, then add monitoring to track progress. ### LLM SEO Check Review: Content Relevance Score - What It Does, Costs, and Delivers - URL: /blog/ai-search-readiness-score-review - Published: 2026-03-04 - TL;DR: LLM SEO Check (getaisearchscore.com) is a Content Relevance Score audit for websites that want to be cited in AI search engines. The current version has five components: Query Coverage, Content Depth, Sub-Intent Coverage, Citation Reality (paid), and Technical Health. This is the second version - the first measured 26 technical checks across four dimensions but our own study showed it didn't predict citations (r=0.009). Strengths: free tier gives full four-component audit (no paywall on core value), per-query breakdown with sub-intent gap analysis, research-backed methodology (AUC 0.915). Limitations: no continuous monitoring, no keyword tracking, not designed for 10K+ page enterprise sites. Starter consultation is 149 one-time with human expert, 4 slots/month. ### Is Your Data Ready for AI? The Website Owner's Diagnostic Checklist - URL: /blog/is-your-data-ready-for-ai - Published: 2026-03-10 - TL;DR: Data readiness for AI has two dimensions: enterprise data readiness (internal data for ML/AI projects) and website data readiness (structured data for AI search engines). Only 7% of enterprises report full AI data readiness (Cloudera/HBR, 2026), and Gartner predicts 60% of AI projects will be abandoned due to data issues. For websites, the diagnostic is more actionable: 15 questions across Machine Readability, Content Extractability, Trust Signals, and Offering Readiness determine whether AI search engines like ChatGPT, Perplexity, and Google AI Overviews will cite your business. ### We Audited 98 Websites for AI Search Readiness. Here's What We Found. - URL: /blog/we-audited-100-websites-ai-search-readiness - Published: 2026-03-11 - TL;DR: We audited 98 websites using 26 automated checks and 1,615 Perplexity citation queries. Average AI Search Readiness Score: 52.8/100. 61.3% of sites score below 60. The #1 failure: 91% of sites have zero customer review markup. Citation rate across all sites: only 18.1%. The core finding: sites have solved traditional SEO basics (95%+ pass SSL, mobile, robots.txt) but fail on AI-specific signals — trust, authorship, FAQ content, and product identifiers. Traditional SEO is no longer a differentiator for AI visibility. ### We Tested Whether AI Search Readiness Score Predicts LLM Citations. It Doesn't. - URL: /blog/study-ai-readiness-score-does-not-predict-llm-citations - Published: 2026-03-13 - TL;DR: A pre-registered study of 485 domains and 90 Perplexity API runs found no statistically significant association between AI Search Readiness Score and LLM citation frequency (Pearson r = 0.009, p = 0.849). Moz Domain Authority was the only predictor to borderline survive multiple comparison correction (adjusted p = 0.047), explaining roughly 2% of variance. Notably, DA predicts citation intensity (how often a cited domain is cited) but not citation selection (whether a domain gets cited at all). The full model explains about 2% of citation variance, suggesting that content relevance and retrieval pipeline mechanics — not structural website characteristics — are the dominant drivers of LLM citation decisions. ### What Determines AI Citations? An Analysis of 658 Sources Across 30 Queries - URL: /blog/ai-citation-analysis-658-sources-30-queries - Published: 2026-03-14 - TL;DR: We tested whether structural website optimization predicts AI search citations using 485 domains across 30 intent-based queries. The result: website structure (schema markup, HTML semantics, trust signals) shows no statistically significant correlation with LLM citation frequency (Pearson r = 0.009). Domain Authority is the only measurable predictor, explaining just 2.2% of variance. Over half of citations changed between identical runs, and YouTube was the single most-cited domain — especially for product queries. Follow-up analyses tested three alternative theories: content relevance gating (62× same-topic vs cross-topic citation rate), threshold effects (none found), and structural necessity (a Score=11 site was cited). AI search appears to sample relevant sources probabilistically rather than rank pages deterministically. ### Content Relevance Predicts AI Citations — Not SEO Score - URL: /blog/content-relevance-predicts-ai-citations-not-seo-score - Published: 2026-03-16 - TL;DR: Content relevance — measured by BM25 lexical matching and embedding cosine similarity — predicts AI search citations with a cross-validated AUC of 0.915. Our 26-check AI Search Readiness Score adds no predictive power beyond content relevance (p = 0.14, AIC improvement < 4 points). BM25 quintile analysis shows a 12× citation gradient from least to most relevant content. Even within the same topic, content relevance predicts which domains get cited (r_pb = 0.37). Structural optimization is hygiene, not strategy. ### How LLMs Actually Parse Your Content: Chunking, Readability, and Citations - URL: /blog/how-llms-parse-your-content-chunking-readability-citations - Published: 2026-03-27 - TL;DR: AI search engines process your content through a 7-step RAG pipeline: crawl, parse, chunk, embed, retrieve, re-rank, generate. Most "LLM SEO" advice targets steps 1-2 (access), but citations are determined at steps 5-7 (retrieval and generation). My study of 441 domains found zero correlation (r=0.009) between structural readiness scores and actual citations - but content relevance showed a 62x difference. Structure is table stakes. Relevance wins. ### How to Make Your Documentation AI-Agent Ready in 2026 - URL: /blog/ai-ready-documentation-2026 - Published: 2026-04-02 - TL;DR: Your documentation now has two audiences: humans and AI agents. Three standards are emerging - llms.txt (static discovery file, 15 min to implement), MCP (bidirectional protocol for deep integration), and Agent Skills (procedural knowledge packages). No major LLM provider has confirmed reading llms.txt at inference time, but the tools landscape is moving fast: Mintlify, GitBook, and Fern auto-generate all three. I implemented llms.txt and skills.json on my own SaaS and tracked bot behavior across a 28-day experiment. The data is still pending, but the implementation cost was low enough that waiting for proof isn't necessary. ### Schema Structured Data for AI Search: Complete Guide (2026) - URL: /blog/schema-structured-data-ai-search-guide - Published: 2026-04-08 - TL;DR: Schema.org structured data helps AI systems read your site - it reduces ambiguity, clarifies entities, and structures data for machine consumption. Sites with schema scored 38 points higher in our audits (66.7 vs 28.7). But in a study of 441 domains and 14,550 domain-query pairs, schema showed zero correlation with actual AI citations (r=0.009). Schema helps AI understand what your content IS, not whether it's worth citing. This guide covers schema by function (Foundation, Content, Entity, Relationship layers), practical mapping by website type, AI-specific implementation principles, and validation approaches. The relationship layer (author, mainEntity, about, mentions) is the most underused and most impactful for AI entity graphs. ### AI Search Optimization Services Compared: Agencies vs Tools vs Freelancers (2026) - URL: /blog/ai-search-optimization-services-compared - Published: 2026-04-12 - TL;DR: AI search optimization services fall into three categories: managed agencies ($2,000-$15,000/month), SaaS audit tools ($0-$200/month), and freelance consultants ($500-$3,000 per project). No category has strong published evidence of causal impact on AI citations. Our own research found zero correlation between technical SEO scores and citations (r=0.009), but content-query relevance predicted citations with AUC 0.915. Before buying any service, ask for published evidence, multi-platform monitoring, content relevance measurement (not just technical checks), specific success metrics, and flexible pricing. Start with a free tool audit to understand your gaps before investing in services. ### How to Evaluate AI Search Optimization Experts: 7 Criteria Before You Hire - URL: /blog/how-to-evaluate-ai-search-optimization-experts - Published: 2026-04-12 - TL;DR: AI search optimization is an 18-month-old specialty with no established credentials, scarce causal evidence, and constantly changing platform behavior. The ratio of genuine experts to people who added a buzzword to their LinkedIn headline is roughly 1:50. Evaluate candidates on seven criteria: (1) published research or data, especially null results, (2) understanding of content relevance vs technical SEO, (3) multi-platform knowledge across Perplexity/ChatGPT/Google AI Overviews/Bing Copilot, (4) honesty about uncertainty, (5) specific measurement methodology, (6) technical depth on Schema.org and crawling, (7) relevant industry experience. Red flag: anyone who guarantees AI search results. Green flag: anyone who has published honest null findings. Location does not matter - this work is fully remote. Start with a free audit to establish a baseline before hiring anyone. ## All FAQs (219) Q: Does GPT-4o rewrite user prompts before web search? A: No, at least not in the configuration we tested. We sent 20 prompts to GPT-4o through OpenAI's Responses API with the web_search_preview tool forced via tool_choice, and for all 8 successful pairs the search query GPT-4o issued internally was the user input verbatim. A 38-word conversational prompt was sent to web search as a 38-word string. A 13-word keyword query was sent as a 13-word string. No keyword extraction, no decomposition into sub-queries, no rewriting. This was true for every successful call in the test window (April 28, 2026). Source: /blog/gpt-4o-passes-prompt-verbatim-web-search Q: How can I see what query an LLM actually sends to web search? A: For OpenAI GPT-4o through the Responses API, the web_search_call.action.query field in the output array contains the literal search query the model issued. For Anthropic Claude with the web_search tool, tool_use blocks in the Messages API response expose the same information. For Perplexity Sonar, no API surface exposes the internal query at all — you see only the final answer and citations. For Gemini with grounding, the groundingMetadata.searchEntryPoint field provides a search summary but not the raw query. Source: /blog/gpt-4o-passes-prompt-verbatim-web-search Q: Why does this matter for AI citation monitoring? A: If LLMs do not rewrite user prompts before search, then the query style your monitoring tool generates is the query style hitting the search backend. A tool that generates 20 SEO-shaped queries is measuring what AI engines return for keyword input. If real users send conversational paragraphs to ChatGPT, the tool is reporting on a different ecosystem than the one prospects experience. Our prior 8-site experiment showed Jaccard 0.04 URL overlap between the two query styles in Perplexity Sonar — the GPT-4o verbatim-pass result confirms this gap is not a measurement artifact of unobserved rewriting. Source: /blog/gpt-4o-passes-prompt-verbatim-web-search Q: Does this apply to all LLMs or just GPT-4o? A: Just GPT-4o on April 28, 2026, in the configuration we tested. Claude with web search exposes tool_use blocks but we have not yet run the same empirical test. Perplexity Sonar does not expose internal queries so the question cannot be answered from API data alone. Reasoning models like o1 and GPT-5 explicitly plan their actions during reasoning steps, and that planning could include query rewriting. The verbatim-pass result for GPT-4o cannot be assumed for reasoning models without running the same test on each. Source: /blog/gpt-4o-passes-prompt-verbatim-web-search Q: What is the LLM web search pipeline and where does rewriting fit? A: Generative search engines have four stages: (1) user input, (2) query planning where the model decides whether to search and how to phrase the search, (3) retrieval where queries hit a search backend like Bing or Google, (4) answer synthesis where the model uses retrieved context to write the answer and select citations. Stage 2 is where rewriting could happen and is the only stage opaque to outside observers unless the engine exposes it through an API. Our test measures stage 2 specifically for GPT-4o. Source: /blog/gpt-4o-passes-prompt-verbatim-web-search Q: Should AI citation monitoring tools generate both SEO and conversational queries? A: Yes, and report them as separate metrics. The two query styles produce nearly disjoint citation sets (Jaccard 0.04 in our 8-site experiment), and engines do not internally normalize between them — at least GPT-4o does not. A monitoring tool that generates only one style is reporting on one ecosystem. To capture both, the tool must generate both styles independently and report them as two separate citation rates rather than averaging them into a single "AI visibility" number that blends two different populations. Source: /blog/gpt-4o-passes-prompt-verbatim-web-search Q: What is the difference between SEO-style and conversational queries in AI search? A: SEO-style queries are short, keyword-shaped strings like "best dive computer 2026" or "buy yoga mat online." Conversational queries are full-sentence user prompts with personal context like "I'm doing my Open Water cert next month, what dive computer would you recommend for around 300 EUR." Real users send conversational prompts to ChatGPT, Claude, and Perplexity; SEO-style queries are an artifact of Google's search box, not how people interact with AI assistants. Source: /blog/ai-citation-rate-half-truth-experiment Q: How much overlap is there between SEO and conversational citation results? A: Across 8 sites and 320 Perplexity Sonar queries, the average Jaccard URL overlap between the two query styles was 0.04 — about 4%. For every 100 unique URLs cited in either set, only 4 appeared in both. AI citation patterns are effectively two parallel ecosystems with very little shared territory. Source: /blog/ai-citation-rate-half-truth-experiment Q: Do all sites lose citation rate under conversational queries? A: No. The pattern is bimodal. Sites with deep educational content can gain (Manduka, a yoga retailer with maintenance and how-to content, gained +23 percentage points). Sites with thin product or sales-pitch content lose (Genie Networks, a B2B network security vendor, lost −44 percentage points). Brand-authority sites are stable in both styles (Ace & Tate dropped only 17pp from a high base). Niche non-English sites tend to be unrepresented in either style (Diveshop.pt was 0% in both). Source: /blog/ai-citation-rate-half-truth-experiment Q: Why does query style change which sites get cited? A: Conversational queries trigger advice-seeking behavior in the model: it pulls from review blogs, forums, expert how-to content, and community discussions. SEO-style queries trigger research-mode retrieval that fetches official brand pages and comparison roundups. The two modes index different parts of the web. Site authority matters in both, but the surrounding ecosystem of cited URLs is almost completely different. Source: /blog/ai-citation-rate-half-truth-experiment Q: What does this mean for monitoring AI citation rates? A: A monitoring tool that generates only SEO-style queries (most do, including our own until this finding) measures roughly half the ecosystem and over-estimates a site's typical self-citation rate by ~12 percentage points on average. The competitor URLs shown to users are largely the wrong ones — they belong to a parallel keyword-based universe, not the conversational one. To get an honest picture, generate both query styles and report them separately. Source: /blog/ai-citation-rate-half-truth-experiment Q: Does this finding contradict published AI citation research? A: It complements it. Profound's 680M-citation dataset and Discovered Labs' platform comparisons describe what AI engines cite, but they don't isolate query style as a variable. Ahrefs found that only 12% of AI-cited URLs overlap with Google's top 10 results across 15,000 queries; our finding extends that result inside AI search itself — even within the same engine, two query styles produce non-overlapping citation sets. Source: /blog/ai-citation-rate-half-truth-experiment Q: What is query fan-out in AI search? A: Query fan-out is the process where an AI search system takes a single user query and decomposes it into multiple specialized sub-queries before retrieving results. Instead of matching your query against one index, the system queries several specialized databases simultaneously - for videos, recipes, local places, products - and merges the results. Google patent US20240289407A1 describes this mechanism in detail. Source: /blog/google-query-fan-out-ai-visibility Q: How does query fan-out affect my website's visibility? A: Fan-out means covering the main topic is no longer enough. A single query generates 5-12 sub-queries, each competing for inclusion in the final AI-generated answer. If your content covers the main topic but misses sub-intents (like safety info, pricing, local availability), competitors who address those specific gaps will appear instead - even if they rank lower in traditional search. Source: /blog/google-query-fan-out-ai-visibility Q: Why does Schema.org matter for query fan-out? A: The Google patent describes specialized "topical search services" for recipes, videos, local places, and products. Each service has its own eligibility criteria based on Schema.org types. A restaurant page without Restaurant schema is invisible to the places service. An e-commerce page without Product/Offer schema is invisible to the shopping service. Schema.org acts as a routing mechanism that determines which specialized database can see your content. Source: /blog/google-query-fan-out-ai-visibility Q: How can I check my sub-intent coverage? A: Three approaches: (1) Manual decomposition - for each target query, list 3-5 sub-intents and check if your pages cover them. (2) LLM-assisted - use ChatGPT or Claude to decompose queries into sub-intents, then audit your content. (3) Automated tools - some AI search audit tools can decompose queries into sub-intents and check cross-page coverage automatically, giving you a coverage ratio and highlighting gaps. Source: /blog/google-query-fan-out-ai-visibility Q: Should I create one comprehensive page or multiple focused pages for fan-out? A: Multiple focused pages generally perform better for fan-out. AI systems extract passages, not entire pages. Three focused pages that each cover 2-3 sub-intents with depth outperform one 10,000-word page that touches every sub-intent shallowly. Think content clusters: a product page for features, a FAQ for sizing/safety, and a blog post for buying guides can collectively cover all sub-intents. Source: /blog/google-query-fan-out-ai-visibility Q: Are fan-out sub-queries the same every time? A: No. Surfer SEO research shows only 27% stability in generated sub-queries for the same original query across sessions. The system also adapts based on context: time of day, user location, and search history all modify which sub-queries are generated. This means you should cover broad intent categories rather than targeting specific exact sub-queries. Source: /blog/google-query-fan-out-ai-visibility Q: Does datePublished in Schema.org affect AI search citations? A: Based on our study of 441 domains, date signals alone do not significantly predict AI citations (domain age r=0.026, p=0.593). However, datePublished helps LLMs resolve conflicts between sources and filter results for time-sensitive queries. It is a weak but useful signal - absence is more harmful than presence is beneficial. Source: /blog/how-publish-date-affects-ai-search-visibility Q: Should I add dateModified to my Schema.org markup? A: Yes. dateModified tells AI crawlers when your content was last substantively updated. This is especially important for evergreen content like guides and comparisons that you revise over time. Google explicitly recommends dateModified for articles. The implementation cost is near zero - add it to your Article or BlogPosting JSON-LD. Source: /blog/how-publish-date-affects-ai-search-visibility Q: Can I fake publish dates to look more recent? A: Do not fake dates. LLMs can detect when "updated January 2026" content only references sources from 2023 or earlier. Google has explicitly warned against artificially updating dateModified without making substantive content changes. The risk of being penalized outweighs any short-term benefit. Source: /blog/how-publish-date-affects-ai-search-visibility Q: How does content freshness differ from publish date? A: Publish date is metadata - a tag in your schema. Content freshness is whether the actual text reflects current information. A page with dateModified=2026 but only 2023-era statistics is stale despite its date tag. AI engines evaluate both the metadata and the content itself. For a broader look at freshness signals, see our article on content freshness and AI search visibility. Source: /blog/how-publish-date-affects-ai-search-visibility Q: Which date formats do AI crawlers understand? A: Use ISO 8601 format (YYYY-MM-DD) in your Schema.org JSON-LD - this is the standard all AI crawlers parse. For visible dates on the page, use human-readable formats like "April 9, 2026" or "Last updated: 2026-04-09." Having both structured and visible dates is ideal. Source: /blog/how-publish-date-affects-ai-search-visibility Q: Can you really manipulate which products AI recommends? A: Yes. The CORE paper demonstrated a 91.4% success rate for pushing products into LLM Top-5 recommendations by appending optimized content to product descriptions. This worked across four major LLMs (GPT-4o, Gemini-2.5, Claude-4, Grok-3) and 15 Amazon product categories. The optimized content was designed to sound natural, not spammy. Source: /blog/how-llms-rank-products-core-paper Q: What are the three content optimization strategies from the CORE paper? A: String-based (text patterns in descriptions), reasoning-based (logical arguments like "why this product is the best choice for X"), and review-based (social proof from customer reviews). Reasoning-based and review-based were the most effective and also the most ethical to apply genuinely. Source: /blog/how-llms-rank-products-core-paper Q: Does traditional SEO still matter for AI product recommendations? A: Yes, significantly. The CORE paper found that LLM output rankings are heavily influenced by the initial order of results returned by external search engines. If your product ranks low in traditional search, it starts at a disadvantage in LLM recommendations regardless of content quality. Source: /blog/how-llms-rank-products-core-paper Q: Is optimizing product descriptions for AI search ethical? A: It depends on the approach. Adding genuine reasoning ("why customers choose this product"), authentic reviews, and clear product benefits is legitimate optimization. Appending hidden or misleading content designed solely to game LLM rankings crosses the line. We advocate for making content genuinely better, not for manipulation. Source: /blog/how-llms-rank-products-core-paper Q: How can I check if my product pages are optimized for AI recommendations? A: Check three things: (1) Do your product pages include reasoning-based content explaining why the product solves a problem? (2) Do you have authentic customer reviews with specific details? (3) Are your comparative advantages clearly stated? Our AI Search Readiness tool checks these signals automatically. Source: /blog/how-llms-rank-products-core-paper Q: Does llms.txt actually work for AI search optimization? A: Based on our 28-day experiment, there is no evidence that llms.txt changes AI crawler behavior. GoogleOther fetched it once, but no other bot accessed it. No change in crawl patterns or citation behavior was observed. It's low-cost to deploy (15 minutes) but currently has no demonstrated benefit. Source: /blog/ai-skills-manifest-experiment-results Q: What is a skills manifest (skills.json) and should I implement one? A: A skills manifest is a JSON file that describes your site's capabilities and API endpoints for AI systems. LightSite AI promoted this concept, claiming it changes bot behavior. Our experiment found zero bots accessed skills.json over 14 days. There is no W3C or IETF standard backing this format and no AI lab has committed to supporting it. Source: /blog/ai-skills-manifest-experiment-results Q: Did any AI bot use the structured content APIs? A: No. We deployed four API endpoints (/api/ai/blog, /api/ai/faq, /api/ai/methodology, /api/ai/blog/:slug) and tracked all bot requests for 14 days. Zero hits from any AI crawler. AI bots continue to crawl standard HTML pages, not structured APIs. Source: /blog/ai-skills-manifest-experiment-results Q: How does this compare to LightSite AI's claims? A: LightSite AI claimed 3x ChatGPT traffic increase and 5x Q&A visits after deploying a skills manifest. We saw +10% ChatGPT traffic (within natural variation) and zero API consumption. Key differences: LightSite had no baseline period, their system uses a proxy that routes bot traffic, and their results are not independently reproducible. Source: /blog/ai-skills-manifest-experiment-results Q: Is this experiment statistically valid? A: This is an observational case study on a single site, not a randomized controlled trial. We cannot prove causation in either direction. What we can say: on our site, deploying the full recommended AI discoverability stack produced no measurable change in bot behavior over 14 days. We are transparent about limitations including no control group, single site, and simultaneous deployment. Source: /blog/ai-skills-manifest-experiment-results Q: What is the difference between traditional SEO and AI search optimization? A: Traditional SEO optimizes for keyword matching and backlink authority to rank in search engine results pages. AI search optimization (GEO) focuses on making your content extractable and citable by large language models. The key difference: AI systems parse your content into passages and evaluate each one independently for clarity, self-containedness, and relevance to the query - not for keyword density or domain authority. Source: /blog/science-behind-ai-search-optimization Q: Do I still need Schema.org markup for AI search? A: Yes, but it's not sufficient on its own. Schema.org helps AI systems identify entities and attributes on your pages, but our research showed that structured data alone doesn't predict citation rates. What matters more is how clearly your natural language text conveys entity-attribute relationships. Think of Schema.org as a supplement to clear writing, not a replacement for it. Source: /blog/science-behind-ai-search-optimization Q: How often should I audit my content for AI readiness? A: AI systems are probabilistic - results vary between queries and over time. We recommend a quarterly audit of your key pages, with continuous monitoring of citation rates for your target queries. Major content updates or site redesigns should trigger an immediate re-audit. Source: /blog/science-behind-ai-search-optimization Q: Is AI search optimization relevant for B2B or only e-commerce? A: It's relevant for any business that wants to be found through AI-assisted search. When a procurement manager asks ChatGPT "what are the best project management tools for remote teams," the same passage-scoring and entity-extraction mechanisms apply. B2B companies with clear, well-structured service descriptions and thought leadership content often perform well in AI citations. Source: /blog/science-behind-ai-search-optimization Q: What is the difference between being cited and being recommended by AI? A: Being cited means AI quotes your content as a source (drives traffic). Being recommended means AI names your brand in its answer (builds awareness). GEO pioneer Olaf Kopp calls these two distinct disciplines: LLM Readability Optimization (citability) and Brand Context Optimization (recommendability). Both matter, and they require different optimization strategies. Source: /blog/science-behind-ai-search-optimization Q: Can ChatGPT crawl React-based websites? A: Yes, but with significant limitations. While it can execute some JavaScript, it often times out or fails to wait for async API calls to complete. If your content isn't in the initial HTML, there is a high risk it won't be indexed for citations. Source: /blog/why-ai-crawlers-javascript Q: How do I know if an AI bot can see my JS content? A: The easiest test is to disable JavaScript in your browser and reload the page. If the content disappears, AI bots likely can't see it either. You can also use our AI Search Readiness Tool to simulate a bot crawl. Source: /blog/why-ai-crawlers-javascript Q: Does Next.js solve this automatically? A: Only if you use Server Components or SSR (getServerSideProps). If you use "use client" for your main content blocks and fetch data inside a useEffect, you are still vulnerable to the "blank page" problem for AI bots. Source: /blog/why-ai-crawlers-javascript Q: Is the Content Relevance audit really free? A: Yes. The free tier runs the full four-component audit (Query Coverage, Content Depth, Sub-Intent Coverage, Technical Health) with per-query breakdowns, sub-intent gap analysis, and top recommendations. No credit card, no trial period, unlimited rescans. The Starter consultation (149 one-time, 4 slots/month) adds Citation Reality via Perplexity and a human expert with 20-40 prioritized rewrite tasks. Source: /blog/free-ai-search-readiness-tool Q: What does the tool check? A: Five components: (1) Query Coverage - what fraction of target queries any page on the site answers; (2) Content Depth - how deeply the best page addresses each query; (3) Sub-Intent Coverage - whether the site covers the full fan-out of information needs; (4) Citation Reality - whether Perplexity currently cites the site (paid only); (5) Technical Health - the 26 legacy technical checks (schema, crawl access, content structure, trust signals) as one subcomponent with 15-20% weight. Source: /blog/free-ai-search-readiness-tool Q: How long does the scan take? A: A few minutes. The scanner discovers pages via sitemap.xml, crawls up to 50 pages with Playwright (simulating AI bots), runs 26 technical checks, generates 20 monitoring queries via GPT-4o, then evaluates content relevance per query. You can edit the queries before analysis runs. Source: /blog/free-ai-search-readiness-tool Q: Does it work for non-e-commerce sites? A: Yes. The Content Relevance Score measures query-content match, which applies to any business type. The query generation adapts to your niche. Technical Health checks include vertical-specific items for e-commerce, SaaS, B2B services, local businesses, and content/media sites. Source: /blog/free-ai-search-readiness-tool Q: How do I interpret my score? A: 0-29: major content and technical gaps, AI engines unlikely to cite you. 30-59: some query coverage but significant gaps in depth or sub-intent coverage. 60-79: solid content relevance, citations plausible for covered queries. 80+: strong coverage across target queries. Note: a high score means strong content relevance, not guaranteed citations. Source: /blog/free-ai-search-readiness-tool Q: What is ChatGPT Shopping? A: ChatGPT Shopping is OpenAI's product discovery feature that lets users find and compare products directly inside ChatGPT conversations. When a user asks "What's the best running shoe under $150?", ChatGPT can display product cards with images, prices, reviews, and direct links — but only from sites with proper structured data and crawl access. Source: /blog/audit-chatgpt-shopping-visibility Q: Does ChatGPT Shopping use Google Shopping data? A: No. ChatGPT Shopping has its own crawler (OAI-SearchBot) and indexing system. Having your products in Google Shopping does not automatically make them visible in ChatGPT. You need to ensure OAI-SearchBot can access your site and that your Product schema markup is complete. Source: /blog/audit-chatgpt-shopping-visibility Q: How do I check if OAI-SearchBot can crawl my site? A: Check your robots.txt file for any rules blocking OAI-SearchBot or ChatGPT-User user agents. Many sites inadvertently block AI crawlers. You should see no Disallow rules for these user agents, or explicitly add Allow: / for them. Source: /blog/audit-chatgpt-shopping-visibility Q: What Product schema fields does ChatGPT Shopping need? A: At minimum: name, description, image, offers (with price, priceCurrency, availability), brand, and sku. For better visibility, also include gtin/mpn, aggregateRating, review, and category. All offers must have valid schema.org availability values like InStock or OutOfStock. Source: /blog/audit-chatgpt-shopping-visibility Q: How is AI search readiness different from regular SEO for e-commerce? A: Traditional e-commerce SEO optimizes for ranking position via keywords, backlinks, and page speed. AI search readiness optimizes for citation in AI-generated answers. Our research found the strongest predictor is content relevance - whether your pages actually answer the queries users ask AI engines, including sub-intents like safety info, comparisons, and alternatives. Technical signals (schema, crawl access) are necessary hygiene but don't predict citations on their own. Source: /blog/ai-search-readiness-checklist-ecommerce Q: Which items on the checklist have the highest impact? A: The content relevance items have the highest impact on citations: mapping your content to actual user queries, closing sub-intent gaps, and building content depth on product and category pages. On the technical side, the top priorities are: robots.txt allowing AI crawlers, Product schema with complete Offer data, and FAQ sections with FAQPage schema. Source: /blog/ai-search-readiness-checklist-ecommerce Q: How often should I re-audit my site? A: Monthly for content relevance - competitor content evolves and new queries emerge. Technical health rarely regresses unless you change CMS or redesign. Re-audit immediately after major content updates. Our free tool allows unlimited rescans. Source: /blog/ai-search-readiness-checklist-ecommerce Q: Can I use this checklist for a non-e-commerce site? A: The content relevance section applies to all site types - query coverage, content depth, and sub-intent coverage are universal. The technical health section is mostly universal too, except the e-commerce-specific items (Product/Offer schema, GTIN/MPN, pricing markup). For SaaS or service sites, replace those with feature page completeness and case study schema. Source: /blog/ai-search-readiness-checklist-ecommerce Q: Does Perplexity have its own crawler? A: Yes. Perplexity uses PerplexityBot as its web crawler. Check your robots.txt to ensure it is not blocked. Perplexity also uses its own indexing pipeline separate from Google, so being indexed by Google does not guarantee visibility in Perplexity. Source: /blog/products-not-showing-perplexity Q: Why does Perplexity cite my competitor but not me? A: The most common reasons are: your competitor has better structured data (Product schema with complete offers), more review signals (aggregateRating), and answer-ready content (FAQ sections, comparison tables). Perplexity favors pages that directly answer the user's question with structured, extractable data. Source: /blog/products-not-showing-perplexity Q: How can I test if Perplexity can see my products? A: Search for your exact product name in Perplexity. If it doesn't appear, search for your brand + product category. Then check: (1) Is PerplexityBot allowed in robots.txt? (2) Does Google's Rich Results Test show valid Product schema? (3) Is your product description at least 100 words of crawlable text (not rendered only by JavaScript)? Source: /blog/products-not-showing-perplexity Q: Which schema type matters most for AI search? A: Product schema with complete offers data (price, currency, availability, brand, sku, gtin) is the highest-impact schema type for e-commerce. For non-e-commerce sites, FAQPage and Organization schema have the highest impact. BreadcrumbList helps all site types by providing navigation context to AI crawlers. Source: /blog/schema-markup-ai-search-ecommerce Q: Should I use JSON-LD or Microdata for AI search? A: Always use JSON-LD. It is the format recommended by Google, and AI crawlers parse it most reliably because it is a standalone script block that does not depend on HTML structure. Microdata is harder to maintain and more error-prone. Source: /blog/schema-markup-ai-search-ecommerce Q: How do I validate my schema markup? A: Use Google's Rich Results Test (search.google.com/test/rich-results) to validate syntax and check for required fields. Then use Schema.org's validator (validator.schema.org) for completeness. Finally, test with our AI Search Readiness tool to see how your markup scores in the Machine Readability dimension. Source: /blog/schema-markup-ai-search-ecommerce Q: Can too much schema hurt my AI visibility? A: No — but incorrect or misleading schema can. AI engines penalize schema that contradicts visible page content (e.g., schema showing a price that doesn't match the displayed price). Always ensure your structured data accurately reflects what users see on the page. Source: /blog/schema-markup-ai-search-ecommerce Q: What is citation rate in AI search? A: Citation rate is the percentage of relevant AI-generated answers that include a link to or mention of your site. For example, if there are 20 queries relevant to your business and your site is cited in 4 of those answers, your citation rate is 20%. It is the AI search equivalent of keyword rankings in traditional SEO. Source: /blog/improve-citation-rate-ai-search Q: How do I track my citation rate? A: Manually: create a list of 20–30 target queries, search them in ChatGPT, Perplexity, and Google AI Overviews weekly, and record when your site appears. Automatically: use our premium citation monitoring feature, which tracks your citation rate across all major AI search platforms and alerts you to changes. Source: /blog/improve-citation-rate-ai-search Q: How long does it take to improve citation rate? A: Most sites see initial improvements within 2–4 weeks after implementing structured data and answer-ready content. Significant citation rate increases (from 0% to 15%+) typically take 30–60 days, as AI engines need time to re-crawl and re-index your updated pages. Source: /blog/improve-citation-rate-ai-search Q: Does traditional SEO affect AI citation rate? A: Partially. Sites with strong domain authority and backlinks have a slight advantage because AI engines consider source trustworthiness. However, a site with low domain authority but excellent structured data and answer-ready content will outperform a high-authority site with poor AI readiness. Source: /blog/improve-citation-rate-ai-search Q: Does ChatGPT use a web crawler? A: Yes. ChatGPT uses two crawlers: OAI-SearchBot (for browsing/search features) and GPTBot (for training data). For your site to appear in ChatGPT answers, at minimum OAI-SearchBot must be allowed in your robots.txt. Blocking GPTBot does not prevent citation — but allowing both gives best results. Source: /blog/why-not-cited-chatgpt Q: Can I submit my site to ChatGPT like Google Search Console? A: No. There is no submission tool or webmaster console for ChatGPT. The only way to get cited is to ensure your site is crawlable, has proper structured data, and contains answer-ready content that ChatGPT finds useful for user queries. Source: /blog/why-not-cited-chatgpt Q: How often does ChatGPT re-crawl sites? A: ChatGPT's crawl frequency is not publicly documented, but evidence suggests popular pages are re-crawled weekly while less popular pages may take 2–4 weeks. Ensuring your sitemap.xml is up-to-date and your pages have fresh lastmod dates helps signal that re-crawling is worthwhile. Source: /blog/why-not-cited-chatgpt Q: Is Perplexity Shopping different from regular Perplexity search? A: Yes. Perplexity Shopping is a dedicated product search mode that displays product cards with images, prices, and reviews. It requires more complete Product schema than regular Perplexity search. Regular search may cite your site as a text source even without Product schema, but Shopping features require structured product data. Source: /blog/perplexity-not-showing-products Q: What is the minimum Product schema Perplexity needs? A: At minimum: name, description, image (high-res, at least 800x800), offers with price and priceCurrency, offers.availability (InStock/OutOfStock), and brand. Without all of these fields, Perplexity Shopping will not display your product cards. Adding aggregateRating significantly boosts the likelihood of being selected over competitors. Source: /blog/perplexity-not-showing-products Q: How do I know if PerplexityBot is crawling my site? A: Check your server access logs for the user agent string "PerplexityBot". If you use Cloudflare or similar CDN, check the bot traffic analytics. If you don't see PerplexityBot visits, ensure your robots.txt is not blocking it and that your sitemap.xml is accessible. Also check Cloudflare Bot Fight Mode — it often blocks AI crawlers silently. Source: /blog/perplexity-not-showing-products Q: My competitors appear in Perplexity Shopping but I don't — why? A: This usually indicates a combination of stronger structured data (complete Product + Offer + Review schema) and better offer clarity (clearer use-case positioning, more reviews). Use the symptom table in this article to narrow down your specific gap, then focus on the Extractability and Offering dimensions of your audit. Source: /blog/perplexity-not-showing-products Q: What are Google AI Overviews? A: Google AI Overviews (previously called Search Generative Experience or SGE) are AI-generated answer panels that appear at the top of Google search results. They synthesize information from multiple sources and include citation links. As of 2026, they appear for over 30% of Google searches. Source: /blog/get-cited-google-ai-overviews Q: Do I need to rank in the top 10 to appear in AI Overviews? A: Having a top-10 organic ranking significantly increases your chances, as Google AI Overviews heavily draw from pages already ranking well. However, pages ranking 11–20 can also get cited if they have superior answer-ready content format and strong E-E-A-T signals. Pages outside the top 30 are rarely cited. Source: /blog/get-cited-google-ai-overviews Q: How are Google AI Overviews different from featured snippets? A: Featured snippets pull from a single source and display a direct excerpt. AI Overviews synthesize information from 3–8 sources into a new AI-generated answer with inline citations. The content format that works best is also different: featured snippets favor exact-match answers, while AI Overviews favor comprehensive, well-structured content across multiple subtopics. Source: /blog/get-cited-google-ai-overviews Q: Can I track my AI Overview citations? A: Google Search Console does not yet provide AI Overview citation data. You can manually track by searching your target queries with AI Overviews enabled. Our premium citation monitoring tool automates this across ChatGPT, Perplexity, and Google AI Overviews. Source: /blog/get-cited-google-ai-overviews Q: Why does AI search care about language consistency? A: AI search engines like ChatGPT, Perplexity, and Google AI Overviews are "answer machines" — they match a user's query (in a specific language) to sources that contain a direct answer in that same language. If your product descriptions are in English and your user is asking in Portuguese, the AI engine cannot reliably identify your page as a relevant source, even if the product perfectly matches the query. Language consistency is not a cosmetic issue — it is a structural data quality issue. Source: /blog/mixed-language-content-ai-search Q: What are hreflang tags and why do they matter for AI search? A: Hreflang tags are HTML attributes that tell search engines (and AI crawlers) which language and region a specific page version is intended for. Without them, a site with mixed-language content creates technical ambiguity: the AI crawler cannot determine whether your site is a Portuguese resource with English product data or an English resource with a Portuguese interface. Adding hreflang tags resolves this ambiguity explicitly, which improves Machine Readability scores and helps AI engines route your pages to the right audience. Source: /blog/mixed-language-content-ai-search Q: Does my schema.org markup need to match the page language? A: Yes. Schema.org fields like Product name and description should be written in the same language as the visible page content. When the schema shows an English product name on a Portuguese page, AI engines detect a data mismatch — a signal associated with poor data quality or auto-generated content. This mismatch reduces the page's trust score and lowers its chances of being cited in AI-generated answers. Source: /blog/mixed-language-content-ai-search Q: Is it better to have separate pages per language or use auto-translation? A: Separate language versions with hreflang tags are always better than auto-translation on a single page. Auto-translation mixed into existing content creates the exact ambiguity that harms AI readability. Dedicated language pages allow proper schema.org markup in the correct language, clear hreflang relationships, and content that is truly answer-ready for each target audience — all of which improve AI search citation rates. Source: /blog/mixed-language-content-ai-search Q: What makes data "AI-ready"? A: AI-ready data has five characteristics: (1) accuracy and completeness — it reflects reality without gaps, (2) consistent structure and labeling — uniformly marked up so algorithms can interpret it without ambiguity, (3) rich metacontext — includes business definitions, data lineage, and clear usage rules, (4) governance — clear access controls, ownership, and privacy compliance, and (5) AI task optimization — prepared for specific workloads such as machine learning or generative AI. Source: /blog/what-is-ai-ready-data Q: How does AI-ready data differ from "clean" data? A: Clean data simply means data without errors, duplicates, or missing values. AI-ready data goes further: it is not only accurate but also structured for machine interpretation (e.g., with schema.org markup), enriched with metadata that explains its meaning and origin, governed with access policies, and specifically optimized for the AI workload it will power. A spreadsheet can be "clean" but still be completely unusable by an AI system. Source: /blog/what-is-ai-ready-data Q: Why do AI models hallucinate, and how does data quality prevent it? A: AI models amplify whatever qualities the data they are fed has. When data is inconsistent or poorly structured, models drift — producing unpredictable and untrustworthy results. A classic example: a hospital readmission prediction model gave false outputs simply because different hospitals recorded admission time in different formats. AI-ready data, with its consistent structure and metacontext, eliminates these inconsistencies before they reach the model. Source: /blog/what-is-ai-ready-data Q: How do I make my website data AI-ready? A: For websites, becoming AI-ready means: (1) adding Schema.org structured data (Product, FAQPage, Organization, BreadcrumbList) so AI crawlers understand your content, (2) ensuring your robots.txt allows AI crawlers (GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot), (3) writing answer-ready content — TL;DR blocks, FAQ sections, comparison tables — so AI can extract direct answers, (4) maintaining NAP consistency and authorship signals for trust, and (5) keeping content fresh and your sitemap.xml up to date. Use our free AI Search Readiness audit to see where you stand. Source: /blog/what-is-ai-ready-data Q: What is a Content Relevance Score? A: A Content Relevance Score (0-100) measures whether a website's content actually answers the queries its audience asks AI search engines like ChatGPT, Perplexity, and Google AI Overviews. It evaluates five components: Query Coverage, Content Depth, Sub-Intent Coverage, Citation Reality (paid scans), and Technical Health. Content signals carry 80-85% of the weight. Source: /blog/what-is-ai-search-readiness-score Q: How is a Content Relevance Score different from a traditional SEO score? A: Traditional SEO scores measure ranking signals: backlinks, keyword density, page speed. A Content Relevance Score measures citation signals: does your content answer the specific queries users ask AI engines, and does it cover the sub-intents behind those queries? A site can rank well in Google but score poorly on content relevance if it doesn't address the questions AI users actually ask. Source: /blog/what-is-ai-search-readiness-score Q: What are the five components of the score? A: The five components are: (1) Query Coverage - what fraction of target queries any page on the site can answer; (2) Content Depth - how deeply the best page answers each query; (3) Sub-Intent Coverage - whether the site addresses the full range of information needs behind each query; (4) Citation Reality - whether Perplexity already cites the site (paid scans only); (5) Technical Health - the 26 legacy technical checks as one subcomponent with 15-20% weight. Source: /blog/what-is-ai-search-readiness-score Q: Why did you rebuild the score from a 26-check model? A: We tested our original 26-check technical readiness score against actual AI citation rates across 441 domains and 14,550 domain-query pairs. The result: r=0.009, p=0.849 - statistically zero. The technical score did not predict which sites get cited. The follow-up study showed content relevance (measured via BM25 plus embedding similarity) predicted citations with AUC 0.915. We rebuilt the product around that finding. Source: /blog/what-is-ai-search-readiness-score Q: Why do 90% of sites fail the customer reviews check? A: Most businesses collect reviews on third-party platforms (Google, Trustpilot, Yelp) but don't embed them on their own website with AggregateRating schema. AI engines that parse structured data can use this review data as a trust signal. The fix requires displaying reviews on your site with Schema.org markup. This is part of the Technical Health subcomponent. Source: /blog/what-is-ai-search-readiness-score Q: Does improving the Content Relevance Score actually increase citations? A: Content relevance is the strongest empirical predictor of AI citations we have found (AUC 0.915). However, we have not yet published a before/after case study proving that applying our specific recommendations raises a real site's citation rate - that experiment is running now. The score measures the signal with the best research backing. That is not the same as a guarantee. Source: /blog/what-is-ai-search-readiness-score Q: How often should I check my Content Relevance Score? A: Re-scan after making content changes to verify improvement. Content relevance shifts as competitor content evolves and AI engines update their retrieval pipelines. Monthly scans catch regressions. The free tier allows unlimited rescans. Source: /blog/what-is-ai-search-readiness-score Q: What happened to the old four-dimension model (MR, EX, TR, OR)? A: The 26 technical checks from the old model are still in the pipeline as the Technical Health subcomponent (15-20% weight). They check real things - schema markup, crawl access, content structure, trust signals - but our research showed they don't predict citations on their own. They are now treated as hygiene, not strategy. Source: /blog/what-is-ai-search-readiness-score Q: Is LLM SEO the same as GEO (Generative Engine Optimization)? A: They are effectively the same discipline under different names. GEO was coined in academic research (Princeton, 2023) to describe optimizing for generative AI search. LLM SEO is the practitioner term emphasizing the large language model layer. Both refer to the same goal: getting content cited in AI-generated responses rather than simply ranked in a list. Source: /blog/what-is-llm-seo Q: Does LLM SEO replace traditional SEO? A: No — it adds a layer on top of it. Traditional SEO remains important because AI engines like Google AI Overviews draw heavily from pages already ranking well in organic search. However, ranking alone is not enough. LLM SEO adds the structured data, answer formats, and entity signals that determine whether a ranking page is actually cited in an AI-generated answer. Source: /blog/what-is-llm-seo Q: What is the most important LLM SEO technique? A: Answer-ready content format combined with Schema.org structured data is the highest-impact combination. AI engines retrieve content in 300–800 token chunks — a clear heading followed by a 40–60 word answer block becomes a single retrievable chunk that directly matches user queries. Schema tells AI engines what your content represents. Neither alone is sufficient — you need both. Source: /blog/what-is-llm-seo Q: How do I measure LLM SEO success? A: The primary metric is citation probability — the percentage of relevant AI queries where your site is cited across multiple runs (LLM responses are non-deterministic). Track 20–30 target queries across ChatGPT, Perplexity, and Google AI Overviews weekly. Across 1,615 citation checks on 98 websites, the average citation rate is 18.1%. Source: /blog/what-is-llm-seo Q: What is the Readiness Paradox in AI search? A: Our data shows that websites scoring 80–100 on AI readiness have only 1.8% citation rate, while sites scoring 0–19 have 38.8%. This is because low-scoring but well-known brands get cited via domain authority, while high-scoring small sites lack brand recognition. Technical readiness is necessary but not sufficient — it must be combined with original data and domain authority. Source: /blog/what-is-llm-seo Q: How do RAG systems chunk web content? A: RAG pipelines split your page content into chunks of roughly 300–800 tokens, typically aligned with heading boundaries. Each chunk is embedded as a vector and stored independently. When a user queries an AI engine, the system retrieves the most semantically similar chunks — not full pages. This means each heading section should be self-contained and answerable without surrounding context. Source: /blog/what-is-llm-seo Q: If I rank #1 in Google, do I automatically appear in Google AI Overviews? A: Not automatically. Google AI Overviews draw heavily from top-ranking pages, so organic ranking helps. But our research showed that technical readiness alone (including ranking signals) doesn't predict AI citations. Pages that rank well but don't actually answer the specific query with sufficient depth and sub-intent coverage get skipped in favor of more relevant content. Source: /blog/ai-search-readiness-vs-traditional-seo Q: Does working on AI search readiness hurt traditional SEO? A: No - virtually all AI readiness improvements also benefit traditional SEO. Adding Schema.org markup improves rich results. Adding FAQ content improves featured snippet potential. Improving content depth and query relevance improves rankings. The work is additive. Source: /blog/ai-search-readiness-vs-traditional-seo Q: Why did your original 26-check technical score fail to predict citations? A: We tested it across 441 domains and 14,550 domain-query pairs. The correlation with actual AI citations was r=0.009 (p=0.849) - statistically zero. The checks accurately detected real technical issues (missing schema, blocked crawlers, thin content), but fixing those issues alone didn't make sites more likely to be cited. Citation depends primarily on content-query relevance, not structural hygiene. Source: /blog/ai-search-readiness-vs-traditional-seo Q: What is the mixed-language problem in AI search? A: AI engines convert page content to vector embeddings for semantic search. A page with mixed languages (e.g., English URLs + German descriptions + French reviews) produces a confused embedding that matches poorly in every language. Traditional SEO handles this via hreflang, but AI engines need all text on a page - including Schema.org fields - to be in the same language. Source: /blog/ai-search-readiness-vs-traditional-seo Q: What are the five components of the new Content Relevance Score? A: Query Coverage (what fraction of target queries the site answers), Content Depth (how deeply pages address each query), Sub-Intent Coverage (whether the site covers the full fan-out of information needs behind each query), Citation Reality (whether Perplexity already cites the site - paid scans only), and Technical Health (the legacy 26 technical checks as one subcomponent, 15-20% weight). Source: /blog/ai-search-readiness-vs-traditional-seo Q: What is an entity passport for AI search? A: An entity passport is the minimum Schema.org structured data a business needs for AI engines to treat it as an identified source: Organization schema with name, URL, founder (Person schema with jobTitle), and sameAs links to LinkedIn and Google Maps. It is part of the Technical Health layer - necessary for trust, but not sufficient for citation without content relevance. Source: /blog/ai-search-readiness-vs-traditional-seo Q: How does content freshness affect AI search citation probability? A: Freshness is a trust signal, not a direct ranking factor. For time-sensitive queries (pricing, availability, comparisons), pages with recent dateModified signals are preferred. For evergreen content (definitions, historical analysis), freshness has less impact. Our data shows sites with dateModified present score 35.6 points higher on AI readiness, though this likely reflects overall structured data maturity. Source: /blog/content-freshness-ai-search-visibility Q: Should I change the URL when I update old content? A: No. Changing the URL destroys all backlink equity and resets authority. Update content in place, change only dateModified in schema and lastmod in sitemap. This preserves authority while resetting the freshness clock. Source: /blog/content-freshness-ai-search-visibility Q: How do I add freshness signals that AI engines can read? A: Three layers: (1) Add datePublished and dateModified to Article or WebPage JSON-LD schema. (2) Set lastmod on each URL in sitemap.xml. (3) Include a visible "Last updated: [date]" on the page. All three should show the same date. Different AI platforms weight these layers differently. Source: /blog/content-freshness-ai-search-visibility Q: How often should I update content? A: Pricing and availability: every change plus quarterly review. Product pages: monthly. Comparison articles: quarterly. How-to guides: annually. FAQ pages: whenever answers change. The minimum signal is updating dateModified in schema when content actually changes. Source: /blog/content-freshness-ai-search-visibility Q: What is the biggest freshness mistake websites make? A: Creating year-specific URLs ("/best-tools-2026") instead of updating content at an evergreen URL ("/best-tools"). This destroys backlink equity. The second biggest: 62% of pages have no date signal at all, making it impossible for AI engines to assess content currency. Source: /blog/content-freshness-ai-search-visibility Q: Do AI engines verify that dateModified reflects real content changes? A: There is no public documentation confirming this, but it is a reasonable assumption. AI systems may compare historical snapshots. Best practice: only update date signals when you make substantive content changes. Source: /blog/content-freshness-ai-search-visibility Q: Which page types need freshness signals most urgently? A: Product pages (only 50.2% have dateModified), category pages (0% coverage), and homepages (16.3%). These pages often contain time-sensitive information but are least likely to have date signals. Articles already have 86% coverage thanks to CMS defaults. Source: /blog/content-freshness-ai-search-visibility Q: Does content freshness affect all AI search engines equally? A: No. Google AI Overviews directly parses JSON-LD dateModified. ChatGPT and Perplexity primarily extract text and may rely more on visible dates and HTML metadata. Implementing all three signal layers (schema, OG meta, visible text) covers all platforms. Source: /blog/content-freshness-ai-search-visibility Q: How do I choose the right AI search readiness tool? A: First, define your primary job: diagnose content gaps, monitor citations over time, or get someone to optimize for you. Apply budget constraints - enterprise monitoring (Conductor) costs five figures annually, while content diagnostics (LLM SEO Check) are free or one-time. Then ask: does the tool measure content relevance or only structural signals? Our research showed structural signals alone don't predict citations (r=0.009). Source: /blog/best-ai-search-readiness-tools-2026 Q: What should an AI search readiness tool actually measure? A: Six things matter: (1) Content relevance - does the tool check whether your content answers the queries your audience asks? (2) AI crawler access - robots.txt rules for GPTBot, PerplexityBot, ClaudeBot. (3) Structured data depth - Schema.org completeness. (4) Citation monitoring - actual citation rates. (5) Methodology transparency. (6) Published evidence that the tool's signals correlate with citation outcomes. No tool today scores perfectly on all six. Source: /blog/best-ai-search-readiness-tools-2026 Q: What is the difference between a content relevance diagnostic and a citation monitoring tool? A: A content relevance diagnostic analyzes your content against specific queries and tells you where the gaps are - which queries you don't cover, which sub-intents you miss. A citation monitoring tool tracks how often AI engines actually cite you over time. The first tells you what to fix. The second tells you if it worked. You typically need both. Source: /blog/best-ai-search-readiness-tools-2026 Q: Are free AI search readiness tools accurate enough? A: It depends on what they measure. Free tools checking structural signals (schema, robots.txt, meta tags) are accurate for what they check - but structural signals don't predict citations. Our free tier runs the full Content Relevance Score (QC, CD, SI, TH) using GPT-4o evaluation. The paid tier adds Citation Reality and human expert analysis. Source: /blog/best-ai-search-readiness-tools-2026 Q: How often should I re-run an AI search readiness audit? A: Re-scan after content changes to verify improvement. Monthly for active sites. Technical Health rarely regresses unless you change CMS. Content relevance shifts as competitors publish and AI retrieval evolves. The free tier allows unlimited rescans. Source: /blog/best-ai-search-readiness-tools-2026 Q: What is the Universal Commerce Protocol (UCP)? A: UCP is a technical standard that enables AI agents (like Google Gemini) to discover merchants, understand their capabilities, and complete purchases directly within AI interfaces — without requiring custom integrations for each store. Think of it as a universal API for agentic shopping. Source: /blog/ucp-agentic-commerce-strategy-ecommerce Q: Does UCP improve my AI search citations? A: No. UCP is a transaction layer, not a discovery layer. It does not improve how often ChatGPT, Perplexity, or Google AI Overviews cite your site. For better citations, focus on AI Search Readiness (schema.org markup, extractable content, trust signals). UCP only helps convert citations into purchases. Source: /blog/ucp-agentic-commerce-strategy-ecommerce Q: When should I implement UCP? A: Implement UCP as Phase 2, only after three conditions are met: (1) your product data is pristine with zero price/availability mismatches, (2) your primary conversion losses are at the cart/checkout stage, and (3) your main traffic source is Google. For most SMBs, waiting for CMS plugin support is the pragmatic choice. Source: /blog/ucp-agentic-commerce-strategy-ecommerce Q: Is UCP the same as Google Shopping? A: No. Google Shopping is a product listing and comparison surface. UCP is a protocol that allows AI agents to execute the full checkout cycle (add to cart, enter payment, confirm order) natively within the AI interface. UCP builds on top of product data but extends far beyond listing. Source: /blog/ucp-agentic-commerce-strategy-ecommerce Q: How does LLM SEO Check differ from Conductor? A: Conductor is enterprise brand monitoring with continuous AI citation tracking, keyword dashboards, and competitor analysis. LLM SEO Check is a one-off content relevance diagnostic: we decompose queries into sub-intents, check whether your content covers them, and tell you where the gaps are. Conductor gives you trends over time. We give you a deep per-query, per-sub-intent diagnosis. Different tools for different problems. Source: /blog/ai-search-readiness-score-vs-conductor-monitoring Q: Is LLM SEO Check better for small businesses? A: For diagnosis, yes. The free tier runs the full Content Relevance Score audit - no paywall on core value. The Starter consultation is 149 one-time, not a recurring contract. But we don't offer continuous monitoring. If a small business needs ongoing citation tracking, they still need a monitoring tool (Conductor, Otterly, or similar) alongside our diagnostic. Source: /blog/ai-search-readiness-score-vs-conductor-monitoring Q: Does your tool provide citation monitoring like Conductor? A: Citation Reality (Perplexity monitoring) runs once per paid scan - it checks whether Perplexity currently cites your site for each monitoring query. It is a snapshot, not a continuous feed. Conductor provides ongoing citation tracking across multiple AI platforms. If you need continuous monitoring, Conductor does that. We focus on the content relevance diagnosis that tells you what to fix. Source: /blog/ai-search-readiness-score-vs-conductor-monitoring Q: How do I buy the Starter consultation? A: Run a free scan first at getaisearchscore.com. Review your Content Relevance Score and per-query breakdown. If you want Citation Reality data plus human expert analysis, purchase the Starter consultation (149 one-time) from your results page via Stripe. We process up to 4 consultations per month to keep quality high. Source: /blog/buy-ai-search-readiness-tool-pricing-guide Q: What does the free tier actually include? A: The full four-component audit: Query Coverage, Content Depth, Sub-Intent Coverage, and Technical Health. Plus per-query breakdowns, sub-intent gap analysis, and top recommendations. No login required, no credit card, unlimited rescans. We don't gate core diagnostic value behind a paywall. Source: /blog/buy-ai-search-readiness-tool-pricing-guide Q: Why is there no subscription/monitoring tier? A: Content relevance is a strategic problem, not a monitoring problem. You fix content gaps, then rescan for free to verify. Continuous monitoring of citation rates is valuable but a different product - tools like Conductor handle that well. Our focus is diagnosis plus expert interpretation, not dashboards. Source: /blog/buy-ai-search-readiness-tool-pricing-guide Q: Why did diveshop.pt score so low (19/100)? A: The low score was primarily due to three factors: (1) Total lack of Schema.org structured data, (2) A missing product sitemap that prevented crawlers from finding product pages, and (3) Language inconsistency where the UI was in Portuguese but product descriptions were in English. Source: /blog/ai-search-readiness-audit-review-diveshop-pt Q: What was the citation rate for the baseline check? A: The baseline citation rate was 0/30 (0%). Despite having relevant products, Perplexity and other AI engines cited competitors like Decathlon and YouTube because diveshop.pt lacked the "answer-ready" content formats they require. Source: /blog/ai-search-readiness-audit-review-diveshop-pt Q: Is this audit relevant for non-dive shops? A: Yes. The blockers identified—sitemap issues, schema gaps, and content extraction hurdles—are common across 80% of e-commerce sites we scan. This case study serves as a universal roadmap for AI search readiness. Source: /blog/ai-search-readiness-audit-review-diveshop-pt Q: Why am I in Google but not in Perplexity? A: Perplexity uses a different index and prioritizes "answer-ready" sources. If your site lacks structured data or blocks PerplexityBot, you will be invisible regardless of your Google ranking. Source: /blog/why-ai-engines-ignore-your-brand Q: How long does it take to show up in ChatGPT after fixes? A: Typically 2-4 weeks. AI engines need time to re-crawl your site and update their semantic index. Using clear Schema.org signals speeds up this process. Source: /blog/why-ai-engines-ignore-your-brand Q: What is answer-centric content? A: Content that prioritizes direct answers to likely user questions over narrative descriptions. It uses clear headings, bullet points, and data tables that LLMs can parse easily. Source: /blog/how-to-write-ai-search-optimized-pages Q: Should I remove marketing copy? A: No, but you should supplement it with structured facts. AI bots skip the fluff to find the features, prices, and specs. Source: /blog/how-to-write-ai-search-optimized-pages Q: How do I track citations without a tool? A: You can manually query target prompts in Perplexity/ChatGPT and record occurrences, but automated tracking is required for meaningful trend analysis. Source: /blog/ai-search-visibility-metrics-guide Q: What is a good citation rate? A: In competitive niches, a citation rate of 15-20% is excellent. Most unoptimized sites start at 0%. Source: /blog/ai-search-visibility-metrics-guide Q: Can I really see results in 7 days? A: You can fix all blockers in 7 days. AI engines typically take another 14-21 days to re-index and reflect these changes in live answers. Source: /blog/7-day-ai-visibility-playbook Q: What is the most critical day? A: Day 2 (Technical) and Day 3 (Schema). Without crawl access and structured data, content improvements cannot be "read" by AI. Source: /blog/7-day-ai-visibility-playbook Q: Is a standard Google Shopping feed enough? A: It’s a start, but AI engines need on-page structured data (JSON-LD) to verify the feed and extract deeper semantic context. Source: /blog/ecommerce-ai-ready-data-guide Q: Does it work for SaaS pricing? A: Yes. Pricing tables should be structured as clean HTML or Schema.org tables to ensure AI can compare your plans accurately. Source: /blog/ecommerce-ai-ready-data-guide Q: Why do I have citations but no sales? A: Check your post-click landing page. If the user expects a specific feature they saw in ChatGPT but can't find it on your page, they will bounce. Source: /blog/convert-ai-citations-to-sales Q: How does UCP help conversion? A: UCP allows AI agents to handle the checkout, removing the friction of manual landing page navigation entirely. Source: /blog/convert-ai-citations-to-sales Q: Who should own AI Search Readiness? A: It’s a cross-functional role between SEO, Content Marketing, and Tech/Dev. The marketing team defines the "answers," while tech ensures they are extractable. Source: /blog/ai-visibility-ops-marketing-workflow Q: How often should I audit? A: Monthly re-scans are recommended to stay ahead of AI engine updates and competitor improvements. Source: /blog/ai-visibility-ops-marketing-workflow Q: What is an AI-citable page? A: It is a web page designed so that AI assistants (like ChatGPT or Perplexity) can easily identify, extract, and cite its key facts, entities, and offers in their responses. Source: /blog/how-to-write-ai-citable-pages Q: How does the AI Search Readiness Score help with writing? A: The score provides a diagnostic breakdown of where your page fails to provide extractable answers or trust signals, allowing you to fix specific blocks before the next crawl. Source: /blog/how-to-write-ai-citable-pages Q: How many factors affect an AI Search Readiness Score? A: There are 26 individual checks grouped into 4 baskets: Machine Readability (7 checks, 25% weight), Extractability (8 checks, 30% weight), Trust & Entity (5 checks, 25% weight), and Organic Reach (6 checks, 20% weight). Each check has a maximum point value, and the basket scores are weighted to produce a final score out of 100. Source: /blog/26-factors-ai-search-readiness-score Q: Which factor has the biggest impact on the score? A: Business Identity (NAP) in the Trust basket carries the highest single-check weight at 15 points. However, the Extractability basket as a whole has the most impact at 30% of the total score. If you can only fix one thing, start with FAQ sections and structured answer blocks — they boost both EX3 (FAQ Content, 10 pts) and EX12 (Rich Content, 10 pts). Source: /blog/26-factors-ai-search-readiness-score Q: What is the JS dependency penalty? A: If your page renders fewer than 50 words of visible text without JavaScript enabled, the entire Machine Readability subscore is multiplied by 0.5. This penalty exists because AI crawlers like GPTBot and PerplexityBot often cannot execute JavaScript, so content hidden behind client-side rendering is effectively invisible. Source: /blog/26-factors-ai-search-readiness-score Q: Can I improve my score without technical changes? A: Some checks are content-only: adding FAQ sections (EX3), improving meta descriptions (EX1), increasing content depth past 800 words (EX7), and adding author bylines (TR5). These do not require developer involvement. However, the highest-impact changes — structured data (MR3), robots.txt (MR1), and JS rendering (MR7) — typically need a developer. Source: /blog/26-factors-ai-search-readiness-score Q: Does the AI Search Readiness Score work for non-English websites? A: Yes. All 26 checks are language-agnostic. Schema.org structured data, robots.txt rules, SSL certificates, and Open Graph tags work identically in any language. The 4 LLM-based checks use GPT-4o, which supports 90+ languages. Your score reflects technical AI readiness, not English proficiency. Source: /blog/ai-search-readiness-international-multilingual Q: How do multilingual sites get scored? A: Each URL is scored independently. If you have /en/ and /pt/ versions of a page, each gets its own score based on the structured data, content, and meta tags present on that specific URL. We recommend scanning your primary market pages first, then secondary languages. Source: /blog/ai-search-readiness-international-multilingual Q: Is there a price difference for international sites? A: No. Pricing is the same regardless of domain location, language, or market. The free scan works for any publicly accessible URL worldwide. Source: /blog/ai-search-readiness-international-multilingual Q: Which AI search engines matter outside the US? A: Perplexity and ChatGPT operate globally and cite sources in any language. Google AI Overviews is rolling out market by market — as of early 2026, it is active in 40+ countries. The readiness signals (structured data, crawl access, entity trust) are the same regardless of which AI engine you target. Source: /blog/ai-search-readiness-international-multilingual Q: What is the fastest way to check AI search readiness? A: Enter your URL at getaisearchscore.com for a free Content Relevance Score across five components - Query Coverage, Content Depth, Sub-Intent Coverage, Technical Health, and (on paid scans) Citation Reality. The scan takes a few minutes and includes per-query breakdowns. For a quick manual check, disable JavaScript and see if your content disappears - that means AI crawlers likely can't see it either. Source: /blog/how-to-measure-ai-search-readiness Q: Can I measure AI search readiness without a tool? A: You can check technical hygiene manually: robots.txt for AI bot blocks, page source for JSON-LD schema, JavaScript rendering test. But you cannot manually assess content relevance - the dominant citation predictor (AUC 0.915) - without query decomposition, embedding similarity, and sub-intent analysis. That requires automated tooling. Source: /blog/how-to-measure-ai-search-readiness Q: How often should I measure AI search readiness? A: Monthly is recommended for active sites. Technical Health rarely regresses unless you change CMS or redesign. Content relevance shifts as competitors publish new content and AI retrieval pipelines evolve. Re-measure after major content updates. The free tier allows unlimited rescans. Source: /blog/how-to-measure-ai-search-readiness Q: What does each score range mean? A: 0-29 (Critical): major content and technical gaps, AI engines unlikely to cite your site. 30-59 (Average): some coverage but significant query gaps. 60-79 (Good): solid content relevance, regular citations plausible. 80-100 (Excellent): strong coverage across target queries. Note: a high score indicates strong content relevance, not guaranteed citations - brand authority and competition also matter. Source: /blog/how-to-measure-ai-search-readiness Q: What is an LLM SEO check tool? A: An LLM SEO check tool evaluates whether your website's content answers the queries users ask AI search engines. The most useful tools measure content relevance (query coverage, depth, sub-intent coverage), not just structural signals. Our research found structural checks alone predict citations at r=0.009 - content relevance predicts at AUC 0.915. Source: /blog/recommended-llm-seo-check-tools Q: Which LLM SEO tool should I start with? A: Start with a content relevance diagnostic to understand which queries your content covers and where the gaps are. Run a free scan at getaisearchscore.com for a Content Relevance Score across five components. Once you know your content gaps, choose a monitoring tool to track citation progress and a content tool if you need help writing. Source: /blog/recommended-llm-seo-check-tools Q: Do I need both a diagnostic tool and a monitoring tool? A: Yes - they serve different purposes. A content relevance diagnostic tells you what to fix (which queries you don't answer, which sub-intents you miss). A monitoring tool tracks whether AI engines actually cite you over time. Most teams need both, but the diagnostic should come first. Source: /blog/recommended-llm-seo-check-tools Q: Are traditional SEO tools enough for AI search optimization? A: No. Traditional tools track keyword rankings and backlinks, which don't predict AI citations. They don't measure content-query relevance, sub-intent coverage, or AI crawler access. You need at least one dedicated LLM SEO tool alongside your traditional stack. But be critical: ask any tool vendor for published evidence that their signals predict citation outcomes. Source: /blog/recommended-llm-seo-check-tools Q: Is the Content Relevance Score audit free? A: The free tier runs the full four-component audit - Query Coverage, Content Depth, Sub-Intent Coverage, and Technical Health - with per-query breakdowns and sub-intent gap analysis. No login, no credit card. The paid Starter consultation (149 one-time) adds Citation Reality via Perplexity and a human expert review with 20-40 prioritized rewrite tasks. Source: /blog/ai-search-readiness-score-review Q: How accurate is the Content Relevance Score? A: The content relevance components (QC, CD, SI) use GPT-4o evaluation plus BM25 and embedding similarity - the same signals that achieved AUC 0.915 in our citation prediction study. The Technical Health subcomponent uses Playwright-based crawling that simulates how AI bots see your page. We have not yet published a before/after case study proving our recommendations raise citation rates - that experiment is running now. Source: /blog/ai-search-readiness-score-review Q: What are the main limitations? A: No continuous monitoring (it is a one-off diagnostic, not a dashboard). No traditional keyword tracking. Not designed for 10K+ page enterprise sites. The tool diagnoses content and technical gaps and tells you what to fix, but you or your team must implement the changes. Source: /blog/ai-search-readiness-score-review Q: How does it compare to Conductor? A: Conductor is an enterprise brand monitoring platform with continuous AI citation tracking. LLM SEO Check is a one-off content relevance diagnostic plus optional human consultation. Conductor gives you dashboards and trends over time. We give you a deep per-query, per-sub-intent diagnosis and a fix list. Different tools for different problems. See our detailed comparison article. Source: /blog/ai-search-readiness-score-review Q: What is the difference between enterprise data readiness and website data readiness for AI? A: Enterprise data readiness refers to preparing internal organizational data (data lakes, feature stores, governance frameworks) for machine learning and AI applications. Website data readiness means structuring your website's content and markup (Schema.org JSON-LD, robots.txt, meta tags, FAQ sections) so AI search engines can parse, understand, and cite it. Enterprise readiness takes months to years and costs $100K+. Website readiness can often be achieved in days to weeks at minimal cost. Source: /blog/is-your-data-ready-for-ai Q: How do I check if AI crawlers can access my website? A: Check your robots.txt file for rules affecting GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot, and Google-Extended. Many CMS platforms block these by default. Then disable JavaScript in your browser and reload key pages — if content disappears, AI crawlers likely can't see it either. You can also use tools like AI Search Readiness Score or Google's Rich Results Test for automated checks. Source: /blog/is-your-data-ready-for-ai Q: What percentage of businesses have AI-ready data? A: According to a March 2026 study by Cloudera and Harvard Business Review Analytic Services (n=230), only 7% of enterprises say their data is completely ready for AI adoption. 27% report their data is "not very" or "not at all" ready. Gartner predicts that 60% of AI projects will be abandoned by 2026 due to inadequate data foundations. Source: /blog/is-your-data-ready-for-ai Q: What are the most common website data readiness mistakes? A: The five most common mistakes are: (1) schema markup that is present but out of sync with visible page content (e.g., wrong prices in JSON-LD), (2) blocking AI crawlers in robots.txt without knowing it, (3) FAQ content without FAQPage schema markup, (4) JavaScript-only content with no server-side rendering fallback, and (5) treating data readiness as a one-time project rather than an ongoing process. Source: /blog/is-your-data-ready-for-ai Q: What is the fastest way to improve my website's AI data readiness? A: Start with machine readability: fix robots.txt to allow AI crawlers, and add Schema.org JSON-LD markup (Product, Organization, FAQPage, BreadcrumbList) to your top 5 pages. These are prerequisites — without crawl access and structured data, no other optimization matters. Then add FAQ sections with schema markup and ensure your content leads with the answer (Bottom Line Up Front). Source: /blog/is-your-data-ready-for-ai Q: What is the average AI Search Readiness Score across websites? A: Based on 98 audited websites, the average AI Search Readiness Score is 52.8 out of 100. Scores range from 2 to 87, with 61.3% of sites scoring below 60. The sample is self-selected (users who submitted their sites), so real-world averages are likely lower. Source: /blog/we-audited-100-websites-ai-search-readiness Q: What is the most common AI search readiness failure? A: 91% of audited websites scored zero on customer review markup (AggregateRating and Review Schema.org). This is the #1 missing trust signal. The second most common failure is missing GTIN/MPN product identifiers (66%) and absent FAQ content (66%). Source: /blog/we-audited-100-websites-ai-search-readiness Q: What percentage of AI search queries cite a given website? A: Across 1,615 citation checks on Perplexity, only 18.1% resulted in citations. This means that even for queries directly related to a site's products or services, AI engines choose other sources more than 4 out of 5 times. Source: /blog/we-audited-100-websites-ai-search-readiness Q: Do traditional SEO best practices help with AI search readiness? A: Traditional SEO basics (SSL, mobile optimization, clean robots.txt, heading hierarchy) have 90%+ pass rates across our dataset — nearly everyone has them. But AI-specific signals (review markup, authorship, FAQ content, product identifiers) have 50-91% failure rates. Traditional SEO is necessary but no longer sufficient for AI visibility. Source: /blog/we-audited-100-websites-ai-search-readiness Q: How many checks does an AI Search Readiness audit include? A: Our audit runs 26 automated checks across 4 dimensions: Machine Readability (7 checks), Extractability (8 checks), Trust & Entity (5 checks), and Offering Readiness (6 checks). The formula is Score/100 = 0.25×MR + 0.30×EX + 0.25×TR + 0.20×OR. Source: /blog/we-audited-100-websites-ai-search-readiness Q: Does AI Search Readiness Score predict LLM citations? A: No. In a pre-registered study of 485 domains across 30 queries and 90 Perplexity API runs, AI Search Readiness Score showed zero statistically significant correlation with citation frequency (Pearson r = 0.009, p = 0.849). This null result held across every analytical specification tested: OLS regression, logistic regression, hurdle model, and sensitivity analysis with Google Rank. Source: /blog/study-ai-readiness-score-does-not-predict-llm-citations Q: What does predict whether a website gets cited by AI search engines? A: Moz Domain Authority was the only statistically significant predictor, but it explains only about 2% of citation variance and works as an "amplifier" (increasing citation frequency for already-cited domains) rather than a "gate" (determining whether a domain gets cited at all). The remaining 98% of citation behavior is driven by unmeasured factors — most likely content relevance to the specific query and the LLM's retrieval pipeline mechanics. Source: /blog/study-ai-readiness-score-does-not-predict-llm-citations Q: Are LLM citations consistent across repeated queries? A: Only moderately. Even at temperature=0 (deterministic output), only 47.5% of citations appeared consistently across all 3 replicates of each query. 29.3% appeared in just 1 of 3 runs, making them essentially random. This instability likely comes from the retrieval (RAG) layer rather than the generation layer. Source: /blog/study-ai-readiness-score-does-not-predict-llm-citations Q: Does this mean GEO (Generative Engine Optimization) is useless? A: Not necessarily. This study tested structural characteristics (schema markup, crawlability, entity signals) and found no correlation with citations. But content-level interventions (adding statistics, quotations, citations to your text) have been shown to improve citation rates by 15–41% in the GEO paper by Aggarwal et al. (2023). Structural readiness may be a necessary prerequisite that provides no additional advantage once met. Source: /blog/study-ai-readiness-score-does-not-predict-llm-citations Q: How was this study designed to avoid bias? A: The study was pre-registered before data collection: hypotheses, score formula, query list, and analysis plan were frozen in advance. The author disclosed a conflict of interest (being the creator of the score tested). The study committed to publishing regardless of the result. All data and code are available upon request. Source: /blog/study-ai-readiness-score-does-not-predict-llm-citations Q: Does website structure predict AI search citations? A: No. In our pre-registered study of 485 domains across 30 queries, AI Search Readiness Score (measuring schema markup, HTML semantics, trust signals, and content structure) showed zero correlation with citation frequency (r = 0.009, p = 0.849). The study was adequately powered to detect any practically meaningful effect. Source: /blog/ai-citation-analysis-658-sources-30-queries Q: What is the strongest predictor of AI citations? A: Domain Authority was the only statistically significant predictor, but it explains just 2.2% of variance. The remaining 98% is driven by unmeasured factors — likely content relevance, retrieval pipeline mechanics, and model training data. Source: /blog/ai-citation-analysis-658-sources-30-queries Q: Are AI search citations consistent or do they change? A: Citations are surprisingly inconsistent. Even at temperature=0, 52.5% of domain-query citation pairs were unstable across 3 replicate runs. Only 47.5% appeared in all 3 runs. A single citation check is unreliable — you need multiple samples. Source: /blog/ai-citation-analysis-658-sources-30-queries Q: Why does YouTube appear so often in AI search results? A: YouTube was the most-cited domain in our dataset (33 citations across 9 queries), with 76% of those from e-commerce queries. This suggests AI retrieval is modality-sensitive: for product comparison queries, video reviews match the format the model is looking for. Source: /blog/ai-citation-analysis-658-sources-30-queries Q: Should I still optimize my website for AI search? A: Structural optimization (clean HTML, schema markup, good meta tags) is hygiene — necessary but not sufficient for citations. Focus on content relevance, format matching (video for products, comparison data for SaaS), and building real domain authority rather than expecting technical fixes alone to drive AI visibility. Source: /blog/ai-citation-analysis-658-sources-30-queries Q: Does content relevance explain the null result? A: Partially. Domains are cited 62× more often for queries in their own vertical (5.17%) than for irrelevant queries (0.08%). Content relevance is clearly the primary gate. However, even within same-topic pairs, Score still shows zero correlation with citation (r = −0.010, p = 0.845). So relevance explains which domains have a chance, but Score does not predict who wins within that pool. Source: /blog/ai-citation-analysis-658-sources-30-queries Q: Is there a minimum Score needed to get cited by AI search? A: No. The lowest-scoring cited domain in our dataset had a Score of 11 out of 100 (motaword.com). Meanwhile, the highest-scoring uncited domain had a Score of 95. Citation rates across score deciles range from 29% to 56% with no monotonic pattern. There is no floor below which citation becomes impossible. Source: /blog/ai-citation-analysis-658-sources-30-queries Q: What is BM25 and why does it predict AI citations? A: BM25 (Best Matching 25) is a text retrieval algorithm that scores how well a document matches a search query based on keyword overlap, adjusted for term frequency and document length. It predicts AI citations because AI search engines like Perplexity use similar retrieval methods — they find pages whose content literally matches the words in a user's query. In our study, pages in the highest BM25 quintile were cited 12× more often than those in the lowest. Source: /blog/content-relevance-predicts-ai-citations-not-seo-score Q: Does AI Search Readiness Score matter for getting cited? A: Not for citation prediction. Our study found that adding the 26-check AI Search Readiness Score to a content relevance model does not improve citation prediction (p = 0.14). Score + Domain Authority alone achieves only AUC 0.547 (barely above random), while content relevance achieves AUC 0.915. Structural optimization (schema, meta tags, crawlability) is necessary hygiene but does not drive citations. Source: /blog/content-relevance-predicts-ai-citations-not-seo-score Q: What predicts whether a website gets cited by AI search engines? A: Content relevance to the specific query is the dominant predictor. A page needs to contain text that closely matches what the user is asking about — both in terms of literal keywords (BM25) and semantic meaning (embedding similarity). Domain Authority provides a small additional boost. Structural factors like schema markup and HTML quality show no independent predictive power. Source: /blog/content-relevance-predicts-ai-citations-not-seo-score Q: How can I improve my chances of being cited by AI search? A: Focus on content relevance: identify the queries your customers ask, then create pages that directly answer those queries with relevant, detailed content. Use the actual keywords your audience searches for. Go deep on your niche rather than spreading thin across topics. Structural optimization (schema, meta tags, crawler access) is table stakes — fix it once and focus your ongoing effort on content. Source: /blog/content-relevance-predicts-ai-citations-not-seo-score Q: Does this mean SEO tools and audits are useless? A: No — structural optimization is still necessary. Clean HTML, proper schema markup, and AI crawler access remove barriers to citation. But they don't cause citations. Think of it as plumbing: broken pipes prevent water from flowing, but fixing them doesn't create water pressure. Content relevance is the water pressure. Source: /blog/content-relevance-predicts-ai-citations-not-seo-score Q: What are the limitations of this study? A: The study used a single LLM model (Perplexity sonar-reasoning-pro), which may not generalize to ChatGPT or Google AI Overviews. The max-page assumption (using the best-matching page per domain) may not reflect actual retrieval behavior. The analysis was exploratory, not pre-registered. And the embedding model used (all-MiniLM-L6-v2) differs from what Perplexity actually uses internally. Source: /blog/content-relevance-predicts-ai-citations-not-seo-score Q: What is chunking and why does it matter for AI citations? A: Chunking is the process of splitting your page content into smaller pieces (typically 400-512 tokens) that get individually indexed and retrieved by AI search systems. Each chunk becomes an atomic unit - the system retrieves and evaluates chunks, not whole pages. If your key answer spans two chunks, neither may be strong enough to get retrieved. Writing self-contained H2 sections of 300-400 words helps ensure each chunk contains a complete, citable answer. Source: /blog/how-llms-parse-your-content-chunking-readability-citations Q: Does content structure affect AI citations? A: Structure affects citations indirectly but not directly. Good heading hierarchy (H2/H3) creates better chunk boundaries during the chunking step. Crawlable, parseable HTML is required for the pipeline to even start. But structural readiness scores show zero correlation with actual citation rates (r=0.009 across 441 domains). Structure is necessary infrastructure - it gets you into the game - but content relevance is what wins citations. Source: /blog/how-llms-parse-your-content-chunking-readability-citations Q: What is the "Lost in the Middle" problem? A: Research by Liu et al. (2023) found that LLMs have a U-shaped attention curve: they attend strongly to information at the beginning and end of their context window, but deprioritize information in the middle. This means front-loading your key claims (BLUF - Bottom Line Up Front) in each section isn't just good writing style - it aligns with how the model's attention architecture actually works. Source: /blog/how-llms-parse-your-content-chunking-readability-citations Q: Which AI search platform is easiest to optimize for? A: Perplexity is the most optimizable because every query triggers web retrieval, giving your content a chance to be found. ChatGPT only searches the web for about 31% of queries (59% for local intent). Google AI Overviews relies heavily on existing Google Search rankings. Claude doesn't browse the web at all - it only uses training data. Source: /blog/how-llms-parse-your-content-chunking-readability-citations Q: How important are FAQ blocks for AI citations? A: A 2025 study by Relixir found 41% citation rate for pages with FAQ content versus 15% without. This makes sense through the pipeline lens: FAQ question-answer pairs are naturally self-contained chunks that map directly to user queries. However, this data hasn't been independently verified, so treat it as indicative rather than definitive. Source: /blog/how-llms-parse-your-content-chunking-readability-citations Q: Do AI search engines actually read llms.txt files? A: As of early 2026, no major LLM provider (OpenAI, Anthropic, Google) has confirmed reading llms.txt at inference time. Google's John Mueller publicly stated that AI services don't check for it. However, llms.txt is useful even without automated consumption - developers and power users manually paste llms-full.txt content into LLM context windows. Think of it as a curated content map, not a ranking signal. Source: /blog/ai-ready-documentation-2026 Q: What is the difference between llms.txt and MCP for documentation? A: llms.txt is a static Markdown file that agents can read passively - like robots.txt for AI. MCP (Model Context Protocol) is a bidirectional protocol that lets agents actively query, search, and interact with your documentation through tool calls. llms.txt is the entry point; MCP is deep integration. Implement both if your platform supports it. Source: /blog/ai-ready-documentation-2026 Q: Which documentation platform is best for AI-agent readiness? A: Mintlify, GitBook, and Fern are the top three. All auto-generate llms.txt, llms-full.txt, and MCP servers with zero configuration. GitBook offers the best value ($0-8/user) with full AI feature parity. Mintlify has the strongest Anthropic partnership. Fern has unique AI analytics showing which LLM providers consume your docs. If you use Docusaurus or other OSS tools, community plugins exist for llms.txt generation but you won't get MCP or analytics. Source: /blog/ai-ready-documentation-2026 Q: What are Agent Skills and how do they relate to documentation? A: Agent Skills (agentskills.io) are folder-based knowledge packages that teach AI agents how to perform tasks. A SKILL.md file contains metadata and instructions using progressive disclosure - only ~30-50 tokens load at startup, with full content loading on demand. Skills complement llms.txt (what your site is about) and MCP (how to access your data) by adding procedural knowledge (how to do things). 26+ platforms support them including Claude, Codex, Gemini CLI, and Cursor. Source: /blog/ai-ready-documentation-2026 Q: How long does it take to make documentation AI-agent ready? A: If your docs platform auto-generates everything (Mintlify, GitBook, Fern), it takes zero effort - the features are on by default. For a custom site, creating an llms.txt file takes 15-30 minutes. Adding a SKILL.md with your project context takes another 30 minutes. Setting up an MCP server requires more investment (hours to days depending on your stack). Start with llms.txt and SKILL.md, then add MCP when you need bidirectional integration. Source: /blog/ai-ready-documentation-2026 Q: Does schema structured data help with AI search citations? A: Schema helps AI systems read and understand your content by reducing ambiguity and clarifying entities. Sites with schema score significantly higher on readiness audits. However, in a study of 441 domains and 14,550 domain-query pairs, there was zero correlation (r=0.009) between readiness scores (including schema) and actual AI citations. Schema is necessary infrastructure but not sufficient for citations - content relevance is the dominant factor. Source: /blog/schema-structured-data-ai-search-guide Q: What schema types should every website have? A: Every website should implement the Foundation layer: WebSite (homepage), Organization (site identity with sameAs links), WebPage (each page with mainEntity), and BreadcrumbList (navigation hierarchy). Then add Content layer types that match your page formats (Article, FAQPage, HowTo) and Entity layer types for what you offer (Product, Service, SoftwareApplication, Course). Source: /blog/schema-structured-data-ai-search-guide Q: What is the relationship layer in schema and why is it underused? A: The relationship layer uses properties like author, publisher, mainEntity, about, mentions, and isPartOf to connect entities. Most sites implement schema types (declaring "this is a Product") but skip relationships between entities. Without relationships, you have isolated labels. With relationships, you have an entity graph that AI systems can traverse to understand context and attribute information correctly. Source: /blog/schema-structured-data-ai-search-guide Q: Should I use JSON-LD or Microdata for AI search? A: Use JSON-LD served server-side in your HTML. AI crawlers may not execute JavaScript, so schema injected by client-side JS may be invisible to them. JSON-LD as a standalone script block in the initial HTML response is the most reliable format for both traditional and AI search engines. Source: /blog/schema-structured-data-ai-search-guide Q: How do I validate schema for AI search specifically? A: Use Google Rich Results Test for syntax validation and Schema.org Validator for structural completeness. Then disable JavaScript and check if your JSON-LD appears in raw HTML. Manually cross-reference visible page content against schema values (prices, names, dates). No tool currently validates AI interpretability specifically, but contextual tools check schema alongside other AI readiness factors. Source: /blog/schema-structured-data-ai-search-guide Q: How much does AI search optimization cost? A: Costs vary widely by delivery model. Managed agencies charge $2,000-$15,000/month for ongoing optimization. SaaS audit tools range from free to $200/month. Freelance consultants typically charge $100-$500/hour or $500-$3,000 per project. One-time audits from agencies start at $500-$5,000. The right choice depends on your budget, internal expertise, and how hands-on you want to be. Source: /blog/ai-search-optimization-services-compared Q: Which AI search optimization agencies are best? A: The honest answer is that no agency has published controlled evidence showing their specific interventions increase AI citations. Known players include LightSite AI (managed GEO), Profound Strategy/NP Digital (enterprise), and Seer Interactive (entity optimization). Many traditional SEO agencies now add AI search to their services. Before choosing, ask for published evidence of causal impact, not just testimonials. Source: /blog/ai-search-optimization-services-compared Q: Should I hire an agency or use a tool for AI search optimization? A: For most small-to-medium businesses, starting with a free audit tool is the highest-ROI approach. Tools show you where your content gaps are at zero cost. If you lack internal expertise to act on the findings, a freelance consultant for a one-time project ($500-$3,000) is the next step. Agencies make sense for enterprises without internal teams who need ongoing management and reporting. Source: /blog/ai-search-optimization-services-compared Q: Where can I buy AI search optimization services online? A: Options include: SaaS tools like LLM SEO Check (getaisearchscore.com), Otterly.ai, or Peec AI for self-service audits. LinkedIn and SEO conference speaker lists for finding freelance consultants. Direct outreach to GEO agencies like LightSite AI or Profound Strategy. Upwork and Toptal are emerging channels but have limited verified specialists in this specific niche. Source: /blog/ai-search-optimization-services-compared Q: Is AI search optimization worth the investment? A: It depends on how much of your audience uses AI search. If your customers increasingly find products or information through ChatGPT, Perplexity, or Google AI Overviews, then yes - but start with free tools to quantify your gaps before investing. The field is immature, so avoid large upfront commitments. Focus on content relevance improvements, which have the strongest evidence base. Source: /blog/ai-search-optimization-services-compared Q: How do I find AI search optimization experts near me? A: AI search optimization is fully remote-friendly, so geographic proximity offers no advantage unless you specifically want in-person workshops. The best experts may be anywhere in the world. Search LinkedIn for people publishing original research about AI search (not just resharing articles), check speaker lists from SEO conferences like Brighton SEO and MozCon, and browse Reddit communities (r/bigseo, r/SEO) for consistent contributors with data. Source: /blog/how-to-evaluate-ai-search-optimization-experts Q: What qualifications should an AI search optimization expert have? A: There are no formal certifications for AI search optimization - the field is too new. Instead, look for: published original research or experiments, demonstrated understanding of content relevance vs technical signals, multi-platform knowledge (Perplexity, ChatGPT, Google AI Overviews), honest communication about uncertainty, and specific measurement methodology. Traditional SEO experience is helpful but not sufficient. Source: /blog/how-to-evaluate-ai-search-optimization-experts Q: What is the biggest red flag when hiring an AI search consultant? A: Guaranteed results. No one can guarantee your site will appear in ChatGPT or Perplexity results. AI citation is probabilistic and influenced by factors outside anyone's control - including the constantly changing behavior of AI platforms themselves. An expert who guarantees outcomes is either dishonest or does not understand the field well enough. Source: /blog/how-to-evaluate-ai-search-optimization-experts Q: How much should I pay for AI search optimization consulting? A: Freelance consultants typically charge $100-$500/hour or $500-$3,000 per project for audits and strategy. Managed agencies charge $2,000-$15,000/month. Tool-plus-consulting packages (like our Starter at €149) sit in between. Start with a free tool audit to understand your gaps before investing in any paid service. Source: /blog/how-to-evaluate-ai-search-optimization-experts Q: Is local SEO expertise relevant for AI search optimization? A: Partially. Traditional local SEO knowledge (Google Business Profile, NAP consistency, local schema) provides a foundation, but AI search citation works differently from local pack rankings. An expert needs to understand how AI platforms handle local intent queries specifically, which involves knowledge of query fan-out and how AI systems route local queries to specialized databases. Source: /blog/how-to-evaluate-ai-search-optimization-experts ## Structured Data APIs - Blog articles & search: /api/ai/blog - FAQ knowledge base: /api/ai/faq - Scoring methodology: /api/ai/methodology ## Machine-Readable Skills Skills manifest: /skills.json ## Contact - Email: hello@getaisearchscore.com - Founded by Alexey Tolmachev, Senior Systems Analyst Source: getaisearchscore.com | gass-llms-full-20260430-0a83bfaa