The short version: Technical SEO is everything that helps search engines find, crawl, understand, and trust your website, from crawlability and site speed to structured data and canonical tags, and it matters because none of your content or link building works if Google cannot reach the page in the first place. Most sites do not need a 60-point audit. They need six or seven things fixed, in the right order.
What technical SEO means
Technical SEO is the non-content, non-link side of search optimisation. It is the infrastructure work: making sure Googlebot can crawl your site, that pages load fast enough that people do not bounce, that your server sends the right signals about which page is the “real” one, and that your site does not accidentally hide itself from search engines through bad code.
Content SEO answers the question “is this page useful and well written.” Technical SEO answers a colder, less glamorous question: “can a search engine even get to this page, read it, and trust what it finds.” You can write the best article on your topic and it will rank nowhere if it’s blocked by robots.txt, buried nine clicks deep, or served with a canonical tag pointing to a different URL. I have seen this exact combination three times in the last two years, once on a client’s own site.
The migration that lost 37% of organic traffic in six weeks
A client, a mid-size UK e-commerce brand selling home fitness equipment, replatformed from Magento to Shopify in early 2025. The design was better. The site was faster. The developer had done a tidy job on the front end. Six weeks after launch, organic traffic was down 37% year on year, and it kept sliding.
Here’s what had happened, and it’s a textbook technical SEO failure: the migration team had set every product page’s canonical tag to point at the collection page it sat under, instead of pointing at itself. So Google was told, page after page, “ignore this, the real page is over here.” Roughly 1,400 product pages were quietly telling Google they didn’t matter. On top of that, the old URL structure used /products/name and the new one used /collections/category/products/name, and only about 60% of the old URLs had 301 redirects set up. The rest 404’d.
We fixed the canonical tags in one afternoon once we found them (Screaming Frog spotted the pattern in under ten minutes of crawling). The redirect gaps took longer, about two weeks of mapping old URLs to new ones from Search Console’s old crawl data and analytics history. Traffic started recovering in week four post-fix and was back to pre-migration levels by week ten. That is a three-and-a-half-month hole in revenue caused entirely by two technical mistakes that had nothing to do with content quality or backlinks. This is the bit people skip when they explain technical SEO in the abstract: it’s not theoretical, it directly moved revenue.
The key elements of technical SEO, explained plainly
Crawlability
Can search engine bots reach your pages at all? This comes down to your robots.txt file (which can accidentally block entire sections of a site with one wrong line), your internal linking (orphan pages with no internal links pointing to them are much harder to discover), and crawl budget on very large sites. For a site under 10,000 pages, crawl budget is rarely the issue. For a site with 500,000 product pages, it can be everything.
Indexability
Being crawlable does not mean being indexed. Noindex tags, canonical tags pointing elsewhere, and duplicate content can all cause Google to crawl a page and then decline to add it to the index. Check Google Search Console’s Pages report and look specifically at “Crawled, currently not indexed,” it’s one of the most ignored reports in the entire tool and it usually points straight at a thin content or duplication problem.
Site speed and Core Web Vitals
Google measures three things here: Largest Contentful Paint (how fast the main content loads, aim under 2.5 seconds), Interaction to Next Paint (how responsive the page feels when clicked, aim under 200 milliseconds), and Cumulative Layout Shift (how much things jump around while loading, aim under 0.1). I’ll say the thing most technical SEO guides will not say plainly: for the vast majority of sites, Core Web Vitals are a tie-breaker, not a lever. If your competitor has better content and more relevant links and you have a faster site, you still lose. Speed matters enormously for conversion rate and user experience. Its direct ranking weight is smaller than the industry has spent five years implying, and Google’s own John Mueller has said as much in webmaster hangouts more than once.
Mobile-first indexing
Google has used the mobile version of your site for indexing and ranking since 2021, for every site. If your mobile site hides content, has smaller image sets, or strips out sections that appear on desktop, that stripped-down version is what Google evaluates. I still find sites in 2026 where the mobile nav hides half the internal links that exist on desktop, which quietly breaks internal linking for anyone Google crawls with its mobile bot, which is now everyone.
HTTPS and site security
This one is close to solved industry-wide, but it’s still worth checking for mixed content warnings, where a secure page loads an insecure image or script and browsers flag it. It’s a small ranking signal on its own now but a real trust signal for users, and Chrome will visibly warn visitors about insecure pages, which kills conversion rate regardless of rankings.
Structured data (schema markup)
Schema is code added to a page that explicitly tells search engines what something is: a product with a price and stock status, a recipe with a cook time, a FAQ, a review with a star rating. It does not directly boost rankings, but it earns you rich results, the star ratings, FAQ dropdowns, and product info that appear directly in search listings. Rich results typically improve click-through rate, sometimes noticeably, because your listing takes up more visual space and answers part of the question before the click. Google’s own structured data documentation is the most reliable source here, agency blog posts on this topic go stale fast because Google changes which schema types qualify for rich results fairly often.
XML sitemaps
A sitemap is a file listing every URL you want indexed, submitted through Search Console. It does not force indexing, it’s a hint, but it speeds up discovery, especially for new pages and large sites. The common mistake is a sitemap stuffed with old, redirected, or noindexed URLs, which sends Google mixed signals about what matters on the site.
Canonicalization
The canonical tag tells search engines which version of a page is the master copy when duplicates or near-duplicates exist, common with e-commerce filters, URL parameters, and www versus non-www versions of the same site. Get this wrong, as in the story above, and you are actively telling Google to ignore your own pages.
Redirects and URL structure
A 301 redirect passes the vast majority of a page’s accumulated authority to its new location. A 302 redirect, meant to be temporary, does not pass the same signal and is frequently used by mistake where a 301 was needed. Redirect chains, where URL A redirects to B which redirects to C, slow crawling and can leak authority at each hop. Two hops is generally fine. Five or six hops, which I have found on older sites that have been through multiple redesigns, is a real problem.
JavaScript rendering
Sites built heavily in React, Vue, or similar frameworks sometimes serve content that only appears after JavaScript executes. Google can render JavaScript, but it does so in a second wave after the initial crawl, and it does not always render everything the way a browser does. If your critical content, product prices, key headings, main body text, only appears after JavaScript runs, test it directly using the URL Inspection tool in Search Console rather than assuming it’s fine.
Log file analysis
Server log files show exactly which pages Googlebot visited, how often, and what response code it got. This is the most underused item on this entire list. Most site owners never look at their logs and instead guess at crawl behaviour from Search Console’s sampled data. Log files show the truth: which sections Google visits daily, which it ignores for months, and where it’s wasting crawl budget hitting dead pages.
A simple order of operations, since most audits get this backwards
If you’re doing this yourself, work in this order, because fixing content before fixing crawlability is wasted effort:
- Run a full crawl with Screaming Frog or Sitebulb and pull the list of 4xx and 5xx errors first
- Check robots.txt is not accidentally blocking important sections
- Check Search Console’s Pages report for anything marked “excluded” and read the reason given for each
- Audit canonical tags on your top 50 pages by traffic, don’t try to check every page manually
- Run Core Web Vitals through PageSpeed Insights on your five highest-traffic templates, not every individual page
- Confirm your sitemap only contains live, indexable, 200-status URLs
- Add or fix schema markup for your product, FAQ, or article pages, whichever matches your content type
The uncomfortable part nobody wants to put in the sales deck
Here’s the bit that agencies rarely say out loud: most technical SEO audits get delivered as a 40-page PDF and then sit in a shared drive untouched, because fixing them requires a developer’s time and developers are usually busy building the next feature, not fixing meta robots tags from a report they didn’t ask for. I have written those PDFs. The client nods, says it’s fantastic, and eighteen months later half the issues are still there because nobody owned the follow-through. Technical SEO work is only as good as the ticket that gets created in the dev backlog and gets prioritised. If you’re hiring anyone, agency or freelancer, for this work, ask them how they get fixes implemented, not just found, because finding problems is the easy 20% of the job.
This is also why more businesses are bringing in someone to sit between marketing and development rather than commissioning another audit, which is where working with an AI consultant for small business who understands both the technical and the practical implementation side tends to get more fixed than another standalone report.
Where technical SEO overlaps with the rest of your marketing stack
Technical SEO doesn’t sit in isolation. Image file size and alt text, both technical concerns, connect directly to how your visuals perform, and if you’re producing graphics for the site it’s worth understanding the basics covered in key graphic design terms so your designer and developer aren’t speaking past each other about compression and formats. If your team is using AI tools to draft site copy or product descriptions at scale, the crawlability and duplicate content risks multiply fast, which is one reason understanding prompt engineering for marketing teams matters even for technical output, and keeping a consistent brand voice when using AI stops AI-generated pages from reading as thin, near-duplicate content that trips the exact indexability issues covered above.
If you’re newer to this field entirely and wondering whether technical SEO is a viable skill to build from home, it is, it’s one of the more employable specialisms inside digital marketing precisely because so few people do the log file and crawl analysis work well, and it’s worth a look alongside other options in our rundown of entry level work from home jobs.
How much technical SEO costs to fix
For a small business site under 200 pages, a proper technical audit plus fixing the top issues typically runs somewhere between £800 and £3,000 depending on whether a developer needs to be involved for template-level changes. For larger e-commerce or enterprise sites with thousands of pages, ongoing technical SEO retainers commonly sit between £1,500 and £5,000 a month, because the work is never truly finished, new pages get added, plugins update, developers push changes that break things without meaning to. Anyone quoting a one-off fee in the low hundreds for a full technical audit on a large site is either doing a shallow automated scan or underpricing the actual hours involved.
To see how any site is put together, paste its URL into the free website mapping tool and it reads the sitemap and lists every page.
Before you request indexing, read the zero-impression index study: most such pages were already indexed.
Frequently asked questions
Is technical SEO more important than content?
Neither works without the other, but technical SEO comes first in sequence. A brilliant article on a page Google cannot crawl or has been told to ignore via a canonical tag will never rank, so technical issues need clearing before content or link building can show their full effect.
How often should a site have a technical SEO audit?
A full audit once or twice a year is enough for most small to mid-size sites, with a lighter monthly check of Search Console’s Pages and Core Web Vitals reports in between. Sites that change frequently, large e-commerce catalogues or content sites publishing daily, benefit from monthly crawls to catch new issues before they compound.
Can I do technical SEO myself without hiring anyone?
Yes, for a small site. Free tools like Google Search Console and a free-tier crawl from Screaming Frog (up to 500 URLs) cover most of what a small business needs. Once a site passes a few thousand pages or involves JavaScript rendering and log file analysis, it usually becomes worth bringing in someone with hands-on experience.
Do Core Web Vitals really affect rankings?
They affect rankings at the margins, mainly acting as a tie-breaker between pages of similar relevance and quality, rather than a major lever on their own. A slow site with excellent, relevant content will usually still outrank a fast site with thin content, though fixing poor speed is still worth doing for conversion rate alone.
If you would rather not build this yourself, start with submit a hosting guest post.
