WordPress SEO

TL;DR — WordPress gives you a good foundation for SEO, but it doesn’t finish the job for you. Out of the box it uses ugly ?p=123 URLs, creates a bunch of thin pagesThin content is web content that provides little or no value to users. Google's spam policies name it 'thin content with little or no added value' — and it's about value per page, not word count. you didn’t ask for, and even has a checkbox that can hide your whole site from Google. Fix the permalinks, install one SEO plugin (not two), and clean up the thin pages — that’s most of the battle.

What WordPress SEO actually means

WordPress SEOWordPress SEO is the process of configuring, optimizing, and maintaining a WordPress site so search engines can efficiently crawl, index, and rank it. WordPress gives you a solid foundation, but its defaults — ?p=123 permalinks, attachment pages, thin archives — need cleanup before a site is actually well-optimized. is just doing SEO on a site that happens to run on WordPress. The goal is the same as anywhere else: help search engines crawl, indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., and rank your pages, and help people find them. What’s different is that WordPress has its own default settings and quirks — and a few of them quietly work against you until you change them.

WordPress runs something like 43% of the entire web, so these quirks are worth knowing.

Fix these first

A handful of defaults cause most WordPress SEO problems:

• The “Discourage search engines” checkbox. In Settings → Reading there’s a box that blocks search engines. It’s meant for sites still being built, and it gets left on and forgotten constantly. One checkbox can keep your entire site out of Google. Confirm it’s unchecked on any live site.
• Permalinks. WordPress ships with ?p=123-style URLs. Switch to Settings → Permalinks → Post name so your URLs read like yoursite.com/your-post-title/. Do this before you publish content — changing it later means old links break unless redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. are set up.
• Thin auto-generated pages. WordPress automatically creates pages for every tag, every date, every author, and even your media files (attachment pages). Most of these are thin and add no value. An SEO plugin lets you hide (“noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed.”) them.

Do you need an SEO plugin?

