Skip to content
Case study · Ambar

The most valuable output of this audit was a project we cancelled.

158 findings across 15 dimensions. 44 of them refuted outright before the client ever saw them. The one that mattered most stopped a planned English content rebuild — because Search Console showed the demand it was aimed at does not exist.

Sector
Womenswear · direct to consumer
Market
Morocco, shipping to 13 countries
Window
August – September 2026
Prepared by
Aymane Louarni
01

The problem

What was structurally wrong

Ambar sells womenswear direct to consumer from Morocco, in four languages, to thirteen countries. Every instrument reported it as one brand in one market, and the plan on the table was a content rebuild aimed at English-language demand.

Three things were structurally wrong, and none of them appear in a rankings report. The catalogue was fully approved in Merchant Center and earning nothing. The site was translated into four locales but only partly localised. And the entity itself was ambiguous — a Turkish clothing brand and a store in Amman share the name, which distorts every averaged figure the account reports.

02

The diagnosis

14 measured dimensions · each with its instrument

The first pass produced 158 raw findings across 15 dimensions. Each was then re-examined by a hostile verifier instructed to refute it: 44 were refuted outright and 56 had their severity corrected downward. Only the survivors were re-scoped against live admin data and put in front of the client.

That step is the most expensive part of the method and the least visible. It is also the reason the figures below can be quoted: each one names the instrument it came from, and anything that could not be traced to an instrument was removed rather than softened.

DimensionMeasuredVerdictSource
Sitemap URLs309 → 297ResolvedShopify Admin API
URLs noindexed by design24CorrectLive crawl
Self-referencing canonicals297 of 297CorrectLive crawl
Products approved in Merchant Center1,508CorrectMerchant Center
Disapprovals0CorrectMerchant Center
Clicks from those product listings0Live defectMerchant Center
Products missing age_group and gender744 of 1,508Live defectMerchant Center
Referring domains396MeasuredAhrefs
Referring domains that are not spam2Live defectManual review, 396 domains
AI crawlers served 200 with full HTML15 of 15CorrectHeader probes
Locales live and genuinely translated4CorrectLive crawl
Stale Spanish metadata fields194Needs actionShopify Admin API
Countries with live shipping rates13CorrectShopify Admin API
URLs carrying FAQPage or HowTo schema0 of 84Live defectCorpus scan

The finding that changed the plan

Search Console showed the site ranking between position 1.0 and 17.0 for its own product terms — bar dress, white satin set, mini trench, earrings — and taking zero clicks from any category or product term. One branded term, ambar denim, sat at position 1.0 with no clicks at all.

Rankings existed. Demand did not. The English content rebuild was aimed at a market that was not searching, and the same account showed why the averages had looked survivable: two unrelated businesses share the brand name, and their impressions were inside every figure being used to justify the work.

So the recommendation was to stop. Not to reduce the scope, or stage it, or run it as a test — to cancel it and spend the budget on the feed, the locales and the entity instead.

03

The intervention

Marked as a revision
BeforeAug 2026
  • 309 URLs submitted, state unresolved
  • canonical strategy inconsistent per locale
  • 4 locales live
  • English content rebuild scheduled
  • no regression check between audits
AfterSep 2026
  • 297 indexable, 24 noindexed by design
  • self-referencing canonicals, sitemaps partitioned per locale
  • 4 locales live
  • rebuild cancelled, budget redirected to feed and locales
  • harness re-runs every check and reports

Shipped in two-week loops. Indexation first, because every other layer is inherited from it — then the measurement instrument, because the numbers being used to make decisions were wrong.

04

The outcome

Measured, and not measured

Two things are measured and reported below. A third — the effect on organic revenue — is not, and will not be printed here until there is a clean before-and-after window to attribute it to.

Indexation state309 submitted URLs reconciled to 297 indexable and 24 deliberately excluded, each with a self-referencing canonical.Resolved
Performance, both pixels gatedLighthouse performance score, p=0.0017, CI [+5, +9]. TBT −1,640 ms (p<0.0001) and LCP −4.17 s (p=0.0001).+6.0 points
Performance, either pixel aloneGoogle alone +1.0, not significant (p=0.246). Meta alone +1.0 (p=0.037), CI [0, +2]. Neither is worth shipping on its own.No effect
Planned English rebuildOn the evidence that the demand it targeted does not exist. The largest number in this case study is the one that was not spent.Cancelled
Organic revenue effectNo clean attribution window yet. It will be published when there is one, or not at all.Not yet measurable

The pixel result is the one worth reading twice: neither pixel alone moves the performance score, and gating both moves it six points. An A/B that tested them one at a time would have concluded there was nothing there.

05

The system

What keeps producing value
A regression harnessEvery check in the audit re-runs on demand and reports. It also encodes the two measurement traps that had already produced wrong numbers, so they cannot produce them again.Standing
Hostile verification as a standing stepNo finding reaches the client until someone has tried to refute it. On the first pass that removed 44 findings and downgraded 56.Standing
A performance measurement protocolFive instrument defects — cache state, consent, third parties, run count and variance — controlled explicitly, because four earlier numbers had been produced by not controlling them.Standing
A named reversion riskA newer unpublished theme carries no noindex block. Publishing it makes every excluded URL indexable again and undoes the sitemap work. That is written down, with the consequence stated, where whoever publishes it will read it.Standing

Sources — Google Search Console, Google Merchant Center, Shopify Admin API, Ahrefs, live crawls and header probes, Lighthouse (20 runs per arm). Engagement window August–September 2026. Published with the client’s written authorisation. Payment-mix economics, legal-surface findings and internal correspondence are excluded by choice, not by omission.

07

Build visibility

Seven questions · no discovery call

Atlas reads the site before the first conversation. These are the seven things worth knowing first.

01 Website02 Business03 Markets04 Current search situation05 Main challenge06 Desired outcome07 Contact
Ambar case study Build visibility