WordPress SEO: Settings, Plugins and Common Mistakes in 2026

Publication date: 17.07.2026

WordPress powers over 43% of all websites, yet it ships without production-ready SEO. Proper plugin configuration, a clean URL structure, and fixing common mistakes can grow organic traffic within 2–3 months.

WordPress and SEO: strengths and weaknesses of the platform

WordPress is attractive for SEO because of its open-source nature, vast plugin ecosystem, and flexible content management. But its popularity creates specific challenges: bloated database tables, conflicting plugins, and complex URL architecture on large sites.

At SEO-Factory, we audit WordPress sites every week. More than 70% of client projects on this CMS share the same clusters of errors: duplicate title/description tags, an incorrect permalink structure, images missing alt attributes, and a zero LCP score caused by unoptimised hero images.

WordPress SEO strengths:

  • Flexible permalinks — you can build any URL hierarchy your business needs
  • Mature SEO plugins — Yoast, RankMath, and All-in-One SEO cover most requirements
  • Easy content management — the Gutenberg editor lets you format SEO-friendly content without code
  • Large community — solutions to almost every problem are already documented somewhere
  • REST API and integrations — straightforward connection to external analytics and automation tools

Weaknesses that need active attention:

  • Plugin bloat — every extra plugin adds HTTP requests and slows the site down
  • Duplicate pages — date archives, tag archives, and category pages generate thin content by default
  • Canonical conflicts — themes and plugins can clash when outputting canonical tags
  • Security surface — WordPress popularity makes it a target; breaches affect uptime and ranking signals

Core WordPress SEO settings

The first step after installing WordPress is verifying the system settings that directly affect crawling and indexing. The admin panel has several critical areas most site owners overlook.

Settings → General: confirm the site title and tagline are correct — they may appear in the homepage title depending on your theme. Make sure the WordPress address and Site address are set to HTTPS. Settings → Reading: the most dangerous toggle — "Discourage search engines from indexing this site." This checkbox is frequently left active after development and hides the entire site from Google. Check it on every audit.

Settings → Discussion: disable pingbacks and trackbacks — they generate spammy backlinks and add server load. Users: make sure public author profiles do not expose unnecessary information or create thin archive pages that dilute crawl budget.

Practical tip: after every major WordPress or theme update, re-check the Reading settings. Some updates reset visibility preferences — your site can silently disappear from Google without any warning.

URL structure and permalinks

Permalinks are the foundation of site architecture. A wrong URL structure is one of the hardest mistakes to fix: correcting it after content is published requires mass 301 redirection and temporarily disrupts rankings.

WordPress permalink settings are at Settings → Permalinks. For most sites the optimal choice is Post name (/%postname%/) or a custom structure with a category prefix: /%category%/%postname%/.

Permalink structure Example URL Recommendation
Post name /wordpress-seo-guide/ Best for blogs and content sites
Month and name /2026/06/wordpress-seo-guide/ Avoid — date makes content feel dated
Numeric ID /?p=123 Avoid — carries no SEO meaning
Category + name /blog/wordpress-seo-guide/ Good for large sites with clear hierarchy
Day and name /2026/06/10/wordpress-seo-guide/ Avoid — redundant date information

Slug rules to follow: use only lowercase letters and numbers, separate words with hyphens, avoid trailing hyphens, skip stop words like "and", "or", "the". Keep slugs short and keyword-focused — the URL should give both users and crawlers an immediate clue about the page topic.

Warning: if you change permalink structure on a live site that already receives traffic, set up 301 redirects from all old URLs first. The Redirection plugin or .htaccess rules handle this reliably.

Yoast SEO vs RankMath in 2026

The Yoast vs RankMath debate is one of the most searched topics in the WordPress SEO space. As of 2026 both plugins are mature products, and the gap between them has narrowed considerably compared to three or four years ago.

At SEO-Factory we have tested both plugins across more than 150 projects. RankMath wins on free-tier features: built-in Schema support, redirects, GSC integration, and up to 5 focus keywords — all at no cost. Yoast is more reliable on complex enterprise projects with non-standard themes and less prone to conflicts with third-party code.

"A client in the e-learning space switched from Yoast Premium to RankMath free tier, saved on their annual subscription, and gained access to a built-in Course schema editor — no developer required."
Yoast SEO vs RankMath feature comparison 2026 Yoast SEO vs RankMath: Feature Comparison 2026 Feature Yoast SEO RankMath Focus keyword analysis (free) 1 keyword 5 keywords Schema markup (free) Premium only Included free Redirect manager (free) Premium only Included free Google Search Console integration Separate plugin Built-in free Stability on large / enterprise sites Very high High Interface usability Classic, familiar Modern, dashboard-first Both plugins produce comparable SEO outcomes — pick based on your workflow
Yoast SEO vs RankMath: feature comparison matrix for 2026

