Is WordPress Good for SEO? An Honest, Complete Answer

Search for this question and you get the same answer twelve times: WordPress is SEO-friendly, install Yoast or Rank Math, write good content. It is not wrong. It is also not useful, because it never says which parts of SEO WordPress affects at all.

Here is the distinction that clarifies everything else. There are three layers to search performance: what your platform does, what your configuration does, and what your content does. WordPress owns the first, influences the second, and is completely irrelevant to the third. Most SEO failures on WordPress sites are layer-three problems, which is why installing a fourth plugin never fixes them.

This piece sorts those layers out: what you get for free, what you must configure, what the SEO plugins genuinely do versus what people believe they do, where WordPress actively hurts you, and how it compares with the platforms people weigh it against. ThemesCraft takes nothing from any plugin or host named here.

What WordPress gives you for free

Out of the box, with no plugins, a default WordPress install already handles a surprising amount of technical SEO. This is the part people mean when they call it SEO-friendly.

Signal	Handled by core	Caveat
Clean, readable URLs	Yes, via permalinks	Default setting is not the good one. Change it before publishing
XML sitemap	Yes, since WordPress 5.5, at /wp-sitemap.xml	Basic. SEO plugins replace it with a better one
Title tags and heading hierarchy	Yes, through the theme	A badly built theme can wreck this
Mobile responsive output	Yes, in any modern theme	Theme-dependent, not core-guaranteed
Canonical tags on posts and pages	Yes	Edge cases need a plugin
robots.txt	Yes, virtual file generated automatically	Overridden if a physical file exists
Image alt text fields	Yes, in the media library	Nobody fills them in. That part is on you
Semantic HTML5 output	Yes, in well-built themes	Page builders frequently degrade this

Two rows deserve attention. The permalink default is not the SEO-friendly one, and changing it after you have published breaks every existing URL unless you add redirects. Set it to Post name on day one. And the native sitemap has existed since 2020, which means the common advice that you need a plugin for a sitemap is several years out of date.

What the SEO plugins actually do

The mental model most people have is that an SEO plugin optimises the site. It does not. It gives you an interface for controlling metadata that WordPress does not expose, and it generates structured data. That is genuinely valuable and it is a narrower job than the marketing implies.

• Editable titles and meta descriptions per post and page, plus templates for archives. Core gives you no control over these.
• Indexing control. Per-page noindex, and site-wide rules for tag archives, author archives, attachment pages and paginated series, all of which generate thin duplicate URLs by default.
• Schema markup. Article, FAQ, HowTo, Product, LocalBusiness, breadcrumbs. Writing this by hand is tedious and error-prone.
• Open Graph and Twitter Card tags so shared links render properly. Not a ranking factor. It affects click-through, which is worth more than most ranking factors people obsess over.
• Redirect management so changed URLs do not become 404s.
• A better XML sitemap than core’s, with control over what is included.

What they do not do: write content, build links, decide what to target, or make a slow site fast. The green light on a content analysis panel measures compliance with a checklist, not quality. Pages with a red light rank every day.

Choosing between them

Plugin	Free tier covers	Best for	Honest caveat
Rank Math	Most features including schema types, redirects and multiple focus keywords	Getting the most functionality without paying	Dense interface. Lots of settings to get wrong
Yoast SEO	Titles, meta, sitemaps, basic schema, one focus keyphrase	Teams who want the fewest decisions	Redirects and internal link suggestions are paid-only
All in One SEO	Comparable core feature set, broad schema support	Sites already standardised on it	Heavy upsell prompts in the free version
SEO Framework	Titles, meta, canonicals, sitemaps, sensible defaults	Anyone who wants it configured and silent	No content analysis, deliberately
Slim SEO	Automatic titles, meta, schema and sitemaps with almost no settings	Minimal footprint, no configuration appetite	Little manual control when you need an exception

Run exactly one. Two SEO plugins active at once produce duplicate meta tags, conflicting canonicals and two sitemaps, which is worse than running none. If you are switching, most offer an importer that moves your existing metadata across. Use it before deactivating the old one.

