WordPress SEO Audit: the 2026 Checklist (with the GEO Layer)

A WordPress site rarely fails because of WordPress itself. It fails because of what gets stacked on top: three plugins each injecting their own canonical tag, hundreds of indexed author and tag archives, a "Discourage search engines" box forgotten since launch. A WordPress SEO audit exists to find these defects, in the order in which they cost the most.

This guide gives you a 5-block method, concrete tests you can run yourself (most in under ten minutes), and the angle classic checklists skip: checking that your site stays readable for AI engines (ChatGPT, Perplexity, AI Overviews).

What is a WordPress SEO audit, exactly?

A WordPress SEO audit is a methodical review of what stops Google (and AI engines) from finding, understanding and citing your pages. It covers four layers: indexing, technical setup, on-page content and performance. On WordPress it has one particularity: most defects come from configuration (settings, theme, plugins), not from the content.

Plan one full review per quarter, plus a light monthly check in Google Search Console (coverage, excluded pages, errors). After a migration or a theme change, audit right away.

Block 1: check that Google can get in (indexing)

Do this block first, because a defect here makes everything else pointless.

1. The visibility setting. In Settings > Reading, the "Discourage search engines from indexing this site" box must be unchecked. It is often ticked during development, then forgotten.
2. The robots.txt file. Open yoursite.com/robots.txt. WordPress generates a virtual one: it normally blocks /wp-admin/ while allowing admin-ajax.php. Make sure no Disallow: / line is lingering and that no cache or security plugin added broad rules. For AI crawlers, read the 2026 robots.txt guide.
3. The sitemap. Since WordPress 5.5, a native sitemap lives at /wp-sitemap.xml. Yoast, Rank Math, AIOSEO and SEOPress replace it with their own. Keep one active sitemap and submit it in Search Console. Details in the XML sitemap guide.
4. URL versions. http://, https://, with and without www should all end in a 301 redirect to a single version. Test all four by hand.
5. Permalink structure. In Settings > Permalinks, avoid the default ?p=123 format. A /%postname%/ format is readable and stable. If you change it on a live site, plan the 301 redirects.

Block 2: hunt parasite indexing (WordPress defect no. 1)

WordPress creates URLs you never wrote: author, tag and date archives, attachment pages, internal search results, ?replytocom= parameters. They dilute your crawl budget and create near-duplicate content.

Worked example (illustrative). A blog shows 240 indexed URLs in Search Console. You count 90 pages and posts actually written. The other 150 are tag archives (80), date archives (40), attachment pages (20) and paginated pages (10). Result: 62% of indexed URLs add nothing. The fix takes half an hour: set tag and date archives to noindex in your SEO plugin, and redirect attachment pages to their parent post.

How to run this test on your site:

• In Search Console, open the "Pages" report and read the list of indexed pages. Compare it with the number of pieces you really published.
• Type site:yoursite.com inurl:tag and site:yoursite.com inurl:author in Google to see what is indexed.
• Check the canonical tag of a post: one tag, pointing to itself. Two canonical tags (theme + plugin) is a frequent case.

The details of noindex directives are in the meta robots and X-Robots-Tag guide.

Block 3: performance and Core Web Vitals

On WordPress, slowness almost always comes from the same causes: heavy theme, page builder, too many plugins loading their scripts on every page, unoptimized images, saturated shared hosting.

Measure with PageSpeed Insights on three page types (home, post, category page), looking at field data when it exists. The three metrics to follow are LCP (main content loading), CLS (visual stability) and INP, which replaced FID in March 2024.

Levers to test, in order:

• Hosting and page cache: a properly configured cache plugin, or the host's own cache.
• Images: WebP format, declared dimensions, lazy loading below the fold. The image SEO and alt text guide covers the method.
• Scripts: disable plugins that load their CSS and JS everywhere when they only matter on one page.
• Fonts and third-party widgets: every external script costs loading time.

Test on mobile first: Google indexes from the mobile version.

Block 4: on-page, structured data and internal links

Review the items SEO plugins display but nobody really checks.

• Title and meta description: unique, relevant, without the site name repeated. Default templates often produce identical generic titles across dozens of pages.
• Heading hierarchy: one H1 per page. Some themes put the site title in an H1 on every page, a classic defect.
• Orphan pages: a page with no incoming internal link is hard to discover. A crawl with Screaming Frog (free up to 500 URLs) or an automated audit finds them.
• Broken links: fix or redirect internal 404s, rather than leaving a plugin running continuously on your server.
• Structured data: Yoast, Rank Math and AIOSEO generate JSON-LD (Organization, WebSite, BreadcrumbList, Article). Validate a few pages with Google's Rich Results Test, and read what schema really changes for AI citations before spending hours on it.

Block 5: the GEO angle, can AI read your site?

This is the block 2024-era WordPress checklists lack. AI answer engines only cite pages they can fetch and extract cleanly. Four checks:

1. AI bots are not blocked by accident. Some security plugins or firewall rules block GPTBot, ClaudeBot or PerplexityBot without telling you. Look at your robots.txt and your CDN or firewall settings.
2. Content is in the initial HTML. If your theme or page builder loads the main text with JavaScript afterwards, a bot that does not run JS will see an empty page.
3. Passages are self-contained. A short, precise answer under each H2 (definition, figure, step) is easier to extract than a long narrative paragraph.
4. Author and date are visible. Author name, update date and sources provide trust signals. Many themes hide or remove the update date.

Priority order: what to fix first

Tools to audit without blowing your budget

Search Console and PageSpeed Insights are free and enough for blocks 1 to 3. Screaming Frog covers crawling a small site. For an overall score that also covers the GEO layer, run a free /100 audit, see a sample report, or get the full PDF report if you want the detailed list of fixes. For a general method independent of WordPress, see the complete SEO audit checklist.

Key takeaways

• Start with indexing: one forgotten setting can cancel months of work.
• On WordPress, defect no. 1 is parasite indexing (tags, archives, attachments), not content.
• Keep one sitemap and one canonical tag per page.
• Measure Core Web Vitals on mobile, per page type.
• Check that AI bots reach complete HTML, otherwise no citation is possible.

Ready to see where you stand? Get your /100 score in a few minutes.