Skip to content
Join the waitlist

Research · October 2026 edition

AI-Search Readiness of Top Sites What the top 9,973 sites say about themselves, and whether a crawler that runs no scripts can read it.

40.0% of the home pages read describe the organization in structured data, and 80.7% carry their main text in the HTML as served. 55.9% of the sites asked have a valid sitemap, and 13.0% of the sites asked have an llms.txt.

Sites asked are the sites read, less those whose robots.txt keeps our crawler from the file, so “of sites asked” and “of sites read” differ.

Measured
24 October 2026
Panel
9,973 domains, Tranco list N26XW
Updated
A full reading each quarter

Crawlers covered

What each one does

This study reads files as one crawler, QueryRevBot. “Open to AI search” uses the crawlers of the crawler study.

The 11 AI crawlers of the crawler study, from OpenAI, Perplexity, Google, Apple, Common Crawl, Meta, Amazon and ByteDance. Other crawlers are not checked.

Key figures

Five readings, each on what it was asked of.

A reading is a count of files read by fixed rules, shown as a share of what it was asked of: the home pages read, the sites asked for a sitemap, the sites asked for an llms.txt. Every tile names its denominator and the count.

What a share is of

  • The share shown largeThe home pages read (4,480), or for a sitemap and an llms.txt the sites that were asked for the file.
  • A narrower shareAmong a smaller group: the pages with structured data (2,203) or the pages that describe an Organization (1,793).
  • A wider shareAmong a larger group, such as the sites read (6,342), where the figure was asked of fewer.
  • Describe the organization in JSON-LD

    40.0%

    of 4,480 home pages read
    Counted
    1,793
    of 2,203 pages with schema.org JSON-LD
    81.4%

    An Organization, or one of its schema.org subtypes, anywhere in a JSON-LD block of the home page.

  • Link outside profiles with sameAs

    28.6%

    of 4,480 home pages read
    Counted
    1,280
    of 1,793 pages describing an Organization
    71.4%

    The organization’s sameAs holds at least one web address outside the site’s own domain.

  • Carry their main text in the HTML

    80.7%

    of 4,480 home pages read
    Counted
    3,615

    At least 150 words of main text in the HTML as served, before any script runs.

  • Have a valid sitemap

    55.9%

    of 6,082 sites asked for a sitemap
    Counted
    3,401

    The sitemap the site names, else /sitemap.xml, is a sitemap with at least one address on the site’s own domain. 260 of the 6,342 sites read were not asked: their robots.txt keeps our crawler from the sitemap.

  • Publish an llms.txt

    13.0%

    of 6,066 sites asked for an llms.txt
    Counted
    787
    of 6,342 sites read
    12.4%

    The crawler study’s rule: a text file at /llms.txt that starts with a Markdown title. 276 of the 6,342 sites read were not asked: their robots.txt keeps our crawler from /llms.txt.

  • Have all five

    7.8%

    of 4,480 home pages read
    Counted
    350

    Organization in JSON-LD with sameAs, main text in the HTML, a valid sitemap and an llms.txt. A count, not a grade.

The five readings side by side
  1. Organization in JSON-LD

    of 4,480 home pages read

    40.0%

  2. sameAs profiles

    of 4,480 home pages read

    28.6%

  3. Text in the HTML

    of 4,480 home pages read

    80.7%

  4. Valid sitemap

    of 6,082 sites asked for a sitemap

    55.9%

  5. llms.txt

    of 6,066 sites asked for an llms.txt

    13.0%

Each bar is a share of its own denominator, named under its label: the home pages read for the first three, the sites asked for a sitemap, the sites asked for an llms.txt.

Show the numbers as a table
ReadingCountedShare
Organization in JSON-LD1,79340.0%
sameAs profiles1,28028.6%
Text in the HTML3,61580.7%
Valid sitemap3,40155.9%
llms.txt78713.0%

Panel

4,480 of 9,973 home pages could be read.

