What is technical SEO?

Technical SEO, explained

SEO is often split into three parts. On-page SEO is what's on each page: content, titles, headings. Off-page SEO is what others do: links and mentions. Technical SEO is the plumbing underneath, the part that decides whether search engines can get to your content at all and whether they see the version you intended.

The core checklist is short. Pages return the right status codes. One canonical URL per page, with redirects for variants like http, www and trailing slashes. An XML sitemap listing only indexable URLs with honest lastmod dates. A robots.txt that blocks crawl traps but not content, and a deliberate choice about AI crawlers. Important content and links in the server-rendered HTML. Structured data that matches the page. A mobile-friendly layout, HTTPS, and pages fast enough to pass Core Web Vitals for most users.

Technical SEO has a ceiling. Getting it right doesn't make pages rank; it removes the reasons they can't. A perfectly crawlable site with thin content still won't rank. But a great page blocked by a stray noindex or buried in a JavaScript app nobody can render won't rank either, so the basics come first.

On a modern framework, most of it can be built once as shared helpers: a metadata function that sets canonicals and robots rules, generated sitemaps, JSON-LD components and a page registry. That's how we set up the technical base on our own product before scaling content.

Why it matters for founders

Technical problems are usually invisible in a browser and silent in analytics. Fixing them early means every page you publish later has a fair chance of being indexed.

Example

Before writing any content, you add a metadata helper that sets canonicals on every page, generate a sitemap index split by page type, add Organization and Breadcrumb JSON-LD, and confirm key pages are static.

Common mistakes

• Chasing speed scores while pages are noindexed or not canonical.
• Expecting technical fixes alone to create rankings.
• One-off fixes per page instead of shared helpers.
• Never rechecking after deploys, migrations or CDN changes.