Export Report
OVERALL SCORE
Level 3, Bot-Aware
- AI Discoverability 80 out of 100
- Agent Ease of Use 77 out of 100
- Security & Trust 90 out of 100
- GEO, AIO and AEO 68 out of 100
- SEO 100 out of 100
- Performance 81 out of 100
- Accessibility 19 out of 100
What AI sees of your website
TikMonitor — See how much any TikTok Live is really making
Real-time diamond counts, gift tracking, chat history with usernames, and alerts on any public TikTok Live.
Next step
Turn this report into a fix workflow
3 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.
| Metric | Score | Status | Passed | Failed | Warning | Evidence |
|---|---|---|---|---|---|---|
| AI Discoverability | 80 | Mostly ready | 45 | 1 | 0 | View details |
| Discoverability | 100 | Strong | 10 | 0 | 0 | |
| Content Readiness | 87 | Mostly ready | 32 | 0 | 0 | |
| Bot Access Control | 58 | Needs work | 3 | 1 | 0 | View details |
| Agent Ease of Use | 77 | Mostly ready | 41 | 3 | 3 | View details |
| API | 85 | Mostly ready | 12 | 1 | 1 | View details |
| Auth | 71 | Needs work | 11 | 0 | 0 | |
| MCP | 66 | Needs work | 6 | 0 | 0 | |
| Skill Discovery | 65 | Needs work | 9 | 2 | 2 | View details |
| Google Agentic Browsing | 100 | Strong | 3 | 0 | 0 | |
| GEO, AIO and AEO | 68 | Needs work | 10 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 5 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| SEO | 100 | Strong | 10 | 0 | 0 | |
| Security & Trust | 90 | Strong | 23 | 0 | 0 | |
| Security & Trust | 90 | Strong | 23 | 0 | 0 | |
| Performance | 81 | Mostly ready | 14 | 0 | 0 | |
| Performance | 81 | Mostly ready | 14 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
69 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Needs attention
AI bot rules in robots.txt
Issue
No explicit User-agent rules were found for major AI crawler tokens.
Details
Why it matters
AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.
Check name
AI bot rules in robots.txt
Score
31/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.
Result
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Validation steps
Classify AI crawler rules
No explicit User-agent rules were found for major AI crawler tokens.
robots.txt lacks explicit AI crawler rules
Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Validate version-specific card shape".
56 Fail
Agent Ease of UseSkill DiscoveryEmerging recommendation
A2A Agent Card
A2A Agent Card failed at "Validate version-specific card shape".
Needs attention
A2A Agent Card
Issue
A2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.
Details
Why it matters
A2A Agent Cards provide protocol-specific discovery for agent identity, skills, input and output modes, transport bindings, capabilities, and security requirements. Legacy A2A also used /.well-known/agent.json, so scanners must classify the card shape before reporting readiness.
Check name
A2A Agent Card
Score
44/100
Status
fail
Category
Skill Discovery
Maturity
Emerging recommendation
Goal
Publish a version-appropriate A2A Agent Card so A2A-compatible clients can discover agent skills and invoke the declared endpoint safely.
Result
A2A Agent Card failed at "Validate version-specific card shape".
Validation steps
Discover A2A Agent Card
The A2A Agent Card was found at a legacy or fallback path.
A2A Agent Card is missing or discovered at a non-canonical path
Validate version-specific card shape
A2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.
A2A Agent Card shape is invalid for its version
Invalid skills
- #0 (search): tags[]
- #1 (contact): tags[]
Validate HTTP delivery
current A2A card is served at the legacy agent.json path
A2A Agent Card HTTP delivery is not standards-aligned
Probe same-origin A2A endpoint
The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.
Advertised same-origin A2A endpoint did not answer a safe probe
Evidence log4 steps · 22 lines
Discover A2A Agent Card [warning]! The A2A Agent Card was found at a legacy or fallback path.INFODiscover A2A Agent CardINFOTry A2A discovery paths in priority order paths=["/.well-known/agent-card.json","/.well-known/agent.json","/agent-card.json","/.well-known/a2a/agent-card.json"]WARNA2A candidate path did not return a usable card path="/.well-known/agent-card.json" statusCode=404 contentType="text/html; charset=utf-8"PASSFound an A2A candidate path="/.well-known/agent.json" statusCode=200 contentType="application/json; charset=utf-8" bytes=1121WARNA2A candidate path did not return a usable card path="/agent-card.json" statusCode=404 contentType="text/html; charset=utf-8"WARNA2A candidate path did not return a usable card path="/.well-known/a2a/agent-card.json" statusCode=404 contentType="text/html; charset=utf-8"WARNSelected non-canonical A2A Agent Card path="/.well-known/agent.json" pathClass="legacy-a2a" requestedUrl="https://tikmonitor.com/.well-known/agent.json"WARNThe A2A Agent Card was found at a legacy or fallback path.Validate version-specific card shape [fail]! A2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.INFOValidate version-specific card shapeFAILCompare missing required card fields actual="none" expected="none"FAILCheck every declared A2A skill has required name, description, and endpoint fields actual=2 expected=0 invalidSkills=[{"index":0,"id":"search","issues":["tags[]"]},{"index":1,"id":"contact","issues":["tags[]"]}]INFOReview declared endpoint interfaces interfaces=[{"url":"https://tikmonitor.com/api/mcp","protocolBinding":"unknown","issues":["unknown protocolBinding"]},{"url":"https://tikmonitor.com/api/rpc/contactForm/submit","protocolBinding":"HTTP+JSON","issues":[]}]FAILA2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.Validate HTTP delivery [warning]! current A2A card is served at the legacy agent.json pathINFOValidate HTTP deliveryWARNCompare card Content-Type with JSON expectation actual="application/json; charset=utf-8" expected="application/json or +json"INFOReview selected discovery path path="/.well-known/agent.json" pathClass="legacy-a2a"WARNHTTP delivery/path warning warning="current A2A card is served at the legacy agent.json path"WARNcurrent A2A card is served at the legacy agent.json pathProbe same-origin A2A endpoint [fail]! The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itFAILA2A endpoint probe did not validate url="https://tikmonitor.com/message:send" statusCode=500 rpcError="Only HTML requests are supported here"FAILThe same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
23 Fail
Agent Ease of UseAPIEstablished
API Catalog
API Catalog failed at "Validate API catalog targets".
Needs attention
API Catalog
Issue
API catalog target https://tikmonitor.com/api/health (status) advertised application/json but returned text/plain.
Details
Why it matters
API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.
Check name
API Catalog
Score
77/100
Status
fail
Category
API
Maturity
Established
Goal
Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.
Result
API Catalog failed at "Validate API catalog targets".
Validation steps
Validate API catalog media type
The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.
API catalog media type is not application/linkset+json
Validate API catalog targets
API catalog target https://tikmonitor.com/api/health (status) advertised application/json but returned text/plain.
API catalog targets are unreachable or media types mismatch
Evidence log2 steps · 11 lines
Validate API catalog media type [warning]! The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.INFOValidate API catalog media typeWARNCompare API catalog media type actual="application/linkset+json" expected="application/linkset+json"WARNCompare RFC 9727 profile parameter actual=false expected=trueWARNThe API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter. status="warning"Validate API catalog targets [fail]! API catalog target https://tikmonitor.com/api/health (status) advertised application/json but returned text/plain.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsPASSAPI catalog target is reachable rel="service-desc" href="https://tikmonitor.com/openapi.json" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/json"PASSAPI catalog target is reachable rel="service-doc" href="https://tikmonitor.com/.well-known/webmcp.json" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/json"FAILAPI catalog target failed validation rel="status" href="https://tikmonitor.com/api/health" statusCode=200 contentType="text/plain" advertisedType="application/json" typeMatches=falseFAILCompare API catalog target failure count actual=1 expected=0FAILAPI catalog target https://tikmonitor.com/api/health (status) advertised application/json but returned text/plain.
Sign in to see 34 other issues and the full report
Create a free account to unlock every issue, evidence details, exports, and higher free limits.
Fix with MCP or CLI
Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.
Score history
Public scan score over time
Public reports for this website origin. Select any point or report link to open that canonical report.
| Scan date | Score | Readiness | Report |
|---|---|---|---|
| 77/100 | Level 4, Mostly Ready | View report | |
| 70/100 | Level 3, Bot-Aware | Current report |