Technical SEO is the work of making sure a search engine can reach your pages, load them, and understand them. None of it is visible on the page, and all of it decides whether your writing ever gets a chance.
It sounds intimidating. In practice it is a short list of questions with clear answers, and most sites have problems in only one or two areas.
Can a search engine reach the page?
Nothing else matters until this is true. A page can be excellent and still be invisible, because a crawler never found it or was told to stay away. Reaching a page is only the start, so how a search engine finds and chooses pages is worth reading first.
Three things commonly block access. A robots file can disallow a section of the site, sometimes left over from when the site was being built. A page can carry an instruction telling search engines not to index it, for the same reason. Or a page can simply have no links pointing to it from anywhere, so nothing leads a crawler there.
Search Console will tell you which of your pages are indexed and which are not, and it usually gives the reason. That report is the first place to look when a page you care about is missing.
Does the same content sit at several addresses?
This is the most common technical SEO problem and the least obvious. A single page can be reachable with and without a trailing slash, with and without www, over http and https, and with tracking parameters attached. To a person these are one page. To a search engine they can look like four.
The effect is that whatever authority the page has gets divided. Fixing it means choosing one address as the real one, redirecting the others to it permanently, and declaring the canonical address on the page itself.
Online shops suffer worst, because filters and sort orders generate addresses endlessly. Consequently a shop with faceted navigation should treat this as the first technical SEO job rather than an afterthought.
How fast is it, on a real phone?
Speed is a ranking factor, but that undersells it. Speed is a conversion factor. People leave slow pages, and they leave before they have read anything.
Test on a mobile connection rather than on office broadband. The usual culprits are large uncompressed images, too much script, and fonts that block the page from painting. Images are almost always the cheapest thing to fix and the biggest single win.
Does it work properly on a phone?
Search engines evaluate the mobile version of your site. If your mobile pages hide content that the desktop pages show, the hidden content effectively does not exist.
Check the obvious things by hand. Is the text readable without zooming? Are the buttons far enough apart to tap? Does anything overflow sideways? These are technical SEO issues even though they look like design ones.
Is the site structure sensible?
A reader should be able to get from your home page to any important page in about three steps. So should a crawler. Pages buried ten clicks down get visited rarely and rank poorly, not because depth is penalised but because attention is finite.
A clear structure also means related pages sit near each other and link to each other, which is exactly the arrangement search engines use to work out what a section of your site is about.
Does the site explain itself in structured data?
Structured data is a small block of machine readable information describing what a page is: an article with an author and a date, a product with a price, a job opening at a company. It does not directly move rankings. It does change how your result can appear.
Add it where it genuinely describes the page and leave it off where it does not. Structured data that claims something the page does not show is worse than none, because it is a machine readable statement that turns out to be false.
How to find your real technical SEO problem
Technical SEO goes wrong when people fix everything at once and learn nothing. Work in order instead.
- Indexing first. Are your important pages in the index at all?
- Duplication second. Is one page pretending to be several?
- Speed third, measured on a phone rather than on a desktop.
- Mobile usability after that.
- Site structure and internal links next.
- Structured data last, because it changes appearance rather than access.
Each step is cheap to check and the order matters. Fixing structured data on a page nobody can reach achieves nothing at all.
Technical SEO you can do without a developer
Plenty of technical SEO needs no code. Compressing images, fixing headings and tidying internal links are content jobs. Redirects, canonical declarations and server speed usually are not.
The useful thing you can do without a developer is diagnose precisely. "The category pages are not indexed and Search Console says they are blocked by robots" is a request somebody can act on in an afternoon. "Our SEO is bad" is not.
Frequently asked questions
What is technical SEO?
It is the work of making sure search engines can reach your pages, load them quickly, and understand what they contain. It covers crawling and indexing, duplicate addresses, speed, mobile usability, site structure and structured data. None of it is visible on the page itself.
How do I know if I have a technical SEO problem?
The clearest signal is a page you care about that is not in the search index at all, or one that ranks far below pages that are obviously weaker. Search Console reports which pages are indexed and usually explains why the others are not, which is the fastest way to find out.
Do I need a developer for technical SEO?
For some of it. Redirects, canonical declarations and server performance normally need one. Compressing images, fixing heading structure and improving internal links do not. The most useful thing a non developer can do is diagnose the problem precisely enough to be actionable.
Why does the same page having several addresses matter?
Because a search engine may treat them as different pages and divide whatever authority the page has earned between them. Choosing one address, redirecting the others to it permanently, and declaring the canonical version on the page keeps that authority together.
How fast does a page need to be?
Fast enough that somebody on a phone on a normal connection does not give up. Measuring on office broadband flatters you badly. Large uncompressed images are usually the single biggest cause and also the cheapest to fix, so start there before touching anything else.
Is structured data worth adding?
It is worth adding where it genuinely describes the page, because it changes how your result can appear in search. It does not directly improve rankings. Adding structured data that claims something the page does not actually show is worse than adding none at all.
How often should technical SEO be checked?
A full review once or twice a year suits most sites, plus a check after any redesign, migration or platform change. Those three events cause most technical problems, because they change addresses and settings in ways nobody thinks to review afterwards.
Does technical SEO matter more than content?
Neither wins on its own. Technical work decides whether your content gets a chance, and content decides whether that chance is worth anything. A site with perfect technical foundations and nothing worth reading ranks for nothing.