The panel is the crawler study’s: the first 10,000 places of Tranco list N26XW, created 14 October 2026. 2 places were not a valid domain and 25 domains of companies that build language models were left out. Our crawler asks for robots.txt first and for the home page only if robots.txt allows it.

  • 44.9%

    Home pages read

    Answered 200 within the redirects with an HTML page that is not a bot check or a placeholder. 4,480 of the 9,973 domains in the panel; 70.6% of 6,342 sites read.

  • 0

    Sites that opted out

    A QueryRevBot group in robots.txt closes the whole site to our crawler. Nothing else is asked, and the site is left out of the per-domain data.

Domains not read, by cause

First the robots.txt answer, then the home page. Shares are of the whole panel. A domain is counted once, under the first thing that stopped it.

Stopped at robots.txt

The name did not resolve1,38913.9%
No answer within 10 seconds3023.0%
Connection or TLS failed2542.5%
Resolved to a private or reserved address520.5%
Refused our crawler (401 or 403)1,05210.5%
Asked us to slow down (429)200.2%
Server error (5xx)600.6%
Redirects that could not be followed250.3%
Another answer1<0.1%
A bot check or a web page, not the file4764.8%
Opted out of the study00.0%

The home page could not be used

robots.txt keeps our crawler from the home page2422.4%
The robots.txt of the page it landed on could not be read160.2%
Over 2 MiB and cut with too little text to measure130.1%
Refused our crawler (401 or 403)5966.0%
A bot check300.3%
A parking page or a default server page3<0.1%
Not an HTML page260.3%
An error answer2632.6%
Redirected to another domain, which is not followed6336.3%
Redirects that could not be followed120.1%
No answer, or the connection failed280.3%

Structured data

49.2% of home pages read carry schema.org JSON-LD.

JSON-LD is read as served. A page whose structured data is added by a script, a tag manager for instance, is not in the HTML a crawler without scripts receives, and counts as having none.

  • 49.2%

    Any JSON-LD

    A block that parses as JSON with a schema.org context. 2,203 of 4,480 home pages read.

  • 1.1%

    A block that does not parse

    Among pages with a JSON-LD script, at least one script that fails to parse. 24 of 2,222 pages with a JSON-LD script.

  • 34.5%

    WebSite

    A WebSite node. 21.9% of the home pages read also describe a SearchAction. 1,544 of 4,480 home pages read.

  • 3.6%

    FAQ

    A FAQPage node, in JSON-LD or microdata. 163 of 4,480 home pages read; 7.1% of 2,203 pages with schema.org JSON-LD.

  • 0.8%

    Organization in microdata only

    An Organization type in microdata and none in JSON-LD. RDFa is not read. 37 of 4,480 home pages read.

The schema.org types on the most home pages
  1. Organization

    34.5%

  2. WebSite

    34.5%

  3. ImageObject

    24.5%

  4. SearchAction

    23.0%

  5. WebPage

    18.4%

  6. ListItem

    13.3%

  7. PostalAddress

    13.2%

  8. ContactPoint

    12.0%

  9. EntryPoint

    11.2%

  10. BreadcrumbList

    11.1%

  11. Person

    6.2%

  12. PropertyValueSpecification

    5.8%

  13. NewsMediaOrganization

    5.6%

  14. SiteNavigationElement

    5.3%

  15. ReadAction

    5.0%

  16. ItemList

    4.0%

  17. CollectionPage

    3.7%

  18. Answer

    3.7%

  19. Question

    3.7%

  20. FAQPage

    3.6%

Each type counted once per home page, as a share of the home pages read. 171 types were seen in all; the most common are shown.

Show the numbers as a table
TypeHome pagesShare
Organization1,54534.5%
WebSite1,54434.5%
ImageObject1,09624.5%
SearchAction1,03123.0%
WebPage82318.4%
ListItem59813.3%
PostalAddress59213.2%
ContactPoint53912.0%
EntryPoint50211.2%
BreadcrumbList49611.1%
Person2786.2%
PropertyValueSpecification2595.8%
NewsMediaOrganization2505.6%
SiteNavigationElement2395.3%
ReadAction2225.0%
ItemList1814.0%
CollectionPage1663.7%
Answer1653.7%
Question1653.7%
FAQPage1633.6%

Organization

What an Organization says about itself.

