Guide WordPress SEO
A SEO technique practitioner's guide to WordPress — the par défaut settings que hurt vous, how the core sitemap and canonical handling en réalité fonctionner, pourquoi vous run exactly un SEO plugin, and the duplicate-content sources WordPress creates on its propre.
Langues
WordPress is SEO-capable, pas SEO-finished. It self-canonicalizes posts since version 2,9 and ships a native XML sitemap since 5,5 — but its defaults aussi leave ?p=123 permalinks, attachment pages, date/tag/author archives, feeds, and internal résultats de recherche tout indexable, and a unique Settings → Reading checkbox peut silently block the whole site. The fixes que en réalité matter: définir /%postname%/ avant publishing, run exactly un SEO plugin (Yoast, Rank Math, or AIOSEO — jamais two, the wp_head conflict produces duplicate metadata), noindex thin archives au lieu de disallowing les, and garder le sitemap to canonical indexable URLs seulement. WordPress 6,4+ disables attachment pages on nouveau installs by par défaut — redirecting straight to the fichier, pas the parent post — but existing sites garder les on and doit migrate manually. Google has jamais said WordPress ranks meilleur or worse que quelconque autre CMS — content and liens decide que, pas the platform.
TL;DR — WordPress donne vous a bon foundation pour le SEO, but it doesn’t finish the job pour vous. Out of the box it uses ugly
?p=123URLs, creates a bunch of thin pages vous didn’t demander pour, and même has a checkbox que peut hide votre whole site from Google. Fix the permalinks, install un SEO plugin (pas two), and clean up the thin pages — that’s la plupart of the battle.
Ce que WordPress SEO en réalité signifie
WordPress SEO is simplement doing SEO on a site que se produit to run on WordPress. The goal is the même as anywhere sinon: aider moteur de recherches explorer, index, and rank votre pages, and aider personnes trouver les. What’s différent is que WordPress has its propre par défaut settings and quirks — and a few of les quietly fonctionner contre vous jusqu’à vous modifier les.
WordPress runs something comme 43% of the entier web, so ces quirks are worth knowing.
Fix ces premier
A handful of defaults causer la plupart WordPress SEO problems:
- The “Discourage search engines” checkbox. In Settings → Reading there’s a box que blocks moteur de recherches. It’s meant pour sites encore being construit, and it obtient left on and forgotten constantly. Un checkbox peut garder votre entier site out of Google. Confirmer it’s unchecked on quelconque live site.
- Permalinks. WordPress ships with
?p=123-style URLs. Switch to Settings → Permalinks → Post nom so votre URLs lire commeyoursite.com/your-post-title/. Do ce avant vous publish content — modification it plus tard signifie old liens break unless redirections are définir up. - Thin auto-generated pages. WordPress automatically creates pages pour every tag, every date, every author, and même votre media fichiers (attachment pages). La plupart of ces are thin and ajouter aucun valeur. An SEO plugin lets vous hide (“noindex”) les.
Do vous besoin an SEO plugin?
WordPress now fait some SEO on its propre — it rend a sitemap 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: WordPress: XML Sitemaps WordPress: rel_canonical But pour contrôler over meta descriptions, hiding thin pages, ajout schema markup, and managing redirections, you’ll vouloir a plugin. The popular ones are Yoast SEO, Rank Math, and Tout in Un SEO. Quelconque of les is fine.
The un rule que really matters: jamais run two SEO plugins at une fois. Ils les deux
essayer to écrire the même tags into votre page’s <head>, and vous fin up with duplicate
and conflicting information que confuses moteur de recherches. Pick un. 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: WordPress: wp_head hook
The chose la plupart personnes obtenir incorrect
“WordPress is bad for SEO” and “WordPress is slow” are myths — quand it’s définir up correctement. A clean install on decent hosting with a lightweight theme and a few sensible plugins competes with anything. The problems personnes blame on WordPress are almost toujours cheap hosting, heavy page builders, aussi nombreux plugins, and giant unoptimized images. Google has jamais said WordPress ranks meilleur or worse que quelconque autre platform; votre content and votre liens decide que.
Vouloir the practitioner’s version — how the core sitemap really fonctionne, the canonical gotchas, the complet duplicate-content liste, and WooCommerce? Switch to the Avancé tab.
TL;DR — WordPress is SEO-capable, pas SEO-finished. It self-canonicalizes singular posts since version 2,9 and ships a native XML sitemap since 5,5 — but defaults leave
?p=123permalinks, attachment pages, date/tag/author archives, feeds, and?s=search pages tout indexable, and the Settings → Reading checkbox peut silently block the whole site. The fixes que déplacer the needle:/%postname%/avant publishing, exactly un SEO plugin (thewp_headconflict from two is réel), noindex thin archives plutôt que disallowing les, and a sitemap of canonical indexable URLs seulement. WordPress 6,4+ disables attachment pages by par défaut on nouveau installs — redirecting to the fichier itself, pas the parent post; existing sites garder les enabled and migrate by hand. Google has jamais said WordPress is meilleur or worse pour le SEO que quelconque autre CMS. 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: WordPress 5.5 XML sitemaps WordPress 6.4 attachment pages
WordPress is SEO-capable, pas SEO-finished
The honest framing is somewhere entre the two marketing claims vous usually hear. WordPress is pas “SEO-friendly out of the box” in quelconque complet sense — but it aussi isn’t bad pour le SEO. It donne vous a strong, controllable foundation and alors leaves a pile of indexable cruft turned on by par défaut. The whole job is knowing qui defaults to modifier and qui auto-generated URLs to suppress.
And to be clair up front: Google has jamais said WordPress ranks meilleur or worse que quelconque autre CMS. As Google’s documentation puts it, “si you’re en utilisant a CMS tel as WordPress, Wix, or Blogger, it’s probable que votre CMS has déjà made a sitemap disponible to moteur de recherches” — the platform is treated comme quelconque autre. Rankings come from content and liens, pas from the logo in votre 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: Google: Build and submit a sitemap
The defaults que hurt — and pourquoi
The “Discourage search engines from indexing this site” checkbox (Settings →
Reading) writes a site-wide noindex and a restrictive virtual robots.txt. It’s the
premier chose I vérifier on quelconque WordPress audit, parce que it’s the unique setting que peut
silently zero out an entier site’s indexation — usually left on from staging.
The ?p=123 par défaut permalink donne aucun topical signal and isn’t a clean URL.
Switch to /%postname%/ — and do it avant publishing. On an established site,
modification the permalink structure signifie URL changements; WordPress va auto-301 the old
numeric URLs pour standard post types, but custom post types and pages don’t toujours
redirection cleanly, so tester. I’d éviter baking the category into the permalink
(/%category%/%postname%/): the day vous reorganize taxonomy vous trigger a mass URL
modifier and throw away ranking history pour aucun proportional benefit.
Attachment pages are the WordPress-specific gotcha personnes forget. Every media
upload historically spawned a standalone URL containing simplement the fichier and some
auto-metadata — thin pages que peut cannibalize the réel ones.
WordPress 6,4 modifié the par défaut so nouveau installs disable attachment pages
entirely — une requête to un now redirections straight to the fichier itself, pas the
parent post. Existing (upgraded) sites garder attachment pages enabled; there’s aucun
Settings-screen toggle pour ce, seulement wp option set wp_attachment_pages_enabled 0
via WP-CLI or editing the option directement on wp-admin/options.php. En pratique
la plupart site owners jamais touch que option and à la place handle it the plugin façon:
noindex the attachment page, or meilleur, redirection it to the parent post via votre SEO
plugin. Don’t assume an older site inherited the WordPress 6,4 par défaut; it didn’t.
Archives, feeds, and search pages. By par défaut 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 liste of WordPress
duplicate-content sources, and almost none of it was a decision vous made.
Contenu dupliqué WordPress creates on its propre
Worth stating plainly parce que it surprises personnes: WordPress manufactures structural contenu dupliqué by par défaut. The recurring sources:
| Source | Exemple | Typical fix |
|---|---|---|
| Category archives | /category/news/ | Garder, or noindex si thin |
| Tag archives | /tag/wordpress/ | Usually noindex (thin, overlapping) |
| Author archives | /author/admin/ | Noindex on single-author sites |
| Date archives | /2023/04/ | Noindex (almost toujours thin) |
| Pagination | /page/2/ | Self-referential canonical (pas page 1) |
| Feed URLs | /feed/ | Noindex feeds |
| Attachment pages | /photo-of-cat/ | Redirection to parent via SEO plugin (WP 6,4+ redirections nouveau installs to the fichier itself à la place) |
| Résultats de recherche | /?s=keyword | Noindex |
The fix is almost jamais to panic à propos de a penalty — Google consolidates duplicates to
a canonical plutôt que penalizing structural duplication. The fix is to noindex
the thin stuff and garder le sitemap clean. And a critical distinction:
noindex ≠ no-crawl. A noindexed page doit stay crawlable so Google peut en réalité
lire the noindex. Si vous disallow it in robots.txt à la place, Google can’t voir the
directive — qui is pourquoi vous noindex thin archives plutôt que blocking les.
The XML sitemap: core vs. plugin
WordPress 5,5 (August 2020) ajouté a native XML sitemap at /wp-sitemap.xml. It’s
réel, but barebones. It dumps in tout public post types, tout public taxonomies, and
author archives — meaning it happily listes exactly the thin pages vous vouloir out of
the index. It has aucun image-sitemap prise en charge and limited contrôler. So En pratique la plupart
sites utiliser le sitemap from Yoast or Rank Math à la place, qui lets vous inclure/exclude
spécifique post types and taxonomies and garder the fichier to canonical, indexable URLs.
Yoast disables the core sitemap and replaces it; that’s attendu.
Two choses le sitemap won’t do pour vous: Google ignores <priority> and
<changefreq> entirely (per Google’s propre docs), and WordPress ne fait pas submit the
sitemap to Google pour vous — vous submit it in Search Console and Bing Webmaster
Outils, and vous pouvez liste it via a Sitemap: directive in robots.txt pour passive
discovery. The 50 000-URL / 50MB limite from the spec encore s’applique; split into a
sitemap index past que.
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 ajouter the tag; it
refactored the function to utiliser the filterable wp_get_canonical_url(), qui is
ce que personnes usually mean quand ils dire “canonical since 4.6.” That’s a bon baseline,
but core doesn’t handle
custom post types consistently à travers themes, doesn’t ajouter canonicals on 404s, and
doesn’t resolve URL-variation duplicates (?utm_source=, www vs. non-www, trailing
slashes) on its propre. SEO plugins replace the core output with plus comprehensive
handling: custom post type canonicals, self-referential pagination canonicals
(pas pointing page 2+ at page 1 — a mistake que deindexes votre deepar pages),
cross-domain canonical pour syndication, and per-page overrides.
Here’s the trap que ties the whole plugin question ensemble:
the balise canonical définir by votre SEO plugin is the authoritative signal — but si votre
theme aussi injects a title tag or its propre SEO meta, vous obtenir a conflict. Some theme
frameworks (Genesis, Thesis) emit leur propre SEO tags. Quand vous activate an SEO
plugin, disable the theme-level SEO, and inspect the rendered <head> to confirmer
exactly un canonical, un title, un meta description.
Un SEO plugin. Jamais two.
Ce deserves its propre heading parce que it’s the la plupart courant self-inflicted WordPress
SEO wound. Jamais run two SEO plugins simultaneously. Yoast, Rank Math, and AIOSEO
tout hook into wp_head() to écrire the title, meta description, canonical, Ouvrir
Graph/Twitter tags, robots meta, and JSON-LD. Run two and ils les deux fire — duplicate
meta descriptions, duplicate (and contradictory) balise canonicals, conflicting Ouvrir
Graph, and conflicting sitemaps. Search Console va flag the duplicate metadata.
Pick un and entièrement uninstall the autre (deactivating leaves database entries behind).
As pour qui un — ils tout cover the core tasks; the choice is use-case and budget:
- Yoast SEO — the largest install base, the familiar traffic-light scoring, great pour beginners and content teams que vouloir a guided workflow. (WooCommerce schema is a paid add-on.)
- Rank Math — the la plupart generous free tier: unlimited focus keywords, redirection manager, 404 monitoring, GSC + GA4 integration, and a strong schema builder (16+ types free). My pick pour developers and power utilisateurs.
- Tout in Un SEO (AIOSEO) — strong WooCommerce integration, internal-link assistant, bon local SEO. Suits agencies and grand stores.
Un caution on Yoast’s green lights: a plus élevé Yoast score doesn’t mean meilleur rankings. It’s a heuristic pour basic on-page formatting — keyword presence, title length, readability proxies. A red-light post routinely outranks an all-green un. Content quality, intent match, authority, and liens matter far plus.
Schema: ce que WordPress fait and doesn’t output
Core WordPress outputs essentially nothing utile pour résultats enrichis — clean HTML Google peut parse, but aucun JSON-LD. As Google notes, “si vous utiliser a CMS, tel as Wix, WordPress, or Shopify, vous pourrait pas be able to edit votre HTML directement… vous may be able to install a plugin que permet vous to specify données structurées.” That’s the chemin:
- Yoast auto-adds Organization/Person, WebSite (with SearchAction), WebPage, BreadcrumbList, and Article schema in JSON-LD.
- Rank Math adds ceux plus 16+ schema types in the free tier (FAQ, HowTo, Product, Examiner, Event…) and a builder pour custom types.
- WooCommerce alone outputs basic Ouvrir Graph product metadata but aucun Product JSON-LD — vous besoin Yoast WooCommerce SEO (paid) or Rank Math Pro pour complet Product schema with price, availability, and examiner aggregate.
WooCommerce, briefly
WooCommerce stacks plus SEO surface on top of standard WordPress. The recurring
problèmes: the /product/ and /product-category/ URL bases (removable, with redirections
on existing sites), product variations creating near-duplicates, and — the big un —
faceted navigation generating thousands of thin filter-combination URLs. Handle
facets the même façon you’d handle les anywhere: ideally JS-based filtering with aucun URL
modifier, sinon rel=canonical to the base category and/or noindex, follow on
filter pages (with exploration allowed so the directive is seen). Shop and category
pagination veut self-referential canonicals, and Google deprecated rel=prev/next
back in 2019 — harmless si présent, but don’t rely on it. Faceted nav has its propre deep
treatment in the Ecommerce SEO pillar.
robots.txt and Core Web Vitals — two rapide notes
WordPress sert a virtual robots.txt (it’s pas a fichier on disk) defaulting to
disallowing /wp-admin/ pendant que allowing admin-ajax.php. Drop a physical fichier at the
root and it overrides the virtual un entirely; SEO plugins let vous edit the virtual
version from the dashboard. The classic mistake is disallowing /wp-content/, qui
blocks CSS/JS/images and breaks rendering — don’t.
On performances: the “WordPress is slow” complaint is a configuration problem, pas a
core problem. LCP problèmes trace mostly to TTFB (cheap shared hosting, aucun opcode cache)
and unoptimized hero images; INP problèmes to JavaScript bloat from page builders
(Elementor, Divi); CLS to images sans dimensions and web fonts sans
font-display: swap. Lightweight themes (GeneratePress, Kadence, Astra) plus a
mise en cache plugin, a CDN, and modern image formats obtenir a well-built WordPress site
via Core Web Vitals comfortably. The detail lives in the Web Performances cluster.
AI summary
A condensed prendre on the Avancé version:
- WordPress is SEO-capable, pas SEO-finished. Strong, controllable foundation; defaults leave indexable cruft turned on. Google has jamais said WordPress ranks meilleur or worse que quelconque autre CMS — content and liens decide que.
- Fix-first defaults: the Settings → Reading “discourage search engines” checkbox
(peut silently
noindexthe whole site);?p=123→/%postname%/avant publishing; suppress thin auto-generated pages. - WordPress-made contenu dupliqué: category/tag/date/author archives, pagination
(
?page=2), feeds (/feed/), attachment pages, and internal search (?s=//page=search). Noindex the thin ones — noindex ≠ no-crawl, so garder les crawlable plutôt que blocking in robots.txt. - Attachment pages: WordPress 6,4+ disables les by par défaut on nouveau installs, redirecting straight to the fichier (pas the parent post); existing sites garder les enabled and doit migrate manually.
- Sitemap: native since 5,5 at
/wp-sitemap.xmlbut barebones (inclut thin taxonomies/authors); la plupart sites utiliser a plugin sitemap pour contrôler. WordPress doesn’t submit it to Google pour vous, and Google ignores<priority>/<changefreq>. - Canonicals: core has self-canonicalized singular posts since 2,9 (4,6 ajouté
the filterable
wp_get_canonical_url(), pas the tag itself); plugins handle CPTs, pagination, and URL variations. The plugin’s canonical is authoritative — a theme que aussi injects a title/meta creates a conflict. - Un SEO plugin, jamais two: les deux hook
wp_headand produce duplicate/conflicting metadata. Yoast (beginners), Rank Math (meilleur free tier), AIOSEO (agencies/Woo). - “WordPress is slow” is a myth — it’s hosting, page builders, plugin bloat, and unoptimized images, pas core.
Documentation officielle
Primary-source guidance relevant to running SEO on WordPress.
- Construire and submit a sitemap — notes que a CMS comme WordPress probable déjà exposes a sitemap; the 50 000-URL / 50MB limites; and que Google ignores
<priority>/<changefreq>. - Intro to données structurées — the “use a plugin to specify structured data” guidance pour CMS utilisateurs.
- Block indexation with noindex — how
noindexfonctionne, and pourquoi a noindexed page doit remain crawlable. - Site Kit is now disponible pour tout — Google’s official WordPress plugin surfacing Search Console and Analytics données in the dashboard.
Bing / Microsoft
- Submitting sitemaps to Bing — submit via Bing Webmaster Outils, or expose le sitemap via a
Sitemap:directive in robots.txt.
WordPress core
- Nouveau XML Sitemaps functionality in WordPress 5,5 — ce que the native
/wp-sitemap.xmlcovers. wp_headhook référence — the action SEO plugins hook to output metadata (and où two plugins collide).
Quotes from the source
On-the-record statements from Google relevant to running WordPress.
Google — sitemaps on a CMS
- “If you’re using a CMS such as WordPress, Wix, or Blogger, it’s likely that your CMS has already made a sitemap available to search engines.” — Recherche Google Central docs. Source
- “Include the URLs in your sitemap that you want to see in Google’s search results.” — Recherche Google Central docs. Source
- “Google ignores
<priority>and<changefreq>tags in XML sitemaps.” — Recherche Google Central docs. Source
Google — données structurées 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.” — Recherche Google Central docs. Source
Google — Site Kit pour 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.” — Recherche Google Central blog. Source
WordPress SEO setup checklist
Run ce on quelconque WordPress site, nouveau or inherited:
- Settings → Reading: “Discourage search engines” is unchecked on the live site.
- Settings → Permalinks: définir to Post nom (
/%postname%/) — ideally avant quelconque content is publié; si modification on a live site, vérifier old URLs 301. - Exactly un SEO plugin installed; quelconque theme-level SEO meta disabled.
- Rendered
<head>inspected: exactly un title, un meta description, un canonical (aucun theme + plugin conflict). - Thin archives noindexed, pas disallowed — tag, date, and (single-author)
author archives; internal search (
?s=); feeds as nécessaire. - Attachment pages redirigé to leur parent post via votre SEO plugin (don’t assume an older install inherited the WP 6,4+ par défaut — que par défaut seulement s’applique to nouveau installs, and redirections to the fichier itself, pas the parent post).
- Sitemap contient seulement canonical, indexable URLs (plugin sitemap, pas the barebones core un, on production).
- Sitemap submitted in Recherche Google Console and Bing Webmaster Outils; a
Sitemap:line ajouté to robots.txt. - robots.txt fait pas disallow
/wp-content/(voudrait break rendering). - Pagination uses self-referential canonicals (pas tout pointing at page 1).
- WooCommerce (si présent): Product schema plugin active; faceted-nav filter URLs controlled via canonical/noindex.
- Core Web Vitals vérifié: lightweight theme, mise en cache plugin, optimized images, image dimensions définir.
The core → theme → plugin → content framework
Assign chaque SEO output to un owner: WordPress core contrôle routing and baseline behavior; the theme renders templates; un SEO plugin owns metadata, canonicals, sitemaps, and schema; editors propre page content and exceptions. La plupart WordPress SEO bugs are ownership conflicts. Fix the earliest owner and validate the combined public output.
WordPress SEO cheat sheet
Par défaut settings to modifier premier
| Setting | Par défaut | Modifier to |
|---|---|---|
| Search visibility (Settings → Reading) | varies | Unchecked on live sites |
| Permalinks | ?p=123 | /%postname%/ |
| Attachment pages | standalone URLs (old installs) | Redirection to parent post |
| Thin archives (tag/date/author) | indexable | noindex (garder crawlable) |
Internal search (?s=) | indexable | noindex |
Duplicate-content sources WordPress rend on its propre
- Category / tag / date / author archives
- Pagination (
?page=2) - Feed URLs (
/feed/) - Attachment pages
- Internal résultats de recherche (
?s=//page=search)
SEO plugin one-liners
- Yoast — biggest install base; beginner-friendly; Woo schema is paid.
- Rank Math — meilleur free tier; 16+ schema types; redirections + 404s free.
- AIOSEO — agency/WooCommerce-leaning; internal-link assistant.
- Rule: un plugin seulement — two les deux 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 filterablewp_get_canonical_url()— it didn’t ajouter the tag. - 5,5 — native XML sitemap at
/wp-sitemap.xml(barebones). - 6,4 — attachment pages disabled by par défaut on nouveau installs, redirecting straight to the fichier itself (pas the parent post); existing installs garder les on.
Gotchas
- The plugin’s canonical is authoritative — a theme injecting its propre title/meta conflicts with it.
noindex≠Disallow: a blocked page can’t have itsnoindexlire.- Don’t disallow
/wp-content/(breaks CSS/JS/image rendering). - A plus élevé Yoast score ≠ meilleur 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.txtWordPress SEO mistakes to éviter
- Running multiple SEO plugins or schema systems with overlapping ownership.
- Modification permalink structure on a live site sans a complet redirection map.
- Indexation every date, tag, author, attachment, search, and thin archive by par défaut.
- Editing theme fichiers directement au lieu de en utilisant maintainable child-theme or plugin ownership.
- Stacking cache and optimization plugins sans testing leur combined HTML and performances effects.
Courant WordPress SEO problèmes
Pages contain duplicate canonicals or schema
Causer: the theme and multiple plugins emit the même element. Fix: identifier un owner and disable overlapping output, alors purge caches.
Search visibility disappears après launch
Causer: the production site retained the “Discourage search engines” setting, a sitewide plugin directive, or staging accès rule. Fix: restore intended visibility and vérifier live directives à travers templates.
Archives or attachment URLs créer duplicate inventory
Causer: par défaut/generated routes are public sans a content objectif. Fix: choisir qui archives deserve indexation, configurer the SEO plugin consistently, and mettre à jour sitemap/internal-link behavior.
Outils pour WordPress SEO
- SEO plugins (pick un): Yoast SEO, Rank Math, or Tout in Un SEO — metadata, noindex contrôler, sitemaps, schema, redirections.
- Google Site Kit — Google’s official plugin; Search Console + Analytics + PageSpeed données à l’intérieur the WordPress dashboard.
- Recherche Google Console / Bing Webmaster Outils — submit votre sitemap, watch indexation and duplicate-metadata warnings, inspect individual URLs.
- Mise en cache: WP Rocket, W3 Total Cache, or LiteSpeed Cache — server-side mise en cache to fix TTFB-driven LCP.
- Image optimization: WebP/AVIF conversion + lazy chargement (la plupart mise en cache plugins or a dedicated image plugin) to cut LCP image weight.
- Lightweight themes: GeneratePress, Kadence, or Astra — construit pour Core Web Vitals plutôt que page-builder bloat.
- Robot d’exploration / site audit: Ahrefs Site Audit or Screaming Frog SEO Spider — surface the thin archives, attachment pages, chaîne de redirectionss, and duplicate canonicals a WordPress site accumulates.
- Multilingual (si nécessaire): Polylang, WPML, or TranslatePress pour translated content and hreflang injection.
Validation tests
Tester an SEO plugin or theme modifier
Tester to run — purge caches and inspect raw output à travers posts, pages, archives, and special routes. Attendu result — chaque template has un intended title, canonical, robots directive, and coherent schema graph. Échec interpretation — un autre owner or mis en cache couche encore conflicts. Monitoring window — immediate. Rollback trigger — revert si output disappears or duplicates à travers a template.
Tester a permalink or migration modifier
Tester to run — trace old URLs and explorer nouveau lien internes/sitemaps. Attendu result — direct redirections reach relevant successful URL canoniques and discovery uses nouveau routes. Échec interpretation — map or generated liens are incomplete. Monitoring window — immediate technically. Rollback trigger — pause si high-value routes 404, loop, or redirection irrelevantly.
Prompts pour WordPress SEO fonctionner
Classify ce WordPress explorer by post, page, category, tag, author, date, attachment, search, pagination, and parameter routes. Recommend qui templates devrait be indexé, consolidated, redirigé, or excluded, and state the evidence requis pour chaque decision.
Examiner ce plugin/theme inventory and sampled HTML. Identifier qui component owns titles, canonicals, robots directives, sitemaps, breadcrumbs, and schema. Flag overlaps and propose a single-owner configuration with validation and rollback steps.
Testez vos connaissances: WordPress SEO
Five rapide questions on getting WordPress configuré pour search. Pick an réponse pour chaque, alors vérifier.
Ressources utiles
My connexe writing
- Canonicalization: A Beginner’s Guide — how moteur de recherches pick a canonical and consolidate signals (the backbone of WordPress duplicate-content cleanup).
- The Beginner’s Guide to PageSpeed (avancé PageSpeed guide) — the performances side, directement relevant to WordPress Core Web Vitals.
- Redirections pour le SEO: A Complet Guide — the redirection mechanics behind attachment-page and permalink migrations.
- The Ahrefs Site Audit Study — données on how widespread technical problèmes (notamment the duplicate-content patterns WordPress creates) really are.
My speaking
- How Search Fonctionne (SlideShare) — my explorer → render → index → serve walkthrough, the model behind every “should this WordPress page be indexed?” decision. (Standing disclaimer s’applique: “This is my understanding of systems… not going to be 100% complete or accurate.”)
From autour the industry
- The WordPress SEO Guide (Joshua Hardwick, Ahrefs) — the practical 20-tip setup companion to ce plus technical treatment.
- WordPress SEO: The Definitive Guide (WPBeginner) — the comprehensive beginner checklist with the largest authority in ce space.
- Nouveau XML Sitemaps Functionality in WordPress 5,5 (WordPress core team) — the principal source on ce que the native sitemap covers.
wp_headhook référence (WordPress Developer Resources) — the action que SEO plugins (and conflicting themes) hook to inject metadata.- WordPress SEO Myths, Busted (Moteur de recherche Journal) — covers the “WordPress is slow / bad for SEO” myths in depth.
Journal des modifications
Mis à jour le 25 juil. 2026.
Résumé éditorial et détails enregistrés des changements.Détails des changements
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
Comparaison complète indisponible — aucun instantané antérieur n’a été archivé pour cette révision.
Mis à jour le 18 juil. 2026.
Résumé éditorial et détails enregistrés des changements.Détails des changements
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
-
Les notes détaillées des changements sont actuellement disponibles en anglais.
Comparaison complète indisponible — aucun instantané antérieur n’a été archivé pour cette révision.