Protal/Audit/musicvideoai.pro
Needs workScanned Sep 19, 11:39 PM

https://musicvideoai.pro.

After a 6.6-second audit, musicvideoai.pro earned a C+ — that's 66/100 weighted across 9 categories. We flagged 9 failing checks.

Don't worry — most sites aren't there yet. The web spent 20 years tuning for search engines — and that work mattered, it's why anyone finds anything online. Standards like /llms.txt and MCP only landed in the last year or two; the web is mid-reset for AI. We're here to map what to fix first.

Checks51 completedDuration0m 6sTimeouts0Enginev2.0 · 9 categories
66/ 100
Grade C+
Needs work
Passing
25
Warnings
3
Failing
9
Skipped
14
Rules that didn't apply
Opportunities
0
Emerging standards
ScopeThis audit covers musicvideoai.pro only. We don't check the rest of your site automatically.

Nine categories, weighted.

Category 1 (Crawler Policy) and Category 3 (Agent Readiness) carry the most weight. Category 2 (AI Semantic Files) carries a small weight — signals like llms.txt and skill.md count, but less than rules with stronger public evidence.

Priority fixes

Ranked by impact on the overall score. Fix these first.

Critical
R4.1§04 Schema.org Structured Data

At least one JSON-LD block

No <script type="application/ld+json"> found.

High
R1.3§01 Crawler Policy

Major retrieval crawlers are named in robots.txt

Explicit policy for 0 retrieval crawler(s) from the current registry: none.

Medium
R2.1§02 AI Semantic Files

/llms.txt exists

/llms.txt not found.

AI crawler coverage

Which major crawlers you've explicitly addressed in robots.txt.

9 addressed
OpenAI
GPTBot
TrainingAddressed
Anthropic
ClaudeBot
TrainingAddressed
Google
Google-Extended
TrainingAddressed
Apple
Applebot-Extended
TrainingAddressed
Common Crawl
CCBot
TrainingAddressed
ByteDance
Bytespider
TrainingAddressed
Perplexity
PerplexityBot
RetrievalAddressed
OpenAI
OAI-SearchBot
RetrievalAddressed
OpenAI
ChatGPT-User
User-triggeredAddressed

Findings

Every rule we checked, grouped by category.

