SEO for UK manufacturers: a practical guide for established firms

For most of the British mid-market manufacturers we work with — engineering firms, fabricators, OEMs doing £2m to £30m of turnover — search is still the single biggest lever for getting in front of the right buyer. It is also the channel most commonly mishandled, because the agencies they speak to are usually pricing in the SaaS playbook against a sales cycle that lasts nine months.

This piece is what we tell those clients. It is opinionated, written from work we have actually done, and assumes you already know your trade.

What's actually changed for manufacturers

Three things matter, and they are interrelated.

One: B2B buyers do most of their research before they ever speak to you. A specification engineer or procurement lead will read between five and ten supplier pages before reaching out. That is not new. What is new is how few of those pages are now Google's classic ten blue links — AI Overviews, "People also ask" and zero-click answers have eaten the top of the page. Your job is to be quoted in those answers, not just listed below them.

Two: technical SEO has gone from optional to load-bearing. Google ranks pages it can crawl, render, and verify quickly. Most British manufacturer sites we audit fail one or more of: server-side rendered HTML for the key pages, INP (interaction to next paint) under 200ms, a sitemap that matches reality, and structured data on products, services and the organisation.

Three: Google's quality raters are looking for first-hand expertise. The Search Quality Rater Guidelines now talk explicitly about experience — the "first E" in E-E-A-T. For an established UK engineer with thirty years of fabrication history, this is good news. The trick is to write the content so the experience is legible from the page.

The technical foundation

Before anything else, we want a site that meets four bars. None of these are exotic — but together they decide whether the rest is worth doing.

• Server-rendered HTML for all key landing pages. If you are on a JavaScript-first stack and the body content only appears after hydration, you are bleeding crawl budget and AI accessibility. Most modern frameworks can pre-render or SSR. Use them.
• Core Web Vitals in the green band. LCP under 2.5 seconds, CLS under 0.1, and — since March 2024 — INP under 200ms. The INP transition caught a lot of mid-market sites out; if you have not been measured against it, you should be.
• An XML sitemap that matches the live URL tree, and a robots.txt that says what you mean. Sites that have been through two CMS changes routinely have a sitemap pointing at URLs that redirect or 404. Fix it.
• Structured data: Organization, Product, Service, BreadcrumbList, and FAQPage where it applies. Validated, not just present. We see invalid JSON-LD on roughly half the manufacturer sites we audit; an invalid block does not help and may quietly cause Google to ignore the page-level signals.

Technical SEO is not glamorous, and it is not the kind of work that an agency wants to bill for forever. We do it once properly and then watch it on a monthly cadence.

Capability content over keyword content

The old playbook said: pick a keyword, write a page, build links. That still works for some queries, but it is a sub-optimal strategy for manufacturers, because most of the queries you actually want to win are long-tail capability queries — "5-axis CNC milling of titanium for medical devices UK", "low-volume injection moulding 50–500 unit runs", "ISO 9001 fabrication contract manufacturer Midlands".

These queries are too narrow to chase keyword-by-keyword. What works is capability content: a structured page per capability, plus per-sector pages that show that capability applied to a real customer problem. We have written separately about getting that expertise out of your experts' heads and onto the page. The result is a site map that looks like the company itself.

A capability page should answer, in this order:

1. What we do, said plainly (one paragraph)
2. What the constraints are — tolerances, sizes, materials, run lengths, certifications
3. What it costs (a range, or the questions that determine cost — but say something)
4. What we have made before, with named industries if not named clients
5. What happens next — a specific, scoped CTA, not "contact us"

This is also the structure that AI Overviews lift from. Which is the next thing.

AI Overviews and the new top of the page

For a procurement-led query, Google now frequently shows an AI-generated summary above the blue links, citing two to four sources. Those citations send traffic; perhaps more importantly, they confer authority. For a B2B manufacturer, being cited in an AI Overview is functionally a referral from Google.

What we have seen work, across a dozen client programmes:

• Write definitions of what you do, on the page that does it. The first 150 words of a capability page should function as a self-contained definition that an LLM could lift verbatim and cite. This is not a marketing intro paragraph. It is a definition.
• Use proper HTML semantics. <h1>, <h2>, ordered and unordered lists, definition lists. AI Overview citations skew heavily toward semantically marked-up content because it parses cleanly.
• Cite your own sources. When you make a claim — "average lead time on a 200-unit injection-moulded run is four weeks" — say where it comes from. Your own production data is a citation. An LLM is more likely to use a page that shows its working.
• Maintain a few longer, authoritative pages per capability. Not blog posts — pillar pages. Updated annually, with a visible "last updated" date.

Measuring what matters

This is the bit most agencies get wrong. They report on keyword rankings, organic sessions, and a sea of impression data, none of which a managing director can act on.

We report on three things:

1. Pipeline-eligible enquiries from organic search, by landing page. Tied to the CRM. If a page does not generate enquiries within a sensible window, it is either the wrong page or in the wrong place in the site.
2. Share of voice on the capability queries that matter. Not a vanity basket of head terms — the long-tail queries that map to actual sales. Tracked monthly. Trended over a year.
3. Technical health. Crawl errors, broken redirects, indexation coverage, Core Web Vitals at the 75th percentile. One page, traffic-light.

Everything else is noise.

Where a £5m engineering firm should start

If you are running a typical mid-market manufacturer with a site that has not had a proper SEO programme on it for two or three years, do these things in order:

1. Audit. Technical, content, and the gap between your live URLs and your sales pipeline. Two weeks.
2. Fix the technical foundation. Render mode, Core Web Vitals, sitemap, structured data, redirect chains. Four to six weeks of focused work.
3. Rebuild the capability and sector pages. One per capability. One per sector you actively sell into. Linked properly. This is the largest piece of work and the most valuable.
4. Install measurement. GA4 properly configured against the CRM, Search Console verified, a monthly dashboard the MD can read in two minutes.
5. Run the programme. Once a month, every month, for at least twelve months. SEO compounds, but only if you are still there. This is exactly the shape of the retainer-based SEO work we run.

We have done this maybe forty times. The pattern is consistent: technical pays for the rest, the capability pages drive the pipeline, and the measurement is what gets the next year's budget signed off.

If any of this is useful, or you would like a sober second opinion on what your current programme is doing, we are at hello@ninestones.co.uk. Thirty minutes, no pitch deck.