Eleven deep guides, rebuilt from seventy-one fragments

The Complete Technical SEO Guide

Technical SEO is invisible when it is right plus expensive when it is wrong. These eleven guides cover the whole subject properly, rather than as a hundred one-paragraph definitions of terms you were only trying to look up once.

11 guidesCrawlingSitemapsStatus CodesMobileAudits
11 guides
Five sections
Audited quarterly on every plan

Technical SEO is everything that decides whether your content ever gets a fair hearing. A page can be the best answer on the internet plus earn nothing, because a file in the root of the site is quietly blocking it. Perhaps a tag is pointing search engines at a different page. Perhaps the server takes four seconds to respond. None of it is visible to a visitor. All of it is checkable, most of it is fixable in an afternoon plus almost nobody looks until something has already gone wrong.

Start Here

What Is Crawling in SEO and How Does It Work?

Everything else on this page is irrelevant if a search engine cannot reach your pages or decides not to keep them. This covers crawling and indexing, the difference between them, what Googlebot actually does, crawl errors, crawl traps, crawl budget, how to check whether your site can be crawled at all plus which pages ought to be kept out on purpose. Eight subjects, one guide, because they only make sense together.

Read the foundation guide
The one that covers all the others

Checking All Of It

Everything above is a subject. This is the process that catches all of them at once, on a schedule, before any of it becomes the reason a site stopped performing.

Included in every plan, from £350 a month

We Run This Every Quarter. Then We Fix It.

Every client gets a full technical audit four times a year covering everything on this page, plus the important part: we do the fixing. An agency that emails you a list of crawl errors has not done the work, it has described it. Technical SEO is invisible when it is right, so the only way to know it is being handled is that somebody keeps checking.

What every audit covers:

Crawling and indexing Robots.txt and sitemaps Status codes and broken links Canonicals and duplication Speed, hosting and mobile Fixed, not just reported
£350per month

One clear retainer. No setup fee. Four full audits a year.

Using these guides

Frequently Asked

Where should I start?
With crawling and indexing, since nothing else matters if search engines cannot reach your pages or decide not to keep them. Then the audit guide, which is the practical version of everything else here. Those two between them will tell you whether you have a problem worth chasing.
Why are there eleven guides where there used to be seventy-one pages?
Because seventy-one one-paragraph definitions were worse for everybody than eleven guides that cover a subject properly. A page explaining what a 410 error is, on its own, helps nobody understand what to do about it. The same eight status codes in one reference table, with the context around them, is genuinely useful. We recommend this kind of consolidation to clients regularly plus it would be odd not to do it to our own site.
Which of these is most likely to be causing a problem right now?
In our experience, three things. Robots.txt, because one wrong line removes a site from search with nothing visibly broken. Canonical tags left pointing at the wrong page, usually after a rebuild. And hosting, where a cheap plan is quietly costing more in lost visibility than a better one would cost to buy.
Do I need technical SEO if my site is small?
You need most of it, though the effort is much smaller. A ten page site still needs to be crawlable, still needs correct status codes plus still needs to work on a phone. What it does not need is crawl budget management, hreflang or anything to do with international structure. Read the pillar guide, the two crawl-control guides plus the audit page and you have covered a small site.
My developer says the site is fine. Is a separate audit worth it?
Usually yes, plus not because your developer is wrong. A site can be built correctly by any reasonable standard and still have problems that only appear from a search engine's point of view: a sitemap listing pages that no longer exist, canonicals pointing at a staging domain, a parameter creating thousands of near-identical URLs. Those are not build faults. They are the things a technical audit is for.
How often should this be checked?
Quarterly for most sites, which is what we run for every client. More often if the site changes frequently, if it has thousands of pages or if anything has recently been rebuilt. The point of a schedule is that technical faults are silent, so the alternative to checking regularly is finding out when somebody notices the enquiries have stopped.