Where WordPress actively hurts your SEO

This is the section the platform’s advocates skip. WordPress has specific, structural tendencies that damage search performance, and all of them are fixable once you know they exist.

1. Speed, by default. WordPress builds every page on request by querying a database and running PHP. Without caching, a shared-hosting WordPress site is measurably slower than a static page. Caching solves this completely and nearly nobody enables it before it becomes a problem.
2. Archive pages creating thin duplicates. Every tag, category, author and date archive is a URL. A site with 300 tags has 300 near-empty pages competing with the posts they list. Noindex the ones that serve no purpose.
3. Attachment pages. WordPress generates a separate page for every uploaded image. These are content-free URLs that Google can and does index. Every SEO plugin offers a switch to redirect them to the parent post. Use it.
4. Plugin bloat in the head. Each plugin adds its own CSS and JavaScript, loaded on every page whether the page uses it or not. Twenty plugins can mean forty extra requests before your content renders.
5. Page builders and markup quality. Several popular builders output deeply nested divs, inline styles and sizeable CSS payloads. The page looks right and Core Web Vitals suffer. This is the single most common cause of a well-written WordPress page that will not perform.
6. Unmanaged URL changes. Editing a post slug changes its URL and WordPress does not create a redirect. The old URL, with whatever links it had accumulated, becomes a 404 silently.

Core Web Vitals on WordPress

Page experience is a real but modest ranking input, and it is where WordPress sites lose ground for avoidable reasons. Four fixes account for most of the available improvement, in this order.

1. Page caching. Serve a stored HTML copy instead of rebuilding the page. The largest single win available, and free options handle it well. Many managed hosts do it at server level, in which case adding a caching plugin can cause conflicts rather than gains.
2. Image handling. Serve WebP or AVIF, size images to their display dimensions, and lazy-load everything below the fold. WordPress lazy-loads by default; it does not compress or convert.
3. Fewer plugins and less blocking CSS or JavaScript. Audit what is actually loading. Deactivating three unused plugins usually beats any optimisation setting.
4. Hosting. Server response time sets the floor for everything else. No plugin compensates for an oversubscribed shared server, and a slow time to first byte caps your best possible score.

Measure with field data in Google Search Console rather than a single lab test. Lab scores fluctuate with test conditions; field data reflects what visitors experienced, which is what is actually evaluated.

How it compares with the alternatives

Platform	Technical SEO control	Speed out of the box	Where it loses
WordPress	Complete. Every tag, redirect and schema type is reachable	Poor until configured	Requires you to do the configuring
Webflow	Strong, with clean markup	Good	Weaker for large content libraries and editorial workflow
Squarespace and Wix	Adequate for most sites	Good	Ceilings you cannot raise on advanced technical work
Shopify	Good for products	Good	Enforced URL structure, limited blog and content tooling
Static site generators	Total	Excellent	Non-technical editors cannot publish without help

The conclusion people do not like: platform choice is one of the smaller variables in search performance. A well-configured WordPress site and a well-configured Webflow site both rank fine. The difference is who has to do the configuring and how high the ceiling goes when your requirements get unusual.

A setup that covers the technical layer

1. Set permalinks to Post name, before publishing anything.
2. Confirm the Discourage search engines box is unchecked.
3. Install one SEO plugin. Only one.
4. Noindex tag, author, date and media archives unless a specific one earns traffic.
5. Redirect attachment pages to their parent post.
6. Enable page caching, at host level if offered, otherwise via one plugin.
7. Serve compressed WebP images sized to their display dimensions.
8. Submit the sitemap in Google Search Console and check the Pages report monthly.
9. Turn on automatic redirect creation for slug changes.
10. Stop. Everything remaining is content and links, and no setting affects those.

Ten items, most of them one-time. If you have done all ten and still are not ranking, the answer is not in your dashboard. It is in what you publish and who links to it.

Two related pieces: our guide to adding keywords in WordPress covers where keywords genuinely belong, which is not the meta keywords tag most tutorials still teach, and essential WordPress plugins explains why plugin count itself is a performance decision.

Frequently asked questions