WordPress makes a set of SEO decisions for you at install, before you write anything. Four of them are wrong for most sites, and none of them is fixed by a plugin.
That is the useful frame for this subject, because "WordPress SEO" is usually presented as a plugin choice, and the plugin is the least consequential part.
The four decisions:
| Default | What it does | Usually wrong because |
|---|---|---|
| Permalink structure | Sets your URL format | The default is not descriptive; changing it later means redirecting every URL |
| Archives all indexed | Categories, tags, authors, dates all live | Tag and date archives are frequently thin duplicates of your posts |
| Core sitemaps on | Serves /wp-sitemap.xml |
It includes archives and author pages you may not want listed |
| Discourage search engines | A single checkbox that blocks everything | Left on after launch, and it explains an alarming number of "why am I not indexed" cases |
Fix those four and you have done most of what "WordPress SEO" means. The rest is content, and content is not a WordPress question.
The checkbox that breaks sites
Settings → Reading → "Discourage search engines from indexing this site."
It is switched on during development and forgotten, and the symptoms are total: nothing indexes, nothing ranks, and the site otherwise looks perfectly healthy.
Check it first, always. It costs five seconds and it is the single most common cause of a WordPress site that has published for months and received nothing.
It also silently disables WordPress's core sitemaps — the setting turns them off automatically — so a missing /wp-sitemap.xml is often this checkbox rather than a sitemap problem.
If a site is not being indexed and the checkbox is off, the diagnosis continues in why a page is not indexed.
Permalinks: the decision that is expensive to change later
Settings → Permalinks. Choose once, properly.
Google's guidance is about readability rather than keywords: "use readable words rather than long ID numbers in your URLs", and "we recommend using hyphens (-) instead of underscores (_) to separate words in your URLs, as it helps users and search engines better identify concepts in the URL."
Notably, Google's URL structure documentation gives no guidance on URL length and none on keyword usage. The advice to stuff keywords into slugs is not from Google.
The practical position for a blog: the post name alone, giving /blog/your-post-title. Short, descriptive, and it does not date your content the way a year-and-month structure does.
Changing permalinks on an established site means every existing URL breaks unless every one is redirected. That is why this is a launch decision, and why it is worth being deliberate about at install rather than convenient. The full treatment is in WordPress permalinks and URL structure.
Archives: WordPress creates pages you did not write
This is the WordPress-specific issue nobody warns you about at install.
Every post automatically generates entries on: its category archive, each tag archive, the author archive, the date archives, and the paginated blog index. On a site with 50 posts and 200 tags, WordPress has published 250-odd pages you never wrote, most of them lists of the same content.
Not all are a problem, and the distinction is worth getting right:
- Category archives are usually worth keeping indexed — they are genuine hub pages if you use few categories deliberately
- Tag archives are usually not, because most sites have many tags with one or two posts each
- Date archives almost never earn anything
- Author archives matter on a multi-author site and are redundant on a single-author one
The fix is noindex, and the mechanism has a trap — Google is explicit: "For the noindex rule to be effective, the page or resource must not be blocked by a robots.txt file… If the page is blocked by a robots.txt file or the crawler can't access the page, the crawler will never see the noindex rule, and the page can still appear in search results."
So blocking archives in robots.txt does the opposite of what people intend. The full method is in WordPress categories and tags for SEO, and the robots.txt half is in robots.txt mistakes.
Sitemaps: you already have one
Since WordPress 5.5, core generates XML sitemaps automatically at /wp-sitemap.xml, with no plugin required.
What it includes by default: all public post types, all taxonomies, author archives, and the homepage. Which is to say, it lists exactly the archive pages you may have just decided to noindex.
Two facts worth knowing before you touch anything:
A sitemap does not cause indexing. Google states it plainly: "a sitemap helps search engines discover URLs on your site, but it doesn't guarantee that all the items in your sitemap will be crawled and indexed."
And most WordPress sites do not need one at all. Google's own threshold: you might not need a sitemap if "Your site is 'small'. By small, we mean about 500 pages or fewer on your site" and it is comprehensively linked internally.
That last point deserves emphasis, because sitemap configuration absorbs an enormous amount of attention on sites where internal linking would do more. Details in WordPress sitemaps, properly configured.
The plugin does less than you think
An SEO plugin gives you fields and defaults. It does not give you rankings.
What it genuinely does: editable titles and descriptions, canonical control, per-page noindex, structured data, and a sitemap that replaces core's.
What it does not do: make content rank, decide what to write, or fix a structural problem. And its content-analysis scores are the plugin's opinion, not a measurement of anything Google reports.
The green light is not a ranking signal. Writing to satisfy it produces exactly the pattern Google's own guidance asks about: "Is the content primarily made to attract visits from search engines?"
Two practical warnings. Run one SEO plugin, never two — they compete over the same output tags. And when a plugin takes over sitemaps, core's is disabled, which is expected rather than broken.
Choosing one, without a ranking or a price, is in choosing a WordPress SEO plugin.
The setup that actually matters
Seven steps, once, at the start.
Step 1 — Turn off "Discourage search engines"
Settings → Reading. Confirm it is unchecked before anything else.
Step 2 — Set permalinks and never change them
Post name. Decide now, because changing later means redirecting every URL you have published.
Step 3 — Decide which archives should exist
Categories few and deliberate, indexed. Tags used sparingly or not at all, noindex. Date archives noindex. Author archives depend on whether you have more than one author.
Step 4 — Choose one SEO plugin and configure the defaults
Title templates, description templates, and the site-wide noindex rules from step three. Setting the templates once is worth more than editing hundreds of pages individually — the craft is in meta titles and descriptions.
Step 5 — Check what your sitemap actually contains
Open it and read it. If it lists tag archives you have set to noindex, you are telling Google two different things.
Step 6 — Verify in Search Console and submit the sitemap
Then read the Pages report rather than the sitemap status — that is where indexing problems are actually visible. Method in Google Search Console reports, read properly.
Step 7 — Fix the internal linking
The step that outperforms all six above on a small site, and the one WordPress does worst by default: related-post widgets and tag clouds are not internal linking. Deliberate links between related posts are. Method in internal linking and topic clusters.
What is not a WordPress problem
Worth separating, because these get treated as platform issues and are not.
Content quality. No setting affects it.
Speed. A real ranking-adjacent concern and an entirely separate subject — speed up WordPress.
Links. Not a platform question at all, and less decisive than commonly assumed — link building when links are not a top three factor.
Keyword choice. Keyword research.
The plugin's content score. Not a Google measurement.
A useful test: if the answer would be the same on any other CMS, it is not a WordPress SEO question. Almost everything is. The four defaults at the top of this page are the genuine exceptions, which is precisely why they are worth the attention.
Frequently asked questions
Do I need an SEO plugin for WordPress?
Not strictly. WordPress generates sitemaps in core since 5.5 and produces titles from your content. A plugin gives you editable titles and descriptions, canonical control, per-page noindex and structured data — useful, but it is a set of fields rather than a source of rankings.
What is the best permalink structure for WordPress SEO?
Post name, giving a short descriptive URL. Google recommends readable words rather than ID numbers and hyphens rather than underscores, and gives no guidance on URL length or keyword usage. Decide at launch, because changing it later breaks every published URL.
Should I noindex WordPress tag and category archives?
Usually noindex tags and date archives, and keep categories indexed if you use few of them deliberately. The noindex must be crawlable to work — Google states that a page blocked by robots.txt will never be seen, so the rule has no effect there.
Does WordPress have a sitemap without a plugin?
Yes. Since WordPress 5.5 core serves an XML sitemap at /wp-sitemap.xml covering public post types, taxonomies, author archives and the homepage. An SEO plugin replaces it with its own, which disables core's.
Why is my WordPress site not showing in Google?
Check Settings → Reading for "Discourage search engines from indexing this site" first. It is switched on during development and forgotten constantly, and it also disables core sitemaps automatically, which makes the symptom look like a sitemap problem.
Do I need a sitemap for a small WordPress site?
Often not. Google says you might not need one if your site is about 500 pages or fewer and comprehensively linked internally. A sitemap aids discovery and does not guarantee crawling or indexing.
Does the SEO plugin's green light mean my page will rank?
No. Content analysis scores are the plugin's own heuristics, not a measurement of anything Google reports. Writing to satisfy them tends toward content made primarily to attract search visits, which is what Google's guidance asks you to avoid.
Can I run two SEO plugins at once?
No. Two plugins compete to output the same title, description and canonical tags, producing duplicated or conflicting output. Pick one and remove the other properly rather than deactivating it.
What to do next
Open Settings → Reading and look at the "Discourage search engines" checkbox. Then open /wp-sitemap.xml or your plugin's sitemap and read what is actually in it.
Those two checks take a minute and catch the two problems that account for most WordPress-specific SEO failures.
Related guides
- WordPress permalinks and URL structure — the launch decision
- WordPress categories and tags for SEO — the pages WordPress writes for you
- WordPress sitemaps, properly configured — including whether you need one
- Choosing a WordPress SEO plugin — without a ranking
- Why a page is not indexed — when the checkbox is not the cause
- Internal linking and topic clusters — the step that outperforms the rest
- Technical SEO: what actually needs fixing — the platform-independent half
- Speed up WordPress — the separate subject
Chapters in this Guide
The WordPress Email Delivery Checklist
Stop your WordPress emails from failing silently. Get the complete setup guide.
Muhammad Basim has worked in digital marketing since 2013, focused on email deliverability and AI-assisted content production. He is the author of The Email Deliverability Playbook and The Email Copywriting Playbook.
Related Articles
Choosing a WordPress SEO Plugin
This page names no winner, and the reason is that the choice matters far less than the category's marketing implies. The major WordPress SEO plugins do the same six things. They have converged, they will continue to converge, and the difference between them is interface preference and a small number of features most sites never […]
Two-Factor and Login Hardening for WordPress
Login attacks against WordPress are constant, automated and indiscriminate. Every public WordPress site receives them, regardless of size or traffic, because the cost of trying is near zero. They are also the least successful route into a WordPress site. Vulnerable plugins account for more compromises than password guessing, which is worth holding onto — login […]
WordPress Email: Why Your Site’s Emails Never Arrive
WordPress sends email in a way that fails modern authentication by default, and it reports success while doing it. That combination is why this problem is so persistent. The site is not broken. Nothing is logged. wp_mail() returns true, the order is placed, the form says thank you — and the message never reaches an […]