Skip to content

Test your website now

Free, no card. We read only public pages.

Run free audit →

Technical SEO

What is technical SEO, and what does it cover?

Technical SEO is the part of SEO that makes a site crawlable, indexable and fast. What it covers, how to check it, and where it stops and content takes over.

Technical SEO is the work that lets search engines crawl, render and index your pages without obstacles: correct status codes, robots rules, canonicals, sitemaps, HTTPS, speed, mobile layout and content present in the HTML. It does not make pages rank by itself, but problems here can stop good content from ranking at all.

Published · Last updated

By Michal Měřínský. Audit methodology.

What technical SEO is

If content is what a page says, technical SEO is whether a search engine can get to it, read it and file it correctly. It is the most measurable part of SEO: most of its questions have a clear yes or no answer.

What it covers

  • Crawlability: robots.txt rules, internal links, no orphan pages, no broken links.
  • Indexability: no accidental noindex, correct canonicals, status 200 for real pages and honest 404s for missing ones.
  • Rendering: content and links present in the served HTML or reliably rendered, not hidden behind interactions.
  • Site structure: readable URLs, sensible hierarchy, breadcrumbs, a sitemap.
  • Security: HTTPS everywhere, with a single redirect from HTTP.
  • Performance: Core Web Vitals and server response time.
  • Mobile: a responsive layout with a correct viewport.
  • Structured data and metadata: titles, descriptions, Open Graph and schema markup.
  • International: hreflang and language declarations, for multilingual sites.

The problems that cost the most

  • A site or section blocked by robots.txt or noindex after a launch.
  • A single-page app whose content and links only exist after JavaScript runs, leaving crawlers an empty shell.
  • Canonicals pointing at the wrong host, such as a staging domain.
  • Large numbers of duplicate URLs from parameters, which dilute signals and waste crawling.
  • Redirect chains and loops after a migration.
  • Slow server responses that limit how much of a large site gets crawled.

How to check it

  • Run a crawl of the site and read the errors by severity.
  • Compare what Search Console's Page indexing report says with what you expected.
  • Inspect your most important URLs in Search Console's URL Inspection tool, including the rendered HTML.
  • Fetch key pages without JavaScript to see what the server returns:
curl -s https://example.com/ | grep -ciE "<h1|<title|rel=\"canonical\""

Where technical SEO stops

Technical SEO removes obstacles. It does not create demand, write better answers or earn links. A technically clean site with thin content still struggles, and a few technical fixes on a site with good content can unlock rankings that were already deserved.

What a scan can and cannot tell you

WebAuditOS checks eligible crawled HTML and samples pages for browser measurements: robots rules, noindex, canonicals, sitemaps, status codes, redirects, served versus rendered content, structured data, metadata, speed and mobile layout, with each finding tied to the evidence.

It cannot see Google's index or rankings, content quality, or your backlinks. And its crawl only reaches pages linked from the start URL or listed in the sitemap.

Read technical findings by severity, not by count. One blocked section outweighs a hundred long titles.

Short answers

Is technical SEO enough to rank? No. It makes ranking possible. Content and reputation decide it.

How often should I check it? After every significant release, and monthly for active sites.

Do JavaScript frameworks hurt SEO? Not inherently. Server rendering or pre-rendering important pages avoids most problems.

What should I fix first? Anything that blocks crawling or indexing, then errors, then speed.

In the product

The checks this maps to

Every check named here runs on every scan, on every plan - what a plan changes is how many pages are crawled, how long the history is kept and what you can do with the result. These are the ids the findings carry, so you can match a line in a report to the explanation above.