WordPress
WordPress SEO Setup: Technical Checklist for Real Results
The technical SEO configuration that actually moves rankings on WordPress — beyond installing Yoast and calling it done — plus the plugin-stacking mistakes that quietly undo the basics.
Installing an SEO plugin on WordPress feels like finishing the job. It isn't — it's unlocking the controls. Yoast or Rank Math will happily let you ship duplicate titles, competing canonicals, and a sitemap full of noindexed pages if nobody configures them past the defaults. Most of the WordPress sites we inherit have one of these plugins installed and functioning technically correctly, while still leaving real ranking value on the table because the configuration was never finished.
Here's what "finished" actually looks like.
Titles and meta descriptions: templates, not one-offs
Set a title template at the plugin level (Yoast: SEO → Search Appearance; Rank Math: similar) rather than relying on every author to write a good title manually — %title% | %sitename% as a baseline, adjusted per content type (posts, pages, product categories if it's WooCommerce). This guarantees every new page gets a reasonable default even if nobody thinks about SEO when publishing.
Then audit existing content for the failure modes templates don't catch:
- Duplicate titles across pages — common on category/tag archives, and on product variants in WooCommerce. Search Console's Pages report under Indexing will show you exactly which URLs are competing.
- Titles that are truncated or generic in search results — under ~60 characters displays fully; longer gets cut with an ellipsis, which is fine occasionally but shouldn't be the default for pages you care about ranking.
- Meta descriptions under ~155 characters, written to earn the click, not stuffed with keywords — Google frequently rewrites descriptions it judges to be low-quality or irrelevant to the query anyway, so a well-written one is also insurance against an auto-generated snippet.
Use the plugin's search preview (both show one) before publishing anything that matters — it catches truncation and awkward phrasing faster than reading the raw fields.
Canonicals: set once, verify constantly
SEO plugins set self-referencing canonicals by default, which is correct for most pages. Where it goes wrong is usually not the plugin — it's a second system also setting canonicals: a caching plugin, a multilingual plugin, or a page builder with its own SEO panel, each unaware of the others. The result is two conflicting canonical tags in the same <head>, and search engines pick one somewhat unpredictably.
Check this directly: view source (not the CMS preview) on your five most important pages and confirm exactly one <link rel="canonical"> tag, pointing at the URL you actually want indexed — HTTPS, your chosen www/non-www convention, no tracking parameters.
Noindex utility pages deliberately, not by accident: internal search results, cart/checkout on WooCommerce, author archives on a single-author blog (they're just duplicating the homepage's content list), and any duplicate listing pages created by tag/category overlap. Most SEO plugins default several of these to noindex already — verify it rather than assume, since defaults change between plugin versions.
Submit the sitemap in Search Console (most plugins generate one at /sitemap_index.xml or similar) and check the Coverage report monthly, not just at launch — crawl errors accumulate quietly as content changes and old URLs go stale.
URL structure and internal linking
Use a clean, flat permalink structure — /blog/post-slug rather than date-based /2024/05/30/post-slug, which ties every URL to a publish date and makes evergreen content look stale by its own URL. Keep hierarchies shallow: two or three levels deep is plenty for almost any site; deeper structures dilute the authority any individual page can accumulate.
Internal linking matters more on WordPress specifically because the default theme and block editor don't do it for you — every contextual link from one post to another has to be added deliberately by whoever's writing. Link from high-traffic evergreen posts to newer content that needs authority; link from category or hub pages down to the specific articles underneath them. Audit for orphan pages periodically — a page with zero internal links pointing to it is much harder for both crawlers and users to find, no matter how good the content is.
Fix broken internal links and use permanent 301 redirects (not 302) for anything that's moved — Redirection or a similar plugin handles this without needing server-level config, and it's worth checking its log periodically for 404s that are worth mapping.
Performance and mobile: the technical SEO factor most sites underinvest in
Core Web Vitals are a ranking factor, and WordPress's plugin-heavy ecosystem is the single most common reason a WordPress site underperforms here relative to a hand-built site with the same content.
- LCP — usually the hero image or a webfont. Use a caching layer (page cache at minimum, object cache if the host supports Redis/Memcached), serve images through a CDN with automatic WebP/AVIF, and make sure the LCP image isn't being lazy-loaded (it shouldn't be — only below-the-fold images should lazy-load).
- INP — driven by JavaScript execution, and WordPress sites accumulate this fast: every plugin that adds a script tag adds to main-thread work. Audit with Lighthouse's "Total Blocking Time" as a proxy and look specifically at third-party scripts (chat widgets, marketing pixels, plugin bloat) as the usual culprits.
- CLS — almost always missing width/height attributes on images or ads loading late and shifting content. WordPress's native image handling sets dimensions correctly if you're not overriding it with custom CSS or a page builder that strips them.
Run this on a representative page, not just the homepage — a blog post template and a product page (if applicable) often have very different Core Web Vitals profiles because they load different sets of plugins and assets.
The audit, condensed
| Area | Check | Common failure |
|---|---|---|
| Titles | Unique per page, template-driven | Duplicate titles on archives/variants |
| Canonicals | Exactly one tag, correct URL | Two plugins both setting canonicals |
| Noindex | Utility pages only | Whole categories accidentally noindexed |
| Sitemap | Submitted, monitored monthly | Set once at launch, never checked again |
| URLs | Flat, permanent redirects for moves | Date-based URLs, 302s instead of 301s |
| Internal links | Deliberate, no orphan pages | Default theme doesn't add these for you |
| Core Web Vitals | Tested per template, not just homepage | Plugin bloat driving up INP |
Where technical SEO stops and content starts
None of this replaces good content, and it's worth saying plainly: a technically perfect WordPress install with thin, generic posts will lose to a technically average site with genuinely useful content, most of the time. What technical SEO does is remove the ceiling — it makes sure good content actually gets crawled, indexed, and displayed the way you intended, instead of losing ranking potential to a duplicate canonical tag or a bloated homepage nobody audited.
We run this checklist as part of every WordPress project we deliver, whether it's a new build or a performance and SEO pass on an existing site. If your WordPress site has the plugin installed but you're not confident it's actually configured, get in touch — an audit usually surfaces two or three fixable issues in the first hour.