Services · Be found
Technical SEO for complex B2B websites.
Technical SEO Scoping Audit · from £8,500
3 to 4 weeks · Robin Dally leads the work
If your content is not getting the search visibility you expected, the cause may be in the site itself: pages Google cannot reach, duplicate URLs, or text that only appears after JavaScript runs. We investigate with your developers and rank the fixes. Robin Dally leads the work.
The short answer
What is technical SEO in 2026?
Technical SEO makes sure search engines and AI tools can reach, understand, and use the right parts of your website. That means clean crawl paths, consistent canonical tags, useful structured data, fast pages, and HTML that does not depend on JavaScript to show its content. Both SEO and answer engine optimisation (AEO) are built on top of it.
Of the llms.txt files in Ahrefs' May 2026 sample received no requests. The sample was 137,210 sites using Ahrefs Web Analytics, 28% of which served a file, and it skews technical. A shortcut file is no substitute for pages that crawlers can reach and read.
Ahrefs, June 2026 · May 2026 dataGooglebot can render JavaScript, but not every automated fetcher can. Important content should be accessible as text.
Google Search Central, JavaScript SEO basicsGoogle says AI Mode and AI Overviews may issue multiple related searches across subtopics and sources, a process called query fan-out. So we check important content across the site, including what a crawler receives before JavaScript runs. Read our write-up on llms.txt
What does an audit for AI search add?
Crawl paths, canonicals, and useful content remain important. On top of those search foundations, we check what AI search tools can reach, and we treat search crawlers and training controls separately.
| Check | Search foundations | What we add for AI search |
|---|---|---|
| Access | Googlebot and Bingbot crawl rules | Search bots and training controls checked separately |
| JavaScript | Googlebot can render JavaScript, with limitations | Test what relevant fetchers receive; make key text accessible |
| Structured data | Accurate schema markup describing visible content | No special schema needed for Google's AI features, so we check yours matches the page |
| Performance | Measure loading and responsiveness | Investigate response errors and failed fetches |
The work
What does a technical SEO engagement include?
In most projects your developers make the code changes. We write the implementation briefs, check the work before and after it ships, and track crawling, indexing, and traffic afterwards.
A ranked list of what to fix
We crawl the site and check it against about 40 points covering indexing, rendering, speed, structured data, internal links, and AI crawler access. Each finding is scored critical, high, medium, or low and comes with an implementation estimate, so you can decide what goes first and what it will cost your developers.
The right pages crawled and indexed
We fix robots.txt rules, XML sitemaps, redirect chains, and canonical tags (the tag that tells Google which of several similar URLs is the main one). On large sites we read the server logs to see which pages Googlebot and AI crawlers fetch, so their time goes on the pages that bring in business.
Pages AI tools can read
On JavaScript-heavy sites, such as those built with React or Next.js, we check what AI crawlers receive. Where the stack allows, we move key content into server-rendered HTML. You also get a written policy on which AI crawlers to allow and which to block.
Structured data Google can trust
We mark up your organisation, authors, and services with structured data, the code that labels the entities a page describes. This entity information can help Google understand and distinguish your business in search.
Speed and internal links, measured
We assess images and scripts against Core Web Vitals, Google's measures of loading, responsiveness, and visual stability. We also find valuable pages that lack internal links. Agreed monitoring helps us investigate regressions when templates change.
Client experience
PEI Group
B2B financial mediaCurrent retainer
SEO and content architecture at publishing scale.
Our experience includes a network of financial-media websites with hundreds of thousands of articles.
Cloudhelix
Past client workThe Cloudhelix engagement started with a website audit to find and fix the technical issues holding back organic visibility. The published case study covers the whole programme, not technical SEO alone.
Read the Cloudhelix case studyHow it starts
Start with a ranked list of what to fix.
A Scoping Audit starts from £8,500 over 3 to 4 weeks and gives you a prioritised backlog. A Build Project starts from £22,000 for a fixed scope over 8 to 16 weeks, and a Monthly Retainer from £5,000 a month with a 6-month minimum. Moving platform or domain? The migration SEO audit starts from £4,500, with checks before and after launch.
Technical SEO Scoping AuditFrom £8,5003 to 4 weeks · prioritised findings with severity ratings and implementation estimates
Before and after launchFrom £4,500
8 to 16 weeksFrom £22,000
6-month minimumFrom £5,000/mo
Before we talk
Questions about technical SEO.
Can you guarantee rankings or AI citations?
No. No one can. Search engines and AI tools decide what they rank and cite, and structured data does not guarantee a place in Google's Knowledge Graph. What you get is a ranked list of faults, and we check the work before and after it ships. We then track crawling, indexing, and traffic. How soon a change shows depends on when your pages are recrawled and on the work agreed.
Is technical SEO still relevant if we're focused on AEO?
Yes. Accessible, indexable pages improve the conditions for retrieval. We check technical barriers before recommending a large content programme.
Our site runs on a platform like WordPress or Webflow. Do we still need this?
A CMS does not settle every technical SEO decision. We check the implementation: templates, internal links, performance, structured data, and crawler access.
Should we allow or block AI crawlers?
We agree the policy with you, distinguishing search from training. OAI-SearchBot is used for ChatGPT search, while GPTBot collects content that may be used for training. Google Search uses Googlebot. Google-Extended is a separate content-use control token, not a crawler user agent; its settings do not control Google Search inclusion. We check current documentation before recommending changes.
Will you work with our development team?
Yes. In most projects your developers make the code changes, and we write the implementation briefs and check the work before and after it ships.
How long does a Build Project take?
Usually 8 to 16 weeks, depending on the size of the site and how deep the problems go. We agree a fixed scope and timeline once the audit shows what needs doing.
Should we talk to you before a migration?
Yes, before you commit to a plan. Checking redirects and indexing on staging can reduce avoidable launch problems. The migration SEO audit includes checks before and after launch.
Think the foundations are holding you back?
Tell us what you are seeing. We will say whether technical SEO is the fix or whether something else comes first.