SEO Audit Template: The Enterprise Playbook

Quick Answer

An SEO audit template is a ready-made framework for reviewing a website’s search health: the checks to run, the order to run them in, the evidence to collect and the way to record and rank what you find. This free SEO audit template is built for large websites. It gives you a 20-step checklist, a scoring sheet that ranks every finding by reach, impact, confidence and effort, an engineering ticket template and a log-file starter query, as a PDF playbook and an Excel workbook. Use it to run an audit that ends in a short, ranked roadmap your teams will ship, rather than a long list of crawler warnings.

Key Highlights

• A 20-step process that covers scoping, data collection, crawling, indexation, rendering, content, links, AI search and governance.
• An Excel workbook with owners, status dropdowns and a scoring sheet whose formulas sort findings into do now, next sprint and backlog.
• A ticket template that turns each finding into work engineering teams accept, with evidence and acceptance criteria.
• A BigQuery starter query that shows how Googlebot spends its crawl across your templates.
• Guidance on adapting the template for smaller sites, Google Sheets and other tools.

What is an SEO audit template?

An SEO audit template is a reusable structure for reviewing how well a website can be crawled, indexed, understood and ranked by search engines. It lists the checks to run, the data each check needs, and the format for recording results, so every audit covers the same ground and nothing important gets skipped. A good one saves days of setup on every project and makes results comparable from one audit to the next.

Most free templates are built for small sites. They work well for a 50-page brochure site, where you can review every page by hand and fix problems one at a time. They break down on large websites, where a single template bug can affect 80,000 pages, where Google cannot crawl everything, and where fixes have to compete for engineering time. On those sites the hard part is not finding problems. It is deciding which ones matter and getting them shipped. This template is designed around that problem.

Why use an SEO audit template instead of starting from scratch

Every audit that starts from a blank page repeats the same setup work: deciding what to check, building spreadsheets, writing the scoring logic and formatting the report. An SEO audit template removes that work, so the first day goes on scoping and data requests instead of building tools. It also makes audits consistent. When the same structure is used every quarter, results can be compared over time, and anyone on the team can pick up where someone else left off.

The bigger benefit is focus. Without a structure, audits drift toward what the crawler reports most loudly, which is usually volume rather than value. A template with a scoring model built in keeps the work tied to revenue templates and evidence, and forces each finding to justify its place on the roadmap. That is what turns an audit from a report into a plan.

Finally, a shared SEO audit template helps the people who receive the results. Engineering, content and leadership teams learn to read the same format, so each new audit lands faster and generates fewer questions.

What a good SEO audit template should include

Whether you use this one or build your own, check that any SEO audit template covers the following. If one of these is missing, the audit will either miss problems or struggle to get them fixed.

• Scope and goals: a place to record which page types and markets matter, so priorities follow the business.
• Data sources beyond a crawler: logs, Search Console and analytics, since a crawler only shows what a bot could find.
• Template-level analysis: grouping by page type, so findings scale to the whole site.
• A prioritization model: a clear way to rank findings by value and effort, not by tool severity labels.
• Ownership: an owner and status for every step and every finding.
• A ticket format: so findings turn into work that delivery teams accept.
• Baselines and follow-up: starting values and re-measurement dates to prove results.
• Governance checks: so the same problems do not return with the next release.

Free templates versus paid audit platforms

Paid platforms such as Botify, Lumar, Oncrawl and the large SEO suites automate crawling, log analysis and monitoring at scale, and they are worth the cost on very large sites. They do not replace an SEO audit template, though. Tools collect and display data; the template decides what to look at, how to rank it and how to hand it to the teams who fix it. Most enterprise teams use both: a platform for the data and a template for the method. If you are choosing a platform, start with the template so you know which data you actually need.

What is inside the template

How to use the 20 steps

The SEO audit template runs in five stages. Steps 1 and 2 set the scope, steps 3 to 6 collect data, steps 7 to 18 diagnose, step 19 builds the roadmap and step 20 protects the results. Work through them in order the first time; later audits can skip straight to the stages that matter most for your site.

1. Write a one-page scope

Start with the business, not the crawler. List the page types that drive revenue or leads, the markets and properties in scope, any migrations, redesigns or traffic drops in the last 18 months, and the teams who can change templates, content, redirects and robots rules. Keep it to one page. It focuses the work, stops the audit turning into a catalog of minor issues, and gives you the context to explain later why each finding matters to the business.

2. Request data access on day one