Of the pages that describe an Organization (1,793), how many give a name and a web address, a logo and the profiles it is on. The Organization is the first node whose address is on the site’s own domain, else the first.

  • 88.8%

    Name and web address

    A name and an absolute web address. 1,593 of 1,793 pages describing an Organization; 35.6% of 4,480 home pages read.

  • 5

    Profiles listed

    The median number of distinct sameAs addresses among the Organizations that list any (1,280); the quartiles are 3 and 6 (nearest rank).

The kinds of profile sameAs points to
  1. Wikidata

    10.7%

  2. Wikipedia

    26.4%

  3. LinkedIn

    58.3%

  4. X

    82.7%

  5. Facebook

    81.5%

  6. Instagram

    62.3%

  7. YouTube

    65.8%

  8. TikTok

    18.4%

  9. GitHub

    6.8%

  10. Crunchbase

    4.0%

  11. Pinterest

    8.4%

  12. Another host

    33.0%

Each kind counted once per site, by the host of the address, as a share of the Organizations with sameAs (1,280).

Show the numbers as a table
The kinds of profile sameAs points toSitesShare
Wikidata13710.7%
Wikipedia33826.4%
LinkedIn74658.3%
X1,05882.7%
Facebook1,04381.5%
Instagram79762.3%
YouTube84265.8%
TikTok23618.4%
GitHub876.8%
Crunchbase514.0%
Pinterest1088.4%
Another host42233.0%

Text in the HTML

80.7% of home pages read carry their main text in the HTML as served.

This is what a crawler that runs no scripts receives. The study does not say what a page shows after its scripts run.

  • 15.3%

    Little text, no shell marks

    Under 150 words of main text, without the marks of an empty app shell. 685 of 4,480 home pages read.

  • 4.0%

    Served as an empty app shell

    Over 5 KiB of HTML, under 50 words of main text, and an application root element or a notice to enable JavaScript. 180 of 4,480 home pages read.

  • 1.4%

    Home page says noindex

    A robots meta tag or an X-Robots-Tag header with noindex and no agent prefix. 62 of 4,480 home pages read.

Home pages over 2 MiB, read as far as the cut and flagged: 49 of 4,480.

Sitemaps and llms.txt

55.9% of the sites asked have a valid sitemap, and 13.0% an llms.txt.

One sitemap file is read per site, and the children of an index are not. An llms.txt is counted by the crawler study’s rule, read again on this panel, so both studies can be set side by side.

  • 67.6%

    robots.txt lists a sitemap

    At least one Sitemap line in a robots.txt file. 3,845 of 5,691 sites with a robots.txt file; 60.6% of 6,342 sites read.

  • 58.7%

    A sitemap index

    The valid file is a sitemapindex. Its children are not read. 2,142 of 3,651 sitemaps found.

What the sitemap request found
  1. A valid sitemap

    55.9%

  2. No sitemap found

    22.0%

  3. A web page, not a sitemap

    4.2%

  4. A file that is not a valid sitemap

    4.1%

  5. The request failed

    13.8%

Shares of the 6,082 sites asked for a sitemap: the 6,342 sites read, less 260 whose robots.txt keeps our crawler from the sitemap. Those 260 sites are not in the bars.

Show the numbers as a table
What the sitemap request foundSitesShare
A valid sitemap3,40155.9%
No sitemap found1,33622.0%
A web page, not a sitemap2564.2%
A file that is not a valid sitemap2504.1%
The request failed83913.8%

Valid sitemaps cut at 5 MiB and counted as valid as far as read: 39 of 3,651 sitemaps found. Sites whose robots.txt keeps our crawler from /llms.txt were not asked for one (276). The trend of llms.txt over time is in the crawler study.

By rank

The same readings, by rank band.

The panel in two bands of the list. Each reading keeps its own denominator, named in the column heading.

