Is WordPress Good for SEO? The Honest Answer

Search the phrase “is WordPress good for SEO” and you get a wall of yes, followed by eleven plugin recommendations. That answer is not wrong, it is just useless. It tells you nothing about what WordPress is doing on your behalf and nothing about what it is quietly doing against you.

The accurate framing is that WordPress is SEO-neutral. It hands you a clean, crawlable, editable foundation, and then hands you six loaded guns with the safety off. The foundation is genuinely good. The guns are enabled by default.

This post names each one: what core does for you, what it flatly refuses to do, where the defaults cost you crawl budget and rankings, and the order in which to fix them on a fresh install.

Is WordPress good for SEO, or just popular?

Both, and the two facts are unrelated. WordPress ranks well because it is easy to publish on, easy to edit, and produces sane HTML that crawlers have parsed for two decades. It does not rank well because of anything magical in the software.

Think of it the way you would think of a text editor. A good editor does not write good prose, it removes the friction between you and the page. WordPress removes the friction between you and a crawlable, indexable, revisable page. Everything past that is your job, your theme’s job, or your host’s job.

WordPress will not lose you rankings. Your theme, your host and your unattended defaults will.

What WordPress genuinely gives you for free

Core ships a real technical SEO baseline that most people credit to their plugin. Clean permalinks, a self-referencing canonical tag on singular views, an XML sitemap, responsive image markup, lazy loading, a virtual robots.txt, revision history and a proper taxonomy system are all in core, with no plugin involved.

Two of those are worth pinning down. XML sitemaps landed in core in WordPress 5.5, so a bare install has been discoverable from first publish since 2020. And rel_canonical() has been outputting canonical tags on singular queries since 2.9, switching to wp_get_canonical_url() in 4.6. Responsive srcset and sizes markup arrived in 4.4.

Capability	In WordPress core?	What you still have to add
Clean, keyword-readable permalinks	Yes, but the default is not Post name	Set it once at Settings > Permalinks
Self-referencing canonical on singular views	Yes, since 2.9	Cross-domain and archive canonicals
XML sitemap	Yes, since 5.5	Exclusion rules, image and video entries
srcset and sizes on images	Yes, since 4.4	WebP or AVIF, real compression, correct hero sizing
Native lazy loading	Yes	Excluding the LCP image from it
robots.txt	Yes, generated virtually	Custom disallow rules for parameter URLs
Revisions, drafts, scheduling, roles	Yes	Nothing. This part is genuinely done
Categories, tags, custom taxonomies	Yes	A policy on which of them should be indexed
Title and meta description templates	No	An SEO plugin
Open Graph and Twitter card tags	No	An SEO plugin
Article, Product, FAQ, HowTo schema	No	An SEO plugin or hand-written JSON-LD
Redirect management	No	A plugin, or rules at the server
Per-URL noindex control	No	An SEO plugin
Breadcrumbs with markup	No	Theme support plus a plugin

What WordPress does not do, whatever the marketing says

WordPress does not do any of the work that actually moves a page up a results page. It does not write your title tags, it does not write meta descriptions, and the fallback title your theme prints is usually just the post name plus the site name.

It does not manage redirects. Change a slug and core will occasionally guess its way to the right destination through its old-slug lookup, but that is a courtesy, not a redirect strategy, and it does not survive a restructure. It does not generate schema beyond whatever your theme happens to emit. It does not stop index bloat, it does not build links, and it certainly does not make you fast. A stock install on cheap shared hosting will fail Core Web Vitals just as reliably as any other CMS on the same box.

None of that is a criticism. It is a division of labour, and knowing where the line sits is the difference between a site you control and a site that surprises you. If you want the full build-out, the walkthrough in our guide to improving WordPress SEO covers the configuration side in more depth than fits here.

Where WordPress actively works against your SEO

This is the part the ranking pages skip. WordPress has a handful of defaults and ecosystem habits that generate crawlable junk without you touching anything. Each one has a specific fix.

Attachment pages

