Research & Data

Do Billiards Sites Block AI Crawlers? 1 of 9 Do

Jun 14, 2026

In billiards, the storefronts stay open and the editorial hub does not. That single split is the whole story of how this niche treats AI crawlers in our June snapshot — a lone media site gating, while the cue and table sellers wave everyone through.

1 of 9 Billiards sites block at least one AI crawler.

Of the Billiards sites we checked, 9 returned a parseable robots.txt — a plain-text file at the domain root that tells automated agents which paths they may fetch — and exactly 1 of those disallows an AI crawler. That works out to an 11.1% block rate. Every figure here is read straight from the sealed file; nothing is estimated, modeled, or extrapolated.

The one blocker is azbilliards.com, a community-and-news destination rather than a shop. The eight that allow everything are gear and equipment sellers. Against the corpus, where 28% of sites with a policy gate at least one crawler, billiards sits comfortably below the line.

Who Gates the Crawlers Here

The split in billiards is clean and informative. The single blocker, azbilliards.com, is the category's editorial and forum hub — the kind of site whose value is its written archive and discussion, the content most worth fencing off from AI training crawlers. Its lone disallow is the entire 11.1%.

Everything else stays open. The eight allowers — pooldawg.com, seyberts.com, ozonebilliards.com, mcdermottcue.com, predatorcues.com, diamondbilliards.com, simoniscloth.com, and vikingcue.com — are cue makers, table builders, cloth suppliers, and pro-shop retailers. Not one of them carries a disallow aimed at an AI agent. For a storefront, being readable by an AI assistant is a feature, not a threat: it keeps the product catalog eligible to be named when a buyer asks for a recommendation.

One more billiards domain, billiardcongress.org, returned no parseable robots.txt at the time of the seal. Absence of a file is not a stated allow and not a block — it is simply silence on the matter. The same retail-open, media-gated pattern turns up in how cigar sites handle AI crawlers, another enthusiast vertical built around shops plus a flagship magazine.

It helps to be precise about what "blocks an AI crawler" means in this study. A block is an explicit Disallow directive aimed at a named AI agent — GPTBot, ClaudeBot, CCBot, and the rest of the tokens in the corpus leaderboard. azbilliards.com carries such a directive; the eight retailers do not.

A site can disallow administrative paths or search endpoints without touching an AI token at all, and that is not counted here as an AI block. Only a directive that names an AI agent moves a site into the blocker column, which is why the billiards count is a clean 1.

That precision is what keeps the 11.1% honest. We are not inferring intent from a missing sitemap or a slow server; we are reading a specific line in a specific file. azbilliards.com chose to write that line, and the read is verbatim.

Of the 9 Billiards sites with a policy, exactly 1 disallows an AI crawler.

What This Block Rate Actually Means

An 11.1% rate is low, and the reason is structural rather than coincidental. When a category is dominated by commercial sellers, the dominant incentive is discoverability — and discoverability argues against blocking. A cue retailer that fences out an AI crawler removes its own products from the answers those assistants generate.

The exception proves the rule. azbilliards.com is the one site whose product is its content — articles, results, and forum threads — so it has a reason to think twice about feeding AI training crawlers for free. That is the same logic that pushes media-heavy categories far up the ranking while retail-heavy ones stay near the floor.

So the honest read is that billiards behaves like a commerce vertical with a single media outlier, not like a publishing vertical. The retail majority sets the tone, and the tone is open.

Billiards sites post an 11.1% AI-crawler block rate.

Where Billiards Sits in the Corpus

An 11.1% block rate places Billiards among the corpus's lighter gatekeepers. The focused window below shows Billiards beside its nearest neighbors in the ranking — drawn verbatim from the sealed snapshot, name first, no rank column.

CategorySitesWith robots.txtBlock ≥1 crawlerBlock rate
Skateboarding109111.1%
Leathercraft109111.1%
Orchids109111.1%
Billiards109111.1%
Productivity1010110%
Marketing1010110%
Hunting1010110%

Billiards shares its exact 11.1% reading with a cluster of hobby and lifestyle categories, just above a band of single-blocker verticals at 10%. Several of these are equipment-and-supply niches that, like billiards, run on storefronts. For a sense of scale against the rest, the extremes table shows the corpus's two ends:

CategorySitesWith robots.txtBlock ≥1 crawlerBlock rate
Gaming99888.9%
Food1010770%
Bowling10900%
Kayaking10400%

The contrast is stark: Gaming gates the overwhelming majority of its sites while neighbors of billiards barely gate at all. The same low-gating posture defines how equestrian sites treat AI crawlers, another tack-and-supply niche where retailers dominate, and it bottoms out entirely in the zero-block kayaking result.

What ties these low-gating verticals together is their commercial center of gravity. Billiards, equestrian, and paddlesports are all dominated by storefronts whose revenue depends on being found, so the population-level posture skews open. Publishing-heavy categories — Gaming, News, Food, Tech — invert that, because the content itself is the asset and AI ingestion is a direct competitive risk. Billiards lands near the floor precisely because eight of its nine policied sites are sellers and only one is a publisher.

Which Bots Are Blocked Most

The single billiards blocker matters less than the corpus-wide pattern of which crawlers get gated, because that pattern tells a retailer which token a competitor would add first. The cut below shows the most-disallowed bots across all 1053 sites, bot name first, count next.

