Web DevelopmentSEO

WordPress SEO: Settings, Plugins and Pitfalls

WordPress SEO is the job of configuring WordPress so search engines can crawl, index and understand your site: the right visibility and permalink settings, one clean sitemap, sensible rules for archives and attachment pages, a fast theme, and accurate titles, descriptions and schema. WordPress handles some of this in core and leaves the rest to themes and plugins, which is where most WordPress SEO problems come from.

This guide is for owners and marketers running a WordPress site, and for developers inheriting one. It stays neutral on plugins and focuses on the settings and structural issues that are specific to WordPress, rather than general SEO advice.

On this page

Does WordPress provide SEO?

WordPress provides the basics, and a lot of the web depends on it. W3Techs reported on September 22, 2026 that WordPress is used by 58.8% of websites whose content management system it can identify, which is 40.2% of all websites.

WordPress usage share, W3Techs, September 22, 2026 Two horizontal bars on a 0 to 100 percent axis. Share of websites with a known content management system that use WordPress: 58.8 percent. Share of all websites that use WordPress: 40.2 percent. The difference is that many sites use no detectable CMS. How much of the web runs on WordPress W3Techs usage survey, September 22, 2026 Sites with a known CMS 58.8% All websites 40.2% 0%25%50%75%100% The gap exists because many sites run no detectable CMS at all.

Scroll the diagram sideways to see all of it.

Source: W3Techs, "Usage statistics and market share of WordPress," September 22, 2026.

Out of the box, core WordPress gives you three SEO-relevant features. Since version 5.5 it generates an XML sitemap index at /wp-sitemap.xml and references it in the virtual robots.txt, according to the WordPress 5.5 sitemaps announcement. It lets you set clean permalinks. And it has a switch to discourage indexing.

What core does not give you: editable titles and meta descriptions per page, schema markup, control over which archive types are indexed, or redirects. That gap is why nearly every WordPress site adds an SEO plugin, and why the choice of plugin, theme and settings matters more than the platform itself.

The five settings to check first

Check these five before touching content. Each one is a common cause of WordPress sites that never rank, and each takes minutes to fix.

  1. Search engine visibility. In Settings, Reading, the “Discourage search engines from indexing this site” box must be unchecked on the live site. WordPress’s Reading screen documentation says that since version 5.3 it outputs a noindex,nofollow robots meta tag, and the sitemap announcement notes that sitemaps are disabled when it is on. It is easy to launch a site with it still ticked from staging. The same documentation adds that it does not block access: “it is up to search engines to honor your request.”
  2. Permalink structure. Settings, Permalinks should not be “Plain” (?p=123). More in the next section.
  3. One sitemap. Core generates /wp-sitemap.xml; most SEO plugins can generate their own. Make sure only one is live and submitted to Search Console and Bing.
  4. Attachment pages. Check the wp_attachment_pages_enabled option on any site created before WordPress 6.4. Details below.
  5. HTTPS and one hostname. WordPress Address and Site Address in Settings, General should both use https and the same host (www or not), so canonicals and internal links agree.

The flow below puts the full audit in order, including the archive decisions most sites skip.

A WordPress SEO settings audit in six steps Six steps in order. 1 Reading: search engine visibility unchecked on the live site. 2 General: WordPress and Site Address both https on one hostname. 3 Permalinks: Post name or a custom structure, never Plain. 4 Sitemap: one sitemap only, core wp-sitemap.xml or the plugin's, submitted to Google and Bing. 5 Attachments: wp_attachment_pages_enabled set to 0 on sites older than 6.4. 6 Archives: decide which of tags, authors, dates and categories are indexed. WordPress settings audit, in order Steps 1 to 3 in wp-admin Settings; 4 to 6 involve your SEO plugin 1 Reading "Discourage search engines" unchecked on the live site 2 General WordPress and Site Address: https, one hostname 3 Permalinks Post name or custom; never Plain (?p=123) 4 Sitemap One only: core or plugin; submitted to Google and Bing 5 Attachments wp_attachment_pages_enabled = 0 on pre-6.4 sites 6 Archives Decide: tags, authors, dates, categories

Scroll the diagram sideways to see all of it.