Ask for server logs, Search Console access on every property, analytics, staging environments, CMS settings and CDN configuration in the first meeting. Log access is the most common delay on large audits, because security and infrastructure teams often need weeks to approve it. Record each request in the workbook with an owner and a date, and chase it while you work on the steps that do not need it.

3. Export verified Googlebot logs

Pull 30 to 90 days of requests and keep only those from verified Googlebot, checked by reverse DNS as described in Google’s guide to verifying Googlebot. Keep the URL, status code, bytes, response time and timestamp. Fake bots claiming to be Google are common, and including them will distort every crawl figure that follows.

4. Export Search Console through the API

The Search Console interface caps exports at 1,000 rows, which is not enough for a large site. Use the Search Console API or the bulk export to BigQuery to pull performance by page and query, the page indexing report, crawl stats and sitemap data. Save the exports with dates so you have a clean baseline to compare against after fixes ship.

5. Run segmented crawls per template

Instead of one giant crawl, run one crawl per major section or template, such as products, categories, articles and locations. Turn on JavaScript rendering for templates that need it. Segmented crawls finish faster, are easier to compare, and map directly onto the teams who own each part of the site.

6. Build the master URL table

Join crawl data, logs, Search Console and revenue data on URL, and tag every row with its template and section. This one table, with columns for crawl hits, indexing status, clicks, conversions and template, is the foundation of every later step. Most of the insight in an enterprise audit comes from comparing columns in this table, not from any single tool.

7. Measure crawl waste

Use the starter query to group Googlebot requests by pattern. If parameter URLs, filter combinations, internal search pages, redirects or error pages take a large share, crawl capacity is being spent on pages that will never earn traffic. Google’s own guidance on managing crawl budget for large sites explains why this matters mainly on very large or fast-changing sites.

8. Check crawl frequency on revenue templates

Compare how often Googlebot visits your money templates against low-value ones. If important product or service pages are crawled once a month while filter URLs are crawled daily, changes to price, stock or content will be slow to show in search. Record the average crawls per URL per month for each template in the workbook.

9. Compare wanted, submitted and indexed URLs

List the URLs you want indexed, the URLs in your sitemaps and the URLs Google reports as indexed. Each gap has a cause. Pages marked discovered but not indexed usually point to weak internal links or crawl priority; pages crawled but not indexed usually point to thin or duplicate content. Write down the reason for each gap, by template.

10. Audit canonicals and hreflang

Compare the canonical you declare with the canonical Google selects, using samples of 50 to 100 URLs per template in the URL Inspection tool. For international sites, check that hreflang sets are reciprocal, point to canonical, indexable URLs, and include a self-reference. Conflicts here are common after migrations and on sites with several URL formats.

11. Diff raw and rendered HTML

For each key template, compare the HTML the server sends with the page after JavaScript runs. Main content, internal links, titles, canonicals, meta robots and structured data should all be present in the initial HTML. If they appear only after rendering, Google may index them late, and many other crawlers, including several AI crawlers, may not see them at all.

12. Review Core Web Vitals by template

Use field data from the Chrome UX Report and the Core Web Vitals report in Search Console, grouped by URL pattern. The Core Web Vitals documentation sets the thresholds for Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Focus on templates that combine poor scores with high organic traffic, since that is where improvements pay back.

13. Score content quality per template

For each template, review a sample of high-traffic, mid-traffic and zero-traffic pages and compare them with the pages ranking in the top three for their main queries. Check whether titles and headings match search terms, whether each page has enough unique, useful content, and whether authorship and sourcing are clear. Score each template from 1 to 5 in the workbook.

14. Find duplication and cannibalization

Look for groups of pages competing for the same query, which is common when product, category, blog and regional teams publish independently. Also look for thousands of pages that share the same boilerplate with one variable changed. For each case, decide whether to improve, merge, redirect or noindex, based on traffic, links and business value rather than word count alone.

15. Validate structured data

Check that each template outputs the right markup for its page type, that it validates without errors, and that every value matches what users can see. Mismatched prices, ratings or availability can lead to manual actions. The schema.org vocabulary lists the available types, and Google’s rich result documentation sets out which ones are eligible for enhanced results.

16. Map click depth, orphans and link flow

Build a link graph from your crawls. Flag important pages more than three or four clicks from the homepage, orphan pages that receive traffic or crawl hits but no internal links, pages with strong backlinks that link nowhere useful, and templates that rely on generic anchors such as “learn more”. Template-level link modules, breadcrumbs and hub pages usually fix these faster than page-by-page edits.