§01Crawler Policy7 shown
✓
R1.1
robots.txt exists
/robots.txt found: 1 user-agent group(s), 1 Sitemap directive(s).
View in methodology
Pass
✕
R1.2
Major training crawlers are named in robots.txt
Explicit policy for 0 training crawler(s) from the current registry: none.
View in methodology
Not addressed: GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, CCBot, Bytespider, Meta-ExternalAgent, cohere-ai.
Pass threshold: ≥4 explicit (registry size 8).
Fail
✕
R1.3
Major retrieval crawlers are named in robots.txt
Explicit policy for 0 retrieval crawler(s) from the current registry: none.
View in methodology
Not addressed: OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot, Google-Agent, Meta-ExternalFetcher, MistralAI-User, DuckAssistBot.
Pass threshold: ≥3 explicit (registry size 9).
Fail
✓
R1.4
No contradictory rules
No wildcard-vs-specific contradictions detected.
View in methodology
Pass
✓
R1.5
No accidental site-wide block
No site-wide wildcard block detected.
View in methodology
Pass
✓
R1.6
Crawl-delay reasonable
No Crawl-delay directives — crawlers use their own pacing (recommended).
View in methodology
Pass
✓
R1.7
Sitemap declared in robots.txt
1 Sitemap directive(s); first one (https://musicvideoai.pro/sitemap.xml) returned 200.
View in methodology
Pass
§02AI Semantic Files4 shown
✕
R2.1
/llms.txt exists
/llms.txt not found.
View in methodology
llmstxt.org is the most quickly-converging AI semantic file proposal. Publishing one is a clear signal of AI-readiness.
Fail
·
R2.2
llms.txt format compliant
No /llms.txt — see R2.1.
View in methodology
Skipped
·
R2.3
/llms-full.txt exists (bonus)
/llms-full.txt not found. This is a bonus file for large content sites; small sites do not need it.
View in methodology
Skipped
✕
R2.4
/skill.md exists
No /skill.md found.
View in methodology
skill.md (agentskills.io) describes what AI agents can do with your product. New standard in 2026, low adoption — adding one is a differentiator.
Fail
§03Agent Readiness6 shown
✓
R3.1
No bot-fight challenge on initial fetch
Clean response on first fetch — no anti-bot challenge markers in headers or body. ProtalBot reached your origin without mitigation. (HTTP 200)
View in methodology
Pass
·
R3.2
Forms have non-JS submission paths
No <form> elements on this page — nothing to evaluate.
View in methodology
Skipped
✓
R3.3
Clickable elements use real <button> and <a> tags
100% of clickable elements use real <button> or <a href> tags (62 of 62). Agents can identify them directly.
View in methodology
Pass
✓
R3.4
Interactive controls have accessible names
100% of interactive controls have accessible names (62 of 62). Agents can identify what each action will do.
View in methodology
Pass
✕
R3.5
.well-known/mcp.json exists
No /.well-known/mcp.json or /.well-known/mcp/server.json found.
View in methodology
MCP is the cleanest protocol for agents to act on your site directly. Without a discovery file, agent runtimes (Claude Desktop, Cursor, ChatGPT) can't find your MCP server in one fetch.
Hosted MCP Coming Soon
Fail
·
R3.6
MCP endpoint reachable
No MCP endpoint declared — see R3.5.
View in methodology
Hosted MCP Coming Soon
Skipped
§04Schema.org Structured Data8 shown
✕
R4.1
At least one JSON-LD block
No <script type="application/ld+json"> found.
View in methodology
JSON-LD is the most reliable signal for AI to understand page intent.
Fail
·
R4.2
@type values are valid Schema.org
No JSON-LD — see R4.1.
View in methodology
Skipped
·
R4.3
Organization schema on homepage
No JSON-LD — see R4.1.
View in methodology
Skipped
·
R4.4
Page-type schema matches inferred page type
Homepage — Organization schema check is R4.3.
View in methodology
Skipped
·
R4.5
Schema required fields complete
No JSON-LD — see R4.1.
View in methodology
Skipped
·
R4.6
Schema content consistent with visible content
No JSON-LD — see R4.1.
View in methodology
Skipped
·
R4.7
FAQPage schema when applicable
Page does not appear to have Q&A structure.
View in methodology
Skipped
✓
R4.8
Multiple JSON-LD blocks don't conflict
≤1 JSON-LD block — no conflict possible.
View in methodology
Pass
§05Metadata6 shown
✓
R5.1
<title> length is reasonable
<title> is 55 chars: "AI Music Video Generator for Musicians | Music Video AI".
View in methodology
Pass
✓
R5.2
<meta description> describes this page
Meta description is 153 chars: "Music Video AI is an AI music video generator for musicians. Upload a song, describe the mood, gener…"
View in methodology
Pass
!
R5.3
Open Graph required tags
4 of 5 required OG tags present: og:title, og:description, og:type, og:url.
View in methodology
Missing: og:image.
Warn
·
R5.4
og:image is valid
No og:image declared — see R5.3.
View in methodology
Skipped
✓
R5.5
Canonical URL
Canonical points to current page: https://musicvideoai.pro
View in methodology
Pass
✓
R5.6
Page language declared via <html lang>
<html lang="en">.
View in methodology
Pass
§06HTML Semantics6 shown
✓
R6.1
Exactly one <h1>
Single <h1>: "AI Music Video Generatorfor Musicians".
View in methodology
Pass
✓
R6.2
Heading hierarchy doesn't skip levels
42 headings, no level skips.
View in methodology
Pass
✕
R6.3
Primary content marked with <main>
No <main> tag or single <article>.
View in methodology
AI crawlers can't reliably distinguish primary content from navigation/ads/footer.
Fail
✓
R6.4
Page uses multiple semantic HTML tags
4 semantic HTML tag types in use: nav, header, footer, section.
View in methodology
Pass
✓
R6.5
Image alt coverage
80/80 (100%) <img> elements have an alt attribute.
View in methodology
Pass
✓
R6.6
Link text descriptiveness
0/27 sampled links (0%) use non-informative text ("click here", "read more", etc.).
View in methodology
Pass
§07Rendering4 shown
✓
R7.1
Page title in initial HTML
Title "AI Music Video Generator for Musicians | Music Video AI" present in initial HTML.
View in methodology
Pass
✓
R7.2
Meta description in initial HTML
Meta description present in initial HTML.
View in methodology
Pass
·
R7.3
Main content text in initial HTML
Rendering check skipped — Playwright failed to launch in this environment.
View in methodology
Skipped
·
R7.4
JSON-LD in initial HTML
Rendering check skipped — Playwright failed to launch in this environment.
View in methodology
Skipped
§08Performance5 shown
!
R8.1
TTFB (Time to First Byte)
TTFB 634ms — slow. AI crawlers usually allocate seconds-budget per site; this eats into content-fetch time.
View in methodology
Measured from a single origin; geographic latency may differ for your users.
Warn
✓
R8.2
Response compression enabled
Content-Encoding: br.
View in methodology
Pass
✓
R8.3
Modern HTTP version (HTTP/2 or HTTP/3, not HTTP/1.1)
Server advertises HTTP/3 via Alt-Svc.
View in methodology
Pass
✕
R8.4
Cache-Control allows caching
Cache-Control: no-store, must-revalidate — no-store forces every crawler hit to fully refetch, wasting their budget.
View in methodology
Fail
✓
R8.5
Initial HTML size
Initial HTML 304KB — well within budget.
View in methodology
Pass
§09Discoverability5 shown
✓
R9.1
sitemap valid + non-empty
https://musicvideoai.pro/sitemap.xml: 12 URLs — valid and non-empty. Looks complete for a small site; if you have more public pages, make sure they're all listed.
View in methodology
Pass
✓
R9.2
Sitemap URLs reachable (sampled)
10/10 sampled sitemap URLs returned 2xx/3xx (100%).
View in methodology
Pass
·
R9.3
RSS/Atom feed (content sites)
Page does not appear to be a content site — feed not expected.
View in methodology
Skipped
✕
R9.4
HTTPS forced + HSTS
http:// version is reachable without redirecting to https://.
View in methodology
Configure your CDN or web server to 301 all http→https traffic.
Fail
!
R9.5
www / non-www consolidated
Both www and non-www variants of musicvideoai.pro return 200 with different canonical hosts.
View in methodology
AI/search engines may treat them as separate sites — page rank and citations get split.
Pick one canonical host and 301 the other.
Warn
Measured from us-east-1 (Virginia)