How to Do an SEO Audit in One Hour (Free Tools Only)

Published 14 September 2026 · 9 min read

An SEO audit in one hour is triage, not a full audit. The goal is to find the handful of problems that stop Google from crawling, indexing, or understanding the site, and to leave with a short, ordered list of fixes. Everything below uses free tools only: Google Search Console, PageSpeed Insights, a free crawler, a browser, and a site: search.

The one-hour plan

Six blocks of ten minutes, each with a fixed tool and a fixed question. If a block runs long, stop anyway and note what you skipped.

0–10 minutes: indexation

Start with the only question that matters if the answer is no: is the site in Google, and are the right pages in it?

1. Search site:example.com in Google. Treat the number as a rough estimate, not a count. Scan the first results for pages that should not be there: staging subdomains, tag archives, internal search pages, PDFs.
2. In Search Console open Indexing → Pages. Compare the indexed count to the number of pages you know the site publishes; a large gap either way is a finding.
3. Read the “Why pages aren't indexed” reasons. Act in the first hour on Blocked by robots.txt, Excluded by 'noindex' tag, Not found (404), and Soft 404. Crawled and Discovered – currently not indexed are usually quality or priority signals, not errors; note the count and move on.
4. Run URL Inspection on three pages: the homepage, the main commercial page, and the newest article. It shows whether the URL is on Google, which canonical Google selected, and when it was last crawled. A Google-selected canonical that differs from yours is a finding.

10–20 minutes: crawl basics

Three things decide what Google may fetch and which URL it keeps. The technical SEO checklist covers them in depth if you have a second hour.

1. Open https://example.com/robots.txt in the browser. Read every Disallow line under User-agent: *. Look for a bare Disallow: /, which blocks the whole site, and rules blocking CSS or JavaScript directories, which stop Google rendering the page. Syntax is in Google's robots.txt introduction.
2. Confirm there is a Sitemap: line and open the URL it points to. It should return HTTP 200, be XML, and list final URLs: https, no redirects, no 404s. Google's documented limit is 50,000 URLs and 50 MB uncompressed per sitemap file (see build and submit a sitemap). Then check Indexing → Sitemaps in Search Console: submitted, status Success, and a discovered-URL count that roughly matches the site.
3. Canonical spot-check. View the source of the homepage, one listing page, and one article and find <link rel="canonical">. It should be an absolute https URL pointing at the page itself unless you are deliberately consolidating duplicates. Also load the http:// and the www or non-www variant of the homepage and confirm each redirects to the canonical host in one hop.

A robots.txt that blocks rendering assets looks like this:

User-agent: *
Disallow: /wp-content/
Disallow: /assets/
Disallow: /_next/

Sitemap: https://example.com/sitemap.xml

Google needs those assets to render the page. The canonical tags guide and the XML sitemap guide show what a correct version of each looks like.

20–30 minutes: on-page on the top 10 pages

You do not have time for every page. Check the ten that earn the traffic and assume their templates behave the same elsewhere.

1. In Search Console open Performance → Pages, last three months, sorted by clicks. Take the top ten. Without Search Console, take the ten pages you most want to rank.
2. For each page record the <title>, the meta description, and the H1. A crawler export is faster than view-source and gives character counts.
3. Titles: unique, descriptive, topic near the front. Google does not document a character limit, but its title link documentation says it may rewrite titles that are too long, boilerplate, or missing. Ten pages that all begin with the brand name is one template finding, not ten.
4. Descriptions: present, unique, a plain sentence about the page. Google says it may use the meta description or generate its own snippet; a missing one means you have no say. Details in the title tags and meta descriptions guide.
5. H1: exactly one, agreeing with the title on what the page is about. A logo wrapped in an <h1> on every page is the most common failure. See the heading structure guide.

Aura's free scan gives a one-page, 18-check readout of the crawl-basics and on-page blocks in about ten seconds: robots.txt, sitemap and llms.txt presence, canonical tag, title between 15 and 70 characters, description between 50 and 170, a single H1, at least two H2s, HTTPS, response time, and HTTP 200 at the final URL. The honest caveat: it looks at one page. It does not crawl the site, so it replaces the spot-check, not the crawler. The full list is in the 18 checks explained.

30–40 minutes: speed

Test templates, not pages. A template fix repairs every page that uses it.

