Technical SEO Services

Core Web Vitals are the three metrics Google uses to measure real-world page experience: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). If those names mean nothing to you, here’s the plain version: how fast your page loads its main content, how quickly it responds when someone clicks or taps, and how stable the layout stays while it’s loading.

INP replaced First Input Delay (FID) in March 2024, and it’s a much harder metric to pass. FID only measured the first interaction; INP measures every interaction throughout the entire page lifecycle and reports the worst one. That means JavaScript-heavy sites that felt fine under FID are now failing under INP.

The March 2026 core update strengthened performance signals further. Google hasn’t confirmed CWV as a direct, heavy ranking factor — they call it a “page experience signal” — but the data is clear: sites with good CWV scores consistently outrank comparable sites with poor scores, all else being equal. It’s a tiebreaker, and in competitive niches, tiebreakers matter.

What’s changed practically is that you can no longer ignore performance and expect to rank. Even small businesses with modest sites need to pass these thresholds. The good news is that most CWV fixes — image optimisation, font loading strategy, reducing JavaScript — also make your site genuinely better for visitors. It’s one of the rare cases where what Google wants and what users want are exactly the same thing.

Google has been cautious about calling speed a direct ranking factor, but the evidence is overwhelming that it matters. The Google/Deloitte “Milliseconds Make Millions” study found that a 0.1-second improvement in mobile load time lifted conversions by 21.6% for lead generation sites and 8.4% for retail. That’s not a ranking improvement — that’s the same traffic converting better because the experience improved.

From a ranking perspective, speed works as both a direct signal (via Core Web Vitals) and an indirect one. Slow pages get higher bounce rates. Higher bounce rates mean less engagement. Less engagement means fewer links, fewer return visits, and weaker user signals. The compounding effect is significant over time.

Mobile speed matters more than desktop. Over 60% of Google searches happen on mobile, and mobile-first indexing means Google primarily uses your mobile version for ranking. If your desktop site is fast but your mobile experience is sluggish, that’s what Google sees.

The practical wins are well-established: modern image formats (WebP/AVIF), lazy loading below-the-fold content, preloading critical fonts, reducing unused JavaScript, improving server response times (TTFB), and leveraging browser caching. Most sites can shave 1-3 seconds off their load time with these fundamentals alone — and the ranking and conversion benefits follow.

Crawl budget is the number of pages Googlebot will crawl on your site within a given timeframe. For most small to medium websites — under 10,000 pages — crawl budget isn’t something you need to worry about. Google will find and crawl all your pages without any special effort on your part.

Where crawl budget becomes a real concern is on large sites: e-commerce stores with thousands of product pages, sites with faceted navigation generating millions of URL variations, or sites with significant amounts of duplicate or thin content. In these cases, Googlebot can waste its crawl budget on pages that don’t matter, leaving important pages undiscovered or stale.

What most small businesses should actually focus on is crawl errors, not crawl budget. If Google is encountering 404s, redirect loops, server errors, or pages blocked by robots.txt that shouldn’t be, those are real problems with real ranking impact. Fixing those is far more valuable than worrying about how many times Googlebot visits per day.

The distinction between crawl budget and index budget is also worth understanding. Getting crawled and getting indexed are two different things. Google might crawl a page but decide not to index it — usually because it’s thin, duplicate, or low-quality. Ensuring your important pages are both crawlable and worth indexing is the real goal.

Structured data is code you add to your pages that helps Google understand what your content is about. It uses a vocabulary called Schema.org to label things — this is a product, this is a review, this is a FAQ, this is a local business — in a way search engines can read reliably.

The direct benefit is rich results: enhanced listings in search that show extra information like star ratings, price ranges, FAQ dropdowns, recipe cards, event dates, or breadcrumb navigation. These listings take up more space in search results and typically get significantly higher click-through rates than plain blue links.

The types of structured data that earn rich results include FAQ schema, HowTo schema, Review/AggregateRating, Product, LocalBusiness, Event, Recipe, and Breadcrumb. Not all schema types generate visible rich results — some just help Google understand your content better, which has an indirect benefit for rankings and for AI-generated answers.

Implementation needs to be done properly. Invalid or incorrectly applied schema won’t earn rich results and can trigger manual actions if Google considers it misleading. We use Google’s Rich Results Test and Schema Markup Validator to test every implementation, and we monitor Search Console for any schema-related issues after deployment.

In 2026, structured data has additional importance for AI search. Google’s AI Overviews and other generative search features rely heavily on structured, well-organised content. Sites with clean schema markup are more likely to have their content surfaced in AI-generated answers.

Technical SEO problems are insidious because they’re invisible to most people. Your site looks fine, your content is solid, but something underneath is quietly eroding your visibility. Here are the warning signs that suggest technical issues are at play.

A sudden traffic drop with no content changes or algorithm update is the classic signal. If your rankings fell but you didn’t change anything, something technical has likely shifted — a robots.txt change, a noindex tag added by accident, a site migration that broke redirects, or a plugin update that altered your page structure.

Pages not appearing in Google despite being published is another red flag. Check Google Search Console’s coverage report. If pages are showing as “Discovered — currently not indexed” or “Crawled — currently not indexed,” there’s a technical or quality issue preventing indexation.

Slow Search Console data, redirect loops, soft 404s (pages that return a 200 status but show error content), and rendering issues (where Google sees a different version of your page than visitors do) are all technical problems that need attention. If any of these sound familiar, a proper technical audit will identify the root cause and the fix.

Because you get the senior specialists doing the work, not an account manager relaying messages. We're a small, senior team: strategy, execution and reporting come from the people who own the result, decisions happen fast, and nothing falls through the gaps between departments. If that sounds like a better fit, get in touch or see how pricing works.