WordPress SEO

The honest answer to is WordPress good for SEO is: it can be, and just as easily can be a mess. WordPress hands you a solid foundation, then leaves almost every decision that matters to you. Two sites on the same version can perform worlds apart depending on the theme, the plugins, the hosting and how the whole thing is set up. This guide walks the parts that decide which side you land on.

01 / The foundationWhat WordPress does well by default

Straight after install, WordPress covers the basics that some platforms fumble. It produces readable permalinks once you switch the setting off the numeric default, gives every page an editable title, and organises content into posts, pages and categories that map naturally onto a site structure. It outputs valid, crawlable HTML and has handled the mechanics of publishing at scale for two decades. None of this makes you rank, but it means you are not fighting the tool to do ordinary things.

02 / The pluginsYoast and Rank Math, honestly

Core WordPress leaves real gaps: it does not manage meta descriptions, control indexing per page, or output rich schema on its own. That is what an SEO plugin is for, and the two worth considering are Yoast SEO and Rank Math. Both handle titles and meta descriptions, generate an XML sitemap, add basic Article and breadcrumb schema, and give you per-page noindex controls. Rank Math bundles more in its free tier; Yoast is the older, more conservative option. Either is fine. The one rule is to run only one, since two plugins writing the same tags collide. And the green-light content scores are a checklist, not a ranking factor — write for the reader first.

03 / StructurePermalinks and site architecture

Your URL structure is a setting you should fix on day one, before anything is published. The default ?p=123 permalink tells a search engine nothing; a clean /services/roof-cleaning/ tells it everything. Set permalinks to the post-name pattern, keep the hierarchy shallow, and be deliberate about categories and tags — WordPress will happily create thin, near-duplicate archive pages for every tag you invent. A tidy structure with clear internal links, covered in our technical SEO guide, does far more than any plugin toggle.

04 / The weak spotSpeed, hosting and Core Web Vitals

Speed is where most WordPress sites lose ground. The platform loads a lot on every request, and a heavy page-builder theme, a stack of plugins, uncompressed images and cheap shared hosting compound into a slow page. That matters because Google uses Core Web Vitals as a ranking signal, with published thresholds of LCP 2.5 seconds or less, INP 200 milliseconds or less, and CLS 0.1 or less for a good experience (see web.dev on Web Vitals). A stock WordPress install rarely clears those on mobile without work: caching, image optimisation, trimming plugins, and hosting that is not the cheapest tier you could find.

05 / Technical SEOSchema, sitemaps and indexing

Beyond speed, the technical layer is manageable but needs attention. Your SEO plugin generates an XML sitemap automatically — submit it in Search Console and check it only lists pages you want indexed. Use the plugin's noindex controls to keep thin tag archives, internal search results and paginated clutter out of the index. Add structured data beyond the plugin defaults where it fits, such as LocalBusiness, FAQ or Product schema, so search engines and AI answer tools can read your pages confidently. This is the same groundwork we cover in our guides on technical SEO and keyword research.

06 / The trapsCommon WordPress SEO mistakes

• Plugin overload. Every plugin adds code, requests and a security surface. Ten SEO-adjacent plugins usually slow you down more than they help.
• Leaving default permalinks. Publishing on ?p=123 URLs and changing them later means redirects and lost signals.
• Indexing everything. Author, date and tag archives create thin, duplicate pages that dilute your site if left indexable.
• Chasing green lights. Stuffing a keyword to satisfy a plugin score, instead of writing for the person reading the page.

07 / The alternativeWhen a custom build beats WordPress

WordPress earns its place when non-technical people need to publish and edit content often. But when speed and stability are the priority and the site changes rarely, a lean custom build frequently wins. A static or framework-built site ships a fraction of the code, so it is faster by default, easier to secure and cheaper to maintain over time — no plugin churn, no update-day surprises. It costs more up front, which is why we walk through the trade-off in our guide on how much a website costs. There is no universal answer; the right platform depends on how the site will actually be run.

08 / The Elevate wayWordPress SEO in practice

At Elevate Labs we work with WordPress when it is the right tool and build lean and custom when it is not, deciding it site by site in Oslo. When we take on a WordPress site we tighten the same levers every time: a single well-configured SEO plugin, a clean permalink and category structure, real speed work against Core Web Vitals, and schema the platform will not add for you. See how it fits the wider picture on our SEO agency page, or browse the full set of Elevate guides.

09 / QuestionsFrequently asked