ShipReady
LiveFree SEO and AEO scanner for AI-generated websites
Built by Caden Sorenson · Launched April 2026
What is ShipReady?
ShipReady is a free SEO and AEO (Answer Engine Optimization) scanner built for websites created with AI coding tools like Claude Code, Cursor, and v0. It audits your deployed site across seven categories, scores each one with a letter grade, and generates a copy-paste prompt you can feed right back into your AI tool to fix every issue.
How It Works
- Enter a URL - Paste any live website URL
- ShipReady scans it - Fetches the page, follows redirects, grabs robots.txt, sitemap, and llms.txt in parallel
- 35+ checks run - Across Meta & Head, Discoverability, On-Page Structure, Social Sharing, Performance, Structured Data, and AEO
- Get your grade - Overall score (A-F) with per-category breakdowns and pass/warn/fail for each check
- Copy the fix prompt - A single markdown prompt with every issue, code snippets, and guidelines ready for your AI coding tool
Seven Audit Categories
- Meta & Head (23%) - Title, description, charset, viewport, canonical, favicon
- Discoverability (19%) - HTTPS, robots.txt, sitemap, noindex, client-side rendering detection
- On-Page Structure (19%) - Heading hierarchy, image alt text, internal links, content depth
- Social Sharing (14%) - Open Graph tags, Twitter Cards, image dimensions
- Performance (9%) - Render-blocking scripts, text compression, modern image formats
- Structured Data (8%) - JSON-LD validation, schema type detection and suggestions
- Answer Engine Optimization (8%) - AI crawler access, llms.txt, question headings, speakable schema, FAQ/HowTo markup
Why AEO Matters
Traditional SEO tools don’t check if ChatGPT, Perplexity, or Claude can find your content. ShipReady scans your robots.txt for blocked AI crawlers (GPTBot, ClaudeBot, PerplexityBot, and more), checks for llms.txt, looks for question-style headings that answer engines can extract, and verifies you have enough content depth to get cited as a source.
Tech Stack
- Astro 5 with SSR for the scanning API endpoint
- Cloudflare Workers for edge deployment with global low latency
- Cloudflare KV for IP-based rate limiting (10 scans/hour)
- Custom regex HTML parser optimized for Workers’ memory constraints
- TypeScript end to end
Build log: how I built ShipReady. Related: best SEO checker tools for developers.
Frequently asked questions
Is ShipReady free to use?
What does ShipReady check that traditional SEO tools don't?
Which sites is ShipReady built for?
How many checks does it run, and across what categories?
Do I need to install anything?
More about ShipReady
- Behind the build I Built an SEO Scanner That Actually Checks if AI Can Find You Lighthouse doesn't check if ChatGPT can crawl your site. So I built ShipReady, an SEO and AEO scanner that audits your site for the age of answer engines.
- From the blog Building Travel Vient: The Real Work Was Not Trusting Claude How I built travelvient.com, a travel site with data on 80 airlines, by letting Claude generate under skills I wrote and catching it when it makes a fact up.
- From the blog Building the Carry-On and Personal Item Size Checkers Two free tools that tell you whether your bag fits a given airline, built on a cited dataset of 50 carriers sourced from official policy pages.
- From the blog How to check if ChatGPT recommends your business How to check whether ChatGPT, Perplexity, and Google AI Overviews name your local business: copy-ready prompts, repeat runs, and a monthly tracking table.
Related projects
- Related project Cub River Kratom A web design case study: a custom Astro 5 site for a Cache Valley retail client, with one business-data file, local and FAQ schema, and nearby-city pages.
- Related project Diamond Pest Pro A web design case study: a custom Astro 5 site for a multi-location Carolinas home-service client, with a page per branch and service plus LocalBusiness schema.
- Related project Dill the Menace A web design case study: a custom Astro 5 site for a Cache Valley client, with one source of truth for business data, local and FAQ schema, and a static deploy.