consultation →
/ SEO and GEO audit

SEO audit report example with a GEO review

Type: Anonymized client audit · Mode: Client sources, public version · Period: Recent 28 day window, exact dates withheld

Start with what to fix, verify and protect. Then inspect the sources, evidence and team tasks. Open the technical register only when you need the detail.

1 · fix1 · verify1 · develop
About this report and how to read the metrics

This public version is based on a completed client audit. Brand, URLs and sensitive values were removed. Exact ratios are not published when their components are withheld.

01 / in short

Summary

Decisions for the owner

This is an anonymized excerpt of a real audit, not a growth forecast. The 7/30/90-day plan describes work and acceptance checks; it does not guarantee rankings or sales.

Fix controllable catalog and measurement issues first, then expand content that has verified demand.

  • Fix: Segment commercial pages, weak groups and utility URLs instead of sending one bulk indexation task.
  • Verify: Reconcile the purchase path across the site, tags and analytics. A missing intermediate event does not prove checkout is broken.
  • Protect: Keep working purchase collection and AI crawler access until a parallel check supports a change.
All metrics
Metric Value
URL sources · sitemap, CMS, Search Console, render 4
sampled pages · commercial and template pages 30+
measurement window · exact dates withheld 28 days
AI crawlers · access checked separately 4
02 / audit map

What we checked.

Each tile is one area we checked. Select it to open the finding.

01 / Search Console, sitemap, CMSFixThe catalog needs group decisions, not bulk reindexingBulk submission does not remove root causes. Pages with real demand are counter evidence and must be protected.02 / GA4, tag setup, backend summaryVerifyCheckout detail is incomplete, but sales are not brokenRebuilding tracking could duplicate purchase. Backend and analytics show similar transaction volume.03 / GA4 referrals, robots and HTTP checksDevelopAI traffic is measurable, but too small for a forecastThe channel exists, but low volume and unattributed AI visits do not prove sustainable returns.
03 / where to start

First steps.

First, what every later decision depends on.

  1. 01Segment URLs and debug checkout.→ Every URL group has a keep, improve, merge or exclude decision, and one purchase path is proven without duplicate events.
  2. 02Fix verified template and Merchant issues.→ Every URL in the control sample passes the repeated technical check after publication.
  3. 03Expand pages with demand and measure AI separately.→ Demand, sales and monthly deltas drive priority.

The full plan is in the detailed review below.

04 / findings

Every finding in three lines.

Numbers and evidence for your marketer sit under “details”.

Fix01 / Search Console, sitemap, CMS · confidence high

The catalog needs group decisions, not bulk reindexing

What we see
Commercial pages, weak listings and utility variants share one problem group. A browser sample rendered, so crawl rate limiting was not misreported as a broken site.
Why it matters
Bulk submission does not remove root causes. Pages with real demand are counter evidence and must be protected.
What we do
The SEO lead assigns keep, improve, merge or exclude to every group. Acceptance: at days 14 and 28, each group retains at least its baseline share of valid URLs; deterioration returns the group to diagnosis.
details for the specialist
Details
Source: Search Console, sitemap, CMS. Period: recent window. Status: corroborated observation. Confidence: high. Coverage: complete URL universe plus template sample.
Verify02 / GA4, tag setup, backend summary · confidence medium

Checkout detail is incomplete, but sales are not broken

What we see
Purchases arrive while delivery and payment steps are not separated. This may be a native integration limit.
Why it matters
Rebuilding tracking could duplicate purchase. Backend and analytics show similar transaction volume.
What we do
Analyst runs a debug checkout. Acceptance: one purchase with transaction ID and value, no duplicate, and an explained backend variance.
details for the specialist
Details
Source: GA4, tag setup, backend summary. Period: 28 days. Status: purchase confirmed, intermediate steps remain a hypothesis. Confidence: medium. Coverage: all ecommerce events and one test journey.
Develop03 / GA4 referrals, robots and HTTP checks · confidence medium

AI traffic is measurable, but too small for a forecast

