Step two
Implementation
We fix the problems the audit found, and install the measurement needed to show what changes afterwards.
- Scope
- Set by the audit backlog
- Depends on
- Catalogue size, systems, integration depth
The principle
You probably do not need another platform.
In most engagements, a large part of the backlog turns out not to be new work. It is tooling that was bought, switched on, and never checked against what the brand actually intended it to do.
So the work is deliberately vendor-using rather than vendor-replacing. A substantial part of an early engagement is configuring your existing CDN and crawler controls, feeds, structured data, analytics and GEO tooling correctly, then proving the effective behaviour rather than the intended behaviour.
We build software only where repeated engagements expose a missing join or a workflow that does not exist in any of the tools. That keeps the bill down and keeps you able to leave.
The work
What implementation covers.
Access and policy
- Configuring Cloudflare or another CDN’s crawler controls and WAF rules.
- Aligning robots.txt, bot categories and your search, training and agent-access policy so they say the same thing.
Product and organisation data
- Correcting product and organisation structured data.
- Reconciling Merchant Center, catalogue and retailer feeds.
- Introducing stable product identifiers, canonical pages and provenance fields.
Measurement
- Configuring analytics, logs, consent controls and tag management.
- Setting up an existing GEO platform with the right brands, markets, personas and prompts.
- Installing lightweight edge telemetry to show which AI services request which pages.
After
Implementation installs the measurement.
The reason implementation comes before monitoring is that there is nothing meaningful to monitor until the data is correct and the telemetry is in place. Once it is, changes become observable: you can see whether an agreed fix actually changed anything.
That is also the point at which the recurring service becomes worth buying, and we will propose it separately rather than bundling it.
Most implementations start with an audit.
We can scope implementation directly if you already have a credible baseline. Otherwise the audit is what makes the estimate honest.