Essential SEO plugins for WordPress

A good plugin stack balances functionality against performance. Every active plugin executes PHP code on each page request, so lean setups consistently outperform bloated ones.

Core plugin categories for a WordPress SEO stack:

  1. SEO plugin (choose one): Yoast SEO or RankMath — handles title, description, canonical, sitemap, and schema markup
  2. Caching: WP Rocket (paid, best performance), W3 Total Cache or WP Super Cache (free alternatives)
  3. Image optimisation: ShortPixel, Imagify, or Smush — automatic compression and WebP conversion
  4. Redirect management: Redirection (free) — 301/302 redirect management and 404 logging
  5. Security: Wordfence or iThemes Security — protection from attacks that affect uptime and domain reputation
  6. Lazy loading: built into WordPress since version 5.5, but verify your theme does not override it

Plugins to avoid or replace:

  • Two SEO plugins simultaneously — they conflict and duplicate meta tags
  • Outdated database optimisers — WP-Optimize is the modern replacement
  • Heavy page builders with redundant CSS — Elementor and Divi generate large CSS payloads that hurt LCP
SEO-Factory rule: if a plugin is not actively used every month — deactivate and delete it. Even a deactivated but installed plugin takes up space and may carry security vulnerabilities.

Image optimisation and Core Web Vitals

Images are the leading cause of poor Core Web Vitals scores on WordPress sites. LCP (Largest Contentful Paint) is in most cases determined by the hero image or the first large media element on the page.

We audited more than 80 WordPress projects in 2026 — in 64% of cases the primary LCP element was an image missing both a preload hint and a WebP version. Fixing those two issues alone reduced LCP by 0.8–1.5 seconds without changing the hosting setup.

WordPress image optimisation checklist:

  • Convert to WebP: ShortPixel or Imagify do this automatically on upload
  • Add loading="lazy" to all below-the-fold images — WordPress does this from version 5.5, but verify your theme does not disable it
  • Add fetchpriority="high" to the LCP image (usually hero) — and disable lazy loading for that image
  • Specify width and height on every image — prevents CLS (layout shift)
  • Fill in alt attributes for every image — both an SEO and an accessibility requirement
  • Use srcset for responsive images — WordPress generates these automatically

The most common CLS causes in WordPress are fonts without font-display:swap, images without explicit dimensions, and dynamically injected ad banners. Check CLS in Chrome DevTools (Performance tab) or in PageSpeed Insights.

For a deep dive into Core Web Vitals metrics and how they affect rankings, see our guide: Core Web Vitals: LCP, INP and CLS explained.


Page speed and caching

WordPress generates pages dynamically by default — PHP runs on every request, queries the database, assembles HTML, and delivers it to the user. Caching breaks this cycle: a ready-made HTML snapshot is stored and served without executing PHP at all.

Real-world result from our experience: a site on shared hosting with no caching has a TTFB of 800–1,200 ms. After setting up WP Rocket plus Cloudflare, TTFB drops to 120–200 ms. For Google PageSpeed that is the difference between "Needs Improvement" and "Good."

The WordPress caching stack, from the ground up:

  1. Hosting with OPcache and PHP 8.2+ — the base layer everything else is built on
  2. Object cache (Redis or Memcached) — caches database query results; available on most VPS hosts
  3. Page caching plugin — WP Rocket is easiest to configure; LiteSpeed Cache is more efficient on LiteSpeed servers
  4. CDN — Cloudflare free tier dramatically reduces TTFB for international visitors
  5. Browser caching — configured via .htaccess or through your caching plugin
WordPress speed optimisation decision tree WordPress Speed: Where to Start Fixing PageSpeed score low? Check LCP in PageSpeed Insights LCP = image Add fetchpriority="high", convert to WebP, preload High TTFB WP Rocket + Redis cache + CDN (Cloudflare) CLS issues Add width/height to images, font-display:swap Re-run PageSpeed and verify
WordPress speed optimisation: a decision tree for diagnosing where to start
Important: after enabling caching, always test forms, shopping carts (for e-commerce), and login pages — some caching plugins cache dynamic content and break functionality.

Canonical and noindex issues in WordPress

WordPress generates dozens of archive page types by default: date archives, tag archives, category archives, author archives. Most of these are thin or duplicate content that dilutes signals for Google.

Common canonical problems in WordPress:

  • URL parameter duplicates?page=2, ?orderby=date, ?replytocom=1 — all may be indexed as separate pages
  • HTTP vs HTTPS duplicates — when HTTPS redirect is not enforced at the server level
  • www vs non-www — two versions of the site without canonical or 301
  • Pagination — /page/2/, /page/3/ without rel="next" or a canonical pointing to the first page
  • Theme and plugin canonical conflict — Google sees two different canonical tags and ignores both