Every image you upload historically got its own URL with almost no content on it. Upload 800 images and you have created 800 thin pages. WordPress 6.4 added the wp_attachment_pages_enabled option: new installs default to disabled, but sites upgrading from earlier versions were set to 1 to preserve existing behaviour. If your site predates 6.4, it is probably still on. Turn it off.

wp option get wp_attachment_pages_enabled
wp option set wp_attachment_pages_enabled 0

Tag and date archives nobody asked for

Tags are free to create and most sites end up with dozens holding one post each. A tag archive with a single entry is a duplicate of that post’s excerpt. Date archives are worse, because they group content by an axis no searcher uses. Set single-use tag archives and all date archives to noindex, and stop inventing tags you will not use ten times.

Pagination with no ceiling

Settings > Reading defaults to ten posts per archive page. A 600-post blog therefore publishes 60 paginated URLs per archive, multiplied across every category and tag. Raise the posts-per-page count on archives, and make sure each paginated URL carries a self-referencing canonical rather than pointing back at page one, which hides the deeper posts from discovery entirely.

Multi-purpose themes shipping forty assets

A theme sold as “works for any business” loads the sliders, portfolio filters, icon fonts and animation libraries for every one of those businesses on every page, including the contact page that uses none of them. Open the network panel on your slowest template and count the requests. Dequeue what that template does not use, from a child theme so an update does not undo it.

add_action( 'wp_enqueue_scripts', function () {
    if ( ! is_front_page() ) {
        wp_dequeue_style( 'theme-slider' );
        wp_dequeue_script( 'theme-slider' );
    }
}, 100 );

Page builders and div soup

Most visual builders wrap a paragraph in five nested divs and inline a block of CSS per section. The semantic damage is mild, since headings usually survive. The performance damage is not: inline style blocks cannot be cached separately, and generated stylesheets are frequently loaded on pages that use two rules from them. If you build with one, the trade-offs are laid out in our look at WordPress visual page builders. Audit the rendered output rather than the editor preview.

Query parameters that clone your URLs

Filter plugins, WooCommerce sorting and add-to-cart links all append parameters, and every distinct parameter string is a distinct URL to a crawler. Core’s canonical tag protects you from indexing the duplicates. It does not protect your crawl budget. Add explicit disallow rules for the parameters that never need crawling.