The same readings, by rank band.
GroupHome pages readOrganization in JSON-LDsameAsText in the HTMLValid sitemapllms.txtAll five
Places 1 to 1,00036240.9%148 of 362 home pages read31.2%113 of 362 home pages read76.5%277 of 362 home pages read55.4%298 of 538 sites asked for a sitemap17.2%92 of 536 sites asked for an llms.txt14.4%52 of 362 home pages read
Places 1,001 to 10,0004,11839.9%1,645 of 4,118 home pages read28.3%1,167 of 4,118 home pages read81.1%3,338 of 4,118 home pages read56.0%3,103 of 5,544 sites asked for a sitemap12.6%695 of 5,530 sites asked for an llms.txt7.2%298 of 4,118 home pages read

Column shares: Organization, sameAs, text and all five of home pages read; sitemap of sites asked for a sitemap; llms.txt of sites asked for an llms.txt.

By country-code domain

The same readings, by country-code ending.

Endings with at least 50 domains in the panel. The readings and their denominators are those of the rank bands above.

The same readings, by country-code ending.
GroupHome pages readOrganization in JSON-LDsameAsText in the HTMLValid sitemapllms.txtAll five
.ru14630.8%45 of 146 home pages read24.7%36 of 146 home pages read81.5%119 of 146 home pages read61.3%114 of 186 sites asked for a sitemap10.9%20 of 184 sites asked for an llms.txt7.5%11 of 146 home pages read
.jp9825.5%25 of 98 home pages read–Not shown85.7%84 of 98 home pages read55.0%66 of 120 sites asked for a sitemap5.8%7 of 120 sites asked for an llms.txt2.0%2 of 98 home pages read
.io7544.0%33 of 75 home pages read32.0%24 of 75 home pages read89.3%67 of 75 home pages read56.0%61 of 109 sites asked for a sitemap25.0%27 of 108 sites asked for an llms.txt21.3%16 of 75 home pages read
.de10943.1%47 of 109 home pages read27.5%30 of 109 home pages read93.6%102 of 109 home pages read64.2%86 of 134 sites asked for a sitemap9.7%13 of 134 sites asked for an llms.txt5.5%6 of 109 home pages read
.uk41–Not shown–Not shown92.7%38 of 41 home pages read63.5%33 of 52 sites asked for a sitemap5.8%3 of 52 sites asked for an llms.txt2.4%1 of 41 home pages read
.br5152.9%27 of 51 home pages read–Not shown74.5%38 of 51 home pages read57.6%38 of 66 sites asked for a sitemap21.2%14 of 66 sites asked for an llms.txt9.8%5 of 51 home pages read
.in46–Not shown–Not shown67.4%31 of 46 home pages read47.4%27 of 57 sites asked for a sitemap12.3%7 of 57 sites asked for an llms.txt2.2%1 of 46 home pages read
.cn43–Not shown–Not shown67.4%29 of 43 home pages read28.3%15 of 53 sites asked for a sitemap1.9%1 of 53 sites asked for an llms.txt2.3%1 of 43 home pages read
.fr4953.1%26 of 49 home pages read–Not shown85.7%42 of 49 home pages read62.2%46 of 74 sites asked for a sitemap4.1%3 of 74 sites asked for an llms.txt0.0%0 of 49 home pages read
.it43–Not shown–Not shown83.7%36 of 43 home pages read60.7%34 of 56 sites asked for a sitemap5.5%3 of 55 sites asked for an llms.txt4.7%2 of 43 home pages read
.tv37–Not shown–Not shown78.4%29 of 37 home pages read63.5%33 of 52 sites asked for a sitemap0.0%0 of 52 sites asked for an llms.txt0.0%0 of 37 home pages read
.co24–Not shown–Not shown–Not shown43.2%16 of 37 sites asked for a sitemap0.0%0 of 37 sites asked for an llms.txt–Not shown
.es37–Not shown–Not shown78.4%29 of 37 home pages read46.8%22 of 47 sites asked for a sitemap6.4%3 of 47 sites asked for an llms.txt2.7%1 of 37 home pages read
.pl35–Not shown–Not shown80.0%28 of 35 home pages read43.5%20 of 46 sites asked for a sitemap10.6%5 of 47 sites asked for an llms.txt2.9%1 of 35 home pages read

Rows under 30 sites are not shown: a share is left out of a table when any denominator it is shown on holds fewer than 30 sites. The count of home pages read is always shown.

Method

How we measured, and what it cannot tell you.

