What the walkthrough covers
Enter your website
Type your home page or your most important money page (pricing, a product or a service page) and press Run AI audit. The audit fetches the page the way an AI crawler does, reads your robots.txt and sitemap, and tests whether bots like GPTBot and ClaudeBot get through your firewall.
Read your AI readiness score
The 0 to 100 score is weighted towards what matters most for AI answers: crawler access (22%) and answer-ready content (20%) count more than technical basics (5%). Next to it, five tiles show whether ChatGPT, Claude, Gemini, Perplexity and Copilot can reach the page at all.
Find where you lose points
The board splits all 43 factors into 8 areas, each with its own score. Green is good, amber needs work, red is a fix. In the demo, structured data scores 34/100 and off-site signals 5/100: those two areas cost the most points.
Open a factor: what we found and how to fix it
Every factor opens to three parts: what we found on your page, why it matters to AI assistants, and how to fix it in plain English. For robots.txt you also get a table of 13 AI crawlers, what each one does and whether your rules allow it.
Plan the biggest wins first
“Fix these first” ranks the fixes by the points they add. Tick the ones you plan to ship and the projected score updates. In the demo, six fixes take the site from 57 to a projected 78. Ship them, then run the audit again.
The fix from the video: a robots.txt that lets AI cite you
The demo site blocked OAI-SearchBot and Claude-SearchBot, the crawlers that fetch pages when someone asks ChatGPT or Claude a question. This is a common pattern when a site copies an “block all AI bots” list. Here is a starting point that keeps you readable in AI answers and, optionally, opts out of training only. Adjust it to your own policy.
User-agent: *
Allow: /
# Let AI assistants read and cite you in answers
User-agent: OAI-SearchBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: Claude-SearchBot
Allow: /
User-agent: PerplexityBot
Allow: /
# Optional: opt out of model training only
User-agent: GPTBot
Disallow: /
Sitemap: https://yourbrand.com/sitemap.xml
Check your firewall or CDN bot settings too: they can block AI crawlers even when robots.txt allows them. The audit tests this with real GPTBot, ClaudeBot and PerplexityBot requests.
Transcript
AI assistants can't recommend a website they can't read. Here's how to check yours, in about thirty seconds.
Meet the free Website AI Audit, from GrowMarketingPro.
Type your website address, and hit audit. We check forty-three factors that decide whether AI can read, trust, and quote your page.
You get one AI readiness score out of a hundred, plus whether ChatGPT, Claude, Gemini, Perplexity and Copilot can reach your page.
Every factor is grouped into eight areas, from crawler access to structured data, so you see exactly where you lose points.
Open any factor to see what we found. Here, robots.txt blocks the search crawlers for ChatGPT and Claude, so neither can cite this site. And the fix is right there.
Fix these first ranks your biggest wins. Tick the fixes you plan to make, and watch your projected score climb.
Run your first audit free, no sign-up needed, at growmarketingpro.com.
The company in the video, Pipeloom CRM at pipeloom.example, is a fictional demo site. The audit results shown are real output from the tool run on that demo site.
Questions people ask
What is the difference between OAI-SearchBot and GPTBot?
OAI-SearchBot and ChatGPT-User fetch your pages when someone asks ChatGPT a question, so they decide whether you can be read and cited in answers today. GPTBot collects data to train future models. You can block GPTBot and still be cited, but blocking OAI-SearchBot keeps you out of ChatGPT search. Anthropic splits Claude the same way: Claude-SearchBot and Claude-User for answers, ClaudeBot for training.
How do I check my robots.txt for AI crawlers?
Open yourdomain.com/robots.txt and look for User-agent lines naming AI bots, followed by Disallow: /. Also check the User-agent: * group, which applies to every bot that has no group of its own. The Website AI Audit reads the file for you and lists 13 AI crawlers as allowed or blocked.
Why is my site marked low on “Readable without JavaScript”?
Most AI crawlers read the raw HTML your server sends and do not run JavaScript. If your text is added by JavaScript after the page loads (common with single-page apps), the crawler sees very little. Server-side rendering or static generation puts the full text in the HTML.
How long until my fixes show up in ChatGPT answers?
There is no fixed timeline. A robots.txt change applies the next time a crawler visits, which can be days for busy sites and longer for small ones. Content and schema changes help only after the page is fetched again. Run the audit again to confirm each fix, then track whether AI assistants name you over the following weeks.
Which fixes should I make first?
Start with access: if AI search crawlers are blocked or your text is invisible without JavaScript, nothing else counts. Then add Organization schema with sameAs links, and expand the page so it answers what buyers ask. The audit’s “Fix these first” list orders these by points for your page.