What Is Technical SEO?
The layer beneath content and links: whether search engines can find your pages, read them, and understand them. It rarely wins rankings on its own - but it stops everything else from working when it is broken.
Technical SEO is the part that determines whether search engines can find your pages, read them, and understand them well enough to rank them.
It is worth being clear about what it does and does not do. Technical SEO rarely makes a page rank on its own. What it does is remove the obstacles preventing your content and links from having their effect. A site with excellent content and a technical problem will underperform a mediocre site without one.
Think of it as the plumbing. Nobody compliments your plumbing. They notice immediately when it fails.
The four stages a page has to pass
Everything in technical SEO maps to one of four stages. Understanding the sequence makes diagnosis much easier, because a failure at any stage makes the later ones irrelevant.
1. Crawling - can it be reached?
A search engine has to discover the URL and be permitted to request it. Things that break this:
robots.txtblocking the path- No internal links pointing at the page (an orphan)
- The page only reachable through a form or a search box
- Server errors or timeouts when the crawler visits
- Redirect chains that go several hops before resolving
Crawl budget matters mainly on large sites. If you have fifty thousand URLs and most are low-value variations, crawlers spend their time on the wrong pages.
2. Indexing - is it stored?
Being crawled does not mean being indexed. A page can be fetched and then deliberately excluded. Common causes:
- A
noindexmeta tag, often left over from a staging environment - A canonical tag pointing at a different URL
- The page judged duplicate or too thin to warrant storing
- Contradictory signals - a sitemap saying index, a meta tag saying do not
That last one is worth emphasising. Mixed signals are common and the outcome is unpredictable.
3. Rendering - can the content be seen?
Modern search engines execute JavaScript, but it is a second pass and it is not guaranteed to be complete.
If your content only exists after JavaScript runs, you are depending on that second pass. It usually works. Sometimes it does not, and when it fails you get an indexed page that appears almost empty.
The reliable approach is server-rendered HTML: the content is in the document when it arrives. This is one of the reasons we build sites this way by default - see website development.
The quick test: view the page source, or fetch it with JavaScript disabled. If your main content is not there, you have a rendering dependency.
4. Understanding - is it clear what the page is about?
Once indexed, the page has to be understood well enough to be matched to a query. This is where structure does its work: a single clear H1, a logical heading hierarchy, descriptive titles and descriptions, sensible URLs, and internal links using meaningful anchor text.
The pieces, briefly
XML sitemaps. A list of the URLs you want indexed. It helps discovery on large or poorly linked sites. It is a suggestion, not an instruction, and it should only contain canonical, indexable URLs - a sitemap full of redirects and 404s is a quality signal in itself.
robots.txt. Controls crawling, not indexing. A blocked page can still appear in results if other sites link to it. To keep something out of the index, use noindex and let the crawler reach the page to see it.
Canonical tags. Tell search engines which version of similar pages is the original. Essential where the same content is reachable at multiple URLs - parameters, filters, pagination, or the classic http/https and www/non-www duplication.
Redirects. A 301 is permanent and passes authority; a 302 is temporary and is treated differently. Use 301 for permanent moves. Avoid chains - redirect old URLs directly to the final destination, not through two intermediate hops.
Structured data. JSON-LD markup describing what a page contains: an Organization, an Article, a Service, a breadcrumb trail, a set of FAQs. It does not directly improve rankings, but it makes eligibility for rich results possible and helps disambiguate entities. Mark up only what is genuinely on the page - marking up content that is not visible is a guideline violation.
Core Web Vitals. LCP, INP and CLS. Modest as a ranking factor, significant for whether people stay. Covered in why website speed matters.
HTTPS. Required, and has been for years. Also check that http redirects to https, and that only one of www or non-www resolves.
hreflang. Only relevant if you serve multiple languages or regions. Easy to get wrong, and wrong is worse than absent.
What technical SEO cannot fix
It is worth being direct about the limits, because technical work is often sold as though it were the whole discipline.
Technical SEO will not make a page rank for a competitive term if the content does not deserve it. It will not create demand for something nobody searches for. It will not substitute for the authority that comes from other sites referencing you.
What it will do is ensure that when you produce something genuinely worth ranking, nothing structural stops it.
The common pattern we see: a business invests in content for a year with disappointing results, and the underlying cause is a rendering problem, a stray noindex, or an architecture so flat that no page reads as important. The content was fine. It never had a chance.
Where to start
If you are looking at your own site:
- Check indexing status in Google Search Console. Compare pages indexed against pages you expect to be indexed. Investigate the gap.
- View source on a key page. Confirm the content is in the HTML.
- Check for accidental
noindextags, especially after a recent launch. - Look at your sitemap. Does it contain only canonical, indexable URLs?
- Test Core Web Vitals on interior page templates, not just the homepage.
- Find orphan pages - anything in the sitemap with no internal links pointing at it.
Those six checks catch a large share of real technical problems. For the recurring ones, see common technical SEO problems.
If your content is not performing and you suspect something structural is in the way, ask us to take a look. A technical audit is where most of our SEO engagements start.