Agent Web Index › findozor.net

Can AI assistants read findozor.net?

Measured on 2026-09-19 by asking the site 7 times — once as a browser, once as each of the 6 crawlers that feed ChatGPT, Claude, Perplexity, Gemini, Meta AI, Apple Intelligence and Doubao — and comparing what came back. The AI-training opt-out tokens that never crawl are read from robots.txt instead.

D57 / 100

0 of 6 crawlers can read this page.

More readable than 11% of the 47,821 sites measured so far. Structured data: Organization.

What each crawler got back

Crawler	HTTP	Result	robots.txt
ClaudeBot (Claude)	—	no-answer	no-file
GPTBot (ChatGPT)	—	no-answer	no-file
OAI-SearchBot (ChatGPT Search)	—	no-answer	no-file
PerplexityBot (Perplexity)	—	no-answer	no-file
Google-Extended (Gemini, AI Overviews) a robots.txt token, not a crawler: it controls how already-crawled pages may be used, and never makes a request of its own	—	not opted out	no-file
Meta-ExternalAgent (Meta AI)	—	no-answer	no-file
Amazonbot (Alexa, Rufus)	—	no-answer	no-file

What to change, in order

Let in the 6 crawlers your own robots.txt already allows+6 crawlers
ClaudeBot, GPTBot, OAI-SearchBot, PerplexityBot, Meta-ExternalAgent, Amazonbot are turned away before reading the page (the connection never completed), while robots.txt permits them — so this block is not written in your site. No CDN signature was found in the response headers, so the refusal comes from the origin server itself or from a WAF this index does not recognise. Fixing it takes this domain from 0 to 6 of 6 crawlers.
Publish sitemap.xml and llms.txt
sitemap.xml and llms.txt are missing, so an assistant has to discover the site by following links. llms.txt is the emerging convention for telling an assistant which pages actually matter.

Get told if this changes

One email only when a measured crawler flips on findozor.net, served to refused or back. No schedule, no newsletter; double opt-in, one-click stop.

The checks

Answers AI agents like it answers people0%
Readable without JavaScript100%
robots.txt lets the crawlers in100%
Facts in JSON-LD67%
Content reachable, not buried78%
Publishes a map of itself0%
Plain structure89%

Re-run this audit live → Full AI-visibility report for findozor.net →

Sites with a similar score

filsendflowers.myshopify.comD 57 finpilot.myshopify.comD 57 fightclub.myshopify.comD 57 fish.myshopify.comD 57 fedopps.myshopify.comD 57 flatiron.myshopify.comD 57 estories.myshopify.comD 57 freecad.orgD 57 diablosource.myshopify.comD 57 headlock.myshopify.comD 57 activity.myshopify.comD 57 netinfox.myshopify.comD 57

Browse the whole index →

Embed this score

Put the badge on findozor.net — it links back here, and re-measures every time this index re-crawls.

<a href="https://shop.lumnika.com/ai-readiness/findozor.net"><img src="https://shop.lumnika.com/ai-readiness/findozor.net/badge.svg" alt="AI readability"></a>

Method. 7 live HTTP requests (one per crawler, one as a browser) plus robots.txt, llms.txt, sitemap.xml and security.txt, 12-second timeout each, from a single vantage point. Blocking AI crawlers is a legitimate choice, not a failure: this page records what is true, not what should be. Domain comes from a shop-platform seed (Shopify/WooCommerce/Magento/BigCommerce/Shopline fingerprint or JSON-LD price), not the Tranco traffic ranking. One page per domain — the homepage — is audited.

Part of the Agent Web Index, 47,821 domains measured, updated continuously.