Technical SEO is the engineering layer beneath your rankings: how search engines discover, crawl, render, and index your pages. It covers site speed, crawl efficiency, JavaScript rendering, structured data, and site architecture. When this layer breaks, even great content goes invisible. When it works, every other SEO investment performs better.
The audit-first rule
We never fix before we diagnose. Most technical engagements we inherit started backwards: a speed plugin, some compressed images, no movement. Speed was never the bottleneck — Google couldn’t reach half the site.
Audits surface the real causes: a UK WooCommerce store with 48,000 indexable faceted URLs for 300 products; a staging site pushed live with a site-wide noindex; category pages rendering client-side so Googlebot saw no articles. Every engagement therefore begins with one of our SEO audits.
Crawl budget, honestly
Under roughly 10,000 URLs, you almost certainly don’t have a crawl budget problem. You have a crawl waste problem: broken links, redirect chains, thin pagination, parameter URLs burning crawler time on pages that will never rank.
Real crawl budget constraints appear at scale — large e-commerce catalogues, marketplaces, publishers with old archives, aggressive faceted search. Google sets crawl frequency from capacity (server health, errors) and demand (popularity, freshness). For a large UK retailer, new products can sit undiscovered for weeks while crawl is wasted on 200,000 filter combinations.
The diagnostic tells you which side of that line you’re on: small sites need waste removed, large sites need log-file analysis and parameter handling. Small businesses are routinely sold “crawl budget optimization” they never needed.
JavaScript SEO: what breaks
W3Techs reports over 98% of websites use JavaScript client-side. JavaScript isn’t bad for SEO — but the failure modes have changed.
Googlebot processes pages in two waves: raw HTML first, JavaScript rendering later — sometimes days later. Script-dependent content can be indexed late, partially, or stripped of context. What breaks:
- Hydration mismatches. Server HTML arrives, then client JavaScript re-renders it; if versions differ, Google may index either.
- JavaScript-injected links. Navigation existing only after scripts run gets discovered late or missed, orphaning sections.
- Delayed content. Lazy-loaded cards and infinite scroll often aren’t in the rendered snapshot Google keeps.
- Client-side redirects and canonicals. Late and unreliable versus server-side HTTP redirects.
Diagnosis: compare raw vs rendered HTML in Google’s URL Inspection tool — render-only content means a JavaScript SEO problem, usually fixed with server-side rendering or pre-rendering on critical templates. This also matters for AI search visibility, since AI crawlers mostly consume raw HTML.
Schema: signal vs decoration
Structured data is the most over-implemented, least strategic area of technical SEO.
Schema isn’t a direct ranking factor. Its value is rich-result eligibility — ratings, prices, availability — making listings more clickable. We prioritize:
- Organization + LocalBusiness — baseline for UK businesses; feeds knowledge panels and local results (local SEO).
- Product with price, availability, reviews — the highest-value schema in e-commerce.
- Article — expected on publishers; supports Top Stories eligibility.
- FAQ schema — sparingly. Google has sharply reduced FAQ rich results.
Schema types that never earn rich results are wasted effort. Invalid schema is worse: markup contradicting visible content can lose eligibility. Validate in the Rich Results Test before and after deployment.
Site architecture and internal linking
Architecture answers one question: how many clicks from the homepage to any important page? Flatter is better.
Deep pages starve: five or six clicks deep means less crawling, less link equity, worse rankings — regardless of content quality. Orphan pages — no internal links — are worse: discoverable only via sitemap, a weak importance signal. Ahrefs found 66.31% of pages in its billion-page study had zero backlinks; internally, the picture is often just as bleak.
Good architecture: three clicks max from homepage to any revenue page, genuine hub pages, contextual links from related content. Every major section should be reachable through visible navigation, not only filters or site search — where technical SEO meets content strategy: architecture distributes authority, content earns it.
Our audit process
Every engagement follows this sequence. No exceptions.
- Full-site crawl — status codes, redirect chains, canonicals, indexation directives, response times.
- Search Console cross-reference — crawl stats, index coverage, Core Web Vitals: what Google uses versus what exists.
- Rendering audit — raw vs rendered HTML on key templates.
- Indexation logic — robots.txt, meta robots, canonicals, hreflang (vital for UK sites serving Ireland/EU), pagination, parameters.
- Field-data performance from the Chrome User Experience Report — lab scores lie when users are on mid-range phones with patchy 4G.
- Structured data — rich-result eligibility, not raw markup presence.
- Prioritized fix list ranked by impact vs effort, with developer-ready specs.
Impact vs effort
| Fix | Impact | Effort |
|---|---|---|
| Accidental noindex / robots blocks | Very high | Low |
| Broken internal links, redirect chains | Very high | Low |
| JavaScript-dependent core content | High | Medium–High |
| Orphaned revenue pages | High | Low |
| Core Web Vitals failures | Medium–High | Medium |
| Schema implementation | Medium | Low |
| Meta description rewrites at scale | Low | High |
Ahrefs found meta descriptions missing on 72.9% of studied sites — common, yet almost never the actual bottleneck.
What technical SEO cannot do
Technical SEO cannot save thin content: 300 words of generic copy matching forty competitors won’t rank no matter how fast the site is — Ahrefs found 90.63% of pages get zero organic traffic, overwhelmingly a content and authority problem.
It cannot fix a drop you don’t understand. Post-update traffic loss is usually about content quality and intent match, not technical debt — and we’ll say so instead of selling a migration.
It cannot guarantee rankings — nobody can. What we guarantee is the diagnostic: what’s broken, what’s wasteful, what to fix first.
And it’s not always worth buying. A small UK service business with a 20-page brochure site that loads fast and indexes cleanly needs an afternoon of basics, not a £2,000 deep-dive. We’ll say that on the first call.
Pricing and timelines in the UK
A focused audit for a small UK business site (under ~500 URLs) runs £800–£1,500 over one to two weeks. Mid-size e-commerce or publisher audits land around £2,000–£4,000 over three to four weeks, including log-file analysis and rendering diagnostics.
Implementation is separate: small fixes ship in days; rendering overhauls need developer time in weeks. One timing reality: Search Console reflects Core Web Vitals changes on a roughly 28-day rolling window, so performance fixes take a month to show in reports. Only ~48% of mobile origins pass all three Core Web Vitals (HTTP Archive Web Almanac / Chrome UX Report), and Google reports 53% of mobile visitors abandon pages taking over three seconds to load — the conversion case for speed is strong.
Frequently Asked Questions
How long does a technical SEO audit take?
A small business site takes one to two weeks from crawl to report. Mid-size e-commerce or publishers take three to four weeks with log-file analysis and rendering diagnostics. We never compress diagnostics below what the site’s complexity demands, because a rushed audit misses the issues that matter most.
Will technical SEO guarantee better rankings?
No — distrust anyone who says otherwise. Technical SEO removes barriers to crawling, rendering, and indexing: it makes ranking possible. Whether you rank depends on content quality, intent match, and authority. We guarantee an honest diagnostic, not positions. Always ask what an agency actually guarantees before you sign anything.
Does a small business website really need technical SEO?
It needs the right amount: a 20-page brochure site needs clean indexation, fast loading, correct local schema, and working internal links — not crawl-budget analysis. The expensive mistake is an enterprise-scale audit for a small site, or skipping the basics.
My site is built with JavaScript. Is that an SEO problem?
Not automatically — only when critical content, links, or canonical tags exist solely after scripts execute. Compare raw vs rendered HTML in Google’s URL Inspection tool — if they match on what matters, your setup needs no intervention. That single comparison catches most JavaScript SEO issues in under five minutes.
Is schema markup a ranking factor?
No. Google confirms structured data is not a direct ranking signal. Its value is rich-result eligibility — ratings, prices, availability — making your listing more prominent and clickable. Treat schema as a click-through-rate investment, prioritizing the types that actually earn enhanced SERP display.
Get a diagnostic before you spend another pound on SEO
If your content isn’t ranking, your pages aren’t indexing, or your developers insist everything is fine while traffic flatlines — start with the crawl. Our audit shows what’s broken, what’s wasteful, and what to fix first.
Book a technical SEO consultation — we’ll tell you honestly whether technical SEO is your problem, including when it isn’t.
