Tech for Retail 2025 Workshop: From SEO to GEO – Gaining Visibility in the Era of Generative Engines

Back to blog

SEO audit example: the report template and its prioritisation table

SEO

Discover Incremys

The 360° Next Gen SEO Platform

Request a demo
Last updated on

1/11/2026

Chapter 01

Example H2
Example H3
Example H4
Example H5
Example H6

You know what an SEO audit covers, and the most concrete question remains: what the document looks like once it is written. Which chapters, in what order, so that it reads for a management team as well as for a developer? Which columns make a recommendation executable? And what do you show to prove that a fix produced an effect? This SEO audit example gives the shape of the deliverable, with a recommendation table template and a review grid to copy.

 

What an audit example has to make visible

 

A useful example does not consist in stacking up metrics: it has to explain what is wrong, why it matters and how to fix it, then turn all of it into a roadmap. The findings change from one site to the next; what is copied is the way the document presents them, proves them and orders them.

 

If the question is still what an SEO audit covers and when to trigger it, that framing is what to read first, with its impact × effort × risk grid; what follows is about the document delivered.

 

The four judgement calls an example makes visible

 

A method describes what to look at; an example shows what has been settled. The guide to perform an SEO audit from framing to delivery says in what order to work; the example says what goes into the document. Four judgement calls become readable in it:

 

  • The level of proof expected: Search Console screenshots, Analytics exports, HTML extracts, lists of affected URLs, before/after.
  • Granularity: anomalies grouped by template rather than page by page, except for business pages, handled by name because a single one weighs more than a batch of secondary pages.
  • Prioritization: separating errors, warnings and remarks, then ordering by impact, effort and risk.
  • Translation into decisions: who does what (SEO, content, dev), when, with which acceptance criteria.

 

The four components of a deliverable

 

The value of a report comes from its structure and its proof, not from its volume. A deliverable is made of four components, visible at a glance:

 

  • Findings: worded in plain language (“discovered URLs are not indexable”, “several pages are competing for the same intent”).
  • Proof: Search Console (coverage, URL inspection, performance), Analytics (engagement, conversions), and observable elements (HTTP status, tags, rendering).
  • Priorities: a severity, then a score using the pillar's impact × effort × risk grid, to make the order arguable, not to produce a mark.
  • Action plan: tasks, owners, dependencies, validation criteria, measurement window.

 

The four hold together: a finding without proof gets contested, proof without a priority piles up, a priority without an owner never leaves the document.

 

The structure of the report: chapters and reading order

 

The report has to be “readable” by several audiences: management (impact and risks), marketing (editorial priorities), the product/tech team (precise tickets). This constraint alone justifies the order of the chapters: the document starts with what interests the person deciding, then works down to the person executing. A report that opens on the methodology forces management to look for its answer on page 12, and it will not look.

 

The executive summary and its four questions

 

The executive summary runs to one or two pages and answers four questions, in this order:

 

  • What is blocking growth? (e.g. incomplete indexing, duplication, slowness on high-intent pages).
  • What can produce a measurable gain quickly? (e.g. snippet optimization to gain CTR, consolidating cannibalizing pages).
  • What are the risks of not fixing it? (e.g. loss of crawl, deindexing, dilution of relevance).
  • What is the 30/60/90-day roadmap? (an execution-driven breakdown).

 

Each answer is quantified on the scope audited, never in the abstract. A market benchmark situates the stake without replacing it: the SEO statistics, with their source and their year, are cited in this chapter, and nowhere else in the report.

 

The seven sections, and the level of detail by audience

 

The body of the report breaks down into seven sections, and this order is the reading order, not the working order:

 

  • 1. Executive summary (expected gains, risks, five priorities).
  • 2. Methodology and scope (data sources, samples, limits).
  • 3. Technical audit (crawling, indexing, performance, structure).
  • 4. Semantic audit (mapping, intent, cannibalization, content).
  • 5. Popularity and link building (link profile, quality, risks), to be calibrated to your sector.
  • 6. Prioritization table (30/60/90-day roadmap).
  • 7. Measurement plan (KPIs, baseline, schedule).

 

