Your agency says the site is fine. Search Console shows organic clicks sliding for a third straight month, the homepage takes a beat too long to settle on your phone, and nobody can tell you which of those problems deserves your budget first. To audit WordPress SEO and performance properly, treat them as one workflow: record a baseline with exact versions, confirm updates and security, prove Google can crawl and index the right URLs, crawl for WordPress-specific bloat, check content and internal links, test speed with real-user field data before debugging in the lab, then rank every fix by business impact and retest.
The short version
You finish with a prioritized fix list tied to templates, owners, and retest dates, not a 400-row error export. Plan on about one focused day for a typical marketing site and closer to a week for a large content site or store. Difficulty is intermediate. You need admin access and comfort reading Search Console, but no code, unless you implement the fixes yourself. For the wider audit beyond SEO and speed, the complete 2026 guide to auditing a WordPress website covers the remaining categories.
Before you start
- Admin access to WordPress, plus hosting control panel access if possible
- Owner or full-user access to Google Search Console and Google Analytics
- A staging copy of the site, or your host's one-click staging tool
- A crawler (a desktop crawler or an online audit tool)
- A spreadsheet for the fix ledger described in Step 8
Step 1: Record a baseline before you change anything
Export 16 months of Search Console performance data and write down every version number the site runs. That means WordPress core, PHP, the active theme and its parent, every plugin, the page builder, and the hosting plan. The fastest route is Tools > Site Health > Info, which has a "Copy site info to clipboard" button.
Versions matter because advice rots quickly. W3Techs counts 62.8% of WordPress sites on version 7 and 30.1% still on version 6, so a fix written for one major version can be wrong for the other. Add a Google Analytics export of organic sessions and conversions by landing page, since traffic without conversions tells you little about business damage.
Tip: Save the baseline as a dated file you never edit. When someone later asks whether the redesign hurt rankings, this file settles the argument.
Step 2: Check updates and security status
Open Dashboard > Updates and list every pending core, theme, and plugin update. Security belongs this early because an SEO audit built on a vulnerable install is wasted effort. WordPress 7.0.2, released July 17, 2026, patched one critical and one high-severity issue, and sites still on 7.0 or 7.0.1 carry that exposure. The official WordPress releases feed lists what each point release fixed.
Next, look for abandoned components. The plugin directory holds more than 60,000 plugins, a count cited in the 2025 State of the Word, and plenty of them have gone years without an update. Check each plugin's "Last updated" date and its tested-up-to version. Confirm your PHP version is still supported.
Pitfall: WordPress 7.1 Beta 3 appeared on July 22, 2026. Beta builds belong on staging only, never production.
Step 3: Confirm Google can crawl and index the pages that matter
Load yoursite.com/robots.txt, then open Settings > Reading and confirm "Discourage search engines from indexing this site" is unchecked. That single checkbox, copied over from staging during a migration, has wiped out more WordPress traffic than most algorithm updates.
Then work through Search Console:
- Open the Pages report and read the reasons pages are not indexed.
- Run URL Inspection on one URL per key template: homepage, service page, blog post, product, category.
- Check that the XML sitemap is submitted and contains only indexable URLs.
- Confirm each important page carries a self-referencing canonical tag and no stray noindex directive.
Pass criterion: every revenue-driving page returns a 200 status, is indexable, canonicalizes to itself, and appears in the sitemap. Also search Google for your staging subdomain. An indexed staging site duplicates your entire catalog.
Step 4: Crawl the site and hunt WordPress URL bloat
Run a full crawl, then sort every URL by template type rather than by error type. WordPress generates low-value URLs on its own: attachment pages for every uploaded image (new installs disable them by default since WordPress 6.4, but older sites often still have them), tag archives with a single post, author archives on single-author blogs, and deep pagination. If you want a WordPress-specific scan running beside your crawler, Wpaudit's Free plan runs automated checks across core audit categories without backend access or a credit card.
Automation deserves its own pass now. The Abilities API arrived in WordPress 6.9, and WordPress 7.0 (May 20, 2026) added a centralized AI hub. Any integration allowed to publish can quietly create duplicate pages, thin content, or unwanted metadata, so filter the crawl by publish date and author to find machine-made URLs.
This is where the template multiplier pays off. One bad canonical on the product template is one fix for 3,000 URLs, not 3,000 fixes. Practitioners auditing 800-plus-page sites on r/TechSEO describe drowning in unprioritized issue lists, and grouping by template is the way out.
Step 5: Audit content, metadata, and internal links
Export titles, meta descriptions, H1s, and word counts from the crawl, then join them to Search Console clicks and impressions per URL. Sort the results into four piles: missing or duplicate titles, pages competing for the same query, content that is outdated or thin, and pages performing fine.
For internal links, compare the URLs in your sitemap against the URLs the crawler found by following links. Anything in the sitemap but never reached by a link is an orphan page. Users on r/SEO report that orphan pages are close to impossible to spot manually once a site passes a few hundred pages, which is why the sitemap-versus-crawl comparison beats reading menus. The WordPress SEO audit checklist lists the metadata checks in more detail.
Pitfall: do not delete low-traffic pages on sight. A page with few clicks may still earn backlinks or convert well, so redirect or merge it into a stronger page instead.
Step 6: Test performance with field data first
Pull Core Web Vitals field data from Search Console and PageSpeed Insights before you run a single Lighthouse test. Field data reflects what real Chrome users experienced over a rolling 28-day window. Lab data is a single simulated load, useful for debugging and misleading as a verdict. Google's Core Web Vitals documentation defines the thresholds below.
| Metric | Good threshold | Field data source | Typical WordPress cause when it fails |
|---|---|---|---|
| Largest Contentful Paint (LCP) | 2.5 seconds or less | Search Console, PageSpeed Insights | Slow hosting, uncached pages, oversized hero images |
| Interaction to Next Paint (INP) | Under 200 milliseconds | Search Console, PageSpeed Insights | Heavy builder JavaScript, chat and tracking scripts |
| Cumulative Layout Shift (CLS) | Below 0.1 | Search Console, PageSpeed Insights | Images without dimensions, late-loading fonts and ads |
INP replaced First Input Delay in 2024, so any audit still reporting FID is out of date. Keep the vitals in proportion: they are user-experience signals, and a page passing all three can still lose rankings to weak content or indexing problems. Chasing a Lighthouse 100 is a poor use of developer hours. Passing field data on your money templates is the target.
Step 7: Diagnose performance causes layer by layer
Work down the stack in order: hosting, caching, theme and builder, plugins, database, images, then scripts. A slow server response points to hosting or missing page caching, and no image compression plugin will fix it.
Page builders come next. Just under a third of WordPress sites run Elementor (W3Techs, September 2026), and builder output often means deep DOM trees, unused CSS, and layout shifts. Then check for plugin overlap: two SEO plugins or two caching plugins fighting each other is common after agency handovers. The free Query Monitor plugin shows which plugin fires the slow database queries. Revision buildup is fixable with the WP_POST_REVISIONS constant in wp-config.php.
Stores need extra attention. WooCommerce runs on about one in five WordPress sites, according to the same W3Techs data, and it brings cart fragment requests, checkout scripts loading sitewide, faceted navigation URLs, and product schema to validate. Test product, category, cart, and checkout templates separately. The WordPress performance audit walks through each layer.
Step 8: Prioritize fixes, test in staging, and retest
Turn every finding into one row with seven columns: business impact, effort, risk, affected templates or URLs, owner, recommended action, and retest date. Call it the fix ledger. It replaces the undifferentiated error list that makes developers tune out and leadership lose patience.
Sort by impact first, then effort. A sitewide noindex on product pages outranks 200 missing alt attributes, however long the alt-text list looks. Community members on r/TechSEO make the same point from the other direction: an audit's value comes from prioritization and context, not the number of findings.
Apply risky changes in staging first, especially core updates, theme changes, and new AI integrations. After deployment, wait at least 28 days before judging field data, because that is how long the rolling window takes to reflect the change.
Troubleshooting
Why does PageSpeed Insights show no field data?
The page or origin has not met the Chrome UX Report's minimum popularity threshold. Google's CrUX methodology confirms the threshold exists but does not disclose the visitor number. Check origin-level data instead, or rely on lab tests and your own real-user monitoring.
Why are pages stuck on "Crawled, currently not indexed"?
Usually Google judged them low value or duplicative. Look for thin tag archives, near-duplicate location pages, or automation-generated posts, then merge, improve, or noindex them.
Why does Lighthouse score well while field data fails?
Lighthouse simulates one load on one device profile. Real users bring slower phones, third-party scripts that fire after consent, and logged-in cart states. Trust the field data.
Why did traffic drop right after a migration?
Check the "Discourage search engines" setting, robots.txt, canonicals pointing at the old domain, and missing redirects, in that order.
Next steps
Scale the audit to the site. A 50-page marketing site can run the whole process with Search Console, PageSpeed Insights, and Lighthouse. Large content sites need a crawler that handles thousands of URLs and a firmer grip on taxonomy archives. Stores need the WooCommerce checks from Step 7 on every transactional template.
Paid suites earn their cost for backlinks, competitor research, rank tracking, and historical data, not WordPress configuration review. Ahrefs lists Lite at $129 a month, rising through $249 and $449 to $1,499 for Enterprise with an annual commitment. Semrush's plans start at $199 a month for Starter, with Pro+ at $299, Advanced at $549, and custom Enterprise pricing. If you need AI-search visibility, add it as an optional layer: check entity clarity, author and organization details, structured data, and whether your key pages get cited. Then schedule the next audit in your maintenance routine.
Frequently asked questions
How often should I audit WordPress SEO and performance?
Run a full audit quarterly and a lighter check monthly. Also audit before and after any redesign, migration, major core update, or new AI integration. Security point releases such as WordPress 7.0.2 justify an immediate update check outside the normal schedule, because delays leave known vulnerabilities open.
Is Google Search Console enough for a WordPress SEO audit?
It covers most foundational checks: indexing status, Core Web Vitals field data, sitemaps, and query performance. It cannot show backlinks from competitors, full-site crawl data such as orphan pages, or WordPress configuration problems like plugin overlap. Pair it with a crawler and PageSpeed Insights before paying for a large suite.
What Core Web Vitals scores should a WordPress site aim for?
Aim for LCP of 2.5 seconds or less, INP under 200 milliseconds, and CLS below 0.1, measured on real-user field data. Prioritize the templates that drive revenue and leads rather than chasing a perfect Lighthouse score on the homepage.
Can an SEO audit find duplicate or outdated WordPress pages?
Yes. A crawl joined to Search Console data exposes duplicate titles, near-duplicate content, thin archives, attachment pages, and posts with declining clicks. The audit identifies them, but a person still decides whether to update, merge, redirect, or noindex each page.
Why do WordPress sites need a different audit than other sites?
WordPress generates its own low-value URLs and depends on plugins, themes, and builders that affect speed and indexing. Attachment pages, tag archives, revision buildup, conflicting plugins, and staging sites rarely show up in generic website checklists, yet they cause many ranking and performance problems.
:::
Related Reading
- 7 Best WordPress Audit Tools for SEO, Security, and Performance in 2026
- Parameter vs WordPress Audit: Key Differences for Site Owners
- 11 SEO Audit Tools to Compare Before Choosing One
- Free SEO Audit Tools vs Paid Suites: Which Gives Better Results?
- White-Label WordPress Audit Reports: A Scalable Solution for Agencies
- Website Audit Buying Guide (2026): Costs, Scope, and Essential Features
- WordPress Audit vs Parameter: Which Website Analysis Approach Wins?
- Wpaudit vs Dedicated SEO Platforms: Which Delivers Better Site Insights?
- WordPress Audit Tool: SEO, Security & Performance
- Features – Ultimate WP Audit
Free A free-forever plan for trying WP Audit with basic WordPress auditing capabilities.