One run with our own crawler, and one more try for the sites that failed on the network. Every figure is a count of files read by fixed rules: no model makes a figure or a label, and there is no score.

  1. The panel

    The first 10,000 places of Tranco list N26XW, less the domains of companies that build language models: 9,973 domains.

    Details

    It is the panel of the crawler study. Tranco ranks registrable domains, combined from several sources over 30 days; list N26XW was created 14 October 2026. 2 places were not a valid domain and were left out, and 25 domains of companies that build language models are not requested at all. The list includes domains that serve no website, such as networks and APIs; they are counted as not read.

  2. What was fetched

    robots.txt, the home page, /llms.txt and one sitemap, each only if robots.txt allows it. Nothing else.

    Details

    For each domain, in this order and one after the other: https://domain/robots.txt (the www. host instead when the domain did not connect); the home page; the robots.txt of the host the home page landed on when that is another host; /llms.txt; and the sitemap, which is the first Sitemap line of robots.txt on the same registrable domain, else /sitemap.xml. No inner page, no script run, no cookie, and no link of an llms.txt is followed. A redirect to another registrable domain is not followed. Requests identified themselves as QueryRevBot, with a page that says how to stop it; at most 16 domains were in flight, requests to one host were at least a second apart, a Crawl-delay was kept up to 10 seconds, and nothing more was asked of a host after a 429 or 503. A domain that failed for network reasons was tried once more at the end.

  3. What counts as read

    6,342 of the 9,973 domains gave a robots.txt answer we could read; 4,480 of them gave a home page we could use.

    Details

    A home page is read when it answers 200 within the redirects with an HTML body that is not a bot check (a 202, or a page with a challenge’s marks) or a placeholder (a parking page or a default server page, by a fixed list of marks). A body over 2 MiB is read as far as the cut and flagged; when the part read holds under 150 words of main text, the page is not counted as read at all, because the cut may have hidden its text and its structured data. A page is decoded by its own character set. Sites that opted out of the study (0) count only as opted out. The causes of every domain not read are listed under Panel.

  4. How structured data was read

    JSON-LD blocks that parse and name schema.org, walked to any depth; microdata types; RDFa is not read.

    Details

    A block of type application/ld+json counts when it parses as JSON, after a wrapping comment or CDATA is removed, with a top-level @context that names schema.org. The reader is bounded: at most 50 blocks, 512 KiB each and 1 MiB in all, depth 16 and 5,000 nodes; past a bound the rest is not read and the page is flagged. An Organization is any node whose @type is Organization or one of its schema.org subtypes, taken from the schema.org vocabulary at release 30.1. Only type names of that vocabulary are published; any other name is published as other. Organization names and sameAs addresses are read but never published: only counts and the kind of profile are.

  5. How text was counted

    Words of main text in the HTML as served, at least 150 for text in the HTML.

    Details

    Main text is the text of main (or an element with role main) when there is one, else of the body without header, nav, footer and aside. Script, style, noscript, template and svg are never counted. Words are counted with Intl.Segmenter, so pages in Chinese or Japanese are counted too. A page of over 5 KiB with under 50 words and an application root element or a notice to enable JavaScript is an empty app shell; the rest under 150 words is little text.

  6. Sitemaps and llms.txt

    A sitemap is valid when it is XML or text with addresses on the site’s domain; an llms.txt by the crawler study’s rule.

    Details

    A sitemap is valid when the file answered 2xx and is XML without a DOCTYPE or ENTITY whose root is urlset or sitemapindex with at least one loc that is an absolute web address on the site’s registrable domain, or a text sitemap of such addresses. A web page served at /sitemap.xml is not a sitemap. A file cut at 5 MiB counts as valid as far as read. An llms.txt counts when /llms.txt answers 200 with a text type, the body is not an HTML page or a robots.txt, and its first non-empty line is a Markdown title.

  7. The network-failure retry

    1,004 sites whose first try ended in a network failure were asked again from the start, from a connection in the United States, on 24 October 2026.

    Details

    A network can fail to reach a site that answers from another. Every site whose result stood on a network failure (no answer, a timeout, a failed connection, an address refused as private or reserved, or a home page, sitemap or llms.txt that did not answer) was asked again from the start, as above, from a connection in the United States, on 24 October 2026, with the same limits and politeness. For each, the better of the two tries is kept: 294 of the 1,004 read more the second time. A name that did not resolve, a refusal (401 or 403), a bot check, a 429 and a 5xx were not a reason to ask again, because they are what the site answered.