The caveat on the fifth section is part of the template: where external authority does not separate the competitors, a detailed link analysis takes up thirty pages for no decision at all. The level of detail is adjusted by audience, without duplicating content:

 

AudienceSections readLevel of detail
Management1 and 6, which read on their ownGains, risks, priorities and schedule
Executors (SEO, content, dev)3 and 4Detail down to URL level
Both together7Shared indicators, baseline and schedule

 

The methodology section: declared scope, sample, limits

 

This is the chapter most often rushed, and the one that separates an honest report from a report claiming to cover everything. It does not choose the scope: it declares it, with its exclusions and the reason for them. Three elements appear in it:

 

  • The segments retained: business pages (categories, products, service pages), blog, support pages, local pages.
  • The templates: grouping by template (listing, product page, article, brand page) is the report's unit of writing, because that is where the root causes sit: you do not list 300 pages with the same anomaly, you group them and quantify the scale.
  • The sample: on a large site, an audit by template paired with a representative sample per segment is worth more than a superficial exhaustive sweep; on a small site, completeness is often reachable and is declared as such.

 

The formula to remember comes down to one line: one template diagnosis is one fix that improves dozens or hundreds of URLs.

 

The point almost no report writes down is what was not looked at. An inaccessible staging environment, a section being rebuilt, partial Analytics access: each of these limits changes the reach of a conclusion; keeping quiet about them lets people believe that the report's silence means the absence of a problem. The objectives are declared in the same place, as hypotheses to be verified, never as a promised result.

 

The prioritization table: columns, scoring, arbitration

 

This is the most reusable part: the one that decides whether the report will produce tickets or stay a PDF. A recommendation table is not a sorted list of anomalies: it is the point where each finding becomes a line of action, with its proof, its owner and its closing condition. The columns are copied; what changes is the discipline with which they are filled in.

 

What each column has to carry to be verifiable

 

Nine columns are enough, and none of them is decorative; three of them take up the impact × effort × risk grid:

 

  • Finding.
  • Type (technical, semantic, UX, popularity).
  • Proof (GSC/GA4 link, export, screenshot).
  • Estimated impact, effort, risk (detailed in the table below).
  • Recommendation.
  • Owner.
  • Validation (how to check that it is fixed).

 

The last one makes the table executable: without it, nobody will be able to say whether the line is closed. A badly filled column produces a precise blockage, and it is always the same ones that empty out when the document is written in a hurry:

 

ColumnWhat it has to carryWhat makes it verifiableThe frequent mistake
FindingWhat is observed, and on exactly which scopeA named template or segment, and the number of URLs affectedA generality with no scope: “internal linking could be better”
ProofThe source that makes the observation reproducibleA dated export, plus three example URLs to inspectA pointer to the tool with no export and no date
Estimated impactWhat moves if it is fixed, and on which indicatorA named indicator, attached to the pages concernedA “high” without proof, which pushes the line ahead
EffortThe workload, and above all what it depends onThe dependencies named: template, release cycle, third partiesA “low” that ignores a quarterly release
RiskWhat the fix can break on deploymentRegressions and side effects namedAn empty box: the risk is discovered in production
OwnerThe person or the team that executesAn identified team name, accepted before deliveryAn empty box or “to be defined”: the line will never start
ValidationThe observable fact that closes the lineA status, a tag, an indexing report to consult againAn intention: “improve indexing” cannot be checked

 

The rule that decides between two lines

 

To order the lines, a score alone quickly shows its limit: two lines can get it for opposite reasons, one affecting few pages but the right ones, the other many with no consequence. Classification into Errors / Warnings / Remarks, the severity that tools flag, therefore comes first: it separates what stops the site from existing in the index from what improves it at the margin.

 

