Public AI readability report

cocbaselinks.com

Scanned Mon, 10 Aug 2026 16:41:04 GMT · https://cocbaselinks.com/

52
out of 100

Critical access or response-content failures found

robots.txt blocks 6 search or retrieval crawlers

Access10/100
Can crawlers fetch it
Readability100/100
Is content in the HTML
Structure60/100
Machine-readable meaning
Answerability60/100
Shaped to be quoted

Send this to whoever can deploy the fix

We’ll email the full findings plus a prioritised fix checklist for cocbaselinks.com. Access failures come first, followed by response-content and structure fixes. No account needed.

Initial response and browser render

Word counts of readable text before and after browser execution. The gap is a rendering dependency, not a claim about every vendor’s crawler behavior.

Initial HTML response
166
words of readable text
Browser render after JavaScript
180
words of readable text

Crawler access

Live requests were sent with each vendor’s published user-agent string. This tests how the site handles the claimed identity; a user-agent alone does not authenticate the vendor. A robots.txt pass with a failed request points to another access control.

CrawlerVendorRolerobots.txtLive request
GPTBotOpenAITrainingBlockedHTTP 403
OAI-SearchBotOpenAISearch indexretrievalBlockedHTTP 200
ChatGPT-UserOpenAILive fetchretrievalBlockednot probed
ClaudeBotAnthropicTrainingBlockedHTTP 200
Claude-SearchBotAnthropicSearch indexretrievalBlockednot probed
Claude-UserAnthropicLive fetchretrievalBlockednot probed
PerplexityBotPerplexitySearch indexretrievalBlockedHTTP 200
Perplexity-UserPerplexityLive fetchretrievalBlockednot probed
Google-ExtendedGoogleTrainingBlockednot probed
Applebot-ExtendedAppleTrainingBlockednot probed
meta-externalagentMetaTrainingBlockednot probed
AmazonbotAmazonSearch indexBlockednot probed
BytespiderByteDanceTrainingBlockednot probed
CCBotCommon CrawlTrainingBlockednot probed

Findings (6)

2 critical access or response issues found in this scan.

critical

robots.txt blocks 6 search or retrieval crawlers

Evidence
OAI-SearchBot (OpenAI) — blocked by "Disallow: /"; ChatGPT-User (OpenAI) — blocked by "Disallow: /"; Claude-SearchBot (Anthropic) — blocked by "Disallow: /"; Claude-User (Anthropic) — blocked by "Disallow: /"; PerplexityBot (Perplexity) — blocked by "Disallow: /"; Perplexity-User (Perplexity) — blocked by "Disallow: /"
Why it matters
These agents support search or user-triggered retrieval rather than model training. Vendor effects differ: OpenAI says blocking OAI-SearchBot excludes a site from ChatGPT search answers, while Anthropic says blocking its search or user agents may reduce visibility or prevent retrieval.
Fix
Allow the documented search and retrieval agents for products you want to be able to request the site. Set training-crawler policy separately, then re-test the live request path.
critical

Your server or CDN blocks 1 AI crawler at the network layer

Evidence
GPTBot: HTTP 403
Why it matters
The live tests using these published crawler identities did not receive the page content.
Fix
Review the WAF or bot-management event that handled the request. Allow the crawler identities you chose. For a security bypass, verify vendor IP ranges or reverse DNS instead of trusting a user-agent string alone.
high

No structured data on the homepage

Evidence
No JSON-LD blocks and no microdata found.
Why it matters
Structured data is how a machine learns your entity name, what you sell, where you operate and how to contact you, without inferring it from prose. Without it, assistants are more likely to describe you vaguely or confuse you with a similarly named company.
Fix
Add JSON-LD for Organization (name, url, logo, sameAs, description) plus the type matching the page — Product, Service, LocalBusiness or Article.
medium

No question-shaped content

Evidence
No question headings and no FAQPage schema found.
Why it matters
Assistants answer questions. Pages organised as explicit question/answer pairs are markedly easier to retrieve and quote than undifferentiated marketing prose.
Fix
Add a server-rendered FAQ section using the real questions prospects ask, marked up with FAQPage schema.
medium

No H1 heading in raw HTML

Evidence
No h1 element found before JavaScript runs.
Why it matters
Headings are the primary structural signal used to chunk a page for retrieval.
Fix
Add a single descriptive H1 to the server-rendered HTML.
low

No llms.txt

Evidence
https://cocbaselinks.com/llms.txt returns an HTML page rather than a plain-text file (soft 404).
Why it matters
An emerging, not-yet-universally-consumed convention: a plain-text map of your most important pages for language models. Low cost, speculative upside.
Fix
Publish /llms.txt listing your key pages with one-line descriptions.

Get these fixed and keep them fixed

The diagnosis stays free. Paid plans generate reviewable robots.txt, JSON-LD and llms.txt artifacts, then re-scan on schedule and email you when a check regresses.

See plansScan another site