UPLIFY18 checks

Anonymized client audit

An SEO and GEO audit that connects visibility to sales

The report separates commercial pages from technical noise, tests measurement limits, protects working systems and gives the team an implementation order.

Evidence status: Anonymized client audit
Source: Client sources, public version
Period: Recent 28 day window, exact dates withheld

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.

Control snapshot

4 URL sources sitemap, CMS, Search Console, render
30+ sampled pages commercial and template pages
28 days measurement window exact dates withheld
4 AI crawlers access checked separately

The 90 second view

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.

What was checked and where confidence ends

Sources

Search Console and sales analytics
CMS, sitemap and URL inventory
Merchant and product markup
Rendered pages, robots and AI crawlers

Coverage

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

Limitations

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

Measurement confidence

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.

18 checks

Full audit map

The three decisions above give an executive summary. The complete review register below shows the checks behind those decisions.

This page shows 18 of 18 checks in the demonstration register. A client report also links each check to its source, accountable role, and working artifact.

Check	Priority	Decision	What we established
01 Inventory and indexationCommercial demand is separated from template noise because different URL groups need different decisions.
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.
02 Technical rendering and crawl controlWe checked the HTML response and separately inspected what users and crawlers see after rendering.
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.
03 Commercial pages and MerchantVisibility is compared with stock, structured data, and each page's role in a sale.
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.
04 Sales and measurement qualityPurchase tracking works, while intermediate events and system reconciliation have limits.
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.
05 GEO, citability, and AI accessCrawler access and citability are separate conditions, and neither guarantees an outcome.
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.
06 Evidence, links, and editorial ownershipAuthority is assessed through claim provenance and maintenance, not a synthetic score.
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.

Priority decisions with evidence

Fix

The catalog needs group decisions, not bulk reindexing

Source: Search Console, sitemap, CMS. Period: recent window. Status: corroborated observation. Confidence: high. Coverage: complete URL universe plus template sample.

Observation: 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.
Decision logic: Bulk submission does not remove root causes. Pages with real demand are counter evidence and must be protected.
Action and verification: 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.

Verify

Checkout detail is incomplete, but sales are not broken

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.

Observation: Purchases arrive while delivery and payment steps are not separated. This may be a native integration limit.
Decision logic: Rebuilding tracking could duplicate purchase. Backend and analytics show similar transaction volume.
Action and verification: Analyst runs a debug checkout. Acceptance: one purchase with transaction ID and value, no duplicate, and an explained backend variance.

Develop

AI traffic is measurable, but too small for a forecast

Source: GA4 referrals, robots and HTTP checks. Period: 28 days. Status: observed. Confidence: medium. Coverage: known AI referrals and four major crawlers.

Observation: AI sources produced visits and at least one commercial outcome, and major crawlers could access public pages.
Decision logic: The channel exists, but low volume and unattributed AI visits do not prove sustainable returns.
Action and verification: 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.

What works and should not change

Preserve purchase collection and crawler access

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

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

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.

The 7, 30 and 90 day plan

7 days

Segment URLs and debug checkout.
Owner
SEO lead and analyst

Acceptance criteria
Every URL group has a keep, improve, merge or exclude decision, and one purchase path is proven without duplicate events.
30 days

Fix verified template and Merchant issues.
Owner
Frontend engineer, content editor and ecommerce manager

Acceptance criteria
Every URL in the control sample passes the repeated technical check after publication.
90 days

Expand pages with demand and measure AI separately.
Owner
SEO/GEO lead

Acceptance criteria
Demand, sales and monthly deltas drive priority.

What the client receives

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

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

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

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

Discuss an audit for your business