A free audit recently gave a UK travel agency's website 18 out of 100. The verdict was brutal: no title, no meta description, a noindex instruction, and search engines locked out. None of it was true. The site's firewall had served the scanner a "Just a moment..." challenge page, and the tool graded that page instead of the real homepage.
That's the quiet problem with most free SEO audit tools. They're fast and they look authoritative, but a score is only as good as the data behind it. When I built the free SEO audit on this site, I started from that failure: every finding has to come from something the scanner actually measured, and anything it couldn't measure gets left out rather than marked as broken.
This guide walks through how the audit works: what it reads, how the AI turns raw data into a scored report, what each score means, and the order I'd fix things in. If you'd rather see your own results first, run the audit in about a minute and keep this page open to read your report alongside it.
What This Kind of Audit Is (and What It Isn't)
An SEO audit is a structured check of the things that decide whether search engines can find, understand and trust a page. The free version is the fast pass: automated, focused on your homepage, and designed to surface the problems worth fixing first.
It isn't a full audit. A free tool can't see your rankings, your traffic, your backlink profile or how real visitors experience your page speed. Those need Search Console access, crawl data across every URL, and time. Any free checker that confidently scores your backlinks from a single page fetch is guessing.
The useful middle ground is a tool that checks what it can verify and says plainly what it can't. That's the line this audit is built on, and it's worth holding any SEO checker you use to the same standard.
How Our Free SEO Audit Works, Step by Step
Step 1: You enter your domain
Type your domain into the box, with or without https:// or www. The tool trims it to a bare hostname and rejects anything that isn't a real public domain, such as a raw IP address or an internal network name. That last check is about security: it stops anyone from using the scanner to probe private servers.
Step 2: You choose where the PDF goes
Next you add an email address. The report opens in a new browser tab as soon as it's ready, and a PDF copy lands in your inbox so you can forward it to a developer or agency. The email is only used to deliver the report.
Step 3: The scanner reads your site
The scanner fetches four things: your homepage, your robots.txt file, your XML sitemap (from the location listed in robots.txt, or /sitemap.xml if none is listed) and your llms.txt file if you have one. It follows redirects one hop at a time, times how long your server takes to respond, and records the response headers.
From the homepage HTML it pulls out the facts that matter for search: the title tag and its length, the meta description, meta robots, the canonical tag, the language attribute and hreflang tags, Open Graph and Twitter card tags, every H1, H2 and H3, every image and whether it has alt text, internal and external links, the structured data types in your JSON-LD, and the visible word count.
Step 4: AI turns the data into a report
The measured data, and only the measured data, goes to Claude, Anthropic's AI model, with strict instructions. Base every finding on the data. Never invent rankings, traffic, backlinks or Core Web Vitals. Quote real values where they help, such as the exact title and its character count.
Claude scores five categories from 0 to 100, lists five to ten issues by severity with a specific fix for each, and picks out three to five strengths and quick wins. The output is locked to a fixed structure, so every report has the same shape and nothing important gets skipped.
When a firewall blocks the scan
Back to the travel agency. Services like Cloudflare Bot Fight Mode often challenge automated requests, and that's a sensible thing for a site owner to want. Instead of grading the challenge page, the audit now detects it and reads the homepage again through Anthropic's web fetch service.
That route returns the page's text and meta tags, but not the raw HTML or server headers. So the report skips checks it can't verify, such as response time and structured data, and says so in the summary. Once the real page was read, the same site scored 68, with problems that actually existed: three competing H1 headings and a 79-character title.
An audit that grades the wrong page is worse than no audit. It sends you fixing problems you don't have.
What the Audit Checks, Area by Area
Every report scores your homepage in five areas. Here's what goes into each one and why it matters.
Technical SEO
This covers HTTPS, the HTTP status and any redirects, robots.txt rules, the XML sitemap and the canonical tag. Together they decide whether search engines can reach and index the page at all. Google's documentation on robots.txt, sitemaps and canonical URLs sets out the rules the scanner checks against.
The stakes are lopsided here. A single Disallow: / line in robots.txt can hide an entire site, which is why the audit treats it as a failure rather than a warning.
On-page SEO
Title tag, meta description, heading structure, image alt text and social sharing tags. The checklist passes a title between 30 and 60 characters. Google doesn't publish a hard limit and shortens title links based on available width, so read 60 as a practical guide rather than a rule.
Meta descriptions pass between 70 and 160 characters. Google may still rewrite your snippet when it finds a better match for the query, but a clear description gives it a strong default to work from.
The audit also looks for one H1. Google doesn't require a single H1, and several won't get a page penalized. One clear main heading still helps people scanning the page and helps AI systems work out what the page is about, which is why multiple H1s show as a warning.
Content quality
Here the AI looks at word count, how clearly the page explains what you offer, and whether it answers what a visitor arrives looking for. Pages under 300 words get a warning. Length isn't a ranking factor by itself, but a homepage with two sentences rarely gives search engines enough to understand who it serves. Google's guide to creating helpful, people-first content is the benchmark.
AI search readiness (GEO and AEO)
This area checks structured data, answer-friendly headings, llms.txt, and whether robots.txt blocks AI crawlers such as OpenAI's GPTBot, ClaudeBot, PerplexityBot or Google-Extended. Blocking those bots can be a deliberate business decision, so the audit reports it as a warning, not a failure.
It's worth being straight about llms.txt. It's a proposed convention, not an official standard, and Google's guidance on AI features and your website says no special files are needed to appear in AI Overviews; the usual SEO best practices apply. The audit treats llms.txt as a low-cost extra, never as the reason a site isn't ranking.
Read more: What Is GEO (Generative Engine Optimization)? A Practical Playbook
Performance and security
Server response time, compression, caching headers, HSTS and page weight. Response times under 600 milliseconds pass, and anything over 1.5 seconds fails. That's a single measurement of server response from one location, so treat it as an early warning rather than a replacement for the real-user data in Google's Core Web Vitals report.
How to Read Your Report
The report opens with an overall score and a short verdict written for the site owner, not the developer. Then come the five category scores, the issue list, and a pass, warn and fail checklist built straight from the raw data, with no AI involved.
| Score | Label | What it usually means |
|---|---|---|
| 85 to 100 | Excellent | Foundations are solid. Your next gains come from content and links. |
| 70 to 84 | Good | A few fixable gaps, often in on-page tags or AI readiness. |
| 50 to 69 | Needs work | Real issues are limiting visibility. Start with the high-severity items. |
| 0 to 49 | Poor | Something fundamental is wrong, such as an indexing block, a missing title or an unreachable page. |
Issues are ranked critical, high, medium and low. A critical issue blocks visibility outright, like a noindex tag on the homepage. A low issue is polish. The checklist is your evidence: if the report says your title is too long, the checklist shows the actual character count, so you can check the claim for yourself.
What to Fix First
Most reports show more problems than anyone can fix in a week. This is the order I work in on client sites, because each step depends on the one before it.
- Remove anything that stops indexing. A noindex tag, a robots.txt block or a homepage returning an error makes every other fix irrelevant.
- Settle HTTPS and redirects. Every version of your domain should land on one secure URL, and your canonical tag should point to that same URL.
- Rewrite the title and meta description. They're what people see in search results, so they shape clicks even before rankings move.
- Fix headings and content. Use one clear H1 that says what you do, then sections that answer the questions your customers actually ask.
- Add structured data. Start with Organization or LocalBusiness schema, then add types that match your content. Google's introduction to structured data lists what's supported.
- Finish with AI readiness extras. Review your AI crawler rules in robots.txt and consider an llms.txt file once the basics are in place.
Steps 3 to 5 can usually be done in your CMS in an afternoon. Steps 1 and 2 sometimes need a developer, and that's where the PDF earns its keep: send it over and everyone works from the same list.
Read more: The Technical SEO Checklist That Still Wins in the AI Search Era
Free SEO Audit vs a Full Professional Audit
A free audit answers one question: are the basics right on the page that matters most? A full audit answers a harder one: why isn't the site growing?
| Free audit | Full professional audit | |
|---|---|---|
| Pages covered | Homepage, robots.txt, sitemap, llms.txt | Every indexable URL |
| Turnaround | About a minute | One to three weeks |
| Rankings and traffic | Not included | Search Console and analytics data |
| Backlinks | Not included | Full link profile review |
| Page speed | Server response time | Core Web Vitals field data |
| Output | Scored report and PDF | Prioritized roadmap with implementation support |
| Cost | Free | Quoted per project |
If your free report comes back mostly green but traffic is still flat, the problem sits somewhere a homepage scan can't see: content gaps, stronger competitors, weak links or a site-wide technical issue. That's the point where a full audit pays for itself. If your traffic dropped suddenly, read the Google core update recovery guide before changing anything.
Frequently Asked Questions
Is the free SEO audit really free?
Yes. There's no sign-up, trial or credit card. You enter your domain and an email address, the report opens in your browser, and a PDF copy is emailed to you.
Will the audit change anything on my website?
No. It only reads public files, the same way a browser or search engine does. Nothing is installed and no login to your site is needed.
Why is my score different from other SEO checkers?
Every tool weights things differently, and many score items they can't measure from a single page. This audit only scores what it actually read from your site and leaves out anything it couldn't verify.
How often should I run a free SEO audit?
After any redesign, CMS migration or theme update, and roughly once a quarter otherwise. Those are the moments when titles, canonical tags and robots rules most often break without anyone noticing.
Start With What You Can Measure
A good audit doesn't promise rankings. It shows you, with evidence, whether search engines and AI tools can read your homepage the way you intend. Fix what it finds in order, and you've removed the reasons a site gets ignored before content and links even come into play.
Run the audit, open the PDF next to this guide, and start with the first critical or high issue on the list. Then run it again after your changes to confirm each fix landed.