SEO audit report example: a real audit of our own site

A real SEO audit report for goorbit.io, from 3 November 2026, and a template to copy: what to check, how to rank what you find, and what a client should read.

Leon Missoul2 min read · Published 3 Nov 2026

In short

A useful SEO audit report separates what blocks a page from what merely could be better, and says who fixes what.
Below is a real SEO audit example: goorbit.io on 3 November 2026, 124 pages crawled, no blockers and two warnings, one of them on purpose.
The SEO audit template under it has the ten checks and the order to report them in, ready to copy for a client.

The audit: goorbit.io, 3 November 2026

This is the audit Orbit ran on its own website that morning, unedited. It crawled 124 pages against 123 in the sitemap, and finished.

Check	Result
Can Google index the pages?	Eligible, no blockers
Can AI assistants reach the content?	Reachable: Googlebot, Bingbot, OAI-SearchBot, ChatGPT-User, PerplexityBot and Claude all got in
HTTPS	Valid, certificate good for 36 more days
Sitemap	Found, 123 addresses, complete
Robots.txt	Found, points to the sitemap
llms.txt	Found
Internal links	No problems found
Structured data	No problems found
Speed on a throttled test	Homepage: largest element at 5.5 s, no layout shift, score 80

What the audit found

The two warnings

Issue	Pages	What it means	What we did
Google knows these pages but hasn’t crawled them	6	Google found them and hasn’t fetched them yet, so they can’t rank	Linking to them from stronger pages, then checking again
Linked pages blocked by robots.txt	1	/start is linked from the site and blocked from crawling	Nothing: it’s the signup redirect, and it’s blocked on purpose

Open issues, most serious first

The second warning shows why an audit needs a person. A tool can tell you a page is blocked; only someone who knows the site can say that’s correct.

What makes this a useful SEO audit report

It starts with whether the site can be found at all. Google and AI assistants, in two lines, before any detail.
Every issue has a count, a meaning and a fix. “6 pages” is a job; “indexing could be improved” isn’t.
It says what was left alone, and why. That’s how a client learns to trust the rest.
The speed test is labeled as a test. One throttled load of one page is a diagnostic, not a verdict on real visitors.

The SEO audit template

Report in this order. The first four can stop a page from ranking at all, so they come before anything else.

Check	What to look at	Who fixes it
Indexing	Pages Google hasn’t indexed, and why: not found, not read, or marked noindex	SEO
Crawling	Robots.txt rules, blocked pages, redirect chains	Developer
AI access	Whether Bingbot, ChatGPT, Perplexity and Claude can read the pages	Developer
Status codes	Broken pages and links, and old addresses that still earn links	Developer
Sitemap	Found, complete, and listing only pages that should rank	Developer
Titles and descriptions	Missing, duplicate or cut off in search results	SEO
Internal links	Pages with few links in, or more than three clicks deep	SEO
Structured data	Errors that lose a rich result	Developer
Speed	Real-visitor data first; a lab test only as a diagnostic	Developer
Languages	Language pairs that point at each other	Developer

Ten checks, in the order to report them

How to rank what an audit finds

Blockers first: anything that keeps a page that should rank out of Google or AI answers.
Then money pages: a warning on the pricing page comes before the same warning on an old post.
Then the cheap ones: many small fixes in one template count as one job.
Leave the rest in a list, and say so. A client doesn’t need 400 notices.

What a clean audit doesn’t tell you

A clean audit means nothing is stopping the site from ranking. It doesn’t mean the site will rank: that comes from pages people search for and sites that link to them. So report an audit next to search numbers, never instead of them, as in this real monthly SEO report.

Running this on any site

Orbit’s Health audit runs on its own and keeps a history, so a fix can be checked and a new problem shows up without anyone starting a crawl. For a first look at any site, the free Scan reads its search, its AI answers and 50 pages, with no account. If you want a crawler beside it, see Screaming Frog alternatives.

Open issues, each with what it costs and how to fix it.

Written by

Leon Missoul, Founder
I started the web agency Luniq in 2025 and built Orbit from the software we used to keep our clients’ sites growing after launch. I write about search, AI answers and how to prove what website work earns.

Questions about Technical SEO

robots.txt is a small text file at the root of a site that tells crawlers which parts they may visit. It controls crawling, not indexing: a blocked page can still appear in search if other sites link to it. It is also where a site lets AI crawlers in or keeps them out.

Google Search Console shows how a site appears in Google search and flags indexing problems, for free. For an outside view of any site, Orbit’s free Scan shows whether its buyers find it on Google and in ChatGPT, what AI crawlers can read, and what to fix first, without an account.

An SEO audit checks whether search engines can crawl and index a site, how fast and stable its pages are, whether links break or redirect in chains, and whether titles, descriptions and content match what people search for. The useful part is the order: what to fix first.

A canonical tag is a line in a page’s code that names the preferred version of that page when the same content can be reached at more than one address. Search engines then show that version and credit it with the links.

Core Web Vitals are Google’s three measures of how a page feels to use: how fast the main content loads (LCP), how quickly the page responds to a tap or click (INP), and how much the layout shifts while it loads (CLS). They are one of many signals Google uses.

Technical SEO is the work that lets search engines and AI crawlers reach, read and trust a site: pages that load fast, links that work, a clear sitemap, the right pages open to crawling and the rest kept out. It doesn’t win rankings on its own, but problems here can cost them.

An XML sitemap is a file that lists the pages a site wants search engines to find, often with the date each one last changed. It helps crawlers discover new and updated pages. Submit it in Google Search Console.

A noindex tag tells search engines not to show a page in their results, while still letting them visit it and follow its links. Use it for pages that should exist but not be found through search, such as thank-you pages.