# Agent-readiness remediation brief

Site: https://storeseo.com/
Platform: astro (99% confidence)
AIScan score: 94/100 — Level 5 (Agent-Native)
Rubric: v2026.08.2

## Failing checks (sorted by weight)
- **[M4] Machine-readable pricing** — PARTIAL
  - Evidence: JSON-LD offer on homepage (price, priceCurrency, price 0 only — paid plans not described): {"@context":"https://schema.org","@type":"SoftwareApplication","name":"StoreSEO","applicationCategory":"BusinessApplication","operatingSystem":"Web, Shopify","url":"https://storese
  - Fix: Publish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.
- **[E4] HTTPS & canonical host** — PARTIAL
  - Evidence: final origin https://storeseo.com · http:// upgrades to https · www.storeseo.com serves its own copy (duplicate origin) · no HSTS header
  - Fix: Serve the site over HTTPS, 301-redirect http:// to https://, and redirect the www/apex variant to a single canonical host so agents don't index two copies of every URL.

## General guidance
- Static-first: `robots.txt`, `llms.txt`, `/.well-known/*` JSON cards.
- Markdown negotiation: serve `text/markdown` when requested via `Accept` header or `?format=md`.
- Bot access: explicit allow/deny per AI user-agent (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Bytespider, Amazonbot, CCBot, meta-externalagent, cohere-ai, Diffbot).
- Capabilities: publish an MCP server card and (optionally) an Agent Skills manifest even if the runtime isn't live — discovery first.
- Re-scan at aiscan.site after deploying.