User-agent: *
Disallow: /*?add-to-cart=
Disallow: /*?orderby=
Disallow: /*?replytocom=

Comment pagination and ?replytocom

Two separate problems from one settings screen. Breaking comments into pages, at Settings > Discussion, mints a comment-page-2 URL for every busy post. Threaded replies produce a ?replytocom link on every single comment, so a post with 90 comments offers 90 extra URLs. Turn comment pagination off unless you genuinely need it, and disallow the parameter.

Author archives on a one-author site

If one person writes everything, the author archive is a byte-for-byte duplicate of your main blog index, and it leaks your login username as a bonus. Redirect it, or noindex it. Multi-author publications are the exception, where author archives carry real authorship signal and should stay.

add_action( 'template_redirect', function () {
    if ( is_author() || is_date() ) {
        wp_safe_redirect( home_url( '/' ), 301 );
        exit;
    }
} );

Which SEO plugin should you actually run?

Pick on two axes only: whether the free tier covers redirects and schema, and what the second site costs. Everything else is interface preference, and every one of these plugins will output correct title tags.

Plugin	Free tier ceiling	Paid entry, per year	Sites per licence	Schema control	Redirect manager	Notable weakness
Rank Math	Highest of the five: titles, sitemaps, 16+ schema types, redirections, 404 monitor, Search Console	PRO at EUR 7.99/month billed annually, ex VAT, renewing at EUR 8.99/month	PRO covers unlimited personal sites; Business 100, Agency 500	Broad, template-driven, most types free	Yes, in the free version	Enormous settings surface and module sprawl; easy to misconfigure
Yoast SEO	Titles, sitemaps, connected schema graph, readability analysis	Premium at USD 118.80, ex VAT	One subscription covers one site or domain	Coherent graph model, fewer point-and-click types	Premium only	Dearest per site by a wide margin, and redirects sit behind the paywall
All in One SEO	Titles, sitemaps, basic schema, social meta	Basic at USD 49.50 first year, normally USD 99.00	Basic 1, Plus 3, Pro 10, Elite 100	Schema generator; richer types on paid tiers	From the Pro tier, USD 199.50 first year	Redirects gated two tiers up, and introductory pricing roughly doubles on renewal
SEOPress	Titles, meta templates, XML and image sitemaps, breadcrumbs	PRO at USD 49	USD 49 for 1, USD 59 for 5, USD 149 unlimited	Visual schema editor, PRO only	PRO only, with 404 monitoring	Free tier is thinner than Rank Math’s; schema and redirects both paywalled
Slim SEO	Automatic titles and meta, JSON-LD, sitemaps, redirects, breadcrumbs, 404 monitor	Pro at USD 59	USD 59 for 1, USD 119 for 10, USD 179 unlimited	Automatic in free; visual builder in Pro	Yes, in the free version	Deliberately almost no manual control, and no content analysis

Two things fall out of that table. Rank Math and Slim SEO are the only ones giving you redirect management for nothing, which matters more than any content-analysis feature. And if you run more than three sites, Rank Math and SEOPress are dramatically cheaper per site than All in One SEO or Yoast.

Core Web Vitals, and why WordPress sites miss them

The three current Core Web Vitals are LCP, INP and CLS, and each is assessed at the 75th percentile of page loads, segmented separately for mobile and desktop. A page passes only when all three sit in the good band at that percentile, which means your median visitor being fine is not the test.

Metric	Good	Needs improvement	Poor	What usually breaks it on WordPress
Largest Contentful Paint	2.5 s or less	2.5 s to 4.0 s	Over 4.0 s	A full-width hero uploaded at 4000 px, lazy-loaded by mistake, served without a page cache
Interaction to Next Paint	200 ms or less	200 ms to 500 ms	Over 500 ms	Slider, popup and analytics scripts competing for the main thread on tap
Cumulative Layout Shift	0.1 or less	0.1 to 0.25	Over 0.25	Images without width and height, web fonts swapping in, cookie bars injected above the fold

Four causes account for most WordPress failures, and only one of them is WordPress’s fault. Unoptimised hero images, render-blocking plugin CSS, no working page cache, and a slow time to first byte from oversubscribed shared hosting. TTFB is the one people miss, because it applies a fixed penalty to every single metric before any of your markup is even parsed.

The cache point deserves emphasis. A site that believes it is cached and is not will fail LCP while every plugin dashboard reports green, because most caching plugins report their own configuration rather than what the browser actually received. The only honest test is the response headers on a cold, logged-out request, which is what Cache Inspector in the WPColt toolbox checks across page cache, server cache and CDN layers. If you are choosing between caching plugins in the first place, our Cache Enabler versus W3 Total Cache comparison covers the trade-offs, and the shorter list in five tips to make your website run faster is the right starting point if nothing is configured yet.

The setup order for a new WordPress install

Do these in order, because several of them are painful to change later. The whole list takes about half an hour on a fresh site.

1. Set permalinks to Post name at Settings > Permalinks. Do it before publishing anything, because changing it later means redirecting every URL you have.
2. Confirm Settings > Reading has “Discourage search engines from indexing this site” unchecked. A staging flag left on is the single most common cause of a site that never gets indexed.
3. Disable attachment pages with wp option set wp_attachment_pages_enabled 0, or through wp-admin/options.php if you have no WP-CLI access.
4. Install exactly one SEO plugin and set your title templates for posts, pages and archives before you write the first post.
5. Decide your indexing policy in that plugin: noindex on date archives, on author archives if you are a single author, and on tag archives until a tag has real depth.
6. Turn off comment pagination at Settings > Discussion, and drop the parameter disallows into robots.txt.
7. Install and configure a page cache, then verify it from the response headers rather than the plugin’s own status panel.
8. Set a maximum upload dimension policy and convert to WebP or AVIF. Exclude your hero image from lazy loading.
9. Verify the property in Search Console and submit the sitemap at /wp-sitemap.xml, or your plugin’s replacement for it.

Mistakes that cost real rankings

The expensive errors are structural, not editorial. Nobody has ever lost meaningful traffic because a meta description was 162 characters.

• Changing the permalink structure on a live site with no redirect map. Every existing ranking URL 404s at once, and the recovery takes months even when you fix it the same week.
• Migrating hosts and leaving the old URLs unredirected. If you are moving, plan the redirects first; our notes on moving a WordPress site cover the sequence.
• Noindexing category archives wholesale. On many sites those archives carry most of the internal linking into deeper posts. Noindex them and you weaken the crawl path to the pages you actually want ranked.
• Trusting a green dashboard over a response header. Cache plugins report intent. Headers report reality, and the two disagree more often than anyone expects.
• Treating a plugin’s content score as the target. A green light means the keyword appears in the places the plugin checks. It is not evidence that the page answers the query better than the pages above it.

WordPress versus Webflow, Wix, Shopify, Ghost and headless

WordPress has the highest SEO control ceiling of any mainstream platform and the worst default performance of the group. That is the honest trade. Ghost and Webflow will beat a stock WordPress install on speed without you doing anything, because neither lets you install forty plugins.

Platform	SEO control ceiling	Skill required	Speed by default	Redirects and schema	Realistic annual cost	Who it suits
WordPress	Total. Every tag, header and route is yours	Moderate to high; the ceiling is only reachable with effort	Poor until configured	Both via plugin; SEOPress PRO from USD 49/year is the cheapest verified option	Domain plus hosting plus optional plugin; hosting is the variable and ranges from a few dollars a month to managed plans an order of magnitude higher	Content sites, publishers and anyone who needs full technical control
Webflow	High for a hosted tool; clean markup, editable meta and redirects	Moderate; visual but genuinely a design tool	Good. Consistently fast without tuning	Redirects built in; schema via custom code embeds	Basic at USD 15/month billed yearly, Premium at USD 25/month	Design-led marketing sites where the team is not technical
Wix	Moderate. Meta, canonicals and redirects are editable, structure is not	Low	Moderate; improved a lot, still template-bound	Redirects built in; limited schema editing	Light at USD 19.77/month, Core USD 29.77, Business USD 39.77, all billed annually	Small local businesses that want one bill and no maintenance
Shopify	Limited. Forced /products/ and /collections/ URL structure	Low to moderate	Good on the storefront; apps degrade it fast	Redirects built in; product schema in most themes	Basic USD 29/month billed annually, Grow USD 79, Advanced USD 299	Product-first stores where transactions matter more than URL control
Ghost	Moderate. Excellent defaults, deliberately few knobs	Low for hosted, high for self-hosted	Excellent. The fastest default in this table	Redirects via a config file; schema output automatically	Ghost(Pro) Starter at USD 18/month billed yearly, Publisher USD 29, Business USD 199; the software is open source and self-hostable	Writers and newsletter publishers who want speed and no maintenance surface
Headless Next.js	Total, and you own every regression too	High. This is a software project	Excellent if built well, dreadful if not	Whatever you write	Hosting can be near zero; the real cost is developer time, and it recurs	Engineering teams with a developer permanently assigned to the site

The verdict: who should and should not use WordPress for SEO

Use WordPress if you publish regularly, if you need control over URL structure, schema and redirects, and if you have either the skills or the budget to keep a theme and a caching layer honest. For a content-led site chasing long-tail organic traffic, nothing else gives you this much control at this price, and the technical baseline in core is real.

Do not use WordPress if you want a five-page brochure site and nobody on the team will ever log in to run an update. You will end up with an unpatched install on shared hosting failing every Core Web Vital, and Wix or Webflow would have served you better. Do not use it for a pure ecommerce catalogue where Shopify’s defaults already do what you need, unless the content side of the business is the point. And do not use it because it is the default choice, which is the reason most people give.

The platform is neutral. What decides your outcome is whether you turn off the defaults that hurt, keep the theme lean, and prove your cache is working rather than assuming it. Once the foundation holds, the work is ordinary content and link work, and our practical SEO tips pick up from there.

Frequently asked questions