Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Technical SEO report: what it should include, with a template

Updated · 8 min read

Short answer A useful technical SEO report answers five questions: can Google find your pages, does it index them, do they load fast for real visitors, is the site secure and penalty-free, and what gets fixed next. Each finding should name the page, why it matters, who fixes it and by when. A health score alone isn't a report.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

What should a technical SEO report include?

Eight sections, in this order, plus structured data (code that labels your business details for search engines) if your site uses it. Most of the numbers come free from Google Search Console and PageSpeed Insights, so a report built on them is easy for you to check yourself.

SectionThe question it answersWhere the data comes from
1. SummaryWhat's broken, what it costs, what's next?The sections below, in plain words
2. IndexingWhich of my pages are in Google, and why are others not?Search Console: Page indexing report, URL Inspection
3. Crawl accessCan Google reach the pages I want found?robots.txt, noindex tags, Sitemaps report
4. Errors and redirectsDo links lead to dead or looping pages?Page indexing report, a site crawler
5. DuplicatesIs Google showing the version of each page I want?URL Inspection (Google-selected canonical)
6. Speed and mobileDo real visitors get a fast, stable page on a phone?Search Console: Core Web Vitals report; PageSpeed Insights
7. SecurityIs the site on HTTPS, unhacked and free of penalties?HTTPS, Security issues and Manual actions reports
8. Fix listWho fixes what, by when, and did last month's fixes work?The auditor's plan

What goes in each section?

1. Summary

Three to five lines a busy owner can read in a minute: the biggest problems, which pages they touch, and whether things got better or worse since the last report. If the summary leads with a score out of 100, ask what moved it and which customer pages are affected.

2. Indexing

The count of pages Google has indexed (stored and can show), and the pages it hasn't, grouped by reason. Search Console's indexing report "shows which pages have errors, warnings, or are excluded from Search" (Google Search Central: Get started with Search Console). The report should separate pages that are excluded on purpose, like thank-you pages or old redirects, from service pages that should rank but don't. Only the second group needs fixing. For what each "not indexed" reason means, see Crawled or discovered, currently not indexed.

3. Crawl access

Whether your robots.txt file or a noindex tag blocks anything you want found, and whether your sitemap is submitted and read. Two common mix-ups a good report catches:

"It is not a mechanism for keeping a web page out of Google." (Google Search Central: Introduction to robots.txt)

To keep a page out of results, Google says to use `noindex` or a password instead (same page). And a sitemap helps but promises nothing: Google calls submitting one "merely a hint" (Google Search Central: Build and submit a sitemap).

4. Errors and redirects

Broken links on your own pages, pages that show "not found" but return a success code (a soft 404), and redirect chains. Not every 404 is a problem. Google says 4xx errors other than 429 "have no effect on crawl rate" (Google Search Central: HTTP status codes and network errors). A page you deleted on purpose can stay gone. The report should flag only dead pages that still get links, visits or ads.

5. Duplicates

Pages Google treats as copies, and which version it picked to show. Your site can suggest a preferred version (the canonical), but "Google might choose a different canonical" than the one you set (Google Search Central: Fix canonicalization issues). The check is the URL Inspection tool in Search Console. Duplicates aren't a penalty: Google says duplicate content "is not a violation of our spam policies" (Google Search Central: SEO Starter Guide).

6. Speed and mobile

The three Core Web Vitals, from real visitors (field data), for mobile first. Google indexes "the mobile version of a site's content" (Google Search Central: Mobile-first indexing best practices).

MetricWhat it measuresGood
LCP (Largest Contentful Paint)How fast the main content showsWithin 2.5 seconds
INP (Interaction to Next Paint)How fast the page reacts to a tapUnder 200 milliseconds
CLS (Cumulative Layout Shift)How much the page jumps while loadingUnder 0.1

Thresholds: Google Search Central: Core Web Vitals. Google says "Core Web Vitals are used by our ranking systems," but good scores don't guarantee you'll rank at the top (Google Search Central: Understanding page experience).

Field data in PageSpeed Insights covers "the previous 28-day collection period" of real Chrome users. Lab data, from a single test run, is for finding the cause (PageSpeed Insights: About). Small sites often have too few visitors for field data. Then the report should say so and fall back on lab tests like Lighthouse, which "has its own panel in Chrome DevTools" (Chrome for Developers: Lighthouse overview). For what speed does and doesn't do for ranking, see Core Web Vitals: does website speed affect Google ranking?.

7. Security

Three yes-or-no lines: every page loads on HTTPS (Search Console's HTTPS report checks this, per Google Search Central: Understanding page experience), the Security issues report is empty, and the Manual actions report is empty. The Security issues report "shows warnings when Google finds that a website might have been hacked" (Google Search Central: Get started with Search Console). A manual action means a Google reviewer penalized the site, which outranks everything else on the list. See Google manual action: how to find it, fix it and ask for review.

8. Fix list

The part you actually pay for. One row per problem, sorted by impact on pages that bring customers.

The template: copy this

Use one table per report. Keep last month's report beside it.

FieldWhat to write
Report date and periode.g. October 1–31, 2026
Summary3–5 lines: top problems, pages affected, better or worse than last time
Pages indexedNumber now, number last report
Important pages not indexedEach URL, Google's reason, planned fix
Blocked by robots.txt or noindex by mistakeURLs, or "none"
SitemapSubmitted? Last read date? Errors?
Broken links and redirect chainsOnly ones on pages people use
DuplicatesPages where Google picked a different version than you wanted
Core Web Vitals (mobile, field data)LCP, INP, CLS: pass or fail, worst page groups
HTTPS, security issues, manual actionsYes or no for each
Structured data errorsFrom the rich result reports, if used
Fix listIssue, page, why it matters, who fixes, effort, due date, status
Last report's fixesDone or not, and what changed after

What should I ask for in a technical SEO report?

These questions separate a report that drives work from one that fills pages:

  • Which pages make money? Ask that every issue be tied to your service, booking or contact pages first. A broken link on a 2019 blog post can wait.
  • Is speed data from real visitors or a lab test? Real-visitor (field) data is what Google's Core Web Vitals report uses.
  • What changed since last time? Without the previous numbers, you can't tell progress from noise.
  • Who fixes each item, and by when?
  • Did last month's fixes work? Each report should close the loop on the last one.
  • Is anything on the list something Google says doesn't matter? See the next section.

Traffic, calls and leads belong in a separate monthly performance report. See Is my SEO working? The numbers to check each month.

Red flags: outdated or empty items in a report

You seeThe fact
FID (First Input Delay) as a speed metricINP replaced FID in Core Web Vitals on March 12, 2024 (Google Search Central Blog: Introducing INP)
A Mobile Usability report or Mobile-Friendly Test resultGoogle retired both starting December 1, 2023 (Google Search Central Blog: More on page experience in Search)
Sitemap "priority" or "changefreq" errorsGoogle says it ignores both values (Google Search Central: Build and submit a sitemap)
"Multiple H1 tags" or "headings out of order" as a serious errorGoogle: "no magical, ideal amount of headings" and order doesn't matter (Google Search Central: SEO Starter Guide)
A promise that adding schema will win stars in results"Google does not guarantee that your structured data will show up" (Google Search Central: General structured data guidelines)

How often should a technical SEO report run?

Monthly is enough for most small business sites. Google suggests checking Search Console "around once every month, or when you make changes to the site's content," and it emails you when it finds new issues (Google Search Central: Get started with Search Console). Run an extra report after a redesign, a platform move or a sudden traffic drop.

Example

A plumber's first report

Summary: 40 pages indexed out of 52. Of the 12 left out, 9 are tag pages excluded on purpose, and 3 are city service pages Google calls duplicates of each other. Mobile LCP fails at 4 seconds because of an uncompressed hero photo. Fix list: rewrite the 3 city pages so each is distinct (owner, 2 weeks), compress the photo (web developer, 1 day).

A dental office's monthly report

Everything passes except INP on the booking page, slowed by a chat widget. The report shows last month's fix (a redirect for an old implants page) worked: that page is now indexed. One new line: remove or delay the widget, then re-check field data after 28 days.

A report to push back on

A 30-page export shows a "health score" of 62, 300 "issues," and FID warnings, with no URLs for the top problems and no due dates. The owner asks for the eight sections above, limited to service and booking pages.

FAQ

Can I make a technical SEO report myself?

Yes, for a small site. Search Console, PageSpeed Insights and Lighthouse are free and cover most of the template. See Google Search Console for a small business.

Is a technical SEO report the same as an SEO audit?

An audit is the one-time deep check that finds the problems. The report is the repeated summary that tracks them and the fixes.

How long should the report be?

Long enough to list each real problem with its page and owner. For a small business site that's usually two or three pages, not thirty.

Does a perfect technical report mean I'll rank?

No. Technical health lets Google find and show your pages; it doesn't make them the best answer. Google says good page experience "doesn't guarantee that your pages will rank at the top" (Google Search Central: Understanding page experience).

Different for you?

Keep learning

NextSearch Console technical SEO audit: a free walkthrough, in orderA free technical SEO audit using only Google Search Console: which reports to open, in what order, what a pass looks like, and which ones a small site can skip.

Do it yourself

Crawlability checklist: make every page reachable by GoogleA crawlability checklist for a small business site: find orphan pages, robots.txt blocks, broken links, redirect chains and server errors, with free tools.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: Get started with Search Console
  2. Google Search Central: Understanding page experience
  3. Google Search Central: Core Web Vitals
  4. Google Search Central Blog: Introducing INP to Core Web Vitals
  5. Google Search Central Blog: More on page experience in Search (April 2023)
  6. PageSpeed Insights: About
  7. Google Search Central: Introduction to robots.txt
  8. Google Search Central: Build and submit a sitemap
  9. Google Search Central: HTTP status codes and network errors
  10. Google Search Central: Fix canonicalization issues
  11. Google Search Central: Mobile-first indexing best practices
  12. Google Search Central: General structured data guidelines
  13. Google Search Central: Introduction to structured data markup
  14. Google Search Central: SEO Starter Guide
  15. Chrome for Developers: Lighthouse overview