Search & SEO: Good work.
Discovered.

Our approach to technical SEO

Where we start

Before we change anything, we crawl the whole site the way a search engine does, using Screaming Frog SEO Spider. It shows us, page by page:

• whether each address loads, redirects or fails
• what search engines see in the raw page, before any JavaScript runs
• which pages compete with each other for the same search
• which pages are hidden by a stray redirect, canonical tag or robots rule

Most problems that look like poor rankings start earlier: the page was never crawled or indexed in the first place. Google’s own guides to robots.txt and JavaScript SEO explain how that happens.

What we check and fix

Technical SEO is unglamorous by design. We work through:

• URL structure, canonicals and redirect hygiene, so one page doesn't quietly cannibalise another
• structured data that actually describes what's on the page, marked up to Google's structured-data guidelines
• information architecture, in step with our information architecture work, so the pages that matter are never more than a few clicks from the home page

The floor everything stands on

None of this replaces good content, and we say so plainly when a client's real problem is what's written on the page rather than how it's built. But a technically sound site is the floor everything else stands on: if a page can't be crawled cleanly, its content quality is irrelevant. That floor starts with the server a site runs on, so we plan hosting alongside the technical work, and where a fix means rebuilding a template rather than editing a tag, that’s custom website development.

What we measure, and what we won’t do

For keyword, competitor and backlink research we work in Semrush and Ahrefs, cross-checking one against the other rather than trusting a single data source. We treat page experience signals — loading, interactivity, visual stability — as one input among several, not a silver bullet, in line with Google's own Core Web Vitals documentation. This site itself scores 100 in Google Lighthouse for accessibility, best practices and SEO, with performance at 98–100 on a simulated mid-range phone — and because that's a public, repeatable test, anyone can run the same check against any site, including ours, for free at pagespeed.web.dev. We won't chase a score at the expense of a page working properly for the people reading it, and we won't invent a fix for a problem the crawl data doesn't actually show.