Skip to content
Article

Technical SEO Checklist for WordPress in 2026

Technical SEO Checklist for WordPress in 2026

Most technical SEO checklists are alphabetical. That is useless when you have limited time, because the items are wildly unequal — one of them takes your entire site out of the index and another adjusts a meta tag nobody reads.

This list is ordered by blast radius.

Tier 1 — these break the site entirely

  1. Settings → Reading → “Discourage search engines” is unchecked. Check this first, every time. It is switched on during development and forgotten at launch more often than any other setting, and it silently blocks the entire site.
  2. robots.txt serves real rules and a working sitemap URL. Visit it. A placeholder domain in the sitemap line is a common leftover.
  3. The sitemap loads and contains your real URLs — including custom post types, which are frequently missing.
  4. Canonical tags point to the correct URL. A canonical pointing at the wrong page tells search engines to ignore the page you are on.
  5. One version of the domain resolves. Pick www or non-www, http or https, and 301 everything else to it.
WordPress technical SEO checklist arranged in five tiers ordered by how much damage each issue causes
Ordered by blast radius, not alphabetically. Work top-down and stop when time runs out.

Tier 2 — these lose you specific pages

  1. No noindex left on pages that should rank. Check templates for hardcoded robots meta tags — these are almost impossible to spot from the front end.
  2. Every page has a unique title and meta description.
  3. Slugs match their page content. A page titled one thing sitting at a URL about something else confuses both users and crawlers.
  4. 404s return a real 404 status, not a 200 with an error message.
  5. Redirect chains collapsed — A to B to C should be A to C.
  6. Pagination handled correctly on archives.
  7. Internal links use absolute, canonical URLs consistently.

Tier 3 — performance and crawl efficiency

  1. Core Web Vitals passing in Search Console field data, not just Lighthouse.
  2. Images in WebP or AVIF with correct srcset.
  3. Width and height on every image, to prevent layout shift.
  4. The hero image eager-loaded and preloaded; everything else lazy.
  5. Unused CSS and JavaScript dequeued per template.
  6. Server response under 600ms.
  7. Caching configured, and verified as actually serving cached responses.
  8. No render-blocking resources in the head that could be deferred.

Tier 4 — structured data and semantics

  1. Organization or Person schema with a stable @id.
  2. Article schema on posts, with accurate published and modified dates.
  3. BreadcrumbList schema matching real navigation.
  4. FAQPage schema where you have genuine FAQs, mirroring visible content.
  5. One H1 per page that describes the page.
  6. Heading hierarchy that does not skip levels.
  7. Descriptive alt text on meaningful images; empty alt on decorative ones.

Tier 5 — the finishing pass

  1. Open Graph and Twitter card tags with a correctly sized image.
  2. AI crawler access decided deliberately in robots.txt.
  3. Search Console and analytics verified, with the sitemap submitted.

How to run this

Work top to bottom and stop when you run out of time — you will have fixed the expensive things. Running it bottom-up is how sites end up with immaculate structured data and a noindex on the homepage.

Re-run tiers 1 and 2 after every launch, migration or major plugin change. Those are the moments when settings silently revert.

This is the same pass I run before touching any project, and it is what a full site audit covers. If you want the results for your site rather than a checklist, send me the URL.

Frequently asked questions

Do I still need an SEO plugin for WordPress in 2026?

Not necessarily. WordPress core generates sitemaps, and a well-built theme can emit titles, descriptions, canonicals and structured data directly. Plugins are useful when non-technical staff need to edit metadata per page. A custom implementation is leaner and gives you exact control.

What is the most common technical SEO mistake on WordPress?

Leaving "Discourage search engines from indexing this site" enabled after launch. It is checked during development and blocks everything. The second most common is a sitemap URL in robots.txt still pointing at a placeholder or old domain.

How often should I run a technical SEO audit?

Tiers 1 and 2 after every launch, migration or major plugin update — those are when settings revert. A full audit twice a year is enough for a stable site, or quarterly if you publish frequently or run many plugins.

Does structured data improve rankings directly?

No, not as a direct ranking factor. It improves how your result is displayed and how reliably answer engines can extract and cite your content. The traffic gain comes from better presentation and citation, not from a ranking boost.