What we see
AI sources produced visits and at least one commercial outcome, and major crawlers could access public pages.
Why it matters
The channel exists, but low volume and unattributed AI visits do not prove sustainable returns.
What we do
The content editor and analyst maintain a separate AI referral report. Acceptance: sessions, outcomes, landing pages and source are reviewed monthly without a composite GEO score.
details for the specialist
Details
Source: GA4 referrals, robots and HTTP checks. Period: 28 days. Status: observed. Confidence: medium. Coverage: known AI referrals and four major crawlers.
Full findings table

Findings

Area Finding Evidence Why it matters What we do Confidence Decision Details
Search Console, sitemap, CMS The catalog needs group decisions, not bulk reindexing Commercial pages, weak listings and utility variants share one problem group. A browser sample rendered, so crawl rate limiting was not misreported as a broken site. Bulk submission does not remove root causes. Pages with real demand are counter evidence and must be protected. The SEO lead assigns keep, improve, merge or exclude to every group. Acceptance: at days 14 and 28, each group retains at least its baseline share of valid URLs; deterioration returns the group to diagnosis. high Fix Source: Search Console, sitemap, CMS. Period: recent window. Status: corroborated observation. Confidence: high. Coverage: complete URL universe plus template sample.
GA4, tag setup, backend summary Checkout detail is incomplete, but sales are not broken Purchases arrive while delivery and payment steps are not separated. This may be a native integration limit. Rebuilding tracking could duplicate purchase. Backend and analytics show similar transaction volume. Analyst runs a debug checkout. Acceptance: one purchase with transaction ID and value, no duplicate, and an explained backend variance. medium Verify Source: GA4, tag setup, backend summary. Period: 28 days. Status: purchase confirmed, intermediate steps remain a hypothesis. Confidence: medium. Coverage: all ecommerce events and one test journey.
GA4 referrals, robots and HTTP checks AI traffic is measurable, but too small for a forecast AI sources produced visits and at least one commercial outcome, and major crawlers could access public pages. The channel exists, but low volume and unattributed AI visits do not prove sustainable returns. The content editor and analyst maintain a separate AI referral report. Acceptance: sessions, outcomes, landing pages and source are reviewed monthly without a composite GEO score. medium Develop Source: GA4 referrals, robots and HTTP checks. Period: 28 days. Status: observed. Confidence: medium. Coverage: known AI referrals and four major crawlers.
05 / limitations and scope

Limitations and scope

Limitations: Margin and a CRM order ledger were outside the public evidence pack, so profit and attribution conclusions remain directional.

Coverage: All main URL sources, more than 30 representative pages across key templates, and the path to a recorded purchase were checked.

Sources:

  • Search Console and sales analytics
  • CMS, sitemap and URL inventory
  • Merchant and product markup
  • Rendered pages, robots and AI crawlers
06 / detailed review

Full data for your marketer.

Every table and calculation from the audit. Owners can skip it.

Plan

Plan

What Who Result Horizon
Segment URLs and debug checkout. SEO lead and analyst Every URL group has a keep, improve, merge or exclude decision, and one purchase path is proven without duplicate events. 7 days
Fix verified template and Merchant issues. Frontend engineer, content editor and ecommerce manager Every URL in the control sample passes the repeated technical check after publication. 30 days
Expand pages with demand and measure AI separately. SEO/GEO lead Demand, sales and monthly deltas drive priority. 90 days
Measurement

Measurement

Status: Working with limitations

Purchase and revenue reach analytics. Before changes, the team must rule out duplicate tags, test consent and reconcile transactions with the backend.

What already works

What already works

Preserve purchase collection and crawler access

Evidence: Key pages render, purchases arrive and major AI crawlers are not blocked.

Decision: Do not change tags and robots in one release. Verify in parallel first.

Target state and change rules

Target state and change rules

Target state: One URL inventory, stable purchase tracking, evidence-backed pages, and a separate AI referral report.

How we test: Changes ship in URL groups and are read after 14 and 28 days against an unchanged control.

When we roll back: A group returns to diagnosis if validity, purchases, or commercial visibility falls below baseline.

Technical register of this example

Technical register of this example

18 checks

The three decisions above are the owner's summary. Review the evidence for each recommendation in this public report excerpt.