The impact × effort × risk grid only comes into play inside each category, as the pillar builds it; the template only takes over its arbitration rule. The objective is not to “push the score up”, but to prevent a critical error from being neutralized by marginal optimizations. In practical terms, a 404 on a high-conversion page comes before a missing alt attribute on old content.

 

A finding documented end to end

 

Each table row points to a finding written in a short, repeatable template, which applies just as well to an indexing anomaly as to a content problem:

 

  • Problem: “X is preventing Y pages from being indexed”.
  • Proof: GSC export, three example URLs, an extract of the code or the rendering.
  • Root cause: template, redirect rule, noindex tag, inconsistent canonical…
  • Fix: technical action, owner and deadline.
  • Validation: how to confirm it in Search Console.

 

Turning it into a ticket, acceptance criteria included, follows the pillar's method. What matters here is that none of the five lines stays empty.

 

A technical finding and a semantic finding, written in the same template

 

The first concerns a listing template, the second content pages left out of the index:

 

LineTechnical findingSemantic finding
ProblemA batch of URLs from the sitemap does not enter the indexPages stay at “Crawled – currently not indexed”
ProofDated indexing export, three URLs inspected, code extractStatus recorded, zero impressions, actual content of three pages
Root causeTemplate canonical pointing to the parent pageSections that all competing results cover, missing
FixRule changed in the template, by development, on a set dateUseful sections added, reindexing requested, by editorial
ValidationThree control URLs re-inspected, then the gap closed across the batchMove to “indexed”, then impressions on the target queries

 

On the technical side, the cause is fixed in a single place, for the whole batch. What is reproduced is not the check, it is the way of writing it; the list of points to check (crawl directives, statuses, redirects, canonicals, rendering, orphan pages) belongs to the detail of a site's technical SEO audit checks and the order to run them in.

 

On the semantic side, this status is frequent when the content is judged too thin against the query; a FAQ is only added where the questions genuinely exist. The finding connects useful content, indexing and performance in a single verifiable line. Deciding whether to create a page, enrich one or merge several is a judgement call in its own right, which belongs to the semantic audit's matching of page to query, cannibalization included. The report carries its conclusion, not its demonstration.

 

Before / after: what the report shows to prove the effect

 

Without a before/after, an audit stays a photograph. On the day it is delivered, the report cannot contain the “after”: it contains the reading that makes the after readable, and the commitment to replay it identically. That is the role of the measurement plan; checking the effects over time follows the pillar's method.

 

The baseline: what you record before fixing

 

The discipline is to establish a baseline before the fix and measure the after. The report attaches three items, put together on the site in its initial state:

 

  • The Search Console before/after exports: pages, queries, errors, indexing, over an explicitly stated reference period.
  • The list of URLs changed, and the mapping of 301 redirects if addresses change.
  • The sample of key URLs inspected (indexing, canonical chosen, rendering), the same ones that will be re-inspected afterwards.

 

On the Analytics side, the initial reading covers engagement and conversion, segmented by organic landing page. These items cannot be reconstituted after the fact: once the fix is deployed, the previous state has disappeared from the interfaces.

 

The measurement window and what you replay

 

You replay exactly the same reading, on the same basket of URLs and queries: changing the scope between the before and the after is the most common way of concluding wrongly. The disappearance of the finding is checked from the re-crawl onwards; the effect on visibility is read over several weeks, the time it takes for indexing to settle on the template.

 

For reworking the title and meta description tags of a template, the initial finding records missing tags, duplicates and unsuitable lengths (usual benchmarks: in the order of 60 characters for the title, 160 for the meta description). The indicator to replay is CTR at comparable position, not raw traffic: a position gain occurring in the same week would make attribution impossible. Hence the closing instruction: annotate the deployment dates.

 

The reusable template and its review grid

 

To turn the report into a template you take out as it is, two items are enough: a checklist of the families of checks and a review grid before sending. They are safety nets, to be run over a document already written.

 

The six families of checks

 