What each figure counts

Every figure, its rule and the denominators it is shown on. Each name leads to the figure on this page.

  • Home pages read

    Shown on: Whole panel, Sites read

    The home page answered 200 within the redirects with an HTML body that is not a bot check or a placeholder.

  • Any JSON-LD

    Shown on: Home pages read

    A script of type application/ld+json that parses as JSON with a top-level @context naming schema.org.

  • A block that does not parse

    Shown on: Pages with a JSON-LD script

    At least one such script that fails to parse.

  • Organization in JSON-LD

    Shown on: Home pages read, Pages with schema.org JSON-LD

    A node, at any depth (@graph, arrays, nested values), whose @type is Organization or one of its schema.org subtypes (vocabulary release 30.1).

  • Organization only in microdata

    Shown on: Home pages read

    An itemtype naming one of those types, and none in JSON-LD.

  • Name and web address

    Shown on: Home pages read, Pages describing an Organization

    The primary Organization (the first whose address is on the site’s registrable domain, else the first) has a non-empty name and an absolute http or https address.

  • Logo

    Shown on: Pages describing an Organization

    The primary Organization has a logo: an address, or an image with an address.

  • sameAs

    Shown on: Home pages read, Pages describing an Organization

    The primary Organization’s sameAs holds at least one absolute http or https address outside the site’s own registrable domain.

  • Profiles linked

    Shown on: Organizations with sameAs

    Per kind of host: Wikidata, Wikipedia, LinkedIn, X, Facebook, Instagram, YouTube, TikTok, GitHub, Crunchbase, Pinterest, another host. A site counts once per kind.

  • Profiles per site

    Shown on: Organizations with sameAs

    The median and quartiles, nearest rank, of the number of distinct sameAs addresses.

  • WebSite, and its SearchAction

    Shown on: Home pages read

    A WebSite node; and one whose potentialAction is a SearchAction.

  • FAQ

    Shown on: Home pages read, Pages with schema.org JSON-LD

    A FAQPage node, in JSON-LD or microdata.

  • Types in use

    Shown on: Home pages read, Pages with schema.org JSON-LD

    The 20 schema.org types found on the most home pages, each counted once per page.

  • Text without scripts

    Shown on: Home pages read

    At least 150 words of main text in the HTML as served.

  • Served as an empty app shell

    Shown on: Home pages read

    Over 5 KiB of HTML, under 50 words of main text, and an application root element or a notice to enable JavaScript.

  • Little text, no shell marks

    Shown on: Home pages read

    Under 150 words of main text, without the shell marks.

  • Home page says noindex

    Shown on: Home pages read

    A robots meta tag or an X-Robots-Tag header, without an agent prefix, with noindex.

  • robots.txt lists a sitemap

    Shown on: Sites read, Sites with a robots.txt file

    At least one Sitemap line.

  • A valid sitemap

    Shown on: Sites asked for a sitemap

    The file of the sitemap request is a sitemap by the rule under Sitemaps and llms.txt.

  • A sitemap index

    Shown on: Sitemaps found

    The valid file is a sitemapindex.

  • llms.txt

    Shown on: Sites read, Sites asked for an llms.txt

    The crawler study’s rule: 200, a text type, not HTML, not a robots.txt, and a Markdown title first.

  • Text in the HTML, and open to AI search crawlers

    Shown on: Home pages read

    Text in the HTML, and robots.txt lets every covered crawler whose purpose is search or user fetch read the home page.

  • All five readings

    Shown on: Home pages read

    Organization in JSON-LD with sameAs, text in the HTML, a valid sitemap and an llms.txt. A count, not a score.

  • Not read, by cause

    Shown on: Whole panel

    Each domain of the panel that was not read, under the first thing that stopped it.

