designmd.co

✓ verified

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

Site type: Not sure

Content access

Can AI read it?

Could not verify

Issues: 0 · could not verify: 24 · passed: 4 · not applicable: 0

Content discovery

Can AI find it?

Could not verify

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

Task use

Can AI act on it?

Could not verify

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

The site links to only 0 other pages that could be sampled.

Issues to fix0

No issues were found.

Suggestions1

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

  • Provides a robots.txt file that permits access for legitimate crawlers and agent systems where appropriate.

    No robots.txt: nothing restricts crawlers. Publishing one lets you state an AI policy.

Could not be verified (52)

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

Request failed 52

A timeout, connection problem or HTTP error got in the way. Re-checking often resolves these.

  • no_captcha Public content is accessible without CAPTCHA or other anti-bot challenges that block legitimate automated access. / — The page answered HTTP 429, so its content could not be checked.
  • page_status The page responds normally (status, redirects, content) / — The page answered HTTP 429, so its content could not be checked.
  • ssr_content Core content is present in the initial HTML response, rather than relying entirely on client-side JavaScript rendering. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_no_soft_paywall Core content isn't blocked by login walls, membership gates, or paywalls. / — The page answered HTTP 429, so its content could not be checked. (/)
  • schema_org Provides JSON-LD structured data based on Schema.org to make entities and page meaning more explicit. / — The page answered HTTP 429, so its content could not be checked. (/)
  • text_content Ensures primary content is available as text, rather than being locked inside images, videos, or non-parsable PDFs. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_content_length The page has meaningful text content, not just a few sentences of boilerplate. / — The page answered HTTP 429, so its content could not be checked. (/)
  • sitemap Publishes a valid XML sitemap to help agents and crawlers discover indexable pages efficiently. the whole site — no sitemap at the conventional locations or in robots.txt (could not fetch: http_429) (/sitemap.xml, /sitemap_index.xml)
  • v_canonical_self_ref The canonical tag points to the current page's standard address, avoiding duplicate page confusion. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_canonical_url A canonical URL tells search engines and AI which version of the URL is authoritative. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_clean_urls Page URLs clearly reflect the content topic, rather than being cryptic parameter strings. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_internal_linking Key content pages are easily reachable from the homepage and main pages. the whole site — The page answered HTTP 429, so its content could not be checked. (/)
  • documentation Provides comprehensive documentation in a format that is easy for machines and agents to parse and use. the whole site — no documentation page found from the page's links or the conventional paths (could not fetch: http_429) (/, /docs, /documentation, /developers)
  • json_responses Returns JSON payloads with stable and predictable schemas across endpoints. the whole site — no public API response was available to inspect (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)
  • mcp_server Provides an MCP (Model Context Protocol) server so agents can access tools, resources, and actions through a standardized interface. the whole site — no MCP endpoint found at the conventional location or in a server card (could not fetch: http_429) (/.well-known/mcp.json, /.well-known/mcp/server-card.json, /mcp)
  • openapi_spec Publishes an OpenAPI or Swagger specification so agents can understand available API endpoints programmatically. the whole site — no OpenAPI description found in page links, /.well-known/api-catalog or the conventional locations (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)
  • search_filter_api Supports query parameters for search, filtering, pagination, and retrieval refinement. the whole site — no API description to read query parameters from (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)
  • structured_api Exposes a well-defined REST or GraphQL API for programmatic access to data and actions. the whole site — no API found through an OpenAPI description or at /api, /api/v1 (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)
  • meta_tags Includes essential metadata such as page title, description, and social sharing tags to improve machine interpretation. / — The page answered HTTP 429, so its content could not be checked. (/)
  • semantic_html Uses semantic HTML elements such as header, nav, main, article, section, and footer so agents can better understand page structure. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_author_attribution Pages attribute content to an author, team, or organization. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_breadcrumb_schema Helps AI understand the page's position and hierarchy within the site. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_contact_visible Both users and AI can easily find your contact or about page. the whole site — no contact or about page found from the page's links or the conventional paths (could not fetch: http_429) (/, /about, /contact)
  • v_faq_schema Page content is structured for AI to directly extract answers. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_heading_structure The page has a clear H1 and uses H2/H3 headings to organize content logically. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_lang_declared The HTML lang attribute is set, helping AI identify the page language. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_meta_title_desc The page has a clear title and meta description, helping AI quickly identify the topic. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_multilingual Multilingual pages have clear corresponding relationships, such as hreflang tags. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_og_tags Open Graph tags provide supplementary title and summary information. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_org_schema Structured data includes basic info like company/organization name, website, and logo. the whole site — The page answered HTTP 429, so its content could not be checked. (/)
  • v_privacy_terms The site has essential pages like privacy policy and terms of service. the whole site — no privacy policy or terms of service found (could not fetch: http_429) (/, /privacy, /privacy-policy, /terms)
  • v_publish_dates Pages include publish or update dates, helping assess content freshness. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_review_schema Products, services, or content include structured Review/Rating data. / — The page answered HTTP 429, so its content could not be checked. (/)
  • v_security_headers Basic security response headers are set, reflecting site maintenance quality. the whole site — The page answered HTTP 429, so its content could not be checked. (/)
  • v_structured_content_blocks Pages contain FAQs, tables, lists, definitions, etc., making it easy for AI to extract and summarize. / — The page answered HTTP 429, so its content could not be checked. (/)
  • indexing_policy Indexing and snippet policy of the page / — The page answered HTTP 429, so its content could not be checked. (/)
  • llms_txt Exposes a /llms.txt file that gives LLM-based systems guidance on important content and site structure. the whole site — no llms.txt published (it is optional) (could not fetch: http_429) (/llms.txt)
  • v_sitemap_freshness The sitemap includes recent pages and isn't neglected over time. the whole site — no sitemap to read dates from (could not fetch: http_429) (/sitemap.xml, /sitemap_index.xml)
  • a2a_agent_card Provides an agent descriptor, such as an A2A agent card at /.well-known/agent.json, to advertise agent capabilities. the whole site — no A2A Agent Card published at /.well-known/agent-card.json (or the older agent.json) (could not fetch: http_429) (/.well-known/agent-card.json, /.well-known/agent.json)
  • agent_auth Supports automation-ready authentication methods such as API keys or OAuth client credentials flows. the whole site — no API or OAuth metadata found (could not fetch: http_429) (/.well-known/oauth-protected-resource, /.well-known/oauth-authorization-server, /.well-known/openid-configuration, /)
  • agent_negotiation Supports agent-to-agent capability discovery or negotiation so systems can adapt to each other dynamically. the whole site — no A2A Agent Card published, so no agent capability negotiation is offered (could not fetch: http_429) (/.well-known/agent-card.json, /.well-known/agent.json)
  • cross_service_handoff Supports handoff between agents or services so tasks can continue across system boundaries. the whole site — no API description to read handoff or integration operations from (could not fetch: http_429) (/.well-known/agent-card.json, /.well-known/agent.json, /.well-known/mcp.json, /.well-known/mcp/server-card.json)
  • event_streaming Supports real-time update channels such as SSE or WebSockets for low-latency agent workflows. the whole site — no API description and no streaming code in the page's inline scripts (bundled scripts were not inspected) (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)
  • idempotency Write operations support idempotency keys or equivalent safeguards to prevent duplicate execution. the whole site — no API description to read idempotency support from (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)
  • proactive_notifications Can proactively notify agents when relevant content, state, or business events change. the whole site — no API description to read notification or alert operations from (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)
  • rate_limits_documented Clearly documents rate limits and returns proper 429 Too Many Requests responses when limits are exceeded. the whole site — no API found to inspect (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)
  • structured_errors Returns machine-readable error responses with clear codes, messages, and actionable context. the whole site — no API found to inspect (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)
  • subscription_api Provides APIs for subscription, lifecycle management, or registration of agent integrations. the whole site — no API description to read subscription or registration operations from (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)
  • webhooks Supports webhooks so agents can receive event-driven updates instead of relying only on polling. the whole site — no API description to read webhooks from (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)
  • webmcp Supports WebMCP or comparable browser-oriented agent interaction patterns for web-based automation. the whole site — The page answered HTTP 429, so its content could not be checked. (/)
  • workflow_orchestration Supports multi-step workflows, task coordination, and stateful execution across actions or services. the whole site — no API description to read workflow, job or task operations from (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)
  • write_api Supports write operations such as POST, PUT, PATCH, and DELETE, enabling agents to create and update resources. the whole site — no API description or Allow header to show write operations (the scanner does not send writes) (could not fetch: http_429) (/, /.well-known/api-catalog, /openapi.json, /openapi.yaml)

How are checks judged?