SEO Services
Clear the technical faults that hold your rankings down
Slow pages, blocked URLs, duplicated content and half-finished redirects cap everything else you do in search. We find what is actually costing you, fix it or write the spec, and tell you what changed.
- A ranked list of faults, with what each one costs you
- Fixes shipped, or a spec your developers can build from
- Pages that load fast on a real phone, not just in a lab
- A migration plan that keeps the rankings you already have
Platforms we work in
How we work
Crawl the site as a search engine sees it
Not as a browser sees it. The gap between the two is where most of the problems live.
Rank the issues by cost
A broken redirect on a page nobody visits is not urgent. One on your highest converting page is.
Fix or specify
We implement directly where we can, and write clear tickets where your team owns the code.
Verify and monitor
Re-crawl to confirm each fix actually took effect, then watch for regressions after future releases.
What is inside this service
- Crawling and indexing
- Core Web Vitals and load speed
- Site architecture and internal links
- Structured data
- JavaScript and rendering
- Migrations and redirects
- Mobile and device parity
- Monitoring so it does not come back
What each part does
- Crawling and indexing
- Making sure the pages you want found can be found, and the ones you do not are not competing with them. Robots rules, sitemaps, canonicals and index bloat.
- Core Web Vitals and load speed
- We profile what is actually slow, which is usually images, third-party scripts or render-blocking code, and fix the cause instead of tuning a score.
- Site architecture and internal links
- How pages connect tells search engines what matters. We restructure so the pages that earn money are reachable in a few clicks and supported by the pages around them.
- Structured data
- Schema that describes what is genuinely on the page. Done properly it is how a machine tells a product from a policy from an opinion.
- JavaScript and rendering
- If your content only exists after a script runs, some crawlers will never see it. We check what the page looks like to a machine, not just to you.
- Migrations and redirects
- Moving a site is where rankings go to die. We map old URLs to new ones before launch, then check what broke after, because something always does.
- Mobile and device parity
- Google indexes the mobile version. We check that the phone version has the same content, the same links and the same structured data as the desktop one.
- Monitoring so it does not come back
- Most technical debt returns quietly after a release. We set up the checks that catch a regression before a crawler does.
Questions we get asked
Either. We can implement directly if you give us access, or write the work up so your developer can act on it without a translation layer. Most teams end up with a mix, because some fixes belong in the CMS and some belong in the template.
It depends on the size of the site. A brochure site is quick. A large ecommerce catalogue with faceted navigation takes considerably longer. You get findings as we go rather than one document at the end, so the quick wins can start early.
Sometimes, and sometimes not. Technical work removes a ceiling. If your content and authority were already good enough to rank and something was blocking them, you see a change quickly. If they were not, this makes the rest of the work possible rather than replacing it.
It changes which problems are likely, not the approach. WordPress sites tend to carry plugin bloat and slow queries. Shopify handles some things for you and refuses to let you change others. We work within what the platform allows, and we tell you when a limit is the platform rather than a choice.
Yes, as a starting point. Tools are good at finding candidates and bad at knowing which ones matter. Everything gets checked by a person before it reaches your list, because working through a raw crawl report top to bottom is how a team spends a quarter on issues that were never costing anything.
Nothing goes live without being tested first. Redirect maps and structured data are checked on a staging copy where you have one. Where you do not, we agree how to roll back before anyone touches anything.
Access to Search Console, analytics and the site itself, plus whoever can answer questions about past migrations. Old migrations explain a surprising number of current problems.