Public AI readability report

uxcontinuum.com

Scanned Wed, 12 Aug 2026 16:43:58 GMT · https://uxcontinuum.com/

96
out of 100

The tested access and response checks passed

No blocking issues found in this scan. Remaining items are refinements.

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

Keep a copy of this report

We’ll email the full findings plus a prioritised fix checklist for uxcontinuum.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
551
words of readable text
Browser render after JavaScript
585
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
GPTBotOpenAITrainingAllowedHTTP 200
OAI-SearchBotOpenAISearch indexretrievalAllowedHTTP 200
ChatGPT-UserOpenAILive fetchretrievalAllowednot probed
ClaudeBotAnthropicTrainingAllowedHTTP 200
Claude-SearchBotAnthropicSearch indexretrievalAllowednot probed
Claude-UserAnthropicLive fetchretrievalAllowednot probed
PerplexityBotPerplexitySearch indexretrievalAllowedHTTP 200
Perplexity-UserPerplexityLive fetchretrievalAllowednot probed
Google-ExtendedGoogleTrainingAllowednot probed
Applebot-ExtendedAppleTrainingAllowednot probed
meta-externalagentMetaTrainingAllowednot probed
AmazonbotAmazonSearch indexAllowednot probed
BytespiderByteDanceTrainingAllowednot probed
CCBotCommon CrawlTrainingAllowednot probed

Findings (1)

No blocking issues. The items below are refinements.

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.

Keep it that way

The diagnosis stays free. Subscribe when you want scheduled re-scans, history and an alert if a later check regresses.

See plansScan another site