How kratt closed A-Mobile OÜ’s revenue leak.
Roadside work is won in the few minutes after something breaks, and every breakdown is a different search. Car in a ditch. Dead battery in January. Out of fuel on the Tartu to Tallinn road. One page cannot be the answer to six emergencies across nine counties, so the caller finds whoever is.
How these were measured: Measured against the live site on 2026-07-26 with Lighthouse 12 and the SEOmator CLI. Accessibility scores 95, not 100: one colour-contrast pair still fails. Every number above can be re-run by anyone in about two minutes.
What we shipped
kratt rebuilt amobile.ee as a 24-page Estonian intent map: six emergency "what do I do right now" pages, twelve county and service spokes with published response times, and a machine-readable layer on every one of them. It ships as static HTML with zero third-party JavaScript, so it opens instantly on a phone with one bar of signal at the roadside.
Six pages that answer the panic instead of selling the service.
Nobody types "towing service Tartu" while their car is nose-down in a ditch. They type "auto kraavis, mida teha". So six pages answer that exact question first, in Estonian, with a three-step plan above everything else: check that you are safe, call this number, photograph it for the insurer. Booking the tow is step two of the answer, not the pitch. Each page carries HowTo and FAQ structured data, so Google and the answer engines can lift the steps straight into the result with A-Mobile attached to them, and every page ends where the caller already is: the phone number.
Every page we built, live
The 2am query. Three-step plan first, phone number at every step, HowTo + FAQ schema underneath.
One page per county and per special service, each publishing the response time from the Tartu base.
The spine. A service-area hub links every spoke, so nothing built above sits orphaned.
Inside the build
What this page does not claim
- No traffic and no rankings. There is no GA4, no Tag Manager and no verified Search Console on this site, so we cannot show you sessions, positions or conversions. Everything claimed above is measurable from outside the business, by anyone, today.
- No before-and-after. The rebuild replaced a site the owner no longer had admin access to, so there is no clean baseline to compare against. We are not going to invent one.
- The response times on the page are the operator's own estimates from the Tartu base, not measured dispatch data.
Where is your business leaking revenue?
A free AI audit finds it, ranked by impact, and it is yours to keep.
Back to all case studies, or see every live build on the portfolio wall.