Your customers have started asking AI instead of Google. When they ask for the best firm in your category, an assistant reads a handful of sites and names a few companies. Most business websites cannot be read by those assistants at all — and it is invisible in Google Analytics, so nobody knows.
Two fields. No signup, no call, no sales sequence. You get a PDF with your score, exactly what is broken, and the code to fix it. Or skip the form entirely and download the cheat sheet — no email needed.
What an AI crawler saw on this very site before we fixed it last week. It is a React app, and these crawlers do not run JavaScript.
GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and CCBot. Most site owners have never heard of any of them.
Open ChatGPT and ask "who are the best [your category] in [your city]?" If you are not named, that is what a buyer sees.
And neither of them shows up in any tool you already use, because Googlebot runs JavaScript and the AI crawlers do not. Google can see you. The assistants cannot.
Open yoursite.com/robots.txt. Site builders, security plugins and CDNs ship
with AI crawlers blocked by default, and nobody ever looked at the file. This one is a
five-minute fix, and the cheat sheet below gives you the exact lines to paste.
If your site is built in React, Vue, Angular, Wix or a no-code app builder, the server often sends an empty page and JavaScript paints the text in afterwards. A human sees a full website. GPTBot sees nothing at all. This one is not a five-minute fix.
Six checks, 100 points. Every number comes from the bytes your server actually sends. Nothing is estimated and nothing is written by an AI — run it twice and you get the same score, and you can verify every finding yourself with "view source".
Our robots.txt shipped with a placeholder the site builder never filled in, so we pointed every crawler at a URL that does not exist. Our sitemap listed all 17 pages under a domain we no longer own, and four of them had slugs deleted months ago. And the site itself is a React app, so an AI crawler read exactly zero words of it. We scored 40 out of 100.
Sitemap: https://[YOUR_WEBSITE_URL]/sitemap.xmlSitemap: https://hiremina.com/sitemap.xmlWe fixed it before we offered to fix yours. If it can happen on a web designer's own site, it can happen on yours — and you would have no way of knowing.
It is the reasonable fear, and the honest answer is uncomfortable: blocking mostly costs you the credit, not the copying. Models trained on the open Common Crawl years before you had a say. What a block reliably prevents is the assistant naming you and linking to you when it answers. You keep the exposure and lose the attribution. If something is genuinely confidential, keep it off a public website entirely, not behind a robots.txt line that is a request rather than a lock.
No. These are different crawlers. Googlebot handles search and is untouched by any of this. Google-Extended only governs Gemini and AI Overviews, and Google states it is not used as a ranking signal. Fixing a broken sitemap helps ordinary search too. There is no ranking downside.
You get a PDF: your score out of 100, every check broken down, the specific things that are wrong on your site, and the exact code to paste in to fix them. It is free and there is no call to sit through. Everything in it is yours to hand to your own developer. If you would rather it was simply done for you, that is the paid part, and you can decide that after you have read the report.
No. An SEO audit tells you how you rank in a list of blue links. This tells you whether an AI assistant can read, understand and quote you when someone asks it a question instead of searching. The two overlap a little and diverge a lot — a site can rank on page one of Google and be completely invisible to ChatGPT. Ours was.