BotSites disallowing (all 1053 sites)
CCBot221
ClaudeBot197
GPTBot197
Bytespider190
Meta-ExternalAgent168

CCBot — Common Crawl's agent — tops the corpus blocklist, with ClaudeBot and GPTBot tied just behind. azbilliards.com's lone disallow is a drop in that bucket, which is why billiards reads as open overall.

Corpus-wide, 295 of 1053 sites block at least one AI crawler.

Reading the Sealed Numbers

These figures come from one point-in-time crawl of public robots.txt files, sealed June 14, 2026 under snapshot sha d0b7ef205c390023. For each Billiards domain we fetched robots.txt at the root, parsed its user-agent and disallow lines, and recorded whether any AI crawler token was disallowed. We report verbatim counts only; nothing is estimated, modeled, or extrapolated. A domain with no parseable file, like billiardcongress.org, is logged as exactly that — neither an allow nor a block.

US Tech Automations runs this read across 1274 sites checked, 1053 with a parseable robots.txt, spanning 128 categories. Billiards contributes 9 of those files, and we report its slice as the 9 it is.

A word on what the snapshot deliberately does not do. It does not retry failed fetches over hours to coax a file out of a slow host, it does not follow redirects into a different domain's policy, and it does not infer a block from a site's general unfriendliness to bots. Each domain is read once, at seal time, exactly as it answered.

That single read is what makes the file content-addressable: anyone holding sha d0b7ef205c390023 can confirm the same nine billiards files yield the same one blocker. The trade-off is that a site briefly offline at seal time lands in the no-parseable-file bucket rather than the allow column — which is precisely why billiardcongress.org is reported as silent rather than open. The discipline favors reproducibility over generosity, and we would rather undercount a permissive site than guess.

Frequently Asked Questions

Q: Which billiards site is the one that blocks AI crawlers?

A: azbilliards.com — the category's editorial and forum hub. It is the single domain among the 9 with a policy that disallows an AI crawler, and it accounts for the entire 11.1% block rate. The eight retail sites all allow every crawler.

Q: Why do the cue and table sellers leave crawlers alone?

A: Discoverability. Storefronts like pooldawg.com and predatorcues.com want AI shopping assistants to read and recommend their products, so blocking a crawler would work against the business. Their robots.txt files carry no AI disallow at all.

Q: Does the 11.1% rate cover every billiards site you found?

A: No. It covers the 9 sites that returned a parseable robots.txt. One more domain, billiardcongress.org, produced no parseable file at the seal, so it is excluded from the block-rate math rather than counted as an allow or a block.

Q: Does a robots.txt disallow actually keep a crawler out?

A: It signals intent, but it does not enforce. robots.txt is an honor-system standard: cooperative agents read it and comply, while a non-compliant one can disregard it entirely. azbilliards.com's disallow asks AI crawlers to stay out; whether each one honors that is up to the crawler.

Put AI-Access Data to Work

For a billiards or cue-supply storefront operator running a catalog like pooldawg.com, AI shopping agents are an emerging path to the buyer, and this snapshot is the baseline to defend: your category is open today, with a lone media site gating. Set a recurring crawl that re-reads robots.txt for azbilliards.com, predatorcues.com, and seyberts.com weekly, and alert the moment a competing storefront adds an AI crawler token to its disallow list — a rival going dark is a discoverability gap you can fill.

A billiards e-commerce RevOps lead is the second fit: they can watch the same set to confirm their own catalog stays readable as AI buying agents grow, and verify nothing on their domain quietly slips into a block. US Tech Automations runs these scheduled robots.txt crawls with change alerts so a shift surfaces the week it happens rather than at the next manual audit. See how the agentic monitoring works.

Corpus-wide, 295 of 1053 sites block at least one AI crawler.

Key Takeaways

  • Of the 9 Billiards sites with a parseable robots.txt, 1 blocks at least one AI crawler — an 11.1% rate.

  • The lone blocker is azbilliards.com, an editorial and forum hub; the eight retail sites all allow every crawler.

  • billiardcongress.org returned no parseable file and is excluded from the block-rate math.

  • Corpus-wide, 295 of 1053 sites (28%) gate at least one crawler, so billiards sits well below the line.

  • CCBot is the most-disallowed bot across all 1053 sites, with ClaudeBot and GPTBot tied just behind.

Source: US Tech Automations Research — Closing Web edition; figures are verbatim counts from public robots.txt files sealed June 14, 2026 (snapshot sha d0b7ef205c390023).

Get this data as a daily feed

The numbers in this report come from a permit feed we monitor daily. Leave your email and we will follow up about a daily feed for your ZIPs and categories.

Prefer to talk first? Contact us.

Cite this report

US Tech Automations Research, 2026-06 edition. “Do Billiards Sites Block AI Crawlers? 1 of 9 Do.” https://ustechautomations.com/resources/blog/do-billiards-sites-block-ai-crawlers-2026

Sealed snapshot sha256: d0b7ef205c390023

Machine-readable data: CSV · JSON · All research & methodology

About the Author

Garrett Mullins
Garrett Mullins
Workflow Specialist

Helping businesses leverage automation for operational efficiency.