How to Do a Full SEO Audit for Free (Tool-by-Tool Walkthrough)

Most SEO audits fail because people start in the wrong place. They open a tool, get a list of 200 warnings about image alt text, and spend an afternoon on cosmetics while a noindex tag quietly keeps half the site out of Google. A useful audit runs in order of impact: the things that stop a page from ranking at all come first, and the polish comes last.

This is a sequenced, free audit you can run in an afternoon. Every step names the free tool and tells you what a pass looks like versus what a fail looks like, so you're not left staring at a result wondering if it's good. It assumes a small-to-medium site (up to a few hundred pages). No paid tools, no signups beyond Google's own, which you should have anyway.

The one thing you can't audit with browser tools is your actual search performance, so we start with the tool that has that data.

Step 1: Google Search Console first, always

Before you touch any on-page tool, open Google Search Console. If the site isn't verified there yet, do that first; it's the single most important free SEO tool and no third-party product has data this accurate about your own site. Then read two reports.

The Pages report (under Indexing). This shows how many of your pages are indexed and, more usefully, why the rest aren't. You'll see reasons like "Crawled - currently not indexed," "Discovered - currently not indexed," "Excluded by noindex tag," or "Blocked by robots.txt."

• Pass: most of the URLs you care about show as "Indexed."
• Fail: important pages sitting under "Excluded by noindex tag" or "Blocked by robots.txt" (a configuration mistake) or a large pile under "Crawled - currently not indexed" (usually a content quality or thin-content signal).

The Performance report. This shows the queries you already rank for, your impressions, clicks, and average position. It tells you which pages are close to the top (position 5-15) and worth improving first. That's where audit effort pays back fastest, on pages already ranking that just need a nudge.

Search Console tells you where the problems are. The rest of the audit tells you why.

Step 2: crawl and index checks

Now confirm nothing is blocking access. Two files and one tag.

Visit yoursite.com/robots.txt directly. Read it. The catastrophic mistake is Disallow: / under User-agent: *, which blocks the entire site; the subtle one is blocking a directory like /blog/ that you actually want crawled. Run the file through the robots.txt validator if the syntax is unfamiliar. Our robots.txt guide explains what each directive does.

• Pass: bots you care about (Googlebot) can reach your content pages.
• Fail: a Disallow line covering pages you want indexed.

Then check for noindex. View the page source of a few important pages and search for "noindex." A <meta name="robots" content="noindex"> on a page you want ranked is a hard block. Search Console's Pages report catches these too, which is why step 1 comes first.

Finally, confirm you have a sitemap. If you don't, build one with the XML Sitemap Generator and submit it under Search Console's Sitemaps report. A sitemap won't force indexing, but it gives Google a clean list of your URLs. Details in our XML sitemap guide.

Step 3: metadata

With access confirmed, audit what's on the page. Start with titles and descriptions, because they're both a ranking factor (the title) and your click-through pitch in results.

Pull each important page's title and meta description into the SEO Character Counter.

• Pass: title reads fully (under about 580 pixels, roughly 60 characters), is unique to the page, and leads with the topic. Description is 140-160 characters and specific.
• Fail: titles truncated mid-word, the same title on every page, or a missing description (which lets Google write its own, usually worse, snippet).

Duplicate titles across pages are one of the most common findings on small sites, usually from a CMS template that never got customized. Our title tag length guide and meta description guide cover the fixes.

Step 4: heading structure

Run each page through the Heading Analyzer. You're checking the outline, not the styling.

• Pass: exactly one H1 that describes the page, followed by H2s for main sections and H3s nested under them, no skipped levels.
• Fail: no H1, multiple H1s competing, or an outline that jumps from H2 to H4. Also common: an H1 that's just the site logo alt text or "Home."

A clean heading outline helps crawlers understand the document and helps screen-reader users navigate it. Our heading structure guide shows good and bad outlines side by side.

Step 5: structured data

Not every page needs schema, but where it fits (articles, products, FAQs, local business info), it makes you eligible for rich results.

If a page should have schema and doesn't, generate it with the Schema Markup Generator and validate the output in Google's Rich Results Test.

• Pass: valid JSON-LD of the right type, no errors in the Rich Results Test, and the page qualifies for a rich result.
• Fail: no schema on a page type that supports it, or schema with errors (a common one: Product markup missing a required price or availability). Our schema markup guide covers which type goes where.

Don't add schema for its own sake. Marking up a plain "About" page with LocalBusiness data you don't have is worse than no schema.

Step 6: redirects

Check that your redirects are clean, especially after any migration or domain change. Run key URLs through the Redirect Checker.

• Pass: a single 301 from old to new, or from non-www to www (whichever you've chosen as canonical). One hop.
• Fail: a chain (URL A to B to C to D), which wastes crawl budget and dilutes the signal at each step, or a loop, which breaks the page entirely with an ERR_TOO_MANY_REDIRECTS error.

Also confirm your http-to-https redirect is a 301 and that you haven't ended up serving both www and non-www versions as separate indexable pages. Our redirect chains guide walks through untangling these.

Step 7: social cards

Last, because it doesn't affect Google ranking, but it affects every click from a shared link. Run your key pages through the Open Graph Checker and preview them with the Social Media Preview.

• Pass: the checker shows a title, description, and an og:image that's an absolute HTTPS URL around 1200x630, and the preview renders a proper large card.
• Fail: no image (usually a relative og:image URL or one injected client-side), or a title that gets cropped in the card. Our Open Graph meta tags guide has the standard fixes.

Putting it in order

The sequence is the point. Search Console shows you where to look, indexing checks make sure Google can see the page, then you work down through metadata, headings, schema, redirects, and social cards in decreasing order of ranking impact. If you only have twenty minutes, do steps 1 and 2 and stop; a page that's blocked or noindexed can't be helped by perfect metadata.

For the single-page version of this, see what is an SEO test, and for the full inventory of which free tool covers which job, free SEO tools.

Frequently Asked Questions

How long does a free SEO audit take?

For a small site, an afternoon. The Search Console review and indexing checks take twenty minutes and catch the highest-impact problems. Metadata, headings, schema, redirects, and social cards add another hour or two depending on how many pages you check. You don't need to audit every page; focus on your homepage, top landing pages, and the pages already ranking in positions 5-15.

Do I really need Google Search Console?

Yes, and it's free. Search Console is the only source of accurate data about how your own site performs in Google: which queries you rank for, your actual positions, and why specific pages aren't indexed. No third-party tool, free or paid, has data this reliable for your site. Verify it before doing anything else.

What's the most common problem a free audit finds?

On small sites, two things dominate: a noindex tag or robots.txt rule accidentally blocking pages (usually left over from a staging or launch config), and duplicate or missing title tags from an uncustomized CMS template. Both are quick fixes with outsized impact, which is why the audit sequence puts indexing and metadata near the top.

Can I audit a competitor's site with these tools?

You can run the on-page tools (metadata, headings, schema, social tags, redirects) on any public URL, including a competitor's, since they read live HTML. What you can't see is their Search Console data: their actual rankings, traffic, and indexing status are private to them. So you can audit a competitor's technical setup but not their performance.

Should I fix every warning the audit finds?

No. Sort findings by severity: blocking issues (noindex, robots.txt blocks, redirect loops) first, real-but-not-urgent issues (truncated titles, missing descriptions) next, and cosmetic ones (a missing og:locale, "alt text could be better") only if you have time. Fixing 200 minor warnings while ignoring one noindex tag is the classic audit mistake.