Source: Ambeltek diagram based on WordPress documentation (Reading and Permalinks screens), the 5.5 sitemaps and 6.4 attachment page announcements.

Pick a structure you will never have to change, because changing it later means redirecting every URL. WordPress’s Permalinks screen documentation lists the options: Plain (/?p=123), Day and name, Month and name, Numeric, Post name (/sample-post), and a custom structure built from tags such as %postname%.

For most business sites and blogs, Post name is the right choice. It is short, readable and does not age. Date-based structures make evergreen content look stale and tie URLs to a publishing date you may want to update. Google’s SEO starter guide notes that keywords in the URL path “have hardly any effect beyond appearing in breadcrumbs,” so choose for readability and permanence, not for keyword placement.

If you are changing permalinks on an established site, treat it as a migration: map every old URL to its new one with 301 redirects before switching. Our redirects guide and website redesign SEO guide cover the process.

Which WordPress SEO plugin should you use?

Choose on features you need, not on reputation, and run exactly one. The main plugins overlap heavily. Bing’s IndexNow page lists Yoast, Rank Math, AIOSEO and SEOPress as WordPress plugins that support IndexNow, and each handles titles and sitemaps in some form. The differences that matter are in the details:

What to checkWhy it matters
Per-post title and description fieldsThe core reason to install a plugin
Sitemap controlCan it exclude noindexed URLs and replace the core sitemap cleanly?
Archive indexing settingsTags, authors, dates, formats and attachments each need a decision
Schema outputWhat it emits by default, and whether you can edit or disable it
Redirect managerNeeded for any URL change, sometimes a paid feature
IndexNowBuilt in, or through the official plugin
BloatAdmin notices, extra scripts on the front end, database tables

The official IndexNow plugin, published by Microsoft on WordPress.org, is an option if your SEO plugin lacks it; our IndexNow guide covers setup. Whatever you choose, do not run two SEO plugins together. Two plugins means two sets of meta tags, two sitemaps and often two schema graphs that contradict each other.

Index bloat: attachment pages, tags and archives

WordPress creates many URLs per piece of content, and most should not be indexed. A single post with a few images and tags can generate a surprising number of addresses:

One WordPress post and the extra URLs it can generate One blog post at the center generates other URLs. Index these: the post itself, and its category archive if categories are maintained as topic hubs. Usually noindex: each tag archive, the author archive on single-author sites, date archives for the year, month and day, and paginated archive pages beyond page one depending on policy. Redirect or disable: one attachment page per uploaded image on sites created before WordPress 6.4. One post, many URLs What a single WordPress post can create, and what to do with each Blog post /post-name/ Index The post itself Category archive, if a real hub Usually noindex Each tag archive Author archive (single author) Year, month and day archives Paginated archives (your policy) Redirect or disable One attachment page per image (sites created before 6.4) Decisions depend on the site; curated tag hubs can deserve indexing. Use noindex, not robots.txt, so crawlers can see the rule.

Scroll the diagram sideways to see all of it.

Source: Ambeltek diagram based on WordPress's 6.4 attachment page change and Google's noindex documentation.

Attachment pages are the classic WordPress problem. The WordPress core team’s note on changes to attachment pages explains that until 6.4, WordPress created an attachment page for every upload, and that on most sites these pages “don’t add any meaningful information” yet “get indexed by search engines, and sometimes even rank.” Since 6.4, new sites redirect attachment pages to the file. The catch: on existing sites, the wp_attachment_pages_enabled option “is set to 1 on upgrade, so that attachment pages continue to work as is.” An older site that has been updated faithfully can still be generating one thin page per image.

Tag archives are the next biggest source. Most sites add tags on the fly, so each tag archive lists one or two posts with the same excerpts as the category page. Google’s starter guide is clear that duplicate content “is not a violation of our spam policies” but that it is inefficient. Noindex tag archives unless you curate them as real topic pages.

When you do noindex something, use a robots meta tag, not a robots.txt block. Google’s noindex documentation warns that if a page is blocked by robots.txt, “the crawler will never see the noindex rule,” and the page can still appear in results. Our duplicate content guide covers canonicals for the cases where noindex is the wrong tool.

Theme speed and page builders

