Technical SEO checklist: the groundwork that comes before content

Everyone has heard that content is king. It's true. But a king doesn't rule from a palace with a leaking roof. Technical SEO is that palace — the foundation, the roof, the doors. If Google can't crawl your site, if pages load slowly, or if the search engine can't work out which version of a page is the real one, your best writing will never get the ranking it deserves.

The uncomfortable part: most of technical SEO is invisible. Done well, nobody notices. Done badly, most site owners don't notice either — they just say "we don't show up on Google." This technical SEO checklist is an attempt to make that invisible layer visible.

What is technical SEO, and how is it different from content SEO?

Content SEO is about what you say. Technical SEO is about whether anyone can hear it. Before Google ranks a page, it does three jobs: it finds the page (crawling), understands and stores it (indexing), and then compares it against everything else (ranking). Technical SEO exists to make the first two steps frictionless.

That's why order matters. A page that can't be crawled won't be indexed; a page that isn't indexed can't rank. When a company publishes two blog posts a week for six months and traffic never moves, the story is rarely about content quality. More often it's a forgotten line in robots.txt or a canonical tag pointing the wrong way.

How does Google actually see your site?

Googlebot visits like a browser, but without the patience. Every site gets a crawl budget, and if that budget is burned on broken links, infinite filter combinations, or near-duplicate pages, your actual content may never get its turn.

The fastest way to see your site through Google's eyes is Google Search Console. It's free, takes ten minutes to set up, and answers the core question directly: which pages are in the index, and which are excluded — and why. Your first hour of technical SEO belongs there, before you buy any tool or talk to any agency.

The technical SEO checklist: what to look at

The headings below are the skeleton of an audit. You don't have to finish them in a day, but every one of them should have an answer.

Crawlability: robots.txt and the sitemap

robots.txt is where you tell Google "don't go here." The problem is that a one-line mistake can shut down the whole site. A Disallow: / left over from a staging environment is a classic that happens far more often than anyone admits.

The XML sitemap does the opposite job: "these pages exist — look at them." If your sitemap doesn't update itself when you publish something new, in practice you don't have one.

Speed and Core Web Vitals

Google measures page experience through Core Web Vitals: how quickly the page becomes visible, how fast it responds to interaction, and whether the layout jumps around while loading. These metrics aren't the whole ranking story — but between two similar pages, the faster one has the edge, and a slow site loses visitors before the results page is even out of sight.

Speed is usually an architecture problem, not a settings problem. A site that rebuilds every page from a database on every visit is not in the same league as one serving pre-built static pages. You can prop up a plugin-heavy install with caching layers — it works, but it's ongoing maintenance. In a static architecture, speed is the default.

Mobile and HTTPS

Google indexes the mobile version of your site. A page that looks flawless on a desktop but has a broken menu on a phone is, as far as Google is concerned, exactly what the phone shows. HTTPS isn't even a debate anymore: a site without a certificate gets a "not secure" warning in the browser and starts the race a step behind. With free certificates widely available, there's no excuse left.

Duplicate content and canonicals

If the same page is reachable with and without www, with and without a trailing slash, with and without URL parameters, Google may treat those as separate pages — and your ranking signals get split between them. The canonical tag is how you say "this is the real address." E-commerce sites multiply this problem through filters and sort parameters; a modest catalog can generate tens of thousands of meaningless URLs.

Structured data

Schema.org markup tells Google explicitly what a page is: this is a product, that's an article, this is an FAQ. It's not a direct ranking boost, but it can earn you stars, prices, and dates in the search results — and that changes click-through rates. In an era where AI-powered search reads your content by machine, speaking machine language too is a sensible investment.

Broken links and redirects

Every deleted page orphans the links that pointed to it. A 404 loses both the visitor and the authority that page accumulated over years. The fix is simple but requires discipline: a 301 redirect from every removed page to its closest living equivalent.

Internal links are part of the checklist too. Pages that nothing links to are hard for Google to find; a service page unreachable from your navigation and related content stays invisible no matter how well it's written. As a site grows, tracking this by hand gets hopeless — a good CMS should warn you about deleted pages and broken links before they ship.

Who should handle technical SEO?

The honest answer: it depends on your architecture. On WordPress, technical SEO is recurring work — plugins update, themes change, and every change triggers another round of checks. That's not a criticism; for a small blog, a couple of well-chosen plugins and a few hours of maintenance a year is plenty, and WordPress is a perfectly reasonable choice.

The equation changes as the site becomes your business. In a statically generated, headless-CMS architecture, most of the list above — speed, clean URLs, automatic sitemaps, canonicals — is set up correctly once, during development, and stays that way. Technical SEO stops being a fire you keep putting out and becomes a foundation you pour once.

Where to start

Three things you can do today: set up Search Console and read the indexing report. Run your homepage and your two most important pages through PageSpeed Insights. Search Google for your own brand and look at which pages appear, with which titles. Those three checks surface most sites' biggest technical problem in half an hour.

The rest is discipline: the same questions asked every time a page ships, speed re-measured every time the design changes. Getting this groundwork in place before you invest in content means the same effort pays back twice.

If you'd rather focus on content and never think about this checklist, that's roughly why Vucod builds sites the way it does — speed, sitemaps, and structured data are part of the architecture from day one, not an audit finding later. Get in touch at vucod.com; every inquiry gets an answer within 48 hours.