Technical SEO is the part of search engine optimization that has almost nothing to do with keywords. It's about whether a search engine can reach your pages, understand them, and trust them enough to show them — independent of how well the words on the page are written.

What is technical SEO?

Technical SEO covers everything that affects a search engine's ability to access and interpret a site: URL structure, HTTP status codes, robots directives, sitemaps, canonical tags, structured data, page speed, and security. None of it is about persuasion — it's about removing friction between your content and the crawler trying to read it.

Common mistake Treating technical SEO as a one-time setup task. Every new page, redirect, or JavaScript framework change can quietly break something that was working before.

Crawling vs. indexing

These two words get used interchangeably, but they describe different stages:

  • Crawling is the process of a search engine bot requesting and downloading a page.
  • Indexing is the decision to store that page's content and make it eligible to appear in search results.

A page can be crawled but not indexed — for example, if it carries a noindex robots meta tag, like the placeholder pagination page on this site. A page can also be blocked from crawling entirely via robots.txt, in which case a search engine never even gets far enough to read a noindex tag on it.

A minimal robots.txt

User-agent: *
Allow: /

Sitemap: https://seopracticelab.example/sitemap.xml

Core elements every page needs

A unique title and meta description

Every page on this site ships a unique <title> and <meta name="description">, written for that specific page rather than copied from a template.

A self-referencing canonical tag

<link rel="canonical" href="https://seopracticelab.example/blog/technical-seo-basics/">

Canonical tags tell a search engine which URL is the "real" one when the same or similar content could technically be reached through more than one address.

A correct HTTP status code

This page should return 200 OK. Broken internal links that quietly return a soft-404, or pages that should redirect but return 200 instead, are both common and both confuse crawlers.

WP

In WordPress, the title, meta description and canonical URL for this exact article would be set from an SEO plugin's meta box (Rank Math, for example) rather than written directly into the HTML head.

How to test it yourself

You don't need special tools to check most of this — a browser is enough:

  • View Source to confirm the title, meta description and canonical are present and correct.
  • DevTools → Network to check the HTTP status code and response headers.
  • Lighthouse (built into Chrome DevTools) for an automated Performance/SEO/Accessibility pass.

The full testing workflow for this project, including Search Console and SecurityHeaders.com, is documented on the SEO Tools page.

HTML vs. WordPress, at a glance

The short version: hand-coded HTML gives you direct control over exactly what gets sent to the browser, while WordPress gives you speed of production at the cost of an extra abstraction layer (the theme and plugins) between you and that same HTML. Both can be equally correct technically — the WordPress SEO section of this project walks through the equivalent settings for each concept covered here.

Next steps

This article intentionally stays at introduction level. Robots.txt strategy, canonical edge cases, structured data, and Core Web Vitals each get their own dedicated article as this project continues — see the Recent Posts list in the sidebar for what's next.