How to Do SEO in WordPress (and Whether You Should)
How to do SEO in WordPress, and the honest case against staying on it. The plugin stack that works, the sitemap trap, and when WordPress is still right.
To do SEO in WordPress, first make sure search engines are allowed to index the site, then lock the URL structure, configure one SEO plugin, decide which WordPress-generated pages should appear in search, connect Search Console, map one query to each useful page, optimize the content, add internal links, control performance, and validate what the site actually outputs.
That is the procedure. The more useful answer is to question the platform before you optimize it. If you are choosing today and have any engineering support, rebuild on a current platform like Webflow or ship natively on Vercel. WordPress is rarely the strongest choice for a site that has to compete in 2026, and a lot of WordPress SEO work is compensating for decisions the platform already made for you.
WordPress does not perform SEO for you. It packages the controls. The work is still deciding what deserves to rank, making the answer useful, and proving that Google can crawl, understand, and trust it.
An SEO plugin is the control panel. It is not the strategy.
Should you be on WordPress at all?
Probably not, if you are choosing today and you have engineering support. A current platform like Webflow, or a native build deployed on Vercel, gives you cleaner output, faster pages, and far more control over schema and automation than any plugin stack will. Publishing through a native setup is also faster than the WordPress editor once the tooling is in place.
WordPress wins in one specific situation, and it is a real one: marketers own the site day to day and there is little or no developer help after launch. The editorial environment is familiar, the workflows are understood, and nobody has to file a ticket to change a headline. That independence is why so many marketing teams stay, and it is a legitimate reason.
The costs arrive with it. Plugins slow the site and become a dependency you cannot cheaply leave. Governance drifts unless someone enforces standards. International SEO at scale is awkward. Schema and automation are less flexible than a headless setup.
So choose WordPress when marketers actively manage the site with minimal engineering reliance, you want a familiar editorial environment, and you are confident you can enforce plugin and governance standards. That last condition is the one teams overestimate. If you cannot commit to it, the platform will eventually manage you.
WordPress SEO is normal SEO with a convenient control panel
WordPress SEO is not a separate discipline or a shortcut around search quality. Google does not give a ranking bonus because a page was built in WordPress, and it does not care whether a plugin gives the page a green light. The CMS makes common SEO fundamentals easier to implement: editing titles, setting canonical URLs, generating sitemaps, adding schema, changing indexation rules, and publishing content without touching a template.
That convenience is real. It is also where teams get fooled. Installing a plugin feels like completing SEO because a new panel appears in the editor with scores and checklists. But the plugin cannot choose a commercially useful query, fix a page that answers the wrong intent, add firsthand evidence, decide whether a tag archive deserves to exist, or earn authority for the site.
If you remember one thing about how to do SEO in WordPress, remember the division of labor: use WordPress and one plugin to implement decisions, then use Search Console and the rendered page to verify those decisions worked.
My old WordPress sitemap showed why publishing is not the same as planning
Before I moved this site from WordPress and Elementor to its current build, I inventoried the old site’s XML sitemaps. They exposed 10 public URLs: the home page, an about page, a certifications page, five separate skill pages, a blog index, and one blog post.
Five of those skill pages overlapped and belonged consolidated into stronger resume sections. The certifications page belonged merged into the about page. The old blog post needed an explicit preserve-or-redirect decision. The sitemap accurately showed what WordPress had published, but it could not tell me which URLs deserved to keep competing in search.
That audit became the redirect map for the WordPress-to-Vercel migration documented on this site’s build page. It also captures the first operating principle for any WordPress site: inventory the URLs the CMS creates, assign each one a job, and stop assuming that publication makes a page strategically useful.
How to do SEO in WordPress, step by step
The ten steps below run from one-time foundation work to the decisions you make for every page. Work them in order. A perfect title cannot rescue a sitewide noindex, and an XML sitemap cannot fix a site full of overlapping pages.
1. Confirm Google is allowed to index the site
In the WordPress dashboard, open Settings, Reading and find Search Engine Visibility. On a production site, “Discourage search engines from indexing this site” should be unchecked. WordPress documents that enabling it can add a noindex,nofollow robots directive to the site, which is useful on staging and disastrous when it follows a launch into production.
Do not stop at the checkbox. Open the source of the home page and a representative post, then search for noindex. Inspect the same URLs in Google Search Console. Themes, plugins, hosting controls, and page-level settings can add their own directives, so the rendered output is the final source of truth.
For a WordPress site not showing up in Google, separate indexation from ranking before changing content. A URL Google is forbidden to store does not have a keyword problem.
2. Choose the permanent domain and permalink structure
Pick one canonical HTTPS hostname, either www or the root domain, and keep the WordPress Address and Site Address aligned with it. Redirect every alternate host and protocol to that version. Consistency matters more than which version you choose.
For a new site, go to Settings, Permalinks and choose a readable structure. The Post name pattern is a clean default for most service and B2B sites because it produces a short descriptive path. News publishers and sites where dates carry meaning may reasonably choose another structure.
For an established site, do not change permalinks just because another pattern looks cleaner. WordPress calls them permanent for a reason. A changed path is a changed URL, so it needs a direct permanent redirect, updated internal links, an updated sitemap, and monitoring. The complete procedure belongs in the website redesign and migration SEO playbook.
3. Install and configure one SEO plugin
Choose one maintained SEO plugin, not three. For SEO and schema, configure Rank Math Pro. Yoast is the plugin most teams reach for by default, and on its own it is not enough, particularly for schema depth and for controlling output consistently across a large template set.
If the site is international, run WordPress multisite with MultilingualPress rather than bolting a translation layer onto a single install. Language and region handling is where WordPress gets ugly fastest, and a multisite structure keeps each market’s URLs and hreflang manageable instead of tangled.
Run its setup process and verify these settings:
- whether the site represents a person or an organization;
- the default title and meta-description templates for posts, pages, and custom post types;
- which content types and taxonomies can appear in search;
- canonical URL output;
- XML sitemap behavior;
- default social-sharing images;
- schema defaults for pages, posts, products, and other real content types; and
- editor permissions for advanced robots and schema controls.
Do not stack WordPress SEO plugins that manage the same fields. Two plugins can output competing canonicals, duplicate schema graphs, multiple sitemaps, or conflicting robots settings. More controls do not create more optimization.
The focus-keyphrase score is also not a ranking signal. Use it as a prompt to check the basics, then apply judgment. A page can score green while targeting the wrong query, repeating commodity advice, or competing with another URL on the site.
4. Decide which WordPress URLs should be indexed
WordPress can create a large search surface from a small amount of content. Posts and pages are obvious, but categories, tags, authors, dates, media attachments, pagination, internal search, and custom post types can all produce URLs too. The right question is not “can this be indexed?” It is “would a searcher choose this page as a useful destination?”
| WordPress surface | Index it when | Exclude or consolidate it when |
|---|---|---|
| Posts and pages | The URL has a distinct query, intent, and useful answer | It duplicates another page or has no reason to exist alone |
| Category archives | The archive is curated, descriptive, and functions as a real topic hub | It is only a chronological list with no independent value |
| Tag archives | The tag represents a maintained topic with enough unique content | Tags were added casually and create thin overlapping lists |
| Author archives | Multiple authors have meaningful bodies of work and bios | A single-author site duplicates the main blog archive |
| Date archives | Time-based browsing is valuable to the audience | Month and year pages simply duplicate post lists |
| Media attachment pages | The attachment page has a genuine user purpose | It creates a thin page for every image with no useful context |
| Internal-search results | Almost never | The URLs are infinite, duplicative, or query-generated |
WordPress documentation notes that media items are posts in their own right and can have attachment-page permalinks. That platform behavior is not an instruction to index every attachment. Make the decision deliberately in the plugin’s search-appearance settings and confirm the result on the live page.
5. Run one sitemap and connect Search Console
Run one sitemap, not two. Modern WordPress ships core XML sitemap functionality at /wp-sitemap.xml, and your SEO plugin will generate its own. Let Rank Math own the sitemap and disable the core one, because two live inventories create duplication and confusion about which set of URLs Google should treat as the real list.
Inspect the sitemap rather than merely confirming it loads. It should contain the pages and post types you want indexed, use the canonical hostname, and exclude redirected, private, duplicate, noindex, staging, and internal-search URLs. Submit the valid sitemap or sitemap index in Google Search Console.
Google’s sitemap guidance is precise: a sitemap helps discovery, but it does not guarantee crawling or indexation. Treat it as a clean inventory supplied to Google, not an approval stamp. If submitted URLs remain excluded, investigate the reason in Search Console and the crawled-currently-not-indexed diagnosis.
6. Map one query and intent to each useful page
Before writing or optimizing a WordPress page, assign it one primary search job. Start with keyword research, then inspect the current result set to see what the searcher expects. A query filled with comparison pages needs a comparison. A service query usually needs a service page. A task query needs a direct procedure.
Keep a simple content map with the URL, primary query, intent, page type, status, and the hub it belongs to. This prevents two posts from quietly targeting the same term and makes gaps visible before they become a pile of disconnected drafts.
Search intent is the constraint that a plugin score cannot see. A technically perfect product page will not win a query where Google consistently ranks tutorials, and adding the phrase ten more times will not change the mismatch. Fix the search-intent alignment before tuning the copy.
7. Optimize the page inside the editor
Now use the WordPress editor and your plugin to implement the page-level work:
- Write a unique, descriptive SEO title that leads with the subject and earns the click.
- Use one clear H1 that states the page’s primary topic.
- Keep the slug short and descriptive before publication.
- Answer the searcher’s main question near the top.
- Use H2s and H3s to organize real subtopics, not to hold keyword variations.
- Add firsthand data, examples, screenshots, decisions, or experience the existing results lack.
- Write a useful meta description, then accept that Google may rewrite it.
- Add descriptive alt text to meaningful images and leave decorative images with empty alt text.
The detailed writing rules live in the guides to title tags and meta descriptions, H1 tags, and information gain. WordPress makes each field editable. It cannot decide whether the page adds anything worth finding.
Be careful when changing image alt text in the Media Library. WordPress documents that the library value becomes the default when an image is inserted, but a later block-level edit can apply only to that instance. Check the image in the page editor, not just the media record.
8. Add internal links in both directions
Every page worth ranking should have a place in the site’s structure. Link it to the relevant topic hub and useful supporting pages. Then return to established content and add links to the new URL, using anchors that describe what the destination covers.
WordPress makes this easy through its link search in the editor, but ease can produce random linking. Build hub-and-spoke internal linking deliberately. The hub should link to its spokes, the spokes should link back to the hub, and adjacent pages should connect when the reader would genuinely benefit.
This work improves discovery and routes existing authority. It also prevents the common WordPress problem where a post exists in the sitemap and chronological archive but receives no contextual links from the pages that already rank.
9. Control theme, image, and plugin performance costs
WordPress can be fast. It can also accumulate a page builder, an oversized theme, duplicate tracking scripts, uncompressed images, a stack of plugins, and several caching layers that fight one another. The CMS is not the performance problem by default. Uncontrolled implementation is.
Start with representative templates, not only the home page. Test a blog post, service page, category page, and any product or conversion template in PageSpeed Insights and Search Console’s Core Web Vitals report. Check mobile behavior, layout shifts, interaction delays, and the largest visible element.
Then work from the heaviest causes:
- resize and compress images before or during upload;
- serve modern image formats where the stack supports them;
- remove plugins that duplicate features or load sitewide assets for one small function;
- use one coherent caching and optimization setup;
- choose a maintained theme that outputs clean responsive templates; and
- retest after theme, builder, plugin, analytics, and consent-tool changes.
Google’s page-experience guidance says Core Web Vitals contribute to search success but do not guarantee top rankings. Aim for a genuinely fast, stable page, not a perfect score that comes at the expense of the content or conversion experience.
10. Validate the output and monitor results
The WordPress dashboard shows configured intent. The rendered page shows what search engines receive. After publishing, verify the status code, title tag, meta description, canonical URL, robots directives, headings, structured data, internal links, and sitemap membership on the live URL.
Use the Rich Results Test or Schema.org validator for structured data, and use Search Console’s URL Inspection tool for Google’s view. Request indexing when a priority page is new or materially changed, then monitor whether it becomes indexed and begins earning impressions for the intended queries.
Review Search Console monthly for indexation, query coverage, average position, clicks, and pages that are competing for the same term. Run a periodic SEO audit after meaningful theme, plugin, taxonomy, or URL changes. WordPress SEO is maintenance because the system keeps changing as people publish.
The plugin can ship a system, but only if the strategy is sound
I have seen the upside of using a WordPress plugin comprehensively. On a mid-market cybersecurity SaaS site, eight schema types were rolled out across commercial and editorial templates through a comprehensive plugin implementation. During the broader schema and architecture window, organic clicks rose 45%, and bottom-of-funnel click capture doubled on nearly flat impressions.
The attribution boundary belongs beside those numbers: the resource architecture changed in the same broad window, so this is not proof that a plugin alone caused the lift. It is proof that WordPress can make a systematic technical change deployable across a large content surface, and that implementation should be measured against a specific business outcome rather than a plugin score.
The cybersecurity SaaS case study has the full program. The separate schema-markup guide covers the types, validation, and eligibility rules. For this workflow, the lesson is simpler: configure the plugin once at the system level, override it only where a page genuinely differs, and validate the output instead of trusting the settings screen.
The WordPress failure mode is time, not configuration
What breaks WordPress sites is rarely a setting. It is accumulation. A site launches clean, and over three or four years it collects a page builder, two analytics tools, a consent manager, three plugins that each do part of the same job, and a theme nobody is willing to touch.
The people change alongside it. Whoever installed the redirect plugin moves on. The agency that added the schema plugin gets replaced. Eventually nobody in the building knows which plugins are load-bearing and which are dead weight, so nothing gets removed, because removing it might break something nobody can name. Page speed degrades steadily, and these sites usually end up slower than comparable ones on newer platforms.
The plugin list outlives the people who chose it. That is the real cost of WordPress.
That decay is the strongest argument against starting here in 2026. If you are already on WordPress, the defence is governance rather than tooling: a documented inventory of every active plugin and what it does, a named owner for each, and a scheduled review that removes anything nobody can justify. A site that cannot answer “what is this plugin for?” is already drifting.
Separate one-time setup from publishing and maintenance
A WordPress SEO checklist becomes manageable when the work is split by frequency.
| Frequency | What belongs there |
|---|---|
| One-time or rare | Domain choice, HTTPS redirects, permalink policy, SEO-plugin configuration, indexation rules, sitemap, Search Console, analytics, schema defaults |
| Every useful page | Query and intent map, title, H1, slug, opening answer, original evidence, headings, images, alt text, internal links, page-level schema |
| Monthly | Search Console indexation and performance, broken links, orphan pages, cannibalization, plugin and theme changes, Core Web Vitals, content decay |
| Before major changes | Full crawl, backup, URL inventory, redirect plan, staging controls, template validation, benchmark report |
This separation keeps a team from repeatedly “setting up SEO” while neglecting the pages that need to earn demand. Configure the machinery, then spend most of the ongoing effort on query selection, useful content, architecture, and measurement.
FAQ
Can I do SEO myself in WordPress?
Yes. You can handle the foundational WordPress SEO workflow yourself if you are comfortable making indexation, URL, plugin, content, and internal-link decisions and checking the result in Search Console. Bring in technical help when themes, custom post types, JavaScript, migrations, server configuration, or conflicting plugins make the rendered output difficult to control.
Does WordPress have good SEO?
Yes, WordPress is a capable SEO platform because it makes content, URLs, metadata, sitemaps, schema, and internal links manageable without requiring code for every change. It is not automatically optimized. A poor theme, weak hosting, duplicate archives, conflicting plugins, or thin content can make a WordPress site perform badly just as easily as any other site.
Do I need an SEO plugin for WordPress?
You do not strictly need one, because WordPress core and a well-built theme handle parts of the foundation. In practice one maintained plugin is the easiest way to control titles, meta descriptions, canonicals, robots directives, schema defaults, social metadata, and sitemap settings consistently, and Rank Math Pro is the one I would configure. Yoast is the common default and it is not enough by itself for schema depth. Use one plugin and verify its output, rather than stacking several.
How do I get my WordPress site indexed by Google?
First, uncheck “Discourage search engines from indexing this site” under Settings, Reading on the production site. Confirm the page does not output noindex, link it into the site’s navigation or content structure, include the canonical URL in the XML sitemap, submit the sitemap in Search Console, and inspect the URL. Indexation is not guaranteed, so a page that remains excluded may need a technical fix, stronger content, or consolidation.
How to change SEO title in WordPress
Open the page or post in the editor and use the SEO title field supplied by your active SEO plugin. If no plugin is active, the theme and WordPress normally derive the title from the page title and site configuration. After saving, inspect the rendered <title> in the page source because a theme or second plugin can override what the editor displays.
Does WordPress have an XML sitemap?
Yes. Modern WordPress includes core XML sitemap functionality at /wp-sitemap.xml, and SEO plugins generate their own sitemap index. Do not leave both running. Let the plugin own the sitemap, disable the core version, then verify the URLs and canonical hostname and submit that single version in Search Console. Having a sitemap helps discovery but does not guarantee indexation or rankings.
How long does WordPress SEO take to work?
The CMS does not determine the timeline. A corrected noindex or title can be recrawled quickly on an established site, while a new domain or competitive query may take months to earn visibility. Measure crawl, indexation, impressions, position, and clicks as separate stages. The more competitive the query and the weaker the site’s authority, the longer the path usually is.