Crawl and citation surface
What search engines and AI crawlers can actually see on first request, and which pages are invisible because they render client side.
Phase one
Diagnose before you prescribe
Strategy is not a deck. It is a written diagnosis of what is broken, what it costs, and the architecture that fixes it, delivered before anyone writes a line of code.
What we diagnose
Four surfaces, in order
Frontend architecture
Routing, rendering strategy, data flow, and the performance ceiling the current stack imposes on everything else.
Measurement integrity
Whether analytics, conversion tracking, and search data agree with each other. They usually do not.
Demand and intent map
The questions your buyers actually ask, split into search intent and assistant intent, mapped against pages that do or do not exist.
Deliverables
What you get at the end of the phase
A findings document that ranks every issue by revenue impact, not by how easy it is to fix. A route architecture that names every page the site should have and what job each one does. A schema and answer plan covering which questions we intend to own. A measurement plan that defines the conversion events before they are implemented.
All four are yours whether or not you continue into the build. We do not hold strategy hostage to win the implementation.
How long does the strategy phase take?
Two weeks for most engagements. Larger properties with multiple domains or a migration in scope run three to four weeks, and we say so before the phase starts.
The timeline is driven by access, not effort. Analytics permissions, search console access, and a conversation with whoever owns the revenue number are the three things that determine whether the phase finishes on schedule.
Get the diagnosis first
You will know exactly what is wrong before you decide who fixes it.