siteanalyzerfree.com
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
siteanalyzerfree.com
Preparing the stored Is Agentic score
siteanalyzerfree.com
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Strong
Weighted across 16 applicable checks
Ready with gaps
Weighted across 12 applicable checks
Strong
Weighted across 3 applicable checks
Strong
Weighted across 1 applicable check
Critical access gaps come first, followed by other applicable readiness gaps.
Make pricing discoverable - add a /pricing page or include pricing as schema.org/Offer structured data, so agents can find it without scraping a marketing page.
Publish API documentation at a discoverable URL (/docs, /api, /developers). Include authentication, endpoints, and example requests.
Document your error responses in your OpenAPI spec: give 4xx and 5xx responses a typed error schema (or use RFC 9457 application/problem+json). A consistent error object with a machine-readable code and a human-readable message lets agents handle failures without guessing.
Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
Declare a versioning policy agents can rely on: version your API (in the URL path or a version header) and publish how you signal deprecation (a Sunset/Deprecation header or a documented timeline). Agents avoid integrating against a surface that can change without warning.
Checks are grouped by relevance for App sites.
1059 chars, semantic headings (1 H1 + 1 H2s), 6.6% content ratio
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh stubs, JavaScript-redirect stubs, or cross-domain hops across 1 checked page
OpenAPI spec found at https://siteanalyzerfree.com/openapi.json (version: 3.0.3)
Canonical URL serves text/markdown and text/html via Accept negotiation with Vary: Accept
OpenID Connect discovery endpoint found at https://siteanalyzerfree.com
OAuth security scheme "OAuth2" declares 9 named scope(s) in the OpenAPI spec (e.g. read:checkup, write:checkup, read:audit)
API returns JSON error responses (404 at https://siteanalyzerfree.com/api/v1/orank-probe-test)
Nonexistent paths return HTTP 404 with markdown guidance for agents - the strongest 404 contract
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://siteanalyzerfree.com/sitemap.xml with 173 entries
JSON-LD Organization found - missing description on this entity
How to pass
Add description to the Organization JSON-LD entity for full score.
No pricing page or pricing data found
How to pass
Make pricing discoverable - add a /pricing page or include pricing as schema.org/Offer structured data, so agents can find it without scraping a marketing page.
Documentation found at /api but not linked from homepage
How to pass
Publish API documentation at a discoverable URL (/docs, /api, /developers). Include authentication, endpoints, and example requests.
All metadata signals present: canonical URL, lang="en", og:image, og:type
Organization schema found but missing: address
How to pass
Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
All trust anchor pages verified: About, Contact, Privacy
All 1 measured page fit an agent context budget (largest ~1K tokens)
Documented REST API detected; endpoints require authentication (API key / OAuth), which is expected for agent access. Best-of-protocols score: 7/7.
Low friction onboarding verified live: sandbox/test environment, zero-friction self-serve registration at /register
MCP server connected via Streamable HTTP - site-analyzer-mcp v1.0.0 (protocol 2024-11-05)
The live API operation https://siteanalyzerfree.com/api/v1/agent/balance.php returns IETF RateLimit headers: ratelimit-limit, ratelimit-policy, ratelimit-remaining.
Partial typed error model: error schema defined but not consistently referenced (or vice versa)
How to pass
Document your error responses in your OpenAPI spec: give 4xx and 5xx responses a typed error schema (or use RFC 9457 application/problem+json). A consistent error object with a machine-readable code and a human-readable message lets agents handle failures without guessing.
API versioning found (URL versioning (servers or paths)) but no deprecation or sunset policy detected - add Sunset/Deprecation headers or a deprecation policy page
How to pass
Declare a versioning policy agents can rely on: version your API (in the URL path or a version header) and publish how you signal deprecation (a Sunset/Deprecation header or a documented timeline). Agents avoid integrating against a surface that can change without warning.
CLI tool mentioned in llms.txt
How to pass
Publish an official CLI tool on npm, PyPI, or Homebrew. A CLI lets agents and developers script interactions with your product without building API integrations from scratch.
100% of operations define typed response schemas, 100% use application/json
REST: agent-friendly schema (11 operations, 100% with operationIds, 100% documented by description or summary)
Compatible: 11/11 ops with IDs, 10/11 with typed schemas
Name search surfaced no pages on siteanalyzerfree.com, although developer resources exist on the site (API docs, OpenAPI spec, auth docs, MCP server) - weak search indexing or transient search noise
How to pass
Check whether your developer resources (API docs, OpenAPI spec, auth docs, developer portal, MCP server, SDK documentation) surface in name-based searches. If they do not, use predictable URLs, link them in llms.txt, and include your product name in page titles and headings. This result reflects one search sample.
Verified in Smithery as tony-abkt/siteanalyzerfree via entry-to-product
MCP server card served at https://siteanalyzerfree.com/api/v1/agent/mcp.php/server-card
Agent mode view found at ?mode=agent (6 signals: llms.txt, openapi, mcp, api, endpoint, agent)
How to pass
Add a ?mode=agent query parameter to your homepage that returns a structured, machine-readable view with API endpoints, authentication info, and key capabilities instead of marketing HTML.
100% of 173 sampled sitemap entries carry lastmod; newest is 1 day(s) old
Found the llms.txt at https://siteanalyzerfree.com/llms.txt.
The llms.txt starts with a heading and has 84 lines, but it contains no markdown links.
How to pass
Format your llms.txt as a navigation index: start with a markdown heading, include markdown links to deeper resources, and keep it under 30,000 characters. If you have more to say, move long-form content into /llms-full.txt or per-section files (e.g. /docs/llms.txt, /api/llms.txt) and link to them from the main index.
When-to-use guidance found in llms.txt
Code fences balanced across 1 markdown document
Developer portal found at /dashboard
Returns markdown when requested via Accept header
All 19 tools on other MCP have detailed descriptions (>= 20 chars)
18/19 tools on other MCP have parameter schemas, 18 with required fields
other MCP exposes 19 tools - substantial tool surface
All 19 tool names follow consistent convention, descriptive, and non-generic
RFC 9728 metadata: resource=https://siteanalyzerfree.com, authorization_servers (1), scopes_supported (11), bearer_methods_supported
PRM + AS metadata both present but AS metadata has no agent_auth block
How to pass
Publish RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource on your resource server (the host that actually serves the API, e.g. api.<apex>) with resource and authorization_servers. Publish RFC 8414 authorization-server metadata at /.well-known/oauth-authorization-server on the AS origin, and include the WorkOS auth.md agent_auth block with identity_endpoint, identity_types_supported drawn from the spec enum (anonymous, identity_assertion, service_auth - the assertion variant, the ID-JAG URN urn:ietf:params:oauth:token-type:id-jag, belongs inside identity_assertion.assertion_types_supported, not at the top level), and the identity_assertion.assertion_types_supported block when you advertise that type, so agents can check their assertion shape is accepted before minting. Cross-link by listing the AS origin in PRM authorization_servers, and point agent_auth.skill back at your published /auth.md. Spec: https://github.com/workos/auth.md.
other MCP returns structured JSON-RPC errors with code and message
other MCP uses modern Streamable HTTP transport
MCP server card found at https://siteanalyzerfree.com/api/v1/agent/mcp.php/server-card but missing fields: name, description, version
How to pass
Publish a server card for each MCP server (draft MCP server-card extension). List each card in /.well-known/ai-catalog.json, or serve it at <server URL>/server-card. /.well-known/mcp/server-card.json is still read for a site with one server, but the extension does not recommend it. Include name, description, and version, and put the server's exact address in remotes[].url (serverUrl is also read) so agents match each card to the right server before connecting. Follow the extension schema for full credit: $schema set to https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json, a reverse-DNS name such as com.example/mcp, and no tools[] (agents always trust the live tools/list). Keep the description to 100 characters or fewer, as the schema requires. A card without that $schema is still read, and then an optional tools[] list completes it.
93 native controls, 0 non-native div-soup affordances (100% native).
93/93 interactive elements have a computable accessible name (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does siteanalyzerfree.com do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does siteanalyzerfree.com do and who is it for? Explain it back to me.
3 steps1 reasoning step
The agent gathered a partial but useful overview of SiteAnalyzerFree from the homepage alone, covering what it does, pricing, and stated differentiators. The site exposed its core value proposition but lacked detail on the 201-point methodology, missing pricing pages (404 error), and comparisons to competitors, forcing the agent to flag significant gaps in answering the 'how it's different' part of the task.