WordPress now does some SEO on its own — it makes a sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. and adds canonical tags. Evidence for this claim WordPress core generates XML sitemaps and outputs canonical link tags for singular content. Scope: WordPress core defaults; plugins and themes can filter or replace output. Confidence: high · Verified: 2026-07-14 WordPress: XML Sitemaps WordPress: rel_canonical But for control over meta descriptionsThe meta description is an HTML head tag — `<meta name=\"description\" content=\"…\">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through., hiding thin pages, adding schema markup, and managing redirects, you’ll want a plugin. The popular ones are Yoast SEO, Rank Math, and All in One SEO. Any of them is fine.

The one rule that really matters: never run two SEO plugins at once. They both try to write the same tags into your page’s <head>, and you end up with duplicate and conflicting information that confuses search engines. Pick one. Evidence for this claim WordPress plugins can hook into wp_head and emit head markup, so overlapping SEO plugins can duplicate output. Scope: WordPress hook mechanics; exact conflicts depend on active plugins and settings. Confidence: high · Verified: 2026-07-14 WordPress: wp_head hook

The thing most people get wrong

“WordPress is bad for SEO” and “WordPress is slow” are myths — when it’s set up properly. A clean install on decent hosting with a lightweight theme and a few sensible plugins competes with anything. The problems people blame on WordPress are almost always cheap hosting, heavy page builders, too many plugins, and giant unoptimized images. Google has never said WordPress ranks better or worse than any other platform; your content and your links decide that.

Want the practitioner’s version — how the core sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. really works, the canonical gotchas, the full duplicate-content list, and WooCommerceWooCommerce SEO is optimizing a WooCommerce store — which runs as a free plugin on WordPress, not as a standalone platform — to rank in organic search. Because you control the whole stack (templates, URLs, plugins, server), the ceiling is high and the ways to misconfigure it are many.? Switch to the Advanced tab.

TL;DR — WordPress is SEO-capable, not SEO-finished. It self-canonicalizes singular posts since version 2.9 and ships a native XML sitemapAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags. since 5.5 — but defaults leave ?p=123 permalinks, attachment pages, date/tag/author archives, feeds, and ?s= search pages all indexable, and the Settings → Reading checkbox can silently block the whole site. The fixes that move the needle: /%postname%/ before publishing, exactly one SEO plugin (the wp_head conflict from two is real), noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed. thin archives rather than disallowing them, and a sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. of canonical indexable URLs only. WordPress 6.4+ disables attachment pages by default on new installs — redirecting to the file itself, not the parent post; existing sites keep them enabled and migrate by hand. Google has never said WordPress is better or worse for SEO than any other CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms.. Evidence for this claim WordPress added core XML sitemaps in 5.5 and attachment-page redirects for new sites in 6.4. Scope: Core version history; existing sites can retain prior attachment behavior. Confidence: high · Verified: 2026-07-14 WordPress 5.5 XML sitemaps WordPress 6.4 attachment pages

WordPress is SEO-capable, not SEO-finished

The honest framing is somewhere between the two marketing claims you usually hear. WordPress is not “SEO-friendly out of the box” in any complete sense — but it also isn’t bad for SEO. It gives you a strong, controllable foundation and then leaves a pile of indexable cruft turned on by default. The whole job is knowing which defaults to change and which auto-generated URLs to suppress.

And to be clear up front: Google has never said WordPress ranks better or worse than any other CMS. As Google’s documentation puts it, “if you’re using a CMS such as WordPress, Wix, or Blogger, it’s likely that your CMS has already made a sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. available to search engines” — the platform is treated like any other. Rankings come from content and links, not from the logo in your admin bar. Evidence for this claim Google says common CMS platforms often generate sitemaps and does not prescribe a CMS-specific ranking advantage. Scope: Google sitemap guidance; absence of a CMS ranking advantage is an editorial inference from platform-neutral requirements. Confidence: medium · Verified: 2026-07-14 Google: Build and submit a sitemap

The defaults that hurt — and why

The “Discourage search engines from indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. this site” checkbox (Settings → Reading) writes a site-wide noindex and a restrictive virtual robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere.. It’s the first thing I check on any WordPress audit, because it’s the single setting that can silently zero out an entire site’s indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. — usually left on from staging.

The ?p=123 default permalink gives no topical signal and isn’t a clean URL. Switch to /%postname%/ — and do it before publishing. On an established site, changing the permalink structure means URL changes; WordPress will auto-301 the old numeric URLs for standard post types, but custom post types and pages don’t always redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. cleanly, so test. I’d avoid baking the category into the permalink (/%category%/%postname%/): the day you reorganize taxonomy you trigger a mass URL change and throw away ranking history for no proportional benefit.

Attachment pages are the WordPress-specific gotcha people forget. Every media upload historically spawned a standalone URL containing just the file and some auto-metadata — thin pagesThin content is web content that provides little or no value to users. Google's spam policies name it 'thin content with little or no added value' — and it's about value per page, not word count. that can cannibalize the real ones. WordPress 6.4 changed the default so new installs disable attachment pages entirely — a request to one now redirects straight to the file itself, not the parent post. Existing (upgraded) sites keep attachment pages enabled; there’s no Settings-screen toggle for this, only wp option set wp_attachment_pages_enabled 0 via WP-CLI or editing the option directly on wp-admin/options.php. In practice most site owners never touch that option and instead handle it the plugin way: noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed. the attachment page, or better, redirect it to the parent post via your SEO plugin. Don’t assume an older site inherited the WordPress 6.4 default; it didn’t.

Archives, feeds, and search pages. By default WordPress generates indexable category archives, tag archives, date archives, author archives, paginated archive pages (?page=2), feed URLs (/feed/), attachment pages, and internal search result pages (/page=search, i.e. ?s=). That’s the canonical list of WordPress duplicate-content sources, and almost none of it was a decision you made.

Duplicate content WordPress creates on its own

Worth stating plainly because it surprises people: WordPress manufactures structural duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. by default. The recurring sources:

The fix is almost never to panic about a penalty — Google consolidates duplicates to a canonical rather than penalizing structural duplication. The fix is to noindex the thin stuff and keep the sitemap clean. And a critical distinction: noindex ≠ no-crawl. A noindexed page must stay crawlable so Google can actually read the noindex. If you disallow it in robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. instead, Google can’t see the directive — which is why you noindex thin archives rather than blocking them.

The XML sitemap: core vs. plugin

WordPress 5.5 (August 2020) added a native XML sitemapAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags. at /wp-sitemap.xml. It’s real, but barebones. It dumps in all public post types, all public taxonomies, and author archives — meaning it happily lists exactly the thin pages you want out of the index. It has no image-sitemap support and limited control. So in practice most sites use the sitemap from Yoast or Rank Math instead, which lets you include/exclude specific post types and taxonomies and keep the file to canonical, indexable URLs. Yoast disables the core sitemap and replaces it; that’s expected.

Two things the sitemap won’t do for you: Google ignores <priority> and <changefreq> entirely (per Google’s own docs), and WordPress does not submit the sitemap to Google for you — you submit it in Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. and Bing Webmaster Tools, and you can list it via a Sitemap: directive in robots.txt for passive discovery. The 50,000-URL / 50MB limit from the spec still applies; split into a sitemap indexA sitemap index is a sitemap of sitemaps — a single file that lists your other sitemap files instead of listing URLs directly. It's how large sites stay under the 50,000-URL / 50MB-per-sitemap limit while submitting just one file. past that.

Canonical handling: core, plugin, and the conflict trap

Core has output rel=canonical via rel_canonical() since WordPress 2.9 (2009) — singular posts and pages self-canonicalize. WordPress 4.6 didn’t add the tag; it refactored the function to use the filterable wp_get_canonical_url(), which is what people usually mean when they say “canonical since 4.6.” That’s a good baseline, but core doesn’t handle custom post types consistently across themes, doesn’t add canonicals on 404s, and doesn’t resolve URL-variation duplicates (?utm_source=, www vs. non-wwwWWW vs. non-WWW is the choice between serving a site from www.example.com (the www subdomain) or example.com (the bare/apex/root domain). Both point to the same content, so it's a canonicalization and consistency decision, not a ranking factor., trailing slashes) on its own. SEO plugins replace the core output with more comprehensive handling: custom post type canonicals, self-referential paginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does. canonicals (not pointing page 2+ at page 1 — a mistake that deindexes your deeper pages), cross-domain canonical for syndication, and per-page overrides.

Here’s the trap that ties the whole plugin question together: the canonical tagA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. set by your SEO plugin is the authoritative signal — but if your theme also injects a title tagThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim. or its own SEO meta, you get a conflict. Some theme frameworks (Genesis, Thesis) emit their own SEO tags. When you activate an SEO plugin, disable the theme-level SEO, and inspect the rendered <head> to confirm exactly one canonical, one title, one meta descriptionThe meta description is an HTML head tag — `<meta name=\"description\" content=\"…\">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through..