1. Pick three templates: the homepage, one listing page, and one article or product page.
2. Run each through PageSpeed Insights. Read the field data first; it comes from real Chrome users. If there is too little traffic for field data, the lab result is all you have, and it is a throttled mobile emulation: a direction, not a measurement.
3. Record the three Core Web Vitals against Google's thresholds, which are assessed at the 75th percentile of page loads.
4. Read only the top two or three Opportunities per template. Write them down; do not fix anything yet.

The thresholds are Google's, documented on web.dev. Three templates is a sample; the Core Web Vitals guide explains the Search Console report that covers every URL.

40–50 minutes: content and links

This is the only block that needs a crawler. Screaming Frog SEO Spider's free tier crawls up to 500 URLs: the whole site for most small sites, a usable sample for larger ones.

1. Crawl from the homepage. When it finishes or hits the 500-URL cap, open the Internal tab.
2. Filter by status code. Internal links to 404s are the quickest wins in the audit: they waste crawl requests and send users nowhere. Sort by inlinks so the most-linked broken URL is at the top.
3. Sort by word count, ascending. Indexable pages with almost no text are thin-page candidates. Whether they are a problem depends on purpose: a contact page with 40 words is fine; 80 tag archives with 40 words each are not.
4. Orphan check. Export the crawled URL list, paste the sitemap's URLs next to it in a spreadsheet, and look for sitemap URLs the crawl never reached; those have no internal links pointing at them. Above 500 URLs the comparison is partial; say so in the notes.
5. Look up the inlink count for the ten pages from the on-page block. An important page with one or two internal links is under-supported; the internal linking guide covers the fix.

50–60 minutes: write the prioritized list

The audit is the list. Everything before this block is note-taking.

1. One line per issue: what is wrong, where (a URL or a template), the evidence, and the fix in one sentence.
2. Sort with one rule. Blockers first: anything that stops Google from crawling, indexing, or reaching an important page: a robots.txt disallow, a noindex on a money page, a sitemap that errors, a canonical pointing at the wrong URL, a redirect chain that ends in a 404. Template-level fixes second: one change that repairs many pages: the title pattern, the H1 in the layout, the LCP image in the article template, blocked asset directories. Page-level fixes last: individual descriptions, individual thin pages, a single broken link.
3. Add a rough effort estimate to each line (minutes, hours, days) and a name if you know who owns it.
4. Cut the list to ten items. A twenty-item list from a one-hour audit is a list nobody works through; keep the rest under “not yet.”

What to skip in one hour

Leaving things out is what makes the hour possible. Skip these on purpose.

• Backlink audit. Search Console's Links report is free, but reading it properly takes hours, and no free tool shows the full link profile.
• Log file analysis. It needs server access and a parser, and it answers crawl-budget questions. Google's crawl budget documentation says most sites do not need to think about crawl budget unless they are large or change rapidly.
• Full Core Web Vitals pass. You sampled three templates. The Search Console Core Web Vitals report, which groups every URL, is the next session.
• Keyword research and content gaps. A separate job with its own method; see the keyword research guide.

Frequently asked questions

Can you really audit a site in one hour?
You can triage it. An hour is enough to find indexation blockers, crawl-basics errors, on-page problems on the ten pages that matter, speed problems on three templates, and broken internal links on a 500-URL sample. It is not enough for backlinks, log files, or a full Core Web Vitals pass. The output is a prioritized list, not a finished audit.

Which free tools do I need for a one-hour SEO audit?
Google Search Console (the Pages, Performance, Sitemaps, and URL Inspection reports), PageSpeed Insights, a free crawler such as Screaming Frog SEO Spider (the free tier stops at 500 URLs), a browser for robots.txt, the sitemap, and view-source, and a Google site: search. Nothing else is required.

What should I fix first after the audit?
Blockers first: anything that stops Google from crawling, indexing, or reaching an important page, such as a robots.txt disallow, a noindex tag on a money page, a sitemap that returns an error, or a canonical pointing at the wrong URL. Then template-level fixes, where one change repairs many pages. Page-level fixes come last.

Does Aura's free scan replace the audit?
No. It covers the crawl-basics and on-page blocks for one page in about ten seconds: robots.txt, sitemap and llms.txt presence, canonical, title and description length, single H1, HTTPS, response time, and HTTP status. It does not crawl the site, measure Core Web Vitals, check backlinks, or do keyword research, so it stands in for the spot-check, not the crawler.

Run the free 18-check scan on one page