Researchers should note three findings. First, the often-repeated estimate that about 96% of online content is unindexed is an illustrative convention, not a measured 2026 total (Britannica deep web overview). Michael Bergman’s landmark 2001 study also found a large gap, using a different method and scope (Bergman deep web study). Second, AI search does not automatically unlock private databases or material behind logins. Search indexes, direct page retrieval, browser agents, and licensed connectors provide different kinds of access. Third, publishers increasingly restrict training crawlers and, in some cases, search crawlers and user-directed fetchers. Those restrictions affect coverage, but do not establish a complete map of what every AI service or Google can see.
The belief that AI has “superior access to the hidden web” is a misconception. AI can help interpret and synthesize accessible material. Direct fetching may reach a public page absent from a particular search index; authenticated connectors, browser sessions, and licensed APIs can extend access where authorization permits.
Where this article fits. This is the data article in AOFIRS’s deep web series: how large the hidden web is, which indexes AI tools actually search, and what crawler-blocking data shows. For the methods, meaning Google operators compared with AI prompts and a worked five-step workflow, see invisible web research methods. If you are new to the subject, start with hidden web beginner guide.
- The often-repeated 96% unindexed estimate is illustrative, not a measured 2026 total (illustrative convention; Britannica deep web overview).
- 416 billion AI-bot requests were blocked by Cloudflare customers between 1 July and early December 2025, according to Cloudflare CEO Matthew Prince (Cloudflare crawler reach report).
- 3.2× more web pages are seen by Google’s crawler than by OpenAI’s, by the same December 2025 account (Cloudflare crawler reach report).
- 79% of 100 top UK and US news sites block at least one AI training bot (Publisher crawler blocking study; updated April 2026).
How Much of the Web Is Actually Hidden?
The hidden web cannot be measured precisely, because the content is by definition unindexed. The most widely repeated estimate puts the indexed, publicly searchable surface web at about 4% of online content and the unindexed deep web at about 96%. Britannica’s current entry illustrates exactly that split. It shows the dark web, the part reached only through an encrypted network with special software, as less than 1% (Britannica deep web overview).
The figure most often cited as the origin of these numbers says something different. Michael K. Bergman’s 2001 white paper in the Journal of Electronic Publishing popularized the term “deep web”. It estimated that public information on the deep web was “400 to 550 times larger” than the surface web, or about 500 times its size (Bergman deep web study). Taken literally, that ratio would make the surface web about 0.2% of content, not 4%. The two figures are not the same measurement. Bergman sampled searchable databases in 2000 and compared their data volume with the pages search engines then indexed. The 4/96 split is a rounded convention used for illustration and does not come from a new survey. Neither figure establishes a reliable present-day percentage or an upper bound on indexed content. Bergman’s estimate is now 25 years old and should be read in its historical scope. A plausible reason the gap has not closed is that information has moved into places crawlers cannot reach: cloud platforms, software-as-a-service applications, mobile app silos, subscription services and authenticated databases. That is a reasoned inference, not a measured result.
“The 96% figure refers to stored content, not necessarily to publicly useful knowledge. Much of it is private by design.”
What the Percentage Does and Doesn’t Mean
Researchers should note two caveats. First, the figure includes inboxes, banking records and internal corporate data that are neither accessible nor legally available. Second, the part that matters most for researchers is the large body of legitimate, publicly available but unindexed material. That includes government registries, court filings, statistical databases, academic repositories, patent systems, digitized archives and specialized collections behind query forms that crawlers do not submit. The scale is real. The Internet Archive alone passed one trillion archived web pages in October 2025, and those archived snapshots can be explored through the Wayback Machine; Google is not a substitute for searching the archive directly (Internet Archive milestone). This material can be reached, but not through standard search engines alone.
Can AI Search Engines Reach Unindexed Pages? It Depends on the Access Method
To test whether AI search has “superior access” to the hidden web, look at what these systems actually query. Mainstream AI answer engines use retrieval-augmented generation (RAG), the approach set out by Lewis et al. (2020). A typical retrieval workflow queries an index, receives passages, and uses them to draft an answer. That discovery step is bounded by the index. Modern tools may also fetch known URLs or operate a browser, so retrieval is not limited to one index. None of these capabilities automatically grants permission to enter private collections.
AOFIRS examines how retrieval systems, crawlers and authenticated sources together determine what AI systems can discover in its research report hidden web research report.
| AI answer engine | Documented retrieval route | What this means for reach |
|---|---|---|
| ChatGPT search | OAI-SearchBot supports search discovery; ChatGPT-User can fetch pages for user actions (OpenAI crawler documentation). | Opting out of OAI-SearchBot excludes content from search answers, though navigational links may remain. User-directed fetching is a separate mechanism. |
| Microsoft Copilot | Microsoft 365 Copilot and Copilot Chat send generated web queries to Bing (Microsoft Copilot web access). | Web discovery depends on Bing; authorized organizational sources are a separate access route. |
| Google AI Overviews and AI Mode | Supporting links require Google indexing and snippet eligibility (Google AI search requirements). | Uses Google Search infrastructure; an AI answer does not list every indexed page. |
| Claude web search | Anthropic documents search and user-fetch agents alongside its training crawler (Anthropic crawler documentation). | Crawler permissions and anti-circumvention rules matter; authenticated browser tools are separate. |
| Perplexity | PerplexityBot supports search results; Perplexity-User fetches pages for user requests (Perplexity crawler documentation). | Public crawling and user-directed fetching differ; the documentation does not imply unrestricted access to gated databases. |
The crawler-level evidence points the same way. Google notes that some pages cannot be crawled without logging in to the site (How Google Search works), and AI crawlers have no credentials of their own. Anthropic states that its crawlers respect anti-circumvention technology and do not try to bypass CAPTCHAs (Anthropic crawler documentation). JavaScript is a further barrier. A study of Vercel’s network found that none of the major AI crawlers, including GPTBot, ClaudeBot and PerplexityBot, rendered JavaScript. They fetched script files but did not run them, so content drawn on the page by client-side scripts was invisible to them. Gemini, which uses Googlebot’s infrastructure, did render it (Vercel crawler study). Unauthenticated crawlers generally cannot retrieve gated assets. Authorized connectors and browser sessions are separate cases. The Vercel findings describe its December 2024 observations, not a universal capability test for all 2026 agents. On script-heavy sites, some crawlers may see only a bare page shell.
Crawler Restrictions in 2026: Training, Search, and Agents Differ
Since mid-2025, more infrastructure controls have let publishers distinguish AI training, search indexing, and user-directed agents. Blocking one does not necessarily block the others.
- Default blocking at infrastructure scale. Cloudflare, which says it manages and protects traffic for 20% of the web, began blocking AI crawlers that access content without permission by default on 1 July 2025. New domains are asked at sign-up whether to allow them (Cloudflare permission-based crawling). In December 2025, CEO Matthew Prince said Cloudflare customers had blocked 416 billion AI-bot requests since 1 July (Cloudflare crawler reach report).
- Crawl access as a paid service. Cloudflare’s Pay Per Crawl program, in private beta since July 2025, answers AI crawlers requesting paid content with an HTTP 402 “payment required” response that states a price (Cloudflare pay per crawl). In July 2026, Cloudflare let all customers manage AI crawlers separately by behavior (Search, Agent and Training), on all pages or only pages that show ads (AI traffic options).
- What changed on 15 September 2026. Cloudflare’s new defaults took effect in revised form. It added a “Disallow AI Training” setting, which publishes a no-training preference in robots.txt. That keeps “Accountable” mixed-use crawlers, a group that includes Googlebot, allowed for search while blocking training-only crawlers from companies such as OpenAI, Anthropic, Meta and Amazon. New ad-supported domains now default to Disallow AI Training, with agents blocked on pages with ads. The stricter “Block” setting now also stops Googlebot, Bingbot and Applebot, search included (Cloudflare crawler controls).
- The asymmetry favors Google. Google’s AI Overviews and AI Mode are fed by the same Googlebot crawl as Search. The separate Google-Extended token limits training and grounding only in some of Google’s other systems (Google AI search requirements). Blocking Googlebot affects Google Search as well as its AI search features. However, Google also documents snippet controls that can limit material shown in AI features; reducing output is different from preventing crawling. In December 2025, Prince said Google’s crawler sees about 3.2 times more web pages than OpenAI’s, 4.6 times more than Microsoft’s and about 4.8 times more than Anthropic’s or Meta’s (Cloudflare crawler reach report). Cloudflare’s September 2026 change lets sites refuse Google’s training use and stay in Search, but it does not shrink Google’s crawl (Cloudflare crawler controls).
- Publishers block AI selectively. In a study of 100 top UK and US news sites, 79% blocked at least one AI training bot and 71% at least one AI live-search or retrieval bot. Common Crawl’s CCBot was the most blocked, by 75% (Publisher crawler blocking study). Across the web, AI crawlers were the user agents most often fully disallowed in robots.txt files in 2025 (Cloudflare yearly review). A research audit found that in a single year, restrictions had made more than 28% of the most actively maintained, critical sources in the C4 training corpus fully off-limits (AI data restrictions study).