17. Recover broken backlinks

Find pages that still have external links but now return a 404 error or sit at the end of a redirect chain. Restore them or redirect them in one hop to the best current equivalent. This is often the fastest authority win in an audit, because the links already exist and only the destination needs fixing.

18. Check AI Overview presence and crawler access

List the key queries that trigger AI Overviews or AI answers, note whether your pages are cited, and check which AI crawlers your robots.txt allows or blocks on every host. These systems still depend on crawlable, indexable, well-structured content, so most fixes overlap with earlier steps, but the review shows where you are missing out.

19. Score and ticket every finding

Enter every finding in the SEO audit template scoring sheet and let the formulas rank them. Write a ticket for each finding above the line using the ticket template: the problem, affected templates, evidence, exact change, acceptance criteria, test method and success metric with its baseline. This is the step most audits skip, and it is the one that decides whether anything changes.

20. Review release governance and monitoring

Check how changes reach production. Is there an SEO review step for templates, redirects and robots rules? Are there automated checks in staging for noindex tags, canonicals and status codes? Is there one owner for robots.txt, sitemaps and redirect maps? Are there alerts when indexed pages, crawl activity or organic traffic drop? Fixes without these controls tend to come back with the next release.

An example one-page scope brief

Step 1 asks for a one-page scope. Here is what a good one looks like for a mid-sized B2B software company, so you can see the level of detail that works.

• Goal: grow organic demo requests from solution and integration pages by 30 percent in two quarters.
• In scope: the main domain, the docs subdomain and the US and UK folders. The careers site and the community forum are out of scope.
• Revenue templates: solution pages, integration pages, pricing and the comparison hub.
• Recent changes: moved from a legacy CMS to a headless setup eight months ago; organic sign-ups fell 18 percent afterwards.
• Owners: web platform team for templates and redirects, content team for solution pages, docs team for the subdomain.
• Capacity: two engineering sprints available next quarter for SEO fixes.

With this brief in hand, the audit can focus on the headless migration, rendering on the new templates and the revenue pages that matter, instead of spreading effort across the whole site.

How the priority score works

Every finding gets a score from 1 to 5 on four factors. The workbook calculates the result for you.

Score = Reach x Impact x Confidence / Effort. A score of 25 or more means do it now, 10 to 24 means next sprint, and anything lower goes to the backlog. A product template missing its canonical tag (reach 5, impact 3, confidence 4, effort 1) scores 60 and goes straight to the top. Missing alt text on blog images (2, 1, 5, 2) scores 5 and waits.

The model is deliberately simple. Its job is not to be precise but to force a conversation about evidence and effort before anything goes on the roadmap. Teams that argue about whether a finding is a 3 or a 4 on impact are already doing better than teams who sort by the severity labels a crawler assigns.

A worked example of the scoring sheet

Here is how three typical findings from a large retail site would be scored and ranked. The numbers are illustrative, but the pattern is common.

The first finding becomes a ticket to block low-value filter combinations in robots.txt and remove crawlable links to them, following Google’s guidance on managing faceted navigation. The second becomes a ticket to add a new arrivals module to category pages and split the product sitemap by date. The third waits until the higher-scoring work ships.

Writing tickets engineering will accept

A finding only turns into a fix when someone builds it, and engineering teams have their own roadmaps. The ticket template is designed to remove the most common reasons a request gets parked. State the problem in one sentence. Name the affected templates or URL patterns, not individual URLs. Attach the evidence: a log chart, a Search Console export or a crawl sample. Describe the exact change, such as the tag, header or rule to add. Write acceptance criteria that a tester can check, and say how success will be measured, with the current baseline.

Keep each ticket to one change. Bundled tickets stall because one part is easy and another is hard. Link related tickets instead, and give each its own priority score so the easy, high-scoring work ships first.

How long an audit takes

On a site with 50,000 to 500,000 URLs, most teams finish in four to eight weeks. Week one goes on scoping and access. Weeks two and three cover data collection and joining datasets. Weeks three to five are diagnosis. Weeks five and six are scoring and ticket writing, and the final two weeks go on presenting results and handing work to delivery teams. On a smaller site with a few thousand pages, one person can usually complete the checklist in one to two weeks.

Adapting the template for smaller sites

