If the systems cannot read the site, nothing else matters.
Technical foundation carries 20 of the 100 points on the Atlas scale — the largest single weight — because it is the only layer whose failure is total. Everything above it is inherited from it.
What actually breaks
7 defects · observed, not hypotheticalThis is the layer that fails silently. A canonical pointing the wrong way costs nothing visible: the page still loads, the copy still reads well, the design still looks finished. The loss shows up two steps away, in a number nobody connects back to a line in the head of a template.
So the work is not a checklist. It is a diagnosis: establish what the systems actually see, compare it to what the site intends to say, and fix the disagreements in the order that moves the number.
| Defect | What it looks like | What it costs |
|---|---|---|
| A canonical naming the wrong URL | Two URLs serve the same product; the canonical names the one you do not sell from. | Rankings consolidate onto a page with no add-to-cart on it. |
| A noindex left on a live template | A staging directive shipped in the head and nobody read the head. | An entire page type disappears from the index, quietly, at once. |
| Facets inside the crawl path | Filter combinations generate URLs without limit. | Crawl budget spent on pages nobody has ever searched for. |
| Content that arrives after the HTML | The document is a shell; the copy is fetched by script. | Some systems read the page and some read an empty one — inconsistently. |
| A sitemap that contradicts the site | Submitted URLs redirect, 404, or are canonicalised elsewhere. | The one file you fully control states an intent the site denies. |
| A migration without a redirect map | Old URLs return 404 where they should return 301. | Accumulated authority is discarded at the moment you most need it. |
| Vitals measured in the wrong instrument | Lab numbers from a warm cache, no consent banner and no third parties. | You optimise something the field data never measured. |
What it moves on the scale
Weights, not scoresMoves 35 of 100 points. The muted categories are not this service’s job, and saying so is the point: a proposal that claims to move all eight is describing a retainer, not a diagnosis.
What you get
Same format as every Atlas documentDelivered as a document, not a dashboard login: dark cover, verdict columns, evidence IDs, a provenance line stating where every number came from. Shipped in two-week loops — the smallest change that moves the number, then the next one.
Proof
What exists, and what does notNo fabricated clients, statistics, testimonials or rankings appear on this site. Where a figure is not evidenced it is not printed, and the absence is stated instead.
Common questions
Answer first, then the reasoningWhat does a technical SEO audit actually cover?
Indexation, canonicals, crawl control and search architecture — the layer every other decision inherits. The output is an indexation ledger: submitted against discovered against indexed, with each gap resolved through a canonical or a redirect rather than left as a count.
Is a finding checked before it reaches me?
Every finding is argued against before it is published. On the Ambar engagement 44 of 158 findings were refuted outright and never shown to the client. A defect that survives that is one you can act on.
Does technical SEO still matter if the content is strong?
It decides whether the content is read at all. This is the only layer where a mistake compounds instead of staying local, which is why content added to a broken foundation returns nothing.
Where it bites hardest
By sectorThree ways to start
None of them is a discovery callScan your own site
A visibility scorecard against the published 100-point scale, an hreflang validator, an answer-readiness reader and a SERP preview measured in pixels — all running in your browser. Nothing is uploaded and nothing is stored.
Run a scanThe AEO & GEO field guide
What changes when a result is assembled rather than listed — and the eight things to fix first. Written for engineers and founders, not for a newsletter funnel.
Read the guideBook a working call
Bring the site and the constraint you already suspect. You leave with the diagnosis whether or not there is an engagement in it.
Book on Cal.comAtlas reads the site before the first conversation. Seven questions; what comes back is a reading against the 100-point scale, the bottleneck named, and the smallest change that moves it.