The implication for researchers is significant: some content visible in Google or an ordinary browser may be unavailable to a particular AI crawler. Training restrictions alone do not prove a live-search gap, and the evidence does not show that every AI service sees a strict subset of Google’s index. Treating any AI summary as a complete survey remains a methodological mistake. Several access methods can extend what a research tool retrieves:
- Authenticated connectors (MCP). The Model Context Protocol is an open standard, introduced by Anthropic in November 2024, for connecting AI assistants to the systems where data lives (Model Context Protocol announcement). As of November 2026, OpenAI’s deep research documentation describes connecting the models to remote MCP servers that offer search and fetch tools, to vector stores, and to connectors such as Dropbox and Gmail. Private data needs a specific setup (OpenAI deep research documentation). This lets agents search databases for which the researcher holds credentials.
- Agentic browsing with user credentials. Agent modes that drive a visual browser can navigate query forms, page through results and work inside sessions the user has signed into. They can perform deep web searches that crawlers cannot, but the access remains the user’s.
- Licensed data access. Some providers give research agents access to collections ordinary crawlers cannot reach, such as paywalled academic literature, clinical trial registries, patent databases and real-time financial data. They do so through contractual APIs rather than crawling, so the license terms set what the agent may retrieve.
Notice the pattern. AI does not acquire unrestricted access merely by generating a query. Additional reach may come from public-page fetching, the researcher’s credentials or subscriptions, or a provider’s licensed data agreements. These routes must be distinguished from ordinary search-index discovery. AOFIRS’s tool guides, from invisible web search guide to deep web search engines, list the destinations; AI can help you choose among them and query them well.
In direct answer: no reliable current percentage establishes how much of the whole web is unreachable. AI search does not automatically access more than Google, and Google visibility does not guarantee AI visibility. Conversely, absence from Google does not make a public URL technically unfetchable. Compare discovery, direct retrieval, authenticated access, and licensed sources separately. Access and analysis are different capabilities.
A Five-Step Research Protocol
For online researchers using the internet as their primary information source, the working protocol follows from the evidence:
- Use AI to map sources, but require named references. Use AI to identify relevant registries, archives and databases, and check that each named collection actually exists, as hallucinated databases remain a known risk.
- Locate entry points using operator-driven keyword search. Google’s index remains the broadest tool for finding gateway pages and individual documents with operators such as site:, filetype:, inurl:, intitle: and exact phrases.
- Access collections directly. Search deep web repositories through their own interfaces, or connect them to your AI via MCP or agents where you have credentials, so the model uses access you legitimately hold.
- Cross-check AI answers against Google and relevant specialist databases. Neither an AI answer’s silence nor a missing Google result proves that information does not exist. Assume every AI synthesis has blind spots created by crawler blocking, paywalls, JavaScript rendering and index gaps.
- Base synthesis on retrieved primary documents. Give the model verified source material for summarization and contradiction checks. AI output is a lead; the document you retrieve from the registry is the evidence.
Most of the deep web has never been reachable by typing keywords or prose into a box. Access has always depended on method: knowing where collections are, how to query them in their own interfaces and how to verify the results. In 2026, AI can speed up that method, but it can also give a convincing illusion of completeness. Use its strengths without mistaking its output for full coverage. The companion article on invisible web research methods turns this protocol into a worked example, and hidden web beginner guide covers source types and verification from first principles.
References
- Adams, C. (2025, October 31). One trillion web pages archived: Internet Archive celebrates a civilization-scale milestone. Internet Archive Blogs. Internet Archive milestone
- Allen, W., & Newton, S. (2025, July 1). Introducing pay per crawl: Enabling content owners to charge AI crawlers for access. The Cloudflare Blog. Cloudflare pay per crawl
- Anthropic. (n.d.). Does Anthropic crawl data from the web, and how can site owners block the crawler? Claude Help Center. Retrieved November 4, 2026, from Anthropic crawler documentation
- Anthropic. (2024, November 25). Introducing the Model Context Protocol. Model Context Protocol announcement
- Becker, B. (2026, September 15). Have it both ways: Stay discoverable in search while disallowing AI training. The Cloudflare Blog. Cloudflare crawler controls
- Belson, D. (2025, December 15). Cloudflare Radar 2025 year in review. The Cloudflare Blog. Cloudflare yearly review
- Bergman, M. K. (2001). White paper: The deep web: Surfacing hidden value. Journal of Electronic Publishing, 7(1). Bergman deep web study
- Cloudflare. (2025a, July 1). Cloudflare just changed how AI crawlers scrape the internet-at-large; permission-based approach makes way for a new business model [Press release]. Cloudflare permission-based crawling
- Cloudflare. (2026a, July 1). AI traffic options [Changelog]. Cloudflare Docs. AI traffic options
- Google Search Central. (2025a, December 18). In-depth guide to how Google Search works. Google for Developers. How Google Search works
- Google Search Central. (2025b, December 10). AI features and your website. Google for Developers. Google AI search requirements
- Greengard, S. (2026, August 22). Deep web. In Encyclopaedia Britannica. Britannica deep web overview
- Lewis, P., Perez, E., Piktus, A., Petroni, F., et al. (2020). Retrieval-augmented generation for knowledge-intensive NLP tasks (arXiv:2005.11401). arXiv. Retrieval-augmented generation paper
- Longpre, S., Mahari, R., Lee, A., Lund, C., et al. (2024). Consent in crisis: The rapid decline of the AI data commons (arXiv:2407.14933). arXiv. AI data restrictions study
- Microsoft. (2026, October 29). Manage public web access for Microsoft 365 Copilot and Microsoft 365 Copilot Chat. Microsoft Learn. Microsoft Copilot web access
- Nero, V. (2025, December 18; updated 2026, April 8). Which news sites block AI crawlers? BuzzStream. Publisher crawler blocking study
- OpenAI. (n.d.-a). Overview of OpenAI crawlers. OpenAI Developers. Retrieved November 4, 2026, from OpenAI crawler documentation
- OpenAI. (n.d.-b). Deep research. OpenAI Developers. Retrieved November 4, 2026, from OpenAI deep research documentation
- Perplexity. (n.d.). Perplexity crawlers. Perplexity Docs. Retrieved November 4, 2026, from Perplexity crawler documentation
- Search Engine Land. (2025, December). Cloudflare: 416 billion AI bot requests blocked since July. Cloudflare crawler reach report
- Zecchini, G., Moore, A. A., Ubl, M., & Siddle, R. (2024, December 17). The rise of the AI crawler. Vercel Blog. Vercel crawler study




