AI Search Readiness Checkby Agent1K

Free SEO audit checklist for a landing page (16 checks, incl. AI search)

The exact 16 checks our free tool runs, in priority order: what each one is, why it matters for Google and AI answers (ChatGPT, Perplexity, Claude), how to check it by hand, and the fix. Do it yourself, or let the free checker run all of them in seconds.

Run all 16 checks automatically

Free, no sign-up. Paste a URL; you get a score out of 100, the failing checks and copy-paste fixes.

Audit my page free →
AI search
  1. AI search bots allowed in robots.txt (weight 15)
    Why: Blocked crawlers can't read your page, so AI answers can't cite or link you.
    Check by hand: Open yourdomain.com/robots.txt. Look for Disallow: / under User-agent: * or under OAI-SearchBot, PerplexityBot, Claude-SearchBot.
    Fix: Allow the search/answer bots (OAI-SearchBot, ChatGPT-User, Claude-SearchBot, PerplexityBot); blocking training-only crawlers is your call.
  2. Copy is in the raw HTML (no JavaScript needed) (weight 15)
    Why: Most AI crawlers don't run JavaScript. A React/Vite shell looks empty to them.
    Check by hand: View source (Ctrl+U), not the inspector. If your headline and copy are not in that text, crawlers that skip JavaScript see an empty page.
    Fix: Server-render or pre-render the landing page (static export, SSR) so the copy is in the HTML.
  3. JSON-LD structured data (weight 10)
    Why: Structured data tells search and AI engines what the page is (product, organization, FAQ, price).
    Check by hand: View source and search for application/ld+json.
    Fix: Add a JSON-LD block: Organization + SoftwareApplication or Product (name, description, offers.price).
  4. /llms.txt exists (weight 5)
    Why: An emerging convention: a short Markdown map of your site for language models. Cheap to add.
    Check by hand: Open yourdomain.com/llms.txt. A 404 means you don't have one.
    Fix: Add /llms.txt: '# Product name', one-line summary, then links to your key pages.
Basics
  1. Page is indexable (no noindex) (weight 10)
    Why: noindex removes the page from search and most AI answers.
    Check by hand: Search the source for noindex, and check response headers for X-Robots-Tag.
    Fix: Remove noindex from the meta robots tag / X-Robots-Tag header (leftover from staging?).
  2. Meta description, 50-160 characters (weight 8)
    Why: It's the snippet search and AI tools quote when they describe you.
    Check by hand: View source and search for name="description"; count the characters.
    Fix: Write one sentence: what it is, for whom, the outcome. 50-160 characters.
  3. Title tag, 15-65 characters (weight 6)
    Why: The title is the headline in every result.
    Check by hand: Read the browser tab, or search the source for <title>.
    Fix: Product name + what it does, under 65 characters.
  4. Exactly one H1 (weight 6)
    Why: One clear H1 tells crawlers what the page is about.
    Check by hand: Search the source for <h1: there should be exactly one.
    Fix: Use exactly one H1 with your main promise.
  5. Canonical link (weight 5)
    Why: Prevents duplicate URLs (www, trailing slash, ?ref=) splitting your ranking.
    Check by hand: Search the source for rel="canonical".
    Fix: Add <link rel="canonical" href="https://yourdomain/"> to the head.
  6. Open Graph tags (share preview) (weight 5)
    Why: Controls the preview card when people share your link (X, Slack, chat apps).
    Check by hand: Search the source for og:title, og:description, og:image, or paste your link into a chat app and look at the preview.
    Fix: Add og:title, og:description and a 1200x630 og:image.
  7. sitemap.xml (weight 4)
    Why: Helps crawlers find every page, and lets you submit to Google Search Console and IndexNow.
    Check by hand: Open yourdomain.com/sitemap.xml, or look for a Sitemap: line in robots.txt.
    Fix: Generate /sitemap.xml and add 'Sitemap: https://yourdomain/sitemap.xml' to robots.txt.
  8. lang attribute on <html> (weight 3)
    Why: Language hints help engines serve the right audience.
    Check by hand: Look at the first tag of the source: <html lang="en">.
    Fix: Add lang="en" (or your language) to the <html> tag.
  9. twitter:card tag (weight 2)
    Why: Without it, links on X show as a bare URL or a small card.
    Check by hand: Search the source for twitter:card.
    Fix: Add <meta name="twitter:card" content="summary_large_image"> next to your og:image.
Landing page
  1. One clear call-to-action (weight 4)
    Why: Visitors from AI answers arrive cold; one obvious next step converts them.
    Check by hand: Look at the first screen on a phone: is there one button that says what happens next?
    Fix: Add one specific button above the fold ('Scan my site free', 'Start 7-day trial').
  2. Price or 'free' stated in text (weight 3)
    Why: AI answers to 'best X tool' often compare price; if yours isn't on the page they guess or skip you.
    Check by hand: Search the visible page for a price, a plan name or the word 'free'.
    Fix: State the price (or 'free') in plain text on the page.
  3. HTML under 500 KB (weight 3)
    Why: Huge HTML (inlined data, base64 images) slows crawling and first paint.
    Check by hand: Save the page source and check the file size: aim for under 500 KB of HTML.
    Fix: Move inlined data and images out of the HTML.
What this checklist does not cover

Backlinks, keyword rankings, Core Web Vitals field data and site-wide crawl errors need Google Search Console or a paid crawler. This list is the on-page part you can fix today on one page, which is where most new landing pages lose AI-search visibility.

Related: AI crawlers in robots.txt (copy rules) · llms.txt format and template · sitemap.xml generator and checker · JSON-LD schema generator