Home/Resources/WordPress SEO Audit
Technical SEO · WordPress

WordPress Technical SEO Audit Checklist

A practical audit framework for crawlability, schema, Core Web Vitals, and on-page hygiene on WordPress sites — demonstrated with a real, live audit of a local business site, real Lighthouse scores, and real issues found.

By Abdullah Ihsan·Hands-On Audit, Not Theory

1. Why WordPress Technical SEO Needs Its Own Checklist

WordPress powers a large share of the web, but the same flexibility that makes it popular — page builders, stacked plugins, themes layered on top of themes — is exactly what creates the most common technical SEO failures: render-blocking CSS bloat, duplicate libraries loaded by competing plugins, missing structured data for local/service businesses, and leftover staging pages that quietly stay indexable.

Generic SEO checklists don't catch these because they're platform-agnostic. A WordPress audit has to specifically look at the plugin stack, the page builder's output, and what the theme/plugins are injecting into every single page load.

2. The Audit Checklist

Organized into five categories. Each item below was actually used — and found failing or passing — in the live audit in Section 3.

Crawlability & Indexation

  • robots.txt isn't blocking CSS/JS, wp-admin exceptions are correct, and the sitemap is declared
  • No orphaned staging/test pages (e.g. a leftover /home-test/ clone) left indexable in the live sitemap
  • XML sitemap (Yoast/RankMath) is current, split sensibly, and submitted in Search Console
  • Canonical tags are self-referencing and consistent on every template
  • No soft-404s — deleted/missing pages return a real 404, not a 200
  • HTTP→HTTPS and www→non-www (or vice versa) redirects are single-hop, not chained
  • Category/tag archives, author pages, and attachment pages aren't creating thin, indexable duplicates

Structured Data & Schema

  • LocalBusiness or Service schema present for local/service businesses (address, areaServed, telephone, openingHours)
  • Organization + WebSite graph present (Yoast/RankMath default) with logo and sameAs social profiles filled in
  • Service-specific pages use Service schema, not just generic WebPage
  • FAQPage schema only on pages with real visible Q&A content
  • Schema validates with zero errors in Google's Rich Results Test

Performance & Core Web Vitals

  • LCP element identified and optimized (usually the hero image/text) — target under 2.5s
  • CSS isn't split into dozens of per-post/per-widget files (classic Elementor/Divi symptom) — combine & minify
  • No duplicate library versions loaded together (e.g. two Font Awesome versions, two icon-font versions)
  • Unused page-builder animation libraries (particles, parallax, carousels) aren't loaded site-wide if used on one page
  • Images are compressed and served as WebP/AVIF with explicit width/height to avoid layout shift
  • Default WordPress scripts that aren't needed (emoji script, embed script) are dequeued
  • A caching layer + CDN is active, not just a page-builder's built-in minifier

On-Page & Content Hygiene

  • Every image has descriptive alt text — check sitewide, not just the homepage
  • One H1 per page, headings in sequential order (no skipping H2→H4)
  • Titles and meta descriptions are unique per page (test with a sitemap crawl, not spot checks)
  • Internal link anchor text matches the destination page's actual topic
  • An HTML sitemap or clear footer navigation exists, not just the XML one

Plugin & Security Hygiene

  • WordPress core/generator version isn't exposed in the page source
  • Plugin count is justified — each plugin earns its weight in page-speed cost
  • No abandoned/unused plugins left active (common after page-builder migrations)
  • Mobile tap targets (sticky CTA bars, menus) don't overlap or obscure other interactive elements

3. Live Case Study: Auditing a Real WordPress Site

To make this checklist concrete, I ran it against a real, live local-business WordPress site (iPhone repair business, Elementor-built, not affiliated with me) — crawling all indexed pages, inspecting the rendered DOM, checking structured data, and running an actual Lighthouse mobile test. No tool copy, no theoretical examples — these are the real numbers.

Stack identified:WordPress + Elementor page builder + Hello Elementor theme + Yoast SEO, with Royal Elementor Addons, Essential Addons for Elementor, and a header/footer builder plugin stacked on top.
63
Performance
76
Accessibility
96
Best Practices
100
SEO (basic)

Google Lighthouse, mobile, emulated Moto G Power on Slow 4G — captured October 2026.

MetricMeasuredVerdict
Largest Contentful Paint (LCP)9.7sFails — target is under 2.5s
First Contentful Paint (FCP)3.2sSlow
Total Blocking Time (TBT)130msBorderline
Cumulative Layout Shift (CLS)0.03Good
Speed Index5.6sSlow
Render-blocking requests~4,120ms est. savingsCaused by ~30 unmerged Elementor CSS files
Unused JavaScript405 KiBDuplicate libraries loaded (3 Font Awesome versions)
Unused CSS83 KiBPer-post Elementor stylesheets not purged
Image delivery424 KiB potential savingsNo WebP/compression

What failed

A leftover test page was live, indexable, and duplicating the homepage

/home-test/ appeared in the XML sitemap with index,follow, no meta description, and two H1 tags — a near-duplicate of the real homepage that was never cleaned up after a design iteration.

100% of images were missing alt text, sitewide

Crawled all 23 indexed URLs programmatically — every single page had zero alt attributes on every image (roughly 300+ images total). Not a one-page oversight; a sitewide default.

No LocalBusiness or Service schema anywhere

Only generic Organization/WebPage/WebSite schema was present. For a local service business, this means no structured address/areaServed/telephone signals, and service pages (screen repair, battery replacement, etc.) carry no Service markup at all — a missed opportunity for rich results on exactly the pages meant to convert.

WordPress core version exposed in page source

A generator meta tag revealed the exact WordPress version, a minor but unnecessary information-disclosure issue.

Severe CSS/JS bloat from an unoptimized Elementor stack

The homepage loaded 200+ requests, including ten separate per-post Elementor stylesheets, three different Font Awesome versions loaded simultaneously, and two versions of the same icon font — none combined or purged.

Mobile tap targets too close together

A sticky bottom Call/Instant-Repair bar overlapped nearby content and sat very close to an adjacent button on mobile, flagged directly by Lighthouse's touch-target audit.

What was done right

  • Clean robots.txt (Yoast-generated), correctly referencing the sitemap, nothing important blocked
  • HTTP→HTTPS and www→non-www redirects both resolve correctly in a single hop
  • Proper 404 handling — real 404 status, not a soft-404
  • Unique titles, meta descriptions, and a single H1 on every real page (only the test page broke this)
  • Valid FAQPage schema present on the FAQ page
  • Zero cumulative layout shift (CLS 0.03) — no janky content jumps

The pattern here is typical of WordPress sites built fast with page builders: on-page SEO basics (titles, metas, single H1, clean robots.txt) are handled well by default via Yoast/RankMath, but performance and structured data get neglected because they require manual, plugin-stack-specific cleanup that no SEO plugin does automatically.

4. Fix Priority Order

When auditing any WordPress site, fix in this order — highest ranking/UX impact per hour of work first:

  1. Deindex or delete leftover test/staging pages— immediate duplicate-content risk removed in minutes.
  2. Fix Largest Contentful Paint— usually the single highest-leverage fix: combine/minify CSS, remove duplicate libraries, compress and lazy-load below-the-fold images.
  3. Add alt text sitewide— low effort, scriptable in bulk via the media library, fixes accessibility and image search together.
  4. Add LocalBusiness/Service schema— directly supports local pack and service-page rich result eligibility.
  5. Audit the plugin stack— remove duplicate icon/animation libraries and anything left active from a past page-builder migration.