WordPress is the platform I work with most, and it is genuinely capable as an SEO platform when it is configured correctly. The problem is most WordPress sites are not configured correctly. The default settings are not optimized for search, the plugin ecosystem creates conflicts that are invisible until they are diagnosed, and the flexibility of the platform means there are a hundred ways to accidentally undermine your SEO without ever realizing it. Getting a working, practical understanding of WordPress-specific SEO is one of the highest-value skills any site owner or marketing manager can develop.

The SEO Plugin Decision

Yoast SEO, Rank Math, and All in One SEO are the three dominant plugins, and any of them can do the job when properly configured. The mistake I see most often is running more than one of them simultaneously — this creates duplicate meta tags in the page head, duplicate XML sitemaps that conflict, and schema markup conflicts where both plugins inject different structured data for the same page. Pick one plugin, configure it carefully, and verify the others are fully deactivated, not just inactive.

Inside my SEO training, I walk through Rank Math configuration in detail because it currently offers the most flexible and granular schema markup builder of the three — which matters given that schema is my specialty. Yoast is more widely documented and supported, and either works well. The choice matters less than the configuration and the commitment to one over the others.

Permalink Structure: Get This Right Early

WordPress defaults to numeric URL structures (?p=123) on fresh installations. These are terrible for SEO and for user experience. Switch to a descriptive permalink structure immediately after installation — ‘Post Name’ (/your-post-title/) is the standard recommendation for most content sites and works well for the majority of use cases. For large publishing sites with category-organized archives, adding a category prefix (/category-name/post-title/) can help organize the URL structure, though it adds a URL segment that becomes permanent.

The critical rule: change your permalink structure once, early, and never change it on an established site without a comprehensive redirect plan in place. Every URL on your site changes when you change the permalink structure. Every inbound link pointing to an old URL breaks. Every search-engine indexed URL returns a 404. If you must change permalink structure on an existing site, implement 301 redirects for every changed URL before the switch goes live and verify them systematically.

XML Sitemaps: What Should and Should Not Be in Them

Your SEO plugin generates an XML sitemap automatically. Verify it is enabled and submit it to Google Search Console. Then audit what the sitemap actually contains. By default, most plugins include post tag archive pages, author archive pages, and date-based archive pages in the sitemap — pages that typically have almost no unique content and no real ranking value. Exclude these from your sitemap and set them to noindex in your plugin settings.

A clean WordPress sitemap contains only pages you actively want indexed: your core pages, your category pages, your published posts, your products or services if applicable. Thin archive pages included in the sitemap dilute the quality signal of everything else you have submitted. Google uses sitemap coverage and indexation rates as quality signals — a sitemap where 80% of submitted URLs get indexed communicates something different than one where 30% are indexed.

Schema Markup in WordPress

WordPress and the major SEO plugins provide basic default schema output — Article, BreadcrumbList, WebSite, and Organization schema appear automatically on most well-configured sites. The gap is in the full range of applicable schema types that require deliberate configuration. A local service business needs LocalBusiness schema with correct service area and opening hours. A law firm needs LegalService schema with practice areas. A recipe site needs Recipe schema with nutrition data. A healthcare practice needs MedicalOrganization schema with credentials.

This is the area I spend the most time on in my SEO University cohort, because it is where WordPress sites consistently leave the most measurable opportunity unrealized. Rank Math has the strongest built-in schema builder. For schemas that no plugin covers well out of the box, adding JSON-LD blocks directly to page templates gives complete control over the output. The Salterra team implements custom schema on WordPress sites for clients who want accurate, comprehensive structured data that goes beyond plugin defaults.

Plugin Conflicts and Their SEO Impact

Every plugin you install has the potential to conflict with other plugins or with your theme’s own code. From an SEO perspective, the most damaging conflicts involve plugins that modify page headers (overwriting or duplicating canonical tags or meta robots directives), plugins that manipulate URL rewrites in ways that create redirect chains or break existing links, and caching plugins that serve stale pages with incorrect directives after configuration changes.

The diagnostic habit that prevents most plugin conflict problems: check your key pages in Google Search Console’s URL Inspection tool after installing any new plugin. Verify that the rendered HTML still shows the correct canonical URL, the correct meta robots directive, and the expected structured data. A plugin that appears harmless in the WordPress admin can introduce SEO-breaking changes to your page output that are invisible until you inspect the rendered source.

Core Web Vitals on WordPress

WordPress sites built with heavy page builders, multiple full-width image sliders, and large collections of installed plugins are among the worst performers on Core Web Vitals metrics. The combination of large unoptimized hero images, render-blocking scripts from multiple sources, and slow database queries on shared hosting creates LCP scores that routinely fall in the ‘Poor’ range on mobile — the device type that Google uses as its primary indexing and ranking signal.

The most reliable performance gains on WordPress come from a combination of approaches: a reputable caching plugin (WP Rocket, W3 Total Cache, or the Cloudflare integration), a CDN for static assets, WebP image conversion either through a plugin or at the server level, and removing plugins you are not actively using. For sites running Elementor or Divi, the performance overhead is real and significant — switching to a lighter page builder or moving to the Gutenberg block editor often produces meaningful improvements without requiring a full redesign.

Common WordPress-Specific Mistakes Worth Catching Early

  • The ‘Discourage search engines’ checkbox in Settings > Reading enabled after launch — this one setting noindexes your entire site and is the source of many panicked support requests
  • Search result pages (?s=query URLs) indexed and crawlable — add a noindex directive to your search template
  • Duplicate content from tag archives that mirror full post content — exclude tags from indexing or implement canonical tags pointing tag pages to the canonical post
  • WordPress URL and Site URL settings inconsistency (one with www, one without) that creates redirect chains on every page load
  • Auto-draft and revision post URLs consuming crawl budget on large sites — limit post revisions in wp-config.php and ensure revision URLs are not crawlable

Getting WordPress SEO right is a learnable process. It requires knowing which settings matter, in what order to configure them, and what to check after every significant change. That is exactly what I cover in my SEO training — platform-specific, practical guidance with real-site walkthroughs that give you the ability to manage WordPress SEO yourself with confidence rather than relying entirely on an agency relationship you cannot evaluate. For the platform comparison, my Shopify SEO training resource covers how these same decisions differ on that platform.