Limits

  • One page per site, the home page, as served to our crawler when it was read. An Organization described on an inner page, often /about, is not seen.
  • Structured data added by scripts is not in the HTML as served and is counted as absent.
  • Valid means the rules above, not a search engine’s rich-result eligibility or a full schema.org validation.
  • A site that refuses our crawler or serves a bot check is not read; it may treat other crawlers differently.
  • One sitemap file is read; the pages it lists and the children of an index are not checked.
  • Main text includes what a page puts inside main. A page without main is counted without its header, navigation and footer, and some boilerplate may remain.
  • The panel includes domains that serve no website (networks, APIs, CDNs); they are counted as not read.
  • A home page that went over 2 MiB and was cut, with under 150 words of main text in the part read, is counted apart and is in no home-page figure: the cut may have hidden its text and its structured data. A page cut with 150 words or more stays in, and is flagged.
  • A row of a rank band or a country-code ending is published only when every denominator its shares are shown on holds at least 30 sites; the quartiles of profiles per site go with it.
  • 1,004 sites were asked twice, the second time from a connection in the United States; the figures keep the better of the two tries for each, so some are counted on what a site served to that connection. A site can serve a different page to a different network or at a different time.

Other studies, and how this one differs

This study reads one fixed panel again every quarter; reads the organization, the sitemap, the llms.txt and the text of the same home page together; counts text in the HTML as served rather than after scripts; and gives every figure on the denominators it is shown on. Their figures are not quoted here; follow the links for them.

Data

Download, cite or embed it.

The data is free to use under CC BY 4.0: copy, share and adapt it, with a credit and a link to this page.

Licence: CC BY 4.0

Cite this study

QueryRev Research (2026). AI-search readiness of top sites, October 2026 edition. https://queryrev.com/research/ai-search-readiness. CC BY 4.0

BibTeX

@misc{queryrev2026readiness10,
  author = {QueryRev Research},
  title = {AI-search readiness of top sites, October 2026 edition},
  year = {2026},
  month = oct,
  publisher = {QueryRev AI},
  url = {https://queryrev.com/research/ai-search-readiness},
  note = {CC BY 4.0}
}

The panel comes from Tranco

Le Pochat et al., “Tranco: A Research-Oriented Top Sites Ranking Hardened Against Manipulation,” NDSS 2019. List N26XW: https://tranco-list.eu/list/N26XW

Embed this chart

An image of the five readings, with a link back. No script: paste it where your page takes HTML.

The five readings of the top sites’ home pages and public files, each as a share of what it was asked of: Organization in JSON-LD, sameAs, text in the HTML, valid sitemap and llms.txt, October 2026. Source: QueryRev Research.
<a href="https://queryrev.com/research/ai-search-readiness#key-figures"><img src="https://queryrev.com/data/ai-search-readiness/2026-10/readings.svg" width="720" alt="The five readings of the top sites’ home pages and public files, each as a share of what it was asked of: Organization in JSON-LD, sameAs, text in the HTML, valid sitemap and llms.txt, October 2026. Source: QueryRev Research."></a>
<p>Source: <a href="https://queryrev.com/research/ai-search-readiness">AI-Search Readiness of Top Sites, QueryRev Research</a> (CC BY 4.0)</p>

Questions

Is this a readiness score?

No. The study gives counts of files read by fixed rules, each with the denominators it is shown on. “All five readings” is a count of home pages that have all five, not a grade, and no site is ranked.

Why is the text counted from the HTML as served?

A crawler that does not run scripts receives the HTML as served, and this study reports what such a crawler receives. It does not say what a page shows after its scripts run.

Does structured data added by a tag manager count?

No. It is not in the HTML as served, so it is counted as absent. That is a limit of reading files without running scripts, and it is listed under Limits.

Which crawlers does “open to AI search” cover?

The AI crawlers of the crawler study, whose list is on that page. The study reads files as one crawler, QueryRevBot; it does not say how any other crawler treats a site.

How do I keep my site out of this study?

Add User-agent: QueryRevBot with Disallow: / to your robots.txt. We still read robots.txt itself, as every crawler must, but nothing else, and your site is left out of the per-domain data and counted only as opted out.

Keep exploring