One SEO plugin. Never two.

This deserves its own heading because it’s the most common self-inflicted WordPress SEO wound. Never run two SEO plugins simultaneously. Yoast, Rank Math, and AIOSEO all hook into wp_head() to write the title, meta description, canonical, Open Graph/Twitter tags, robots meta, and JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal.. Run two and they both fire — duplicate meta descriptions, duplicate (and contradictory) canonical tags, conflicting Open Graph, and conflicting sitemaps. Search Console will flag the duplicate metadata. Pick one and fully uninstall the other (deactivating leaves database entries behind).

As for which one — they all cover the core tasks; the choice is use-case and budget:

• Yoast SEO — the largest install base, the familiar traffic-light scoring, great for beginners and content teams that want a guided workflow. (WooCommerce schema is a paid add-on.)
• Rank Math — the most generous free tier: unlimited focus keywords, redirect manager, 404 monitoring, GSC + GA4 integration, and a strong schema builder (16+ types free). My pick for developers and power users.
• All in One SEO (AIOSEO) — strong WooCommerce integration, internal-link assistant, good local SEO. Suits agencies and large stores.

One caution on Yoast’s green lights: a higher Yoast score doesn’t mean better rankings. It’s a heuristic for basic on-page formatting — keyword presence, title length, readability proxies. A red-light post routinely outranks an all-green one. Content quality, intent match, authority, and links matter far more.

Schema: what WordPress does and doesn’t output

Core WordPress outputs essentially nothing useful for rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. — clean HTML Google can parse, but no JSON-LD. As Google notes, “if you use a CMS, such as Wix, WordPress, or Shopify, you might not be able to edit your HTML directly… you may be able to install a plugin that allows you to specify structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding..” That’s the path:

• Yoast auto-adds Organization/Person, WebSite (with SearchAction), WebPage, BreadcrumbList, and Article schemaArticle schema (Article, NewsArticle, or BlogPosting) is structured data marking up a written piece's headline, author, and dates — Google labels it the \"Article rich result,\" but it's a better-displayed existing result, not a distinct new card, and it isn't required for Top Stories or Discover eligibility. in JSON-LD.
• Rank Math adds those plus 16+ schema types in the free tier (FAQ, HowTo, Product, Review, Event…) and a builder for custom types.
• WooCommerce alone outputs basic Open GraphOpen Graph (OG) tags are `<meta>` elements in a page's head, defined by the Open Graph protocol (ogp.me, created by Facebook), that describe a page as a shareable object — its title, description, image, URL, and type. They control how a link preview card looks when the page is shared on Facebook, LinkedIn, Slack, Discord, WhatsApp, and iMessage. They are not a direct Google ranking factor, though Google reads og:title, og:image, and og:site_name as inputs to how a result appears. product metadata but no Product JSON-LD — you need Yoast WooCommerce SEOWooCommerce SEO is optimizing a WooCommerce store — which runs as a free plugin on WordPress, not as a standalone platform — to rank in organic search. Because you control the whole stack (templates, URLs, plugins, server), the ceiling is high and the ways to misconfigure it are many. (paid) or Rank Math Pro for full Product schema with price, availability, and review aggregate.

WooCommerce, briefly

WooCommerce stacks more SEO surface on top of standard WordPress. The recurring issues: the /product/ and /product-category/ URL bases (removable, with redirects on existing sites), product variations creating near-duplicates, and — the big one — faceted navigationFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals. generating thousands of thin filter-combination URLs. Handle facets the same way you’d handle them anywhere: ideally JS-based filtering with no URL change, otherwise rel=canonical to the base category and/or noindex, follow on filter pages (with crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor. allowed so the directive is seen). Shop and category pagination wants self-referential canonicals, and Google deprecated rel=prev/next back in 2019 — harmless if present, but don’t rely on it. Faceted nav has its own deep treatment in the Ecommerce SEOEcommerce SEO is the practice of optimizing an online store so its product and category pages rank in organic search and attract purchase-intent visitors. It uses the same Google algorithm as any other site, but compounds the usual SEO work with commerce-specific challenges like faceted navigation, product variants, and platform-imposed URLs. pillar.

robots.txt and Core Web Vitals — two quick notes

WordPress serves a virtual robots.txt (it’s not a file on disk) defaulting to disallowing /wp-admin/ while allowing admin-ajax.php. Drop a physical file at the root and it overrides the virtual one entirely; SEO plugins let you edit the virtual version from the dashboard. The classic mistake is disallowing /wp-content/, which blocks CSS/JS/images and breaks renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. — don’t.

On performance: the “WordPress is slow” complaint is a configuration problem, not a core problem. LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good. issues trace mostly to TTFBTime to First Byte — the time from the start of a request to when the first byte of the response arrives. It's a diagnostic metric (not a Core Web Vital) and a major input to FCP and LCP; ≤0.8 s is good. (cheap shared hosting, no opcode cache) and unoptimized hero images; INPInteraction to Next Paint — the input-to-paint latency at the 75th percentile of a page's interactions. ≤200 ms is good. issues to JavaScript bloat from page builders (Elementor, Divi); CLSCumulative Layout Shift — a unitless score for unexpected visual movement, taken from the largest burst (session window) of layout shifts, not the lifetime sum. ≤0.1 is good. to images without dimensions and web fonts without font-display: swap. Lightweight themes (GeneratePress, Kadence, Astra) plus a caching plugin, a CDN, and modern image formatsThe file encoding used to store an image (JPEG, PNG, WebP, AVIF, SVG, GIF) — it drives file size and Core Web Vitals, but carries no direct ranking weight. get a well-built WordPress site through Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. comfortably. The detail lives in the Web Performance cluster.

TIP Crawl the combined WordPress theme and plugin output

This raw-HTML baseline catches repeatable template findings and states what it did not evaluate. Rendered JavaScript and Search Console remain separate checks.

Run a scoped WordPress crawl with my free Scout Site Audit Free Free

1. Crawl representative posts, pages, archives, and special routes.
2. Group metadata, canonical, indexability, and heading findings by template owner.
3. Fix the theme or plugin source, rerun the same scope, and verify priority URLs in Search Console.

