You stay in front
I won't contact your clients, join your calls unless you want me there, or put my name on anything. If you'd prefer to introduce me as part of your team, that's fine too, and it can change from client to client.
If your clients are asking for local search and nobody in-house wants to take it on, I can do it for you under your name. It's often too fiddly to hand to a junior and too small to hire for. You keep the client relationship, the reporting and the margin.
I won't contact your clients, join your calls unless you want me there, or put my name on anything. If you'd prefer to introduce me as part of your team, that's fine too, and it can change from client to client.
Rankings with the searches, the locations and the dates they were checked, plus a list of what was changed. So when a client asks a hard question, you've got the detail to answer it.
A profile rebuild is a project. Ongoing local work is usually a monthly block of days. The day rate is £350, which often works out cheaper than a project price. Give me a ring and we'll work out which suits you.
If a client's premises are in the wrong place for the searches they want, distance will beat anything either of us does. It's better to hear that from me before you sell it.
Small and mid-sized UK agencies with a handful of local clients and no local specialist. Web design studios whose clients keep asking why they can't be found. Marketing consultants who need delivery behind them.
Agency work suits me too, because it's repeatable and you already know what a good report looks like.
These are written up in full on my other site. They're anonymised to sector and platform, because I don't name clients without asking them first. Most of the agency work I'm asked for is technical, so these are too.
A rebrand, a domain move and a replatform landing on one fixed date. The 300-row redirect map was ready to ship and only 22 of its targets resolved. It shipped at 493 rows and 478 verified single-hop 301s.
Search Console showed close to 30,000 pages not indexed against a sitemap of 777 URLs, and it had been escalated as an emergency. Of the 9,200 URLs Google had surfaced, 7,127 were pagination parameters already covered by a live Disallow rule and decaying on their own. Every real content page I checked was indexed, so the right answer was to leave it alone.
Analytics collapsed overnight. Search Console showed arrivals down 19% while captured sessions were down 59%, which pointed to a tracking fault rather than lost traffic. A consent banner had stopped the tags firing. There was a smaller, genuine decline underneath, which was measured separately.
All 2,244 URLs classified rather than a sample, each decision carrying its own traffic and conversion evidence. Then 3,008 keywords mapped against what the archive already ranked for. That gave the client a clear plan for every post.
The obvious culprit was the hero image. A flag-gated live test cleared it and pointed at 156KB of render-blocking JavaScript instead. That turned a vague performance complaint into a specific brief for the client's own developers. The write-up covers the diagnosis and the brief, not before and after figures.
GA4, Search Console and SE Ranking pulled straight from their APIs and generated to house style. Crawling moved to the cloud on a schedule, and the QA built into the pipeline rather than done by eye at the end. It's how I can take on your reporting without adding to your workload.
The phone's quickest. Tell me what the client needs and I'll tell you whether I'm the right person for it.