WordPress handles the fundamentals well. Clean markup, sensible URL structure available in settings, and a plugin ecosystem covering everything the core does not.
It also ships with defaults that create problems at scale, and its plugin culture encourages installing more rather than configuring what exists. Most WordPress SEO work is a short list of settings and a shorter list of things to switch off.
Permalinks, Before Anything Else
The default permalink structure on some configurations produces URLs with dates or numeric identifiers. Change it to post name under Settings, Permalinks, and change it before publishing anything.
Changing permalinks on an established site means every URL changes, which is a migration requiring redirects, per the migration guide. On a new site it costs nothing. This is the single most consequential setting and it is the hardest to change later.
Date based permalinks are worth avoiding specifically because they make content look stale in the URL regardless of how recently it was updated, and they add depth for no benefit, per the site architecture guide.
Category and Tag Archives Are the Default Problem
WordPress generates an archive page for every category, every tag, every author, and every date. On a site with thirty tags each containing one post, that is thirty thin pages.
This is the most common source of index bloat on WordPress sites and it produces exactly the thin content dilution covered in the pruning guide.
What to do: keep category archives indexable where categories are genuine and contain meaningful numbers of posts, since those function as hub pages. Noindex tag archives unless you are using tags as a deliberate second taxonomy with real content behind them. Noindex date and author archives on single author sites, where they duplicate the main archive entirely.
Every major SEO plugin exposes these toggles. Finding them takes two minutes and most sites never do.
Attachment Pages Should Not Exist
WordPress historically created a separate page for every uploaded media file, containing the image and nothing else. On a site with two thousand images that is two thousand near empty pages.
Newer versions and most SEO plugins redirect these to the attachment file or to the parent post by default, and the setting is worth verifying rather than assuming. Search Console indexing reports on older WordPress sites frequently show large numbers of these still indexed.
One SEO Plugin, Configured, Rather Than Several
The major SEO plugins overlap almost entirely. Running two simultaneously produces duplicate meta tags, conflicting schema, and canonical tags fighting each other, which is worse than running neither.
Pick one, configure it properly, and delete the others rather than deactivating them. The choice between the main options matters far less than configuring whichever you pick.
The settings actually worth attention in any of them: title and description templates for each content type, the indexing toggles for archives described above, schema type per post type, and the XML sitemap configuration.
Schema From Plugins Needs Checking
SEO plugins generate schema automatically, and the automatic output frequently describes the site inaccurately.
The common errors: Organization schema with a placeholder logo or a name that does not match how the business is actually written elsewhere, which is the entity consistency problem covered in the About page guide. Article schema applied to pages that are not articles. Multiple plugins each generating their own blocks.
Validate what is actually being output rather than trusting the plugin, using the free validators covered in the schema guide. Automatic schema is a starting point, not a finished implementation.
Plugin Weight Is the Performance Problem
WordPress performance complaints usually trace to plugin count rather than to WordPress. Each active plugin can add queries, scripts, and stylesheets to every page load, including pages where the plugin does nothing.
A contact form plugin loading its scripts on every page rather than only on the contact page is the archetype. So is a slider plugin loading on pages with no slider.
The audit worth running: deactivate plugins one at a time on a staging copy and measure. Most sites find two or three plugins accounting for a disproportionate share of load, and frequently they are plugins nobody uses anymore, per the Core Web Vitals guide.
Page Builders Are the Largest Single Risk
Visual page builders produce heavily nested markup, frequently load substantial JavaScript, and in some configurations render content client side.
That last one is the genuine problem, because content rendered client side may be invisible to crawlers that do not execute JavaScript, per the rendering guide. A page that looks fine in a browser can contain nothing in its server response.
The check is direct: view source on a page built with your builder and search for a paragraph you can see on screen. If it is absent from the source, the builder is rendering client side and the content has an indexing problem.
Themes Matter Less Than People Claim
Theme marketing routinely advertises SEO optimisation, which is largely meaningless. Themes control markup structure and performance, not ranking.
What genuinely varies between themes: heading hierarchy correctness, whether images get dimension attributes, script and stylesheet weight, and mobile rendering. Those are real differences and none of them are what theme marketing means by SEO optimised.
A lightweight theme with correct markup outperforms a heavy multipurpose theme with an SEO badge, and the difference shows up in Core Web Vitals rather than in any direct ranking factor.
Comments and Pagination
WordPress paginates comments by default past a threshold, creating additional URLs for the same post. Those should canonicalise to the post rather than being indexed separately.
Whether to keep comments at all is a separate decision covered in the comments guide. The WordPress specific point is that unmoderated comment spam accumulates faster here than on most platforms, because WordPress is the most targeted platform for automated spam.
Hosting Is Where Performance Actually Gets Decided
Cheap shared hosting produces slow server response times that no amount of plugin optimisation resolves, since the delay happens before anything is sent.
Time to first byte is the measure worth checking, and it is the one thing genuinely fixed by paying more. Where server response is consistently slow, caching plugins mask the symptom on cached pages and do nothing for uncached requests.
A caching plugin is worth having regardless. It is a mitigation rather than a fix when the underlying hosting is the constraint.
What Not to Install
Plugins promising automatic SEO improvements, keyword density analysis, or automated internal linking based on keyword matching. The first two optimise for things that do not exist, and the third produces link patterns that read as automated because they are.
Multiple caching plugins, which conflict. Multiple schema plugins, which duplicate. Anything promising submission to hundreds of search engines, which stopped being a thing decades ago.
Multilingual WordPress Needs a Deliberate Choice
The main translation plugins take different structural approaches, some using subdirectories, some subdomains, some separate installs in a network.
That choice determines your domain structure, which is the decision covered in the international SEO guide and the one that is expensive to reverse. Picking a plugin without considering the structure it imposes means the structure gets decided by a plugin default.
Whichever you choose, verify the hreflang output rather than trusting it. Missing return links are the most common failure and translation plugins generate them automatically with varying reliability.
Updates Are a Maintenance Obligation, Not an Optional Task
WordPress sites break through neglect more often than through misconfiguration. A plugin left unupdated for a year eventually conflicts with a core update, and the failure frequently manifests as something subtle rather than a visible error.
The specific SEO risk is a plugin update changing output without anyone noticing. Schema disappearing, canonical tags changing, or noindex being applied where it was not before.
Checking a handful of key pages after any significant update takes ten minutes and catches the class of problem that otherwise runs for months before someone investigates a traffic decline.
Verifying the Setup Works
After configuring, check what crawlers actually receive rather than what the plugin dashboard reports. Plugin settings describe intent, and the server response describes reality.
The NotionCue AI Crawler Audit reports what specific crawlers get from a URL, which catches page builder rendering issues and schema that exists in the admin and not in the output.
Start your free NotionCue trial and verify a page built with your page builder specifically. That is where WordPress sites most commonly lose content without anyone noticing.
Open Search Console's page indexing report on any established WordPress site and look at the indexed count against your actual post and page count. A large excess usually means tag archives, attachment pages, or paginated comments are being indexed, and all three are fixable in an afternoon.
Common Questions
Which SEO plugin is best?
The differences matter far less than configuration. Pick one, configure the archive indexing settings and schema properly, and do not run a second one alongside it.
Does WordPress rank worse than custom builds?
No. Platform is not a ranking factor. What varies is how easy each platform makes it to get the fundamentals right, and WordPress makes it easy provided the defaults are reviewed.
Should I use AMP?
Google removed the AMP requirement for Top Stories some years ago and the format now carries maintenance cost with limited benefit. For most sites, improving the main site's performance is the better investment.