suno.com

✓ verified

Checked on 2026-10-29 Checked 6 of up to 6 pages standard 2.0

Site type: Not sure

Content access

Can AI read it?

Issues found

Issues: 5 · could not verify: 0 · passed: 20 · not applicable: 3

Content discovery

Can AI find it?

Issues found

Issues: 1 · could not verify: 0 · passed: 7 · not applicable: 1

Task use

Can AI act on it?

Could not verify

Issues: 0 · could not verify: 17 · passed: 1 · not applicable: 2

Issues to fix6

Improvement No JSON-LD or microdata found. Content access
Where
/pricing, /about, /v6
Impact
AI crawlers and assistants may be unable to read or trust this content.
Evidence
no JSON-LD or microdata found
How to fix
Add JSON-LD (`<script type="application/ld+json">`) describing the page, such as WebSite, Organization or Article.

schema_org / v_schema_org

Improvement The page is mostly images or video with little text. Content access
Where
/v6
Impact
AI crawlers and assistants may be unable to read or trust this content.
Evidence
media-heavy page: 33 media elements for 323 word-equivalents of text
How to fix
Add text that describes or accompanies the images and videos: headings, captions and a written summary.

text_content

Improvement The canonical URL points to a different page than this one. Content discovery
Where
/home
Impact
Pages may be missed, indexed under the wrong address, or never surface in AI answers.
Evidence
canonical points to a different page: https://suno.com/
How to fix
Make the canonical point to this page, unless this page is deliberately a duplicate of another.

v_canonical_self_ref

Best practice Uses semantic HTML elements such as header, nav, main, article, section, and footer so agents can better understand page structure. Content access
Where
/pricing
Impact
A best practice, not a barrier: AI can still read the site, but this helps it understand and cite it more accurately.
Evidence
only 0 semantic elements found (need 3):
How to fix
Use semantic elements such as header, nav, main, article, section and footer instead of generic divs.

semantic_html

Best practice The page has FAQ-style content but no FAQPage markup. Content access
Where
/pricing, /v6
Impact
A best practice, not a barrier: AI can still read the site, but this helps it understand and cite it more accurately.
Evidence
the page has FAQ-style content (11 question headings) but no FAQPage markup
How to fix
Mark up the questions and answers with FAQPage JSON-LD that matches the visible text.

v_faq_schema

Best practice Pages contain FAQs, tables, lists, definitions, etc., making it easy for AI to extract and summarize. Content access
Where
/home, /pricing, /about
Impact
A best practice, not a barrier: AI can still read the site, but this helps it understand and cite it more accurately.
Evidence
1 structured block type(s) found (need 2+): lists with 3+ items (6)
How to fix
Use lists, tables with headers, definition lists or Q&A blocks so key facts are easy to extract.

v_structured_content_blocks

Suggestions1

These checks passed. The notes below would make them stronger.

  • Exposes a /llms.txt file that gives LLM-based systems guidance on important content and site structure.

    Valid. The pages are listed as bare URLs; the documented format is Markdown links, `[name](url): note`, which tools can read more reliably.

Could not be verified (17)

These are not counted as problems: the scanner could not complete them.

Not discovered 17

Nothing was found at the standard locations or in the page's links. That does not prove it is absent.

  • json_responses Returns JSON payloads with stable and predictable schemas across endpoints. the whole site
  • mcp_server Provides an MCP (Model Context Protocol) server so agents can access tools, resources, and actions through a standardized interface. the whole site
  • openapi_spec Publishes an OpenAPI or Swagger specification so agents can understand available API endpoints programmatically. the whole site
  • search_filter_api Supports query parameters for search, filtering, pagination, and retrieval refinement. the whole site
  • structured_api Exposes a well-defined REST or GraphQL API for programmatic access to data and actions. the whole site
  • agent_auth Supports automation-ready authentication methods such as API keys or OAuth client credentials flows. the whole site
  • cross_service_handoff Supports handoff between agents or services so tasks can continue across system boundaries. the whole site
  • event_streaming Supports real-time update channels such as SSE or WebSockets for low-latency agent workflows. the whole site
  • idempotency Write operations support idempotency keys or equivalent safeguards to prevent duplicate execution. the whole site
  • proactive_notifications Can proactively notify agents when relevant content, state, or business events change. the whole site
  • rate_limits_documented Clearly documents rate limits and returns proper 429 Too Many Requests responses when limits are exceeded. the whole site
  • structured_errors Returns machine-readable error responses with clear codes, messages, and actionable context. the whole site
  • subscription_api Provides APIs for subscription, lifecycle management, or registration of agent integrations. the whole site
  • webhooks Supports webhooks so agents can receive event-driven updates instead of relying only on polling. the whole site
  • webmcp Supports WebMCP or comparable browser-oriented agent interaction patterns for web-based automation. the whole site — No WebMCP tool registration was found in the page or its same-site scripts. Tools registered at runtime or in other scripts can only be seen by running the page.
  • workflow_orchestration Supports multi-step workflows, task coordination, and stateful execution across actions or services. the whole site
  • write_api Supports write operations such as POST, PUT, PATCH, and DELETE, enabling agents to create and update resources. the whole site

How are checks judged?