Measure first.
Build second.
Most projects start with a proposal and find out later whether it was the right one. This one starts with a reading, so the plan argues from evidence rather than from a hunch.
Start with an audit ↗Four stages, and none of them skip.
Each one ends in something you can hold: a document, a staging URL, a report. If a stage produces nothing you can read, it did not happen.
We crawl the site the way a search engine does, pull whatever Search Console and field data already exist, and profile what real visitors experience. This is where most assumptions get corrected. The thing people believe is costing them traffic usually is not the thing that is.
- A ranked list of findings, each with the reasoning shown.
- Days
Findings become a plan: what to fix, in what order, and why that order. You see the reasoning, not just the conclusion, so you can push back on it. Nothing gets built before you approve the scope.
- A scoped plan with the order of work and what it costs.
- Days
Changes ship in increments you can review on a staging URL rather than arriving as one reveal at the end. Performance budgets and structured-data validation run on every build, so a regression fails before it reaches production instead of being found months later in a traffic report.
- Working changes on staging, then production.
- Weeks
After launch we track the target queries and Core Web Vitals on field data. Field data takes about 28 days to fully reflect a change, so the first honest report comes a month out. If something did not move, we say so and revise the approach rather than presenting a chart that avoids the question.
- A report against the metrics agreed at the planning stage.
- Ongoing
What that actually means for you.
You talk to whoever is doing the work. No account manager relaying messages to a team you never meet.
The plan comes with its reasoning shown, so you can argue with it before anything gets built.
Field data takes about that long to reflect a change, so the first real report comes a month after launch.
Four things this will never do.
Each of these costs money in the short run. They are printed here so you can hold us to them.
No ranking promised on a date
Rankings depend on competition and on an algorithm nobody outside Google controls. Anyone promising a position by a deadline is selling you the risk and keeping the fee.
No redesign proposed before measurement
The thing a client believes is costing them traffic usually is not the thing that is. A proposal written before the reading is a guess with an invoice attached.
Nothing borrowed against your domain
No bought links, no private networks, no shortcut that works for two quarters and then comes due. What gets built has to survive the next algorithm update.
No report that drops its bad months
If something did not move, that is in the report with the reason and the revised approach. A chart that avoids the question is worse than no chart.
Still deciding? Fair.
The questions that usually come up at exactly this point in the page.
Every engagement starts with measurement, not a proposal. We audit the current state, rank the findings by what they cost you, and only then scope the work. You approve that scope before anything is built.
Pricing depends on scope, which is why it follows the audit rather than preceding it. Send the site URL and what you are trying to fix, and you will get a scoped estimate rather than a number pulled from a rate card.
Technical fixes to indexation often show within days. Ranking movement typically takes weeks to months, and content-driven growth compounds over two to three quarters. Any firmer number than that is a guess presented as a promise.
We say so, before you commit money to it. Talking a client out of work that will not pay off costs one project and keeps a reputation, which is the better trade.