The public excerpt contains 18 checks from the 100+ point methodology. The register explains decisions in an anonymized client audit; the brand, URLs and sensitive metrics are withheld. Acceptance criteria describe planned checks, not results already achieved.

Open the technical register: 18 checks

Inventory and indexation

Commercial demand is separated from template noise because different URL groups need different decisions.

Check Priority Decision Recommended action Evidence
SG-01 P1 Fix Assign each URL to keep, improve, merge, or exclude. The sitemap, CMS, and Search Console inventories differ and need reconciliation before bulk action.
SG-02 P1 Protect Retain commercial pages with confirmed demand. They render, index, and carry either search or sales evidence.
SG-03 P2 Verify Separate service and parameter URLs from weak categories. Similar visibility does not mean the same cause or the same remedy.

Technical rendering and crawl control

We checked the HTML response and separately inspected what users and crawlers see after rendering.

Check Priority Decision Recommended action Evidence
SG-04 P1 Fix Align canonical, indexability, and sitemap rules by group. The remedy belongs at template level, not on a random individual URL.
SG-05 P2 Verify Repeat mobile rendering checks on the main templates. Pages are available, but JavaScript content completeness needs its own check.
SG-06 P3 Monitor Do not change robots rules in the template release. A combined release would obscure the cause of any crawl change.

Commercial pages and Merchant

Visibility is compared with stock, structured data, and each page's role in a sale.

Check Priority Decision Recommended action Evidence
SG-07 P1 Fix Reconcile product markup, feed data, and the page. A price, stock, or identifier mismatch leaves the SEO conclusion incomplete.
SG-08 P2 Develop Improve collections with demand but a weak answer. Priority goes to pages where demand is proven and the content does not help selection.
SG-09 P2 Merge Consolidate pages without an independent role. A merge follows query, link, and product coverage checks.

Sales and measurement quality

Purchase tracking works, while intermediate events and system reconciliation have limits.

Check Priority Decision Recommended action Evidence
SG-10 P0 Protect Preserve the working purchase event. A purchase with transaction ID and value arrives; changes first pass a diagnostic order.
SG-11 P1 Verify Run checkout from cart to purchase without a duplicate. Missing delivery and payment steps may reflect the integration rather than a broken checkout.
SG-12 P1 Reconcile Compare analytics transactions with the internal ledger. Without a CRM ledger, analytics revenue is not financial truth.

GEO, citability, and AI access

Crawler access and citability are separate conditions, and neither guarantees an outcome.

Check Priority Decision Recommended action Evidence
SG-13 P2 Protect Keep access open for the main AI crawlers. HTTP and robots checks show no explicit blocker for the tested bots.
SG-14 P2 Develop Add concise answers with dates, sources, and limits. A verifiable fact with a method is stronger than a general marketing claim.
SG-15 P3 Measure Report AI referrals separately from forecasts. Existing visits do not prove returns, and some sources cannot be identified.

Evidence, links, and editorial ownership

Authority is assessed through claim provenance and maintenance, not a synthetic score.

Check Priority Decision Recommended action Evidence
SG-16 P2 Strengthen Tie commercial claims to primary evidence. The page should show where a fact came from and when it was last checked.
SG-17 P2 Assign Give commercial pages an accountable role and review cycle. Correct content becomes stale when nobody owns the next review.
SG-18 P3 Monitor Track citations beside search and sales signals. GEO is useful as a separate view but does not replace business outcomes.
Method and appendices

Method and appendices

  • URL inventory and keep / improve / merge / exclude rules
  • Canonical, indexability, sitemap, and template map
  • Ecommerce event and transaction reconciliation
  • AI crawler matrix and GEO observation log
What the client gets

What the client gets

  • Owner decision brief
  • Source and limitation map
  • Evidence backed finding register
  • 7/30/90 tasks with acceptance criteria
  • URL, Merchant and measurement appendix
/ next step

Next step with UPLIFY

Need the same link between SEO, GEO and commercial data?

We define sources and evidence mode first, then deliver decisions your owners can verify.

Order an SEO audit — €300 (EUR) · SEO audit service