Six free tools.
Built for the way AI reads your brand.
Generative AI doesn't crawl your site the way Google does. It reads the metadata you wrote, the schemas you embedded, the plain-text files you forgot to publish. These tools help you fix that — one artifact at a time.
AI Readiness Scan
Submit your domain. We query three frontier models — ChatGPT, Gemini, Perplexity — and grade what they say back. You get a composite readiness score, an SEO-for-AI checklist, an AI Overview check, and quick-win code in roughly ninety seconds.
llms.txt Generator
Compose the manifest file that frontier models look for. Brand description, canonical sources, key facts — formatted to spec and ready to drop at your site root.
JSON-LD Generator
Generate Organization, Product, and FAQ schema with the fields Google Rich Results actually validates. Output is schema.org-compliant and copy-paste ready.
Schema Validator
Paste a URL. We fetch it, parse every structured data block, and tell you what an AI agent actually sees — including the silent failures Google's tool misses.
Ask the Models
Paste a prompt and a brand name. We grade clarity, brand accuracy, and specificity across three models and tell you exactly what to rewrite.
SEO for AI Checklist
Twenty-seven things AI looks at on your site, organized by category. Each item explains why it matters, what to ship, and how to verify it landed.
Scan. Generate. Validate.
Most teams run them in order. The scan tells you what's broken. The generators ship the fix. The validator confirms it landed before you commit.
Scan first.
Drop your domain into the AI Readiness Scan. It reads your robots.txt, checks for llms.txt and JSON-LD, queries three frontier models, and flags every gap. Treat the output as a punch list, not a verdict.
Run the scan →Generate the missing artifacts.
The scan tells you which files you're missing. The llms.txt and JSON-LD generators write them. The prompt grader rewrites your own outreach copy so it reads cleanly to models. Ship the diff.
Open the generators →Validate before you commit.
Run the Schema Validator on a staging URL before merging. The checklist gives you the long-form why behind each item. The loop closes — until the next model release rewrites the rules.
Open the validator →