Aller au contenu

Technical WordPress SEO: the guide

WordPress powers a huge share of the web, but its default settings are designed to publish fast, not always for clean SEO. Several silent behaviors (typography filter, category URLs, theme-inherited H1) create technical problems that few publishers notice.

This guide brings together real cases met in production and their fixes, to take back control of what WordPress actually publishes. The linked articles are in French.

1. Content & typography

By default, WordPress applies the wptexturize filter, which automatically converts your straight quotes, apostrophes and ellipses into typographic versions. Handy for reading, but a problem as soon as it mangles a snippet of code, an attribute or a configuration extract pasted into a post. How excerpts are handled (the <!--more--> tag) also shapes what Google and your readers see on listing pages.

The WordPress wptexturize filter By default, WordPress automatically replaces straight quotes and apostrophes with typographic versions, which can mangle code or attributes. You type "SEO" the post's wptexturize filter enabled by default WordPress displays “SEO” the post’s
Handy for prose, a problem when it mangles a snippet of code, an attribute or a configuration extract.

2. URLs & duplicate content

WordPress can serve the same category content under several URLs (with or without a trailing slash, pagination variants), all returning an HTTP 200 code. The result: technical duplicate content that spreads signals instead of concentrating them. It is one source of duplication among others (HTTP vs HTTPS, tracking parameters), all covered in the Crawling & indexing guide.

Duplicate category URLs WordPress can serve the same category content under several URLs that all return a 200 code, creating duplicate content to consolidate with a canonical URL. SEO category 1 single content /categorie/seo/ 200 /categorie/seo 200 /categorie/seo/page/1/ 200 1 URL canonical
Several URLs returning 200 for the same content dilute signals: only one should remain canonical.

3. H1 & robustness

Many themes display the site name as an <h1> on every page, duplicating this strong semantic signal instead of reserving it for each page’s own title. And because an unprotected WordPress remains exposed to comment floods that can bring the server down, robustness is part of SEO hygiene too: a site that stops responding stops being crawled.

One H1 per page Many themes repeat the site name as the H1 on every page; it is better to reserve the H1 for each page’s own title. To avoid: the same H1 everywhere Home H1: Site name Services page H1: Site name Blog post H1: Site name Recommended: an H1 specific to each page Home H1: Home Services page H1: Our services Blog post H1: Post title
The H1 is a strong semantic signal: repeating it across the site dilutes it instead of qualifying each page.

A WordPress site to audit or harden for SEO?

An indexing problem, duplicate content, a poorly marked-up theme or a site that buckles? Tell me about your project.