Free tool · SEO audit
Free SEO audit tool: check any page, no sign-up
One page at a time. I fetch the page, its robots.txt and sitemap from my server, without running JavaScript. Nothing is saved.
The guide
Why I start every SEO review with these checks
I have done SEO since 2008, and the first hour of a new project still looks the same. Before keyword research, before content plans, I check that Google can reach the page, is allowed to index it, and can tell what it is about. When one of those basics is broken, nothing else I do will show up in results.
Most of the time the basics are fine and the audit takes ten minutes. When they aren't, the fix is usually small and the effect is large. A stray noindex, a canonical pointing at the wrong page or a redirect chain left behind after a redesign can hold back a site that is otherwise well built. I learned that on my own site: after I moved it to Next.js in September 2026 and changed the inner URLs, the new pages were technically clean, but the old addresses returned 404s and most of the site dropped out of Google. I wrote up what that migration taught me.
This tool runs those first checks on one page from the raw HTML, the way a crawler first sees it. It won't replace a full crawl or Search Console, but it will tell you quickly whether a page has a technical problem or whether you need to look at content and competition instead.
What the audit checks, and how much each one matters
Indexing (high priority)
HTTP status, redirects, noindex in the HTML and the X-Robots-Tag header, robots.txt for Googlebot, the canonical tag and whether the URL is in your sitemap. A failure here can keep the page out of Google entirely, so it caps the score.
Title and meta description
Length, and whether they exist at all. The title is still one of the clearest signals of what a page is about. The description doesn't affect rankings, but it is often the text people read before they decide to click.
H1 and heading structure
One H1 that names the topic, H2s that split the content into sections, and levels that run in order. I also show the full heading outline so you can read the page's structure at a glance.
Images and links
Images with no alt attribute, internal links with empty anchor text or nofollow, and how many internal and external links the page has. Internal links are how Google finds and weighs your pages.
Content length
Words in the main content, not the menus and footer. Word count isn't a ranking factor, but very short pages rarely answer a search properly.
Technical and sharing
HTTPS, server response time, the mobile viewport tag, the lang attribute, HTML size, structured data types and Open Graph tags for social and chat previews. Missing markup? The JSON-LD schema generator builds it.
How to read your results
Start with the What to fix first list. It puts problems (red) before warnings (amber), and within each, the checks that affect indexing come before the ones that affect clicks or sharing. If the list is short, you are in good shape.
Then look at the score in context. A page with no Open Graph image and a slightly long title might score in the 80s and be perfectly fine. A page that scores 40 because of a noindex has one problem, but it is the only one that matters until it's fixed. I cap the score for hard blocks for that reason: a high number shouldn't hide a page that Google can't index.
Open the detail lines when something looks odd. They show the exact canonical URL, the redirect chain with each status code, the images missing alt text and the schema types found. That is usually enough for a developer to find the setting or template causing it.
Score 85 and above
The on-page basics are right. If the page still doesn't rank, the reason is more likely content depth, search intent, links or competition. Run the copy through the content quality checker, then compare the page honestly with what currently ranks.
Score 60 to 84
Usually a handful of amber items: a missing description, no schema, a heading level skipped, thin internal linking. None are emergencies. Fix them in the template if the same issue repeats across pages.
Below 60
Something serious, often a noindex, a robots.txt block, a 4xx or 5xx status or a canonical pointing elsewhere. Run the URL through the indexing checker for a closer look at those, then confirm with URL Inspection in Search Console.
Worked example: auditing a local service page
Say you run a limo company and your airport transfer page isn't getting traffic. Here is how I'd use the audit, in order:
- Check the indexing group first. If the status, noindex and robots checks pass and the canonical points to itself, Google is able and allowed to index the page.
- Read the title. Does it say what the page is and where, in words a customer would search? "Airport Transfers" on its own leaves out the city.
- Read the outline. I often find service pages whose only H1 is the business name, with no heading that mentions the service.
- Look at internal links. If the page only has links from the menu, add a sentence on the homepage and related pages that links to it with clear anchor text.
- Check the word count. A service page with 120 words and a booking form gives Google, and the customer, very little to go on. Add what people ask on the phone: vehicles, areas covered, how pricing works, what happens if a flight is late.
That is close to the process I follow for the limo and chauffeur companies and med spas I work with, before anything else changes. The rest of the airport page work is in my airport transfer SEO guide.
Mistakes I see in audits again and again
- The same title on every page, usually just the business name, so Google rewrites them.
- Logos and hero images marked as the H1, leaving the page with no text heading.
- A canonical tag copied from the homepage template onto every page.
- Staging settings left on after launch: a noindex tag, a robots.txt that blocks everything, or both.
- Service pages reachable only from a dropdown menu, with no links from the text of other pages.
- Schema that describes things the page doesn't show, such as reviews or FAQs that aren't visible to visitors.
What a one-page audit can't tell you
A single-page check is a starting point. It can't see how many pages on your site share the same problem, how Google has actually indexed them, which queries they show for, or how your content compares with the pages that outrank you. For that I use Search Console, a full crawler and, on bigger sites, server logs.
It also reads the HTML your server sends, before any JavaScript runs. Most sites render their main content on the server, so that's what Google sees first. If yours builds the page in the browser, some checks may report missing headings or text that a visitor can see, and that's worth knowing in itself.
If the audit comes back clean and the page still isn't performing, the next questions are about quality and intent. My guide to core update recovery covers how I tell a technical problem from a quality one. If traffic fell on a particular date, check the Google algorithm update tracker to see whether an update was rolling out. And if you'd rather have someone go through the whole site, that's what my technical SEO audits are for.
FAQ
SEO audit tool questions
Is this SEO audit really free?
Yes. There is no sign-up and no email gate. The only limit is a fair-use cap of a few audits a minute per person, because each audit fetches pages from my server.
Does it audit my whole website?
No, one page per run. That is deliberate: most problems I find live in a template, so auditing the homepage, one service page, one blog post and one product or location page usually shows you what affects the rest. For a full crawl, use Screaming Frog or Sitebulb.
What does the score mean?
It is my own weighting of the checks on this page. Problems that stop indexing count most, things like Open Graph tags count least, and a hard block such as noindex caps the score at 40. Google does not use any score like it, so treat it as a to-do list, not a grade.
Why is my word count lower than I expected?
The tool counts the main content only. It reads the <main> or <article> element if your page has one, otherwise the body without menus, headers and footers. Text that only appears after JavaScript runs isn’t counted either.
Does the audit run JavaScript?
No. It reads the HTML your server sends, the same first pass Google makes. If your title, canonical or content only appear after JavaScript runs, Google may still see them later, but less reliably, and this tool will report them as missing. That is worth knowing in itself.
Does it check backlinks or Core Web Vitals?
No. Backlinks need a link index, and Core Web Vitals come from real Chrome users. Use Search Console and PageSpeed Insights for those. The response time here is one download of the HTML from my server, useful for spotting a slow server, not a replacement for field data.
More free tools
Want the whole site checked, not one page?
Send me the URL. I'll look at indexing, templates and internal links across the site and tell you what I'd fix first, for free.