---
title: "Technical SEO Checklist for WordPress: The Server Half"
url: https://hostmy.blog/technical-seo-checklist-wordpress/
date: 2026-10-31
modified: 2026-10-31
lang: en
author: "Aditya Sharma"
description: "The server half of technical SEO for a WordPress blog: HTTPS, status codes, robots.txt, sitemap, response time and versions, with a command for each."
categories:
  - "WordPress"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2668-1024x538.jpg
word_count: 1288
---

# Technical SEO Checklist for WordPress: The Server Half

The server half of technical SEO is everything that happens before WordPress writes a page. It covers whether the request reaches your site, what status comes back, how fast the first byte arrives, and whether the same page answers on more than one address. It is the half that plugins cannot fix, because it lives in the server and the domain settings.

This technical SEO checklist for WordPress covers that half for a blog. It does not cover the page half, such as titles, headings and schema, which your SEO plugin and your writing handle. Each item says what to check, how to check it with one command, and what a bad result means. Google sets three minimum technical requirements for a page to be eligible for Search, and the list below is built around them.

![Numbered outline of this post, Technical SEO Checklist for WordPress: The Server Half: 1 What Google requires at minimum; 2 HTTPS and one preferred address; 3 robots.txt and the sitemap; 4 Versions and security; 5 How often to run it; 6 A worked example: a blog that moved host.](https://hostmy.blog/wp-content/uploads/2026/10/hmb-diagram-2668.png)The route through this post.

## What Google requires at minimum

Google's [technical requirements](https://developers.google.com/search/docs/essentials/technical) are short. Googlebot must not be blocked, so the page has to be publicly accessible and not blocked by robots.txt. The page must work, which means the server returns an HTTP 200 success status, because error pages are not indexed. And the page must have indexable content, in a file type Google supports and not in breach of its spam policies. Meeting them does not guarantee indexing, but missing one rules a page out.

Those three map to the server half directly. The first is robots.txt and firewalls, the second is status codes, and the third is whether the text arrives in the HTML. Everything else in this checklist supports one of them.

## The checklist

| Check | What it protects | Command or place to look |
| ----- | ---------------- | ------------------------ |
| HTTPS works and is forced | A secure, single address for every page | curl -sI on the http address |
| One preferred address | No duplicate versions of the site | Test www and non-www |
| Status codes are right | Real pages return 200, missing ones return 404 | curl -sI on a page and a bad address |
| robots.txt is sane | Googlebot is not blocked | View the file |
| Sitemap is reachable | Pages are found | View the sitemap |
| Response time is steady | Crawling and visitors are not slowed | Time to first byte |
| PHP and database are supported | Security and plugin compatibility | Host settings |
| No accidental noindex | Pages can be indexed | Page source and headers |
| Redirects are single hops | No chains or loops | curl -sIL |

## HTTPS and one preferred address

A site should answer on one address. If http, https, www and non-www all load as separate pages, search engines can see several copies, and visitors can land on an insecure one. Check that each variant ends up at the same final address with a permanent redirect.

`for u in http://yourdomain.com https://yourdomain.com http://www.yourdomain.com https://www.yourdomain.com; do curl -s -o /dev/null -L -w "%{http_code} %{url_effective} $u\n" $u; done`

Every line should show the same final address and a 200. Where one differs, set up a redirect, and see [WordPress redirect plugin or server rule](/wordpress-redirect-plugin-or-server-rule/) for where. The same single-address idea applies after a move, as in [the site migration SEO checklist](/site-migration-seo-checklist/).

## Status codes

Google needs a 200 from a page it can index, and it treats other statuses as signals. Check one real page, one address that should not exist, and one redirect.

`curl -sI https://yourdomain.com/a-real-post/ | head -1
curl -sI https://yourdomain.com/no-such-page-12345/ | head -1`

You want a 200 on the first and a 404 on the second. A 200 on the second is a soft 404, covered in [WordPress 404 errors: causes and fixes by type](/wordpress-404-errors/).

## robots.txt and the sitemap

The robots.txt file at the root should not block pages you want crawled, and it should name your sitemap. [WordPress robots.txt: what to allow, block and test](/wordpress-robots-txt/) covers reading it, and [WordPress sitemap: where it is and how to fix it](/wordpress-sitemap/) covers the other file. Check both load, and that the sitemap lists only addresses that return 200.

## Response time

A slow or erratic server is a technical SEO problem as well as a visitor problem. This prints the time to first byte, which is the part of the delay that is the server's own. Run it a few times at different hours.

`curl -o /dev/null -s -w "%{time_starttransfer}\n" https://yourdomain.com/`

A steady figure is a good sign. A figure that swings wildly or climbs at busy hours points at the host, and [what a real WordPress uptime problem looks like from the logs](/wordpress-downtime/) shows how to read it. Google also says that server errors and rate limiting, such as a 429, make it crawl less. Whether any of this matters for a small blog depends on its size.

## Versions and security

WordPress asks for current versions of PHP and the database, and a host that runs old ones leaves you exposed and breaks newer plugins. [Choosing PHP and MySQL versions](/wordpress-php-version/) covers the choice, and [best hosting for bloggers](/best-hosting-for-bloggers/) lists what to ask a host. These are server settings, so they are the part you cannot fix with a plugin.

## Accidental noindex

A staging setting, a plugin option or a response header can tell search engines not to index a page, and it is easy to leave in place. The checks are in [the site migration SEO checklist](/site-migration-seo-checklist/), and they take a minute: look at the robots meta tag and the X-Robots-Tag header on a real post.

## How often to run it

Run the whole checklist after any move, any change of host, and any change to security or caching settings, and once a quarter otherwise. Most of it can be done in ten minutes, and a failure caught the day it appears is cheap. The same list belongs in [what to actually monitor on a WordPress site](/wordpress-monitoring/), so that a change to any of these shows up as an alert.

## Common server faults and what they mean

| Fault | What you see | What to check |
| ----- | ------------ | ------------- |
| Mixed content | The browser warns the page is not fully secure | Images or scripts still loading over http |
| An expired certificate | A full-page browser warning | The certificate renewal at the host |
| A redirect loop | The page never loads and the browser reports too many redirects | Two redirect rules fighting, such as http to https set in two places |
| Intermittent 5xx errors | Pages fail now and then | The log, and server load |
| A slow first byte at busy hours | Pages crawl at certain times of day | Host limits and caching |
| Blocked by a firewall | Visitors or crawlers get a 403 | Security plugin, host and CDN rules |

Each of these is a setting on the server or the domain, not a fault on the page, which is why they are hard to spot from the dashboard. A certificate warning is the loudest and the easiest to fix. A redirect loop and a firewall block are the quietest, because the site may work for you and fail for a crawler.

## A worked example: a blog that moved host

A blog moves to a new host, and everything looks right. Then the checks show that the site answers on both the www and non-www address with a 200, so each page exists twice. The sitemap still lists the old addresses. And response time is steady at midday but climbs at night. None of that is visible on the page, and each is fixable in an afternoon: add the redirect for the preferred address, regenerate the sitemap, and ask the host about the evening slowdown. The lesson is that a move changes the server half of technical SEO, so run this checklist the same day.

## Where Host My Blog fits

The server half is where a managed host or care plan earns its place, because it is the part a site owner cannot see from the dashboard. On the blogs we look after, status codes, response time and versions are checked as part of the month. If you would rather not be the one running the commands, [our care for bloggers](/for-bloggers/) covers it.

If you ran the first command on your own domain today, would all four addresses end up in the same place?