Audits, migrations and the unglamorous technical work that decides whether your pages can rank at all.
Most stores I look at are not being held back by their content. They are being held back by pages Google cannot crawl, templates that render after the crawler has left, or a migration that quietly dropped a third of the internal links.
The work starts with what Google actually sees, which is rarely what the site owner sees.
Findings are ordered by the traffic at stake. A critical-severity issue on a page nobody lands on is not urgent, and I will say so.
If you need content written at volume or link acquisition, that is not what this is. I fix the technical reasons good content is not ranking.
A full crawl against rendered HTML, compared with what is actually indexed. The gap between those two is where most of the lost traffic lives.
Core Web Vitals from field data where it exists, not a lab score on the home page. A fast home page and a slow category template is the usual pattern.
Every finding carries an estimate of the organic revenue it is costing. That is what decides the order, not the colour of the severity label.
Template, schema and redirect work implemented rather than handed over as a document, unless you have a team who would rather do it themselves.
Daily checks for the first fortnight after anything significant moves, so a regression is caught while it is still cheap to reverse.
For sites that are indexed but not ranking, where nobody can say which of the technical problems actually matters.
For a replatform, redesign or domain move, where the rankings are the thing most likely to be lost.
For retailers who want the technical side held steady rather than audited once and forgotten.
Not quite the right fit? Builds, replatforms and ongoing support for stores that have outgrown a template.
Pricing is bespoke to scope. Figures are a starting point, confirmed in writing before work starts.
Twenty minutes, no charge. Or email the detail and you will get a reply the same day.
He understands the business, he understands how to communicate the business needs to the development team, and is able to analyse and understand issues, bottlenecks and future problems. He has high standards and makes sure nothing is getting done without meeting those standards.
One published engagement, with the figures attached.
Andertons ran on a legacy IBM WebSphere Commerce estate that was holding the business back. I worked alongside the Head of Technology and Lee Anderton on the 14-month replatforming programme to BigCommerce, with one objective above all others: keep the search traffic that a retailer of this profile lives on.