Tap to enlarge

The report scores 82 out of 100, crawls 24 of 31 discovered URLs, reports two missing-title warnings, and says rendered JavaScript and AI checks were not evaluated.

AI summary

A condensed take on the Advanced version:

• WordPress is SEO-capable, not SEO-finished. Strong, controllable foundation; defaults leave indexable cruft turned on. Google has never said WordPress ranks better or worse than any other CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. — content and links decide that.
• Fix-first defaults: the Settings → Reading “discourage search engines” checkbox (can silently noindex the whole site); ?p=123 → /%postname%/ before publishing; suppress thin auto-generated pages.
• WordPress-made duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.: category/tag/date/author archives, paginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does. (?page=2), feeds (/feed/), attachment pages, and internal search (?s= / /page=search). NoindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed. the thin ones — noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed. ≠ no-crawl, so keep them crawlable rather than blocking in robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere..
• Attachment pages: WordPress 6.4+ disables them by default on new installs, redirecting straight to the file (not the parent post); existing sites keep them enabled and must migrate manually.
• SitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing.: native since 5.5 at /wp-sitemap.xml but barebones (includes thin taxonomies/authors); most sites use a plugin sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. for control. WordPress doesn’t submit it to Google for you, and Google ignores <priority>/<changefreq>.
• Canonicals: core has self-canonicalized singular posts since 2.9 (4.6 added the filterable wp_get_canonical_url(), not the tag itself); plugins handle CPTs, paginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does., and URL variations. The plugin’s canonical is authoritative — a theme that also injects a title/meta creates a conflict.
• One SEO plugin, never two: both hook wp_head and produce duplicate/conflicting metadata. Yoast (beginners), Rank Math (best free tier), AIOSEO (agencies/Woo).
• “WordPress is slow” is a myth — it’s hosting, page builders, plugin bloat, and unoptimized images, not core.

Official documentation

Primary-source guidance relevant to running SEO on WordPress.

Google

• Build and submit a sitemap — notes that a CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. like WordPress likely already exposes a sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing.; the 50,000-URL / 50MB limits; and that Google ignores <priority>/<changefreq>.
• Intro to structured data — the “use a plugin to specify structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding.” guidance for CMS users.
• Block indexing with noindex — how noindex works, and why a noindexed page must remain crawlable.
• Site Kit is now available for all — Google’s official WordPress plugin surfacing Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. and Analytics data in the dashboard.

Bing / Microsoft

• Submitting sitemaps to Bing — submit via Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility., or expose the sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. through a Sitemap: directive in robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere..

WordPress core

• New XML Sitemaps functionality in WordPress 5.5 — what the native /wp-sitemap.xml covers.
• wp_head hook reference — the action SEO plugins hook to output metadata (and where two plugins collide).

Quotes from the source

On-the-record statements from Google relevant to running WordPress.

Google — sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. on a CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms.

• “If you’re using a CMS such as WordPress, Wix, or Blogger, it’s likely that your CMS has already made a sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. available to search engines.” — Google Search Central docs. Source
• “Include the URLs in your sitemap that you want to see in Google’s search results.” — Google Search Central docs. Source
• “Google ignores <priority> and <changefreq> tags in XML sitemapsAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags..” — Google Search Central docs. Source

Google — structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. on a CMS

• “If you use a CMS, such as Wix, WordPress, or Shopify, you might not be able to edit your HTML directly. Instead, your CMS may have a search engine settings page, or you may be able to install a plugin that allows you to specify structured data.” — Google Search Central docs. Source

Google — Site Kit for WordPress

• “Site Kit is Google’s official WordPress plugin — it gives you insights on how people find and use your site… with data from multiple Google tools.” — Google Search Central blog. Source

WordPress SEO setup checklist

Run this on any WordPress site, new or inherited:

• Settings → Reading: “Discourage search engines” is unchecked on the live site.
• Settings → Permalinks: set to Post name (/%postname%/) — ideally before any content is published; if changing on a live site, verify old URLs 301.
• Exactly one SEO plugin installed; any theme-level SEO meta disabled.
• Rendered <head> inspected: exactly one title, one meta descriptionThe meta description is an HTML head tag — `<meta name=\"description\" content=\"…\">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through., one canonical (no theme + plugin conflict).
• Thin archives noindexed, not disallowed — tag, date, and (single-author) author archives; internal search (?s=); feeds as needed.
• Attachment pages redirected to their parent post via your SEO plugin (don’t assume an older install inherited the WP 6.4+ default — that default only applies to new installs, and redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. to the file itself, not the parent post).
• SitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. contains only canonical, indexable URLs (plugin sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., not the barebones core one, on production).
• Sitemap submitted in Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. and Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility.; a Sitemap: line added to robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere..
• robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. does not disallow /wp-content/ (would break renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM.).
• PaginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does. uses self-referential canonicals (not all pointing at page 1).
• WooCommerceWooCommerce SEO is optimizing a WooCommerce store — which runs as a free plugin on WordPress, not as a standalone platform — to rank in organic search. Because you control the whole stack (templates, URLs, plugins, server), the ceiling is high and the ways to misconfigure it are many. (if present): Product schemaProduct schema (schema.org/Product) is structured data that tells search engines a page's product name, price, availability, and reviews so it can appear in Shopping-style rich results. It's separate from a Google Merchant Center feed, though Google reconciles the two. plugin active; faceted-nav filter URLs controlled via canonical/noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed..
• Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. checked: lightweight theme, caching plugin, optimized images, image dimensions set.

The core → theme → plugin → content framework

Assign each SEO output to one owner: WordPress core controls routing and baseline behavior; the theme renders templates; one SEO plugin owns metadata, canonicals, sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., and schema; editors own page content and exceptions. Most WordPress SEOWordPress SEO is the process of configuring, optimizing, and maintaining a WordPress site so search engines can efficiently crawl, index, and rank it. WordPress gives you a solid foundation, but its defaults — ?p=123 permalinks, attachment pages, thin archives — need cleanup before a site is actually well-optimized. bugs are ownership conflicts. Fix the earliest owner and validate the combined public output.

WordPress SEO cheat sheet

Default settings to change first

Duplicate-content sources WordPress makes on its own

• Category / tag / date / author archives
• PaginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does. (?page=2)
• Feed URLs (/feed/)
• Attachment pages
• Internal search results (?s= / /page=search)

SEO plugin one-liners

• Yoast — biggest install base; beginner-friendly; Woo schema is paid.
• Rank Math — best free tier; 16+ schema typesSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor.; redirects + 404s free.
• AIOSEO — agency/WooCommerceWooCommerce SEO is optimizing a WooCommerce store — which runs as a free plugin on WordPress, not as a standalone platform — to rank in organic search. Because you control the whole stack (templates, URLs, plugins, server), the ceiling is high and the ways to misconfigure it are many.-leaning; internal-link assistant.
• Rule: one plugin only — two both hook wp_head() → duplicate metadata.

Version facts worth remembering

• 2.9 — core canonical (rel_canonical()); singular posts self-canonicalize. 4.6 refactored it into the filterable wp_get_canonical_url() — it didn’t add the tag.
• 5.5 — native XML sitemapAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags. at /wp-sitemap.xml (barebones).
• 6.4 — attachment pages disabled by default on new installs, redirecting straight to the file itself (not the parent post); existing installs keep them on.

Gotchas

• The plugin’s canonical is authoritative — a theme injecting its own title/meta conflicts with it.
• noindex ≠ Disallow: a blocked page can’t have its noindex read.
• Don’t disallow /wp-content/ (breaks CSS/JS/image renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM.).
• A higher Yoast score ≠ better rankings.

Sample WordPress template output

Put representative posts, pages, categories, tags, authors, media, and search URLs in urls.txt:

while IFS= read -r url; do
  html=$(mktemp); status=$(curl -sSL -o "$html" -w '%{http_code}' "$url")
  titles=$(grep -Eio '<title>[^<]*</title>' "$html" | wc -l | tr -d ' ')
  canonicals=$(grep -Eio '<link[^>]+rel=["'"']canonical["'"'][^>]*>' "$html" | wc -l | tr -d ' ')
  robots=$(grep -Eio '<meta[^>]+name=["'"']robots["'"'][^>]*>' "$html" | head -1)
  printf '%s\t%s\ttitles=%s\tcanonicals=%s\t%s\n' "$status" "$url" "$titles" "$canonicals" "$robots"
  rm -f "$html"
done < urls.txt

WordPress SEO mistakes to avoid

• Running multiple SEO plugins or schema systems with overlapping ownership.
• Changing permalink structure on a live site without a complete redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. map.
• IndexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. every date, tag, author, attachment, search, and thin archive by default.
• Editing theme files directly instead of using maintainable child-theme or plugin ownership.
• Stacking cache and optimization plugins without testing their combined HTML and performance effects.

Common WordPress SEO issues

Pages contain duplicate canonicals or schema

Cause: the theme and multiple plugins emit the same element. Fix: identify one owner and disable overlapping output, then purge caches.

Search visibility disappears after launch

Cause: the production site retained the “Discourage search engines” setting, a sitewide plugin directive, or staging access rule. Fix: restore intended visibility and verify live directives across templates.

Archives or attachment URLs create duplicate inventory

Cause: default/generated routes are public without a content purpose. Fix: choose which archives deserve indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., configure the SEO plugin consistently, and update sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing./internal-link behavior.

Tools for WordPress SEO

• SEO plugins (pick one): Yoast SEO, Rank Math, or All in One SEO — metadata, noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed. control, sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., schema, redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't..
• Google Site Kit — Google’s official plugin; Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. + Analytics + PageSpeed data inside the WordPress dashboard.
• Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. / Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. — submit your sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., watch indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. and duplicate-metadata warnings, inspect individual URLs.
• CachingCaching stores a copy of a page or resource — in a browser, a CDN edge node, or a search crawler's own cache — so it can be served again without regenerating or re-downloading it. It isn't a direct ranking factor, but it feeds page speed and crawl efficiency.: WP Rocket, W3 Total Cache, or LiteSpeed Cache — server-side caching to fix TTFBTime to First Byte — the time from the start of a request to when the first byte of the response arrives. It's a diagnostic metric (not a Core Web Vital) and a major input to FCP and LCP; ≤0.8 s is good.-driven LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good..
• Image optimization: WebP/AVIF conversion + lazy loadingLazy loading defers loading of off-screen or non-critical resources — usually images and iframes — until they're about to enter the viewport. The native way to do it is the loading=\"lazy\" HTML attribute, which needs no JavaScript. (most caching plugins or a dedicated image plugin) to cut LCPLargest Contentful Paint — render time of the largest visible image or text block, relative to when the page started loading. ≤2.5 s (at the 75th percentile) is good. image weight.
• Lightweight themes: GeneratePress, Kadence, or Astra — built for Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data. rather than page-builder bloat.
• CrawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. / site audit: Ahrefs Site Audit or Screaming Frog SEO Spider — surface the thin archives, attachment pages, redirect chainsA → B → C instead of A → C. Each hop loses link equity and adds latency., and duplicate canonicals a WordPress site accumulates.
• Multilingual (if needed): Polylang, WPML, or TranslatePress for translated content and hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. injection.

Validation tests

Test an SEO plugin or theme change

Test to run — purge caches and inspect raw output across posts, pages, archives, and special routes. Expected result — each template has one intended title, canonical, robots directive, and coherent schema graph. Failure interpretation — another owner or cached layer still conflicts. Monitoring window — immediate. Rollback trigger — revert if output disappears or duplicates across a template.

Test a permalink or migration change

Test to run — trace old URLs and crawl new internal linksAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them./sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing.. Expected result — direct redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. reach relevant successful canonical URLsHow search engines pick one canonical URL among duplicates and consolidate signals onto it. and discovery uses new routes. Failure interpretation — map or generated links are incomplete. Monitoring window — immediate technically. Rollback trigger — pause if high-value routes 404, loop, or redirect irrelevantly.

Prompts for WordPress SEO work

Classify this WordPress crawl by post, page, category, tag, author, date, attachment, search, paginationPagination splits a large set of content — product listings, blog archives, search results — across multiple sequentially numbered URLs. For SEO, each paginated page should be crawlable, indexable, and self-canonical; Google no longer uses rel=prev/next, but Bing still does., and parameter routes. Recommend which templates should be indexedStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., consolidated, redirected, or excluded, and state the evidence required for each decision.

Review this plugin/theme inventory and sampled HTML. Identify which component owns titles, canonicals, robots directives, sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., breadcrumbsBreadcrumbs are a secondary navigation trail (Home > Category > Page) that shows where a page sits in a site's hierarchy. They create internal links that pass PageRank, and when marked up with BreadcrumbList structured data they can drive the path Google shows in desktop search results., and schema. Flag overlaps and propose a single-owner configuration with validation and rollback steps.

Test yourself: WordPress SEO

Five quick questions on getting WordPress configured for search. Pick an answer for each, then check.

Resources worth your time

My related writing

• Canonicalization: A Beginner’s Guide — how search engines pick a canonical and consolidate signals (the backbone of WordPress duplicate-content cleanup).
• The Beginner’s Guide to PageSpeed (advanced PageSpeed guide) — the performance side, directly relevant to WordPress Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data..
• Redirects for SEO: A Complete Guide — the redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. mechanics behind attachment-page and permalink migrations.
• The Ahrefs Site Audit Study — data on how widespread technical issues (including the duplicate-content patterns WordPress creates) really are.

My speaking

• How Search Works (SlideShare) — my crawl → render → indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. → serve walkthrough, the model behind every “should this WordPress page be indexed?” decision. (Standing disclaimer applies: “This is my understanding of systems… not going to be 100% complete or accurate.”)

From around the industry

• The WordPress SEO Guide (Joshua Hardwick, Ahrefs) — the practical 20-tip setup companion to this more technical treatment.
• WordPress SEO: The Definitive Guide (WPBeginner) — the comprehensive beginner checklist with the largest authority in this space.
• New XML Sitemaps Functionality in WordPress 5.5 (WordPress core team) — the primary source on what the native sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. covers.
• wp_head hook reference (WordPress Developer Resources) — the action that SEO plugins (and conflicting themes) hook to inject metadata.
• WordPress SEO Myths, Busted (Search Engine Journal) — covers the “WordPress is slow / bad for SEO” myths in depth.

WordPress SEO

WordPress SEO is the process of configuring, optimizing, and maintaining a WordPress site so search engines can efficiently crawl, index, and rank it. WordPress gives you a solid foundation, but its defaults — ?p=123 permalinks, attachment pages, thin archives — need cleanup before a site is actually well-optimized.

Related: CMS, Platform SEO

WordPress SEO

WordPress SEO is the practice of configuring and maintaining a WordPress-powered site so that search engines can crawl, indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., and rank its pages — and so people can find that content in organic search. WordPress powers roughly 43% of all websites, so platform-specific SEO knowledge is highly practical.

The work spans three layers: technical configuration (permalinks, sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere., canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content.), on-page content (titles, meta descriptionsThe meta description is an HTML head tag — `<meta name=\"description\" content=\"…\">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through., structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding.), and performance (Core Web VitalsGoogle's three real-user UX metrics — LCP (loading), INP (responsiveness), and CLS (visual stability) — used by Google's ranking systems, with no official weight attached, measured on field data., cachingCaching stores a copy of a page or resource — in a browser, a CDN edge node, or a search crawler's own cache — so it can be served again without regenerating or re-downloading it. It isn't a direct ranking factor, but it feeds page speed and crawl efficiency., image optimization). WordPress handles some of this automatically — it self-canonicalizes singular posts since version 2.9, ships a native XML sitemapAn XML sitemap is a UTF-8 file listing the canonical URLs on your site (with optional lastmod) so search engines can discover and prioritize them. It's a discovery and diagnostic aid, not a guarantee of indexing — and Google ignores its priority and changefreq tags. since 5.5, and redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. www/non-www — but its defaults also leave a lot indexable that shouldn’t be.

The single most important thing to understand: WordPress is SEO-capable, not SEO-finished out of the box. A default install ships ?p=123 permalinks, generates attachment pages, date archives, tag archives, author pages, feeds, and indexable internal search results — and a single “Discourage search engines” checkbox in Settings → Reading can silently block the entire site. Most sites add one (and only one) SEO plugin — Yoast, Rank Math, or All in One SEO — to control metadata, noindexNoindex is a directive that tells search engines to keep a page out of their index, so it won't appear in search results. It works only on pages a crawler can actually fetch — a page blocked in robots.txt can never be noindexed. thin pages, manage canonicals and redirects, and generate a leaner sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing.. Google has never said WordPress ranks better or worse than any other CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms.; rankings come from content and links, not the platform.

Related: CMS, Platform SEO

Changelog