About Crawl Readiness

Who's behind it

Crawl Readiness is built and operated by Tundrastone, an Ontario, Canada business. The founder is Jay Michael, a solo builder. This is a one-person shop — no venture capital, no offshore team. What you see is what's shipped.

• Legal entity: Tundrastone (Ontario, Canada)
• Founder: Jay Michael
• Jurisdiction: Governing law is Ontario, Canada
• Public identity: github.com/Grubbomatic

What we do

The Crawl Readiness suite covers three things:

• Audit: The free AI readiness check and tool suite (llms.txt, schema, robots.txt validators and generators) score your site against 50+ AI crawlers.
• Monitor: The LLM Monitor queries real AI providers (ChatGPT, Claude, Perplexity, Google AI Overviews) with real customer prompts and tracks whether they actually mention your brand — daily.
• Distribute: The same tools are available through our MCP server (Claude Desktop, Cursor, Cline, Windsurf) and our Chrome extension.

For the exact scoring model and per-check weights, see the methodology page.

How we handle your data

When you run a check we store the URL, the resulting score, and the per-check results. We do NOT store full page HTML — only extracted signals (robots.txt directives, meta tags, structured-data blocks). For paid Monitor projects we also store your prompts and the AI provider responses.

• Hosted on: Vercel (application) + Supabase (Postgres database and authentication)
• Anonymous checks: retained indefinitely as public report cards (the /report/[id] URL is shareable)
• Signed-in check history: stored in your account, deletable from your dashboard
• Monitor query results: retained per your subscription; deleted 30 days after account cancellation
• Row-level security (RLS): enforced on all user-scoped tables in Supabase — you can only read your own rows
• SSRF protection: every URL you submit is DNS-resolved and rejected if it points to a private IP or non-http(s) scheme

Full details in the privacy policy.

Security & incident reporting

If you find a security issue — an auth bypass, an information leak, an SSRF gap, anything that could put user data at risk — please email crawlreadiness@gmail.com with "security" in the subject line. We aim to acknowledge within 48 hours.

No bug bounty program yet — we're small. But we take reports seriously and credit responsible disclosure when the reporter wants it.

Reaching us

• General support: crawlreadiness@gmail.com
• Bug reports: GitHub Issues (for the MCP server) or email for everything else
• Refunds & billing: email within 14 days of a charge; handled case-by-case
• Report a domain that shouldn't be on the public leaderboard: email with the report URL; we remove within 5 business days if you own the domain