# AnswerReady — full machine-readable guide

Scan any public website against an evidence-backed AEO, GEO, and SEO rubric, then inspect every score contribution and validated PlatPhorm enrichment result.

Rubric version: 2026-07-11.1
Scoring: pass earns 100% of criterion weight, warn earns 50%, fail earns 0%.
Validity: every criterion requires at least one source-backed evidence record; scoreVerified confirms deterministic recomputation.

## Categories and criteria
### AI Discovery (20 points)
Public files and policies that let answer engines discover the site.
- llms.txt is available (6): A concise, root-level content map gives answer engines an explicit discovery surface.
- llms-full.txt is available (3): A bounded full-text companion gives agents richer context without scraping the entire site.
- AI crawler policy is explicit (5): Explicit crawler rules are more trustworthy than assuming access from an absent policy.
- MCP discovery manifest is valid (3): A valid MCP manifest advertises real, agent-operable capabilities.
- Agent policy is published (3): A machine-readable agent policy defines safe public and protected behavior.

### Crawlability (20 points)
Signals that let crawlers safely find, select, and index canonical pages.
- robots.txt is available (4): robots.txt is the baseline crawl-policy surface.
- XML sitemap is available (6): A valid sitemap provides bounded, explicit URL discovery.
- robots.txt references the sitemap (2): The reference joins crawl policy and URL discovery.
- Canonical URL is declared (4): Canonical selection reduces duplicate and conflicting source identities.
- Page is indexable (4): A page cannot be cited consistently if page-level policy blocks indexing.

### Structured Meaning (20 points)
Machine-readable semantics used for entities, previews, and API discovery.
- JSON-LD is syntactically valid (7): Valid JSON-LD is the strongest page-level machine-readable entity signal.
- JSON-LD identifies useful entity types (3): Typed entities are more useful than syntactically valid but untyped graphs.
- Open Graph metadata is complete (4): Stable title, description, image, and type metadata improve source previews.
- Social card metadata is available (2): A card declaration supports consistent previews across secondary discovery channels.
- Machine-readable API schema is available (4): OpenAPI or MCP discovery lets agents verify available operations instead of guessing.

### Answer Quality & Trust (25 points)
Content, attribution, and freshness signals that support defensible citations.
- Title is descriptive (4): A concise title establishes the page’s primary answer context.
- Description summarizes the page (4): A useful description provides a compact statement of intent and scope.
- A single primary heading is present (3): One clear H1 gives parsers a stable primary topic.
- Content has useful depth (4): Substantive visible text is more likely to contain answerable, citable detail.
- Content exposes answer structure (3): Question headings, lists, tables, and FAQ markup make answer units easier to extract.
- Authorship or publisher is attributable (3): Attribution supports provenance and confidence in a citation.
- Claims link to supporting sources (2): Outbound source links provide inspectable provenance for factual claims.
- Freshness is machine-readable (2): Published or modified dates help engines reason about time-sensitive claims.

### Reach & UX (15 points)
Syndication, locale, transport, mobile, and response-time readiness.
- Document language is declared (2): Language metadata improves parsing, accessibility, and locale selection.
- RSS or Atom feed is available (3): Feeds provide durable, incremental discovery for changing content.
- Mobile viewport is configured (2): Mobile usability affects both readers and mobile-first indexing.
- Primary HTML responds promptly (5): Fast server response improves crawl efficiency and user access.
- Final page uses HTTPS (3): Secure transport is a baseline trust and integrity requirement.

## Public routes
- https://answerready.platphormnews.com/api/health
- https://answerready.platphormnews.com/api/v1/health
- https://answerready.platphormnews.com/api/docs
- https://answerready.platphormnews.com/api/rubric
- https://answerready.platphormnews.com/api/mcp
- https://answerready.platphormnews.com/openapi.yaml
- https://answerready.platphormnews.com/openapi.json
- https://answerready.platphormnews.com/llms.txt
- https://answerready.platphormnews.com/llms-full.txt
- https://answerready.platphormnews.com/llms-index.json
- https://answerready.platphormnews.com/robots.txt
- https://answerready.platphormnews.com/sitemap.xml
- https://answerready.platphormnews.com/sitemap-index.xml
- https://answerready.platphormnews.com/rss.xml
- https://answerready.platphormnews.com/feed.xml
- https://answerready.platphormnews.com/atom.xml
- https://answerready.platphormnews.com/manifest.webmanifest
- https://answerready.platphormnews.com/.well-known/mcp.json
- https://answerready.platphormnews.com/.well-known/agents.json
- https://answerready.platphormnews.com/.well-known/security.txt
- https://answerready.platphormnews.com/.well-known/trust.json

## External evidence boundary
PlatPhorm Insights and SitemapOps inputs are schema-validated before sending. Returned JSON is size-bounded and schema-validated. Invalid, unexpected, oversized, or unavailable output is labeled degraded and never presented as verified evidence.