The checklist falls into six families, each becoming a sub-part of the report when it carries findings:

 

  • Crawling: what the crawlers reach, and what stops them.
  • Indexing: what enters the index, what is kept out of it and on what grounds.
  • Technical quality: consistency of the signals, statuses, page structure.
  • Content: intent covered, completeness, uniqueness of the reference page.
  • Measurement: data sources, baseline, validation indicators.
  • Citability (GEO): what makes a page usable as a source by generative engines.

 

The table's “Type” column takes up these families: you read the report by family to check the coverage, by priority to decide. The sixth is named even when it has not been investigated: a family declared out of scope is a piece of information, a family absent from the contents page reads as an oversight.

 

Precision, traceability, non-redundancy, measurability

 

On the finished document, four criteria head off most of the reproaches a report gets:

 

  • Precision: name URLs, templates, sections, not generalities.
  • Traceability: every recommendation has to point to a piece of proof.
  • Non-redundancy: group the findings by root cause, avoid repeating the same problem across twenty pages.
  • Measurability: define a validation criterion.

 

Reviewed this way, a report often loses a third of its volume and gains its ability to produce tickets. The cost of that discipline lies elsewhere: copying findings, proof and priorities by hand from an export into a spreadsheet.

 

Continue reading

 

Depending on what you are missing to get from the template to the document:

 

  • You have the shape of the report, but nothing to produce its proof. SEO audit tools are chosen according to what each one produces.
  • The report is delivered to you by a third party and you have to sign it off before paying. The deliverables of an agency SEO audit are detailed there.
  • The fixes are delivered and the before/after is no longer enough. SEO tracking puts indicators, annotations and the monitoring of gains in place over time.
  • You do not yet know what your site is made of. Website analysis maps the templates, the page roles and the traffic segments.

 

Gathering findings, proof and priorities into a single exportable record is precisely the task covered by the audit and mapping module.

 

FAQ on SEO audit examples and templates

 

How do you present audit results in a clear and actionable way?

 

A clear report opens with a decision-driven executive summary, then presents the findings classified by severity and ordered by impact, effort and risk, with their proof. It ends with a dated roadmap, with owners and validation criteria.

 

Is there a reusable template across types of site?

 

A reusable template exists, provided it stays adaptable. The structure “executive summary → methodology → technical → semantic → prioritization → measurement” works for most sites. What changes is the level of detail, the sampling according to volume and the weight of the popularity section.

 

What does a complete audit look like (format, chapters, deliverables)?

 

A complete audit is a document in seven chapters, which includes a prioritization table. It delivers a diagnosis with example URLs, a roadmap connected to the objectives and a validation criterion for each recommendation. Its value comes from its structure and its proof, not from its volume.

 

What is the difference between a technical analysis and a semantic analysis?

 

Technical analysis checks that the engines can crawl, render and index the pages: structure, HTTP statuses, directives. Semantic analysis checks that each page targets a clear intent, with relevant and differentiating content. In the report, both follow the same finding template and the same prioritization grid.

 

How many pages should you audit to get a reliable sample?

 

The number of pages to audit depends on the size of the site. A large site is audited by template, with a representative sample per segment; a small site can often be audited exhaustively. In both cases, the report's methodology declares the scope and its limits.

 

How do you turn a list of findings into a prioritization?

 

You first classify the findings into Errors / Warnings / Remarks, then order them by impact, effort and risk inside each category. What unblocks crawling and indexing comes first, then what affects high-value pages. A critical error always comes before a minor optimization.

 

Which KPIs should you track after the audit to validate the gains?

 

After the audit, you track indexing, errors, impressions, clicks, CTR and positions in Search Console, and engagement and organic conversions in Analytics. Validation compares a baseline recorded before the fix with the same reading replayed after deployment, with the deployment dates annotated.

Discover other items

See all

Next-Gen GEO/SEO starts here

Complete the form so we can contact you.

The new generation of SEO
is on!

Thank you for your request, we will get back to you as soon as possible.

Oops! Something went wrong while submitting the form.