What to block with noindex in WordPress:

  • Date archives (unless they have unique editorial value)
  • Author archives (for single-author or brand sites)
  • Tags (if you have hundreds duplicating categories)
  • Search results (/?s=) — this is critical; search result pages should never be indexed
  • Technical pages: /wp-login.php, /wp-admin/

Both Yoast and RankMath have content type toggles where you can noindex entire groups of pages in one click. After making changes, update your sitemap and verify in Google Search Console that excluded pages are no longer indexed.

XML Sitemap and robots.txt

An XML sitemap is a map of your site for crawlers. It does not guarantee indexing, but it significantly speeds up the discovery of new and updated pages. The robots.txt file is the first thing Googlebot checks — it tells the crawler which sections are off limits.

Yoast SEO and RankMath both generate XML sitemaps automatically. The default Yoast sitemap is at /sitemap_index.xml. After plugin activation, submit the sitemap URL in Google Search Console.

What belongs in your sitemap:

  • All indexable posts and pages
  • Categories (if they carry unique content)
  • An image sitemap (for photo-heavy or portfolio sites)

What must not be in your sitemap:

  • Pages tagged noindex
  • Paginated archive pages (/page/2/ onwards)
  • Date and author archives if they are noindexed
  • Pages with URL parameters

Recommended additions to the default WordPress robots.txt:

  • Disallow: /wp-admin/ — block the admin panel (keep Allow: /wp-admin/admin-ajax.php)
  • Disallow: /wp-includes/ — core WordPress system files
  • Disallow: /?s= — internal search results
  • Sitemap: https://yoursite.com/sitemap_index.xml — point crawlers to your sitemap

For authoritative reference, see the official Google documentation on XML sitemaps.

Always verify: after any change to robots.txt, use the Robots.txt Tester in Google Search Console. A single incorrect rule can block your entire site from Google.

Common WordPress SEO mistakes

Across 200+ WordPress projects, the most frequent SEO errors fall into predictable groups. Most are quick to fix, but left unaddressed they consistently suppress traffic.

The most critical errors we prioritise in every audit:

  • Site is blocked from indexing — the "Discourage search engines" checkbox in Reading settings was never unchecked
  • Missing HTTPS or mixed content — HTTP resources on an HTTPS page suppress rankings and trigger browser warnings
  • Two SEO plugins active simultaneously — canonical conflict and duplicate meta tags
  • Search results are indexable/?s= is not blocked with noindex
  • Date archives generate hundreds of thin pages diluting crawl budget
  • Sitemap not submitted to Google Search Console — Google has not discovered a portion of the site
  • Images missing alt attributes — flagged in every automated audit
  • Broken links (404s) not redirected — link equity is lost, user experience suffers

Less obvious mistakes that rarely appear in automated reports:

  • No breadcrumbs — breadcrumbs help Google understand structure and appear as rich SERP elements
  • Incorrect hreflang — on multilingual sites, hreflang errors cause Google to serve the wrong language version
  • Orphaned 404s from deleted plugins — the plugin generated pages, you removed it, but the URLs remain in GSC as errors
  • Fonts loaded without font-display:swap — invisible text during load hurts both CLS and user experience

For a complete audit methodology, see our guide: Technical SEO Audit: Step-by-Step Guide.


Frequently Asked Questions

Which SEO plugin is better in 2026: Yoast or RankMath?

Both plugins are comparable in core functionality. RankMath offers more features in its free version and has a more modern interface. Yoast is a proven tool with a long-standing reputation. The choice depends on your project requirements and experience.

Why is my WordPress site slow despite having caching enabled?

The most common reasons are unoptimised images, too many active plugins, no CDN, or underperforming hosting. Run PageSpeed Insights and eliminate issues one by one.

How do I fix duplicate canonical tags in WordPress?

Install a primary SEO plugin that manages canonical tags automatically. Check that your theme and third-party tools are not outputting their own canonical tags. Review your setup via a Google Search Console audit.

Does WordPress Multisite affect SEO?

Yes. Multisite complicates management of canonical tags, sitemaps, and robots.txt. Each subsite requires separate configuration. We recommend dedicated plugins per domain or subdomain to keep settings clean.

How many SEO plugins should I run at the same time?

One primary plugin (Yoast or RankMath) plus 2–3 supporting plugins for images, caching, and redirects is sufficient. More plugins slow the site down and can conflict with each other in unexpected ways.

Need professional SEO optimisation for your WordPress site?

SEO-Factory delivers a full technical audit, plugin setup, and error remediation — so your WordPress site can actually rank.

Get WordPress SEO help

Or contact us →