Your theme sets the ceiling for performance, and plugins lower it. W3Techs reports that Elementor is used by 31.5% of WordPress sites, which shows how many sites are built with page builders that add their own markup, styles and scripts. That is not automatically a problem, but it is where to look first when Core Web Vitals fail.

Google’s thresholds, published on web.dev, are the same on any platform: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads. Google’s page experience documentation confirms that “Core Web Vitals are used by our ranking systems,” though no single page experience signal decides rankings.

On WordPress, the usual culprits are sliders and hero videos above the fold, several plugins each loading their own scripts on every page, unoptimized images without dimensions, and web fonts loaded from multiple sources. Our site speed optimization guide covers fixes in order of impact.

Schema and AI crawlers on WordPress

Schema on WordPress usually comes from your SEO plugin, so audit what it outputs rather than assuming it is right. Run key templates through a schema validator and check three things: that the Organization or Person entity is filled in with real details, that there is one graph rather than duplicates from a theme and a plugin, and that the types match what is on the page. Our guide to structured data for AI search lists which types matter most.

For AI visibility, two WordPress-specific checks are worth doing. First, look at robots.txt: security plugins and hosting firewalls sometimes block AI crawlers such as OAI-SearchBot or PerplexityBot without telling you. Second, confirm that important content is in the HTML, not injected by a JavaScript widget, since many AI crawlers do not render scripts. Bing’s webmaster guidelines list “hiding critical content behind client-side rendering” among the things to avoid, and the same applies to AI crawlers.

Keeping WordPress SEO healthy after launch

WordPress sites drift. Plugins update, editors add tags, and themes change output. A quarterly check keeps the drift in check:

  1. Confirm the visibility setting is still off and the sitemap still returns only indexable URLs.
  2. Check Search Console’s Page indexing report for new attachment, tag or parameter URLs.
  3. Remove plugins you no longer use, and look for any that add front-end scripts site-wide.
  4. Re-test Core Web Vitals on your main templates after any theme or builder update.
  5. Review new tags and merge the ones that duplicate existing categories.

WordPress is a solid platform for SEO when it is configured deliberately, and a source of index bloat when it is not. If you are weighing a rebuild, our Astro SEO write-up shows the alternative, and our web development service builds and cleans up both.

Frequently asked questions

What is SEO for WordPress?

It is the work of configuring a WordPress site so search engines can crawl, index and understand it: correct visibility and permalink settings, one clean sitemap, sensible indexing rules for archives and attachments, a fast theme, and accurate titles, descriptions and schema. Content and links still matter as much as on any other platform.

Does WordPress provide SEO out of the box?

Partly. Since version 5.5, WordPress core generates an XML sitemap at /wp-sitemap.xml, and it has a setting to discourage indexing. It does not give you per-page title and description fields, schema, or control over which archives are indexed. That is why most sites add an SEO plugin.

Which WordPress SEO plugin is best?

There is no single best one. Yoast SEO, Rank Math, AIOSEO and SEOPress are the best-known options, and Bing lists all four as supporting IndexNow. Choose on what you need, such as redirects, schema control or archive settings, and run only one at a time.

Should I noindex tag pages in WordPress?

Usually, unless your tag archives are curated and genuinely useful. Most sites create tags ad hoc, which produces many thin archive pages that repeat post excerpts. Keep categories indexed if they work as real topic hubs, and noindex tags you do not maintain.

What happens to attachment pages in WordPress?

Since WordPress 6.4, new installations redirect attachment pages to the file itself. Sites upgraded from older versions keep attachment pages switched on, because the wp_attachment_pages_enabled option is set to 1 on upgrade. Check this option on any site built before 6.4.

Does the 'Discourage search engines' setting block my site?

No. It adds a noindex, nofollow robots meta tag and disables the core sitemap, but WordPress's own documentation notes it is up to search engines to honor the request. It does not block access, so use real authentication for staging sites.

OK

Olga Kunger

Founder & Lead Strategist, Ambeltek

Olga leads Ambeltek's web development, AI SEO, and GEO work — helping brands rank on Google and get cited by AI engines. More about Olga →

Need a site built to rank and get cited?

Fast, structured websites. Launch tier from $5k, live in about two weeks.