The WordPress Technical SEO Checklist: 30 Checks From 100+ Audits

Every check below comes from the same place: 100+ real WordPress audits, where the same problems appear again and again regardless of industry. You don't need to be technical to work through it. Each check tells you where to look, what good looks like, and what to do when you find trouble.

What is technical SEO for WordPress?

Technical SEO is the foundation layer of search visibility: whether Google can reach your pages (crawling), store them (indexing), understand them (structure and schema), and serve them fast (performance). Content and links decide how high you rank. Technical SEO decides whether you're in the race at all.

WordPress makes this layer both easier and sneakier. Easier, because the platform handles the basics sensibly out of the box. Sneakier, because themes, plugins, and WooCommerce quietly generate thousands of URLs, scripts, and markup decisions you never see, and any of them can hold rankings back.

How do you run a technical SEO check on WordPress?

Work through the five layers in order. Crawl and index problems come first because nothing else matters until Google can reach and store your pages.

Layer 1: Crawlability (checks 1-7)

1. Robots.txt sanity. Visit yoursite.com/robots.txt. It should allow your content, block junk, and name your sitemap. A single stray Disallow: / makes your whole site invisible.
2. Sitemap exists and is clean. Your XML sitemap should list only real, indexable pages: no 404s, no redirects, no noindexed URLs.
3. Crawl budget waste. In Search Console's Crawl Stats, look at what Googlebot actually fetches. Tag archives, date archives, feeds, and parameter URLs eating a large share means your money pages wait in line.
4. Redirect chains. Old redesigns stack redirects. Anything more than one hop wastes crawl budget and leaks link equity.
5. Orphan pages. Pages with zero internal links pointing at them look worthless to Google. Crawl your site and compare against your sitemap to find them.
6. Server response health. Slow or erratic responses make Googlebot back off. Check the average response time in Crawl Stats; sustained spikes are a hosting conversation.
7. Staging leftovers. Search site:yoursite.com for test pages, staging subdomains, and duplicate copies that should never have been crawlable.

Layer 2: Indexation (checks 8-14)

8. Coverage report review. Search Console's Pages report is the single most valuable screen in technical SEO. Every excluded URL has a stated reason; read them.
9. Crawled, currently not indexed. Google saw the page and declined it. Usually a quality or duplication signal, not a bug.
10. Discovered, currently not indexed. Google hasn't even crawled it yet: a crawl budget or priority problem.
11. Canonical conflicts. One page, one indexable version. Check www vs non-www, trailing slashes, and HTTP vs HTTPS all resolve to a single URL.
12. Accidental noindex. Themes and plugins sometimes ship noindex on templates nobody checks. Verify your money pages don't carry it.
13. Index bloat. Search site:yoursite.com and count. Far more results than real pages means tag archives, attachments, and thin pages are diluting your site in the index.
14. Duplicate content traps. WordPress-specific: tag pages competing with posts, attachment pages, paginated comment URLs, and WooCommerce filtered categories.

Layer 3: Architecture and internal links (checks 15-20)

15. Click depth. Your important pages should be reachable within three clicks of the homepage. Deeper means less crawl attention and less authority.
16. Internal link distribution. Money pages should receive the most internal links. On most sites I audit, the contact page beats every service page, which is backwards.
17. Anchor text quality. "Click here" tells Google nothing. Descriptive anchors pass meaning along with authority.
18. Breadcrumbs. Visible breadcrumbs with BreadcrumbList schema clarify structure for users, Google, and AI engines at once.
19. URL structure. Short, readable, keyword-bearing slugs without dates or parameter garbage.
20. Pagination handling. Paginated archives should be crawlable and self-canonicalized, not canonicalized to page one.

Layer 4: Schema and rendering (checks 21-25)

21. Schema validity. Run key templates through Google's Rich Results Test. Plugin-generated schema errors silently cancel your rich-result eligibility.
22. Schema completeness. Most WordPress sites mark everything as Article and stop. Services, prices, FAQs, and your author entity deserve markup too.
23. Connected graph. Best-practice schema references itself: the Service points to the Person, the FAQ to the page. Scattered snippets describe fragments.
24. JavaScript rendering. If your theme or builder renders content with JavaScript, verify Google sees the content, not a shell. Use Search Console's URL inspection and view the rendered HTML.
25. Mobile parity. Google indexes the mobile version. Content hidden or removed on mobile effectively doesn't exist.

Layer 5: Performance and security (checks 26-30)

26. Core Web Vitals on real-user data. Check the field data in PageSpeed Insights, not just the lab score. LCP under 2.5s, CLS under 0.1, INP under 200ms.
27. Image weight. The most common LCP killer on WordPress: full-size uploads and hero images without modern formats.
28. Render-blocking payload. Page builders and plugin stacks ship CSS and JavaScript to every page whether used or not.
29. HTTPS consistency. Every internal link, canonical, and asset on HTTPS; no mixed-content warnings.
30. Hack hygiene. Search site:yoursite.com for spam pages you didn't write. Injected content is more common than most owners believe and quietly poisons everything else on this list.

Which technical SEO issues hurt WordPress sites most?

Not all 30 checks are equal. Across my audits, these are the problems that most often explain a ranking gap, in rough order of frequency:

• Pages excluded as crawled or discovered but not indexed
• Crawl budget spent on tags, archives, feeds, and parameters
• Broken or missing schema markup
• Canonical and duplicate-content conflicts
• Redirect chains left over from past redesigns
• Core Web Vitals failing on mobile field data

If you're short on time, run those six first. They're the same six failure patterns explained on the homepage diagnosis section, and they account for most of the traffic gaps I get hired to close.

What tools do you need?

Notice what's missing: paid audit tools. They're convenient, but every check in this guide runs on free tooling. What paid tools can't buy is the judgment about which finding matters, which is the actual job.

How often should you audit?

Quarterly for most sites, plus immediately after any major change: a redesign, a theme or builder switch, a plugin overhaul, or a migration. Technical debt accumulates through updates you didn't watch, and a quarterly pass catches it while it's small.

Is a monthly technical audit necessary?

No, for most sites. Monthly full audits are agency-retainer theater. What deserves monthly attention is lighter: a glance at Search Console's coverage and Core Web Vitals reports, which takes ten minutes and catches regressions early. Save the full 30-point pass for quarters and post-change moments.

Technical SEO vs on-page SEO: what's the difference?

On-page SEO is what your pages say: titles, headings, content, and keywords. Technical SEO is whether search engines can reach, read, and trust those pages at all. They fail differently too: weak on-page SEO ranks you lower, while broken technical SEO removes you from consideration. That's why this checklist comes before any content work, and why the best content on the internet can't rescue a site Google can't crawl.

Can plugins fix technical SEO?

Partially, and it's worth being precise about the boundary. RankMath or Yoast handles sitemaps, meta tags, basic schema, and canonical tags well, when configured properly rather than left on defaults. That covers maybe a third of this checklist.

What no plugin can do: read your Search Console coverage report and diagnose why pages sit unindexed, find crawl budget waste, untangle redirect chains, judge which duplicate content matters, build a connected schema graph, or fix templates failing Core Web Vitals. Plugins are checklist items; they're not the auditor. If a plugin could fix technical SEO, this page and my job wouldn't exist.

When should you hire a consultant instead?

Three signals, honestly: traffic dropped and you can't find the cause here, the checks above surfaced problems you're not comfortable fixing on a live site, or your time is worth more than the afternoon this takes. In any of those cases, a professional technical SEO audit runs all 30 checks against your site's real data and hands you the findings ranked by impact, from $49.