The template is built for scale, but it works on smaller sites with a few changes. Below about 1,000 pages you can usually skip log analysis and run one full crawl instead of segmented ones. Template sampling becomes page review, since you can look at every important page directly. The scoring sheet and ticket template still help, because even small teams have more fixes than time. If you mainly need page-level checks, our SEO audit checklist covers them in detail.

Using it in Google Sheets and other tools

The workbook opens in Excel, and you can upload it to Google Drive and open it with Google Sheets; the formulas and dropdowns carry over. The log query is written for BigQuery, but the logic, grouping requests by URL pattern and counting status codes, works in any SQL warehouse or even a spreadsheet pivot table for small log samples. Crawl exports from Screaming Frog, Sitebulb, Lumar, Botify or Oncrawl can all be pasted into the master URL table, as long as each row has a URL column to join on. Our review of enterprise SEO software compares the main crawlers and log tools.

Common mistakes this playbook helps you avoid

• Reporting every crawler warning. A list of 400,000 issues hides the three that matter. The scoring sheet forces every finding to earn its place.
• Skipping server logs. Without logs you are guessing how Google spends its crawl. The starter query gets you a first answer in under an hour.
• Fixing pages one by one. On large sites one template bug repeats across thousands of URLs. The checklist works at template level so one ticket fixes the whole section.
• Findings with no owner. A recommendation without an owner and a ticket rarely gets shipped. The workbook has an owner column on every step and every finding.
• No baseline. If you cannot show the numbers before the fix, you cannot prove the work paid off. Each ticket records a success metric and its starting value.
• Treating it as a one-off. Problems come back with the next release unless the process changes. The final step reviews governance so fixes stay fixed.

What to do after the audit

Share three versions of the results. Executives need a one-page summary of what is at risk, what the fixes are worth and what resources are required. Engineering needs the tickets with evidence and acceptance criteria. Content and regional teams need guidelines and examples. Then re-measure 30, 60 and 90 days after each fix ships: crawl activity on the affected templates, indexed pages per sitemap, impressions, clicks and conversions. Run a lighter version of the checklist every quarter and the full process once a year or before any migration. Our website migration SEO guide covers the extra checks a migration needs, and our guide to SEO reporting covers dashboards for tracking results.

Who this template is for

• In-house SEO leads at companies with large sites who need a repeatable audit process and a way to win engineering time.
• Agencies and consultants who audit enterprise clients and want a structure that ends in a roadmap, not a report.
• Product and engineering managers who own a site’s templates and want to understand what SEO teams will ask for.
• Marketing leaders who need to know what is holding organic growth back and what it will take to fix.

How to use it alongside our guides

The template is the working file; the guides explain the method. Start with our enterprise SEO audit guide for the full process and a worked example. Use our enterprise technical SEO guide when findings point to rendering, faceted navigation or release testing, our JavaScript SEO guide for rendering problems, and our internal linking guide when the link graph needs work. For the bigger picture on running search at scale, read our guide to enterprise SEO.

Key Takeaways

• This free SEO audit template turns an audit into a ranked roadmap: 20 steps, a scoring sheet, a ticket template and a log query.
• Collect data first: logs, Search Console, segmented crawls and revenue, joined in one URL table tagged by template.
• Diagnose at template level, so one ticket fixes thousands of pages.
• Rank findings by reach, impact, confidence and effort, and write a ticket with an owner for every finding above the line.
• Review governance and re-measure at 30, 60 and 90 days so fixes stay fixed and results are proven.

Frequently asked questions

Is the SEO audit template free?

Yes. Fill in the form and we email you the PDF playbook and the Excel workbook. There is no cost and no trial.

Does it work for small websites?

Yes, but it is designed for larger sites. On a site with a few hundred pages you can skip the log analysis and template sampling steps and use the checklist and scoring sheet on their own.

Which tools do I need?

A crawler such as Screaming Frog, access to Google Search Console and your analytics, and ideally server logs. The log query is written for BigQuery but is easy to adapt to other warehouses.

Can I use it in Google Sheets?

Yes. Upload the Excel file to Google Drive and open it with Google Sheets. The formulas and dropdowns carry over.

How is this different from an SEO audit checklist?

A checklist lists what to check. This template also covers how to collect the data, how to rank what you find and how to turn findings into tickets, which is what large sites need to get fixes shipped.

Why do you ask for a WhatsApp number?

So we can follow up once if you want help running the audit. We do not share your details, and you can tell us not to contact you.

Can you run the audit for us?

Yes. Our enterprise SEO services include full audits with log analysis, roadmaps and support while your teams ship the fixes.