Study 01 · Global Digital Authority Benchmark Series · Australia 2026

Over 2 in 5 Australian business websites with an observable crawler policy block the AI crawlers they need

A structured benchmark of 409 publicly identifiable Australian business websites (commercial operating entities) across 10 industry groups, measuring which AI search crawlers can — and cannot — access them.

Author Douglas Lord
Research instrument PTODA C01 Crawler v1.2 — deterministic robots.txt scanner
Commercial operator AUTHORITY44™
Scan date 17 June 2026, AEST
Sample 409 practitioner domains · 10 sectors · 314 with readable robots.txt policy
42%
of Australian business domains with a readable robots.txt file block at least one AI retrieval crawler

Of 314 practitioner domains whose crawler policy could be directly observed, 133 — 42.4% — block at least one crawler used by AI search systems to discover and cite content.

We separate observable AI-crawler policy from infrastructure non-response. A block declared in robots.txt is a policy decision; a 403, timeout or unscannable response is an access outcome, not evidence of crawler policy. These are reported separately below.

Of the blocked sites, 90.2% are broad access restrictions catching AI crawlers incidentally rather than AI-specific decisions.

Methodology update (v1.2). This report has been updated to align with the harmonised AI Crawler Access Study methodology used across Australia, the United States, Great Britain and Singapore. Version 1.2 applies a practitioners-only sample definition (commercial operating entities only), the standardised 21-user-agent crawler set, and revised handling of access-denied responses. Figures published under Version 1.0 are superseded. All results on this page reflect the Version 1.2 frozen dataset (n=314). Data: PTODA C01 Crawler v1.2 · series master frozen 17 June 2026.

Key findings

The numbers at a glance

Policy-layer figures are based on 314 practitioner domains whose robots.txt was successfully retrieved and parsed. A further 95 domains returned no observable policy (39 access-denied, 56 unscannable) and are reported separately in the Infrastructure layer section. They are not counted as open or blocked.

57.6%
Open to all AI crawlers
181 of 314 policy-observed sites, with no robots.txt restriction preventing AI search discovery
36.0%
Fully blocked to all AI crawlers
113 sites block all tested retrieval crawlers
6.4%
Partially blocked
20 sites block some crawlers but not all
90.2%
Broad blocks — not targeted at AI
120 of 133 blocked sites also block Googlebot, so the block is a broad restriction rather than an AI-specific decision
9.8%
Deliberate AI-only blocks
13 sites specifically blocked AI crawlers while keeping Googlebot accessible
21
AI crawlers tested
14 retrieval (Group A) and 7 training (Group B) user-agents, the harmonised series crawler set

The central finding: Most blocked businesses are not actively choosing to exclude AI search. They have broad access restrictions set years ago that are now inadvertently catching AI crawlers. This is a configuration problem, not a strategic decision.

Infrastructure layer

Access outcomes — not crawler policy

We separate observable AI-crawler policy from infrastructure non-response. A block in robots.txt is a policy decision. A 403, timeout or unscannable response is an access outcome, not evidence of crawler policy. These 95 domains are reported here and excluded from every policy-layer figure.

39
Access denied (HTTP 403/401/429)
9.5% of the 409 domains approached. The edge (WAF / managed CDN) refused the robots.txt request, so no crawler policy could be observed. Not counted as open or blocked.
56
Unscannable
13.7% of domains approached. No readable response through connection failure, timeout or 5xx error. No policy observable.
314
Policy observed
76.8% of domains approached returned a readable robots.txt. This is the denominator for all policy-layer findings on this page.

Why this matters: a domain that denies the crawler at the infrastructure layer has not expressed an AI-crawler policy — it has prevented one from being read. Treating such a response as “open” would overstate access; treating it as “blocked” would overstate restriction. Reporting it separately keeps the policy-layer figures based only on directly observed robots.txt behaviour.

Block origin

Intentional vs infrastructure-imposed

Of the 133 sites blocking AI retrieval crawlers, the source of the block was classified into three categories.

57.1%
Explicit — author-set
76 sites. Block is in the site's own robots.txt. May be intentional or legacy configuration.
38.3%
Indeterminate
51 Cloudflare-hosted sites without a managed-robots signature. Likely explicit blocks — cannot be confirmed by automated analysis alone.
4.5%
Infrastructure-imposed
6 sites. Block originates from Cloudflare's managed robots.txt feature — a platform default the owner may never have consciously set.

The infrastructure-imposed subset is the most commercially significant finding: these site owners may be blocking AI search discovery without ever having made that decision. The indeterminate category — 51 Cloudflare-hosted sites — most likely represents explicit blocks, but the configuration path cannot be confirmed by automated means alone.

Sector analysis

Block rates by industry

Block rates vary across the 10 sectors. Real Estate and Accounting & Finance are highest; Professional Services lowest. Rates are computed on policy-observed domains per sector (readable robots.txt only).

% blocking ≥1 retrieval crawler (of policy-observed domains per sector)
Real Estate
57.1%
Accounting & Finance
53.3%
Education & Training
50.0%
Technology & SaaS
50.0%
Retail & Ecommerce
45.9%
Healthcare
41.9%
Legal
36.1%
Hospitality & Tourism
33.3%
Building & Trades
31.2%
Professional Services
23.3%

Real Estate at 57.1% and Accounting & Finance at 53.3% are the highest-blocking sectors. That matters, since AI search is reshaping how Australians find property and financial advice. Technology & SaaS at 50.0% remains among the study's most counterintuitive findings: the sector most aware of AI is among the most likely to be invisible to it. Professional Services at 23.3% is the most open.

Per-crawler analysis

Which crawlers are blocked most

Group A (retrieval/citation crawlers) drives the headline finding. Group B (training crawlers) is reported separately, because blocking training crawlers is often a deliberate and legitimate content-protection decision.

Group A — Retrieval & Citation Crawlers (14 tested)
GPTBot OpenAI40.8%
ClaudeBot Anthropic40.4%
anthropic-ai Anthropic39.5%
Bingbot Bing / Copilot39.5%
ChatGPT-User OpenAI39.2%
Claude-User Anthropic39.2%
PerplexityBot Perplexity37.9%
Googlebot baseline38.2%
Group B — Training Crawlers (7, separate)
CCBot Common Crawl41.7%
Bytespider ByteDance41.4%
Amazonbot Amazon41.1%
Applebot-Extended Apple40.8%
meta-externalagent Meta40.8%
Google-Extended Gemini training40.4%
FacebookBot Meta39.8%

The Googlebot parity finding is the most important number in the dataset. Googlebot is blocked at 38.2%, right alongside the AI retrieval crawlers (GPTBot 40.8%, ClaudeBot 40.4%). This confirms that the vast majority of AI crawler blocks are broad restrictions, not targeted AI decisions. Businesses blocking AI crawlers are mostly also blocking Google. The 14 retrieval crawlers cluster tightly (37.9%–40.8%), indicating that where AI is blocked, it is typically blocked uniformly across operators rather than selectively.

Platform analysis

CMS correlation

Block rates by content management system among policy-observed domains. WordPress is the only platform with a large enough base for a reliable rate; the others are shown for completeness but rest on small samples and should be read with caution.

Block rate by detected CMS (policy-observed domains)
Shopify
36.4% (n=11)
WordPress
33.9% (n=56)
Drupal
10.0% (n=10)
Webflow
0% (n=4)

Most sites return no identifiable CMS signature, so platform-level rates are based on the minority that do. WordPress at 33.9% (n=56) tracks close to the overall sample average, the broadest cross-section of Australian business websites. Drupal at 10.0% (n=10) is directionally low, consistent with Drupal's enterprise and government skew where robots.txt is more deliberately managed, but the small base means this is indicative rather than conclusive. Webflow (n=4), Joomla (n=2) and Squarespace (n=1) have too few domains in this sample to report a meaningful rate.

Methodology

How this study was conducted

Study specification

Methodology version
PTODA C01 Crawler Methodology (v1.2, June 2026). Citeable, versioned specification covering sample criteria, the 21-user-agent crawler list, classification logic, and the policy/infrastructure layer split.
Research instrument
PTODA C01 Crawler v1.2 — a deterministic robots.txt scanner. Same input produces the same result; the study is reproducible by re-running the instrument against the published sample.
Sample
409 publicly identifiable Australian business websites (commercial operating entities — practitioners) across 10 industry groups, sourced from named public directories. Portals, aggregators, government, industry bodies, research institutes and not-for-profits are excluded under the harmonised series entity-type rule. No client sites. No sites selected by outcome.
Sectors
Retail/Ecommerce, Real Estate, Legal, Healthcare, Building/Trades, Accounting/Finance, Hospitality/Tourism, Education/Training, Technology/SaaS, Professional Services
Measurement
Public robots.txt parsed per user-agent across 21 AI crawlers (14 retrieval, 7 training). Homepage meta robots and X-Robots-Tag headers examined. CMS and CDN/host detected from homepage signals.
Bot identity
PTODA-C01-Crawler/1.2 — identified honestly in every request. robots.txt respected; polite rate limits applied.
Scan date
17 June 2026, AEST. Point-in-time snapshot.
False positive prevention
WordPress /wp-admin/ disallows, Crawl-delay directives, and sitemap declarations explicitly excluded from blocked classification. Validated against 14 fixture tests before batch ran.
URL structure
Root-level domains only. Businesses whose primary AU presence is a sub-path of an international domain were replaced with root-domain equivalents. Some businesses that would otherwise qualify are not included.
Policy vs infrastructure layers
Of 409 domains approached, 314 returned a readable robots.txt policy (the policy-layer denominator). 95 returned no observable policy and are reported separately: 39 access-denied (HTTP 403/401/429 at the edge) and 56 unscannable (connection failure, timeout or 5xx). Access-denied and unscannable domains are never counted as open or blocked.

Series freeze reference

Dataset version
AI Crawler Access Study Series v1.2 — frozen 17 June 2026. The authoritative dataset for the Australia, United States, Great Britain and Singapore comparative analysis. All figures on this page derive from the v1.2 series master; figures published under v1.0 are superseded.
Limitations

Caveats

Disclosure & Intellectual Property

Roles. This study is published by the Periodic Table of Digital Authority (PTODA), the methodology owner. It was conducted using the PTODA C01 Crawler v1.2, a deterministic robots.txt reference instrument, under PTODA C01 Crawler Methodology v1.2. AUTHORITY44 provided technical infrastructure and execution support as commercial operator. Douglas Lord is the founder of both PTODA and AUTHORITY44; this relationship is disclosed in full. The sample was constructed from named public directories with no reference to commercial relationships. The methodology is fully documented and reproducible. This study publishes aggregate, anonymised findings only. No named individual site results are published.

Attribution chain: Douglas Lord (researcher, author) · Periodic Table of Digital Authority (publisher & methodology owner) · PTODA C01 Crawler v1.2 (research instrument) · AUTHORITY44™ (commercial operator) · Digital Dominator Pty Ltd ABN 28 616 931 116 (operating entity).

Intellectual property notice: This study, its methodology, findings, data, and all associated content are the original work of Douglas Lord and the property of Digital Dominator Pty Ltd (ABN 28 616 931 116). The Periodic Table of Digital Authority™ is a coined framework and trade mark pending (TM 2644497). AUTHORITY44™ is a trade mark pending (TM 2643932). All rights reserved.

You may cite findings from this study with appropriate attribution identifying the author (Douglas Lord), the publisher (Periodic Table of Digital Authority — periodictableofdigitalauthority.com), and the research instrument (PTODA C01 Crawler v1.2). You may not reproduce this study in full, present these findings as your own research, or use the framework name or trade marks without prior written consent. Use of this research is subject to the Terms of Use.