SEO audit and AI technical check
SEO and technical audit: make sure Google and AI can read your site
The GeoRush audit crawls your site the way a search engine does and shows what stops Google and AI assistants from reading it: errors, broken links, titles, thin content, speed and structured data. The AI technical check shows which AI bots your robots.txt blocks, whether you have an llms.txt, and gives you the code to fix it.
Updated on
The problem: AI cannot cite what it cannot read
Before ChatGPT, Perplexity or Google AI Overviews can recommend you, they have to reach your page, read it and understand it. A robots.txt that blocks OAI-SearchBot, a stray noindex, a canonical pointing to the wrong URL, or a page nothing links to is enough to leave you out, no matter how good your content is.
None of this is visible in a browser. That is why GeoRush combines two checks: a full SEO crawl audit and an AI technical check. Technical readiness is also one of the five pillars of the GEO Score, the 0–100 number GeoRush uses to sum up your GEO (generative engine optimization) performance.
How it works
- 1
Start the audit
GeoRush starts at your homepage, follows internal links and adds the URLs in your sitemap. It respects your robots.txt: blocked URLs are not crawled, but they are listed for you.
- 2
Every URL is analyzed
HTTP status, redirects, canonical, noindex, title, meta description, H1, word count, images, hreflang, links and JSON-LD structured data.
- 3
Real speed is measured
Your 10 pages with the most internal authority are loaded in headless Chromium emulating a phone on slow 4G with a 4x slower CPU.
- 4
The AI technical check runs
It checks which AI crawlers your robots.txt lets in, whether /llms.txt exists, your sitemap, Organization and product markup, and whether your homepage has real text.
- 5
You get the fix
Every issue comes with a plain-language explanation, the fix and, when useful, code to paste. The most important ones go straight into your action plan.
What you see
- A 0–100 site health score, with issues split into errors, warnings and notices, grouped into six areas: indexing, links, content, performance, structured data and international.
- Indexing: pages that fail to load, redirect chains, broken or missing canonicals, noindex pages listed in your sitemap, and sitemap URLs that redirect or error.
- Links: broken internal links, orphan pages (sitemap only), pages more than 3 clicks from the homepage, and an internal authority score from 0 to 100 per page, with suggested new links.
- Content: missing, duplicate or badly sized titles and descriptions, missing or multiple H1s, thin content and near-duplicate pages.
- Performance: server response over 800 ms, HTML over 1.5 MB, images over 300 KB, images without dimensions or in legacy formats, plus mobile Core Web Vitals (LCP, CLS, TBT).
- Structured data: which JSON-LD blocks you have (Organization, Product, FAQPage, Article, BreadcrumbList and more) and which required properties are missing.
- Changes since your previous audit, so you can see what broke or got fixed in between.
AI technical check: which bots it looks for in robots.txt
AI crawlers do different jobs. GeoRush splits them into two groups so you can decide on purpose.
| Group | Bots checked | What they do | If you block them |
|---|---|---|---|
| Answers | OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, Googlebot, Bingbot | Read your site to answer a user, or for the assistant's search index. | Your site cannot show up as a source in those answers. |
| Training | GPTBot, ClaudeBot, Google-Extended, CCBot, Applebot-Extended, Meta-ExternalAgent | Collect text to train future models. | No effect on today's search-backed answers. Your call. |
More in the guide robots.txt for AI bots.
Generators: code ready to paste
The Technical tab has generators pre-filled with your brand data. Copy, paste, and run the check again.
robots.txt
Lines that let in the crawlers behind AI answers. Replace or merge with your existing /robots.txt.
llms.txt
A short guide to your site for AI assistants: what you do and where the important pages are. See what llms.txt is.
Organization JSON-LD
Tells search engines and AI who you are, your logo and your official profiles. Goes in the <head> of your homepage.
FAQ and Product JSON-LD
Markup for your FAQ page and your product or pricing page. You fill in real prices, currency and ratings.
What you do with it
Start with the errors: they stop pages from being read at all. Then let answer bots in if they are blocked, publish your llms.txt and add Organization markup. Run the audit again and review the changes.
The audit does not use AI credits. How many URLs it crawls depends on your plan: up to 25 on Free, 150 on Starter, 500 on Growth and 2,000 on Agency. On WordPress, the GeoRush GEO plugin can publish llms.txt, the robots.txt lines and JSON-LD for you (see AI content).
Can AI bots read your site?
The free check reviews your site for AI readiness and gives you an A–E grade with the first fixes. No account needed.
Frequently asked questions
Keep reading
Page speed
Lighthouse speed reports with an A–F grade, waterfall, filmstrip, history and monitors with alerts.
AI content
Which page answers each question, what it lacks versus the pages AI cites, and drafts written by Claude.
robots.txt for AI bots
What each AI bot does, which ones to allow so AI can cite you, and a ready-to-copy robots.txt.
What is llms.txt
What llms.txt is, how to write one with a ready example, and what to expect from it, without the hype.