Technical SEO in London

Full technical audit

A crawl of the whole site compared with what Google has indexed, a render check, speed field data and a hand review. Only confirmed issues, each with a screenshot and a fix.

Crawl and indexing control

Canonicals, robots rules, XML sitemaps, parameters, pagination and orphaned pages brought into order so Google spends its time on the pages that earn.

Core Web Vitals work

Largest Contentful Paint, Interaction to Next Paint and layout shift fixed in the templates, images and scripts, measured against Chrome field data rather than a lab score.

Rendering and JavaScript

What Google renders checked against what visitors see, with server rendering or pre-rendering where a framework hides content from the crawler.

Structured data

Organisation, service, product, FAQ and breadcrumb markup written to match the visible page, validated and monitored for errors.

Migration and redesign support

Redirect maps, staging checks, launch-day monitoring and the first weeks after, so a new site keeps the rankings the old one earned.

Developer notes and tickets

Every fix we do not ship ourselves is written as a ticket your team can act on, with the reason and the test for done.

Monthly re-crawl and alerts

The site re-crawled each month and Search Console watched, so a regression is caught in days rather than at the next audit.

How we do it

We begin with a crawl of the whole site and set it against Search Console: the pages Google has indexed, the pages it has seen and chosen not to, and the pages it has never found. Where the hosting allows it we read the server logs, because they show where Googlebot actually spends its time. Then we render the key templates the way Google does and compare what comes back with what a visitor sees. The audit lists only problems we have confirmed, with a screenshot each and the fix beside it. A tool export is not an audit.

The order of work matters. Indexing and crawl control come first, because nothing else counts until Google can reach and keep the right pages. Rendering is next, so the content that exists is the content that gets indexed. Then speed, measured against Chrome field data for real London visitors rather than a lab score, because Google uses the field data. Structured data comes last, written to match what is visibly on the page, never to decorate it. On a migration or redesign the order inverts: the redirect map and the staging checks happen before anything is launched.

The fixes get shipped. Muhammad Abubakar, our Full-Stack Developer and Lead, builds the technical systems behind fast, reliable websites and clean search foundations, and Abdur Rehman handles WordPress work. If you would rather your own developers make the changes, every item is written as a ticket with the reason and the test for done, and we check the release. The technical SEO checklist shows the categories we work through, and the Core Web Vitals guide explains the speed measures in plain English.

What changes and when

Technical fixes are usually re-crawled within two to eight weeks. Local search changes often show within one to three months. Competitive London head terms usually take six to twelve months. These are typical ranges from our own work, not a promise for your site, and we report progress every month so you can see which it is.

Technical work is the fastest strand to show in Google’s own data, because the signal is direct: a page that could not be indexed is indexed; a template that failed the Vitals thresholds passes them. Expect indexing and coverage changes within the two-to-eight-week re-crawl window, field data for Vitals to update over the following 28 days, and the effect on impressions and clicks to follow in the months after. If a site had deep problems, removing them is the condition for everything else, not the result in itself, and we will be clear about which is which in the plan.

How it is measured

What we report: the number of pages indexed against the number that should be, crawl errors and their trend, the share of page views that pass the Core Web Vitals thresholds in field data, structured-data errors, and then the impressions and clicks on the pages we fixed. Where it comes from: Google Search Console (Pages, Core Web Vitals and Enhancements reports), the Chrome User Experience Report, our own crawls, and your server logs where you give us access. How often: a written report every month and a review every quarter. All of it in accounts you own.

What we do not report: a lab speed score on one page on a fast desktop, a tool’s "site health" percentage, or a count of issues "fixed" that nobody can check. If the figure is not in Google’s data or reproducible in a crawl, it is not in the report.

What it costs to find out

Nothing. The free SEO audit is written by an SEO specialist from the team and delivered within two working days. Its third section is a technical check done by hand: indexing, mobile rendering, speed from Chrome field data and PageSpeed Insights, structured data and internal links, with a screenshot for each item we confirm. It will tell you whether you have a technical problem worth paying to fix or whether your site is fine and the gap is somewhere else.

Technical SEO is sold as a project (an audit and a fix programme with an end date) or as part of a managed retainer. What drives the price is the number of templates and URLs, the platform, whether we ship the fixes or your team does, and whether a migration is involved. What each tier includes is on the pricing page; our terms are on the before you sign page.

Common mistakes we see on London sites

• A redesign launched without a redirect map, so every URL changed at once and the rankings went with the old ones. The redesign checklist exists because this is the most expensive mistake we see.
• Faceted navigation on property, fashion and furniture sites left open to crawling, with thousands of filter combinations indexed and the pages that earn buried behind them.
• Hero images of two or three megabytes and a stack of marketing scripts loading before the content, so a page that looks quick on an office connection fails Largest Contentful Paint on a phone.
• A staging site left indexable, outranking the live one for the company name.
• Structured data that describes a page the visitor cannot see: ratings with no reviews on the page, FAQs that are not there, opening hours that disagree with the Business Profile.
• A JavaScript framework rendering the service content on the client, so Google indexes a heading and a spinner.
• Mixed signals on canonicals: the sitemap says one URL, the canonical tag another, the internal links a third.

How it fits with other services

Technical work is the floor the other strands stand on. In a managed campaign it is the first month’s priority and a standing item after that. A platform move or a redesign is its own project, SEO migration, with a timeline built around the launch date. Stores have their own version of these problems, facets and feeds above all, covered on the ecommerce SEO page. If the site is being rebuilt from scratch, our web design team builds it with these foundations in from the start, which is cheaper than retrofitting them. Speed and layout work overlaps with conversion rate optimisation: the same fixes that satisfy Google make the page easier to use.

Proof, stated plainly

We have not yet published a stand-alone technical SEO case study. The technical work we can point to sits inside rebuilds: Gladstone Garage in York, a site rebuilt around MOT, service and repair alongside local SEO, and Leam Taxis in Leamington Spa, whose rebuilt site and local work took it to first place for airport-transfer searches, with impressions up 60 to 300 percent across tracked terms. Both are outside London and we say so. Ask us for a reference call, or read the cases we do publish, each with its source and date.

Get your free SEO auditA person reviews your site within two working days. Three fields, no call required.