WordPress SEO: how to set up a WordPress site to rank, step by step
WordPress already does a lot of SEO for you. This guide covers the few settings that quietly break rankings, why one SEO plugin beats three, and how to get a WordPress site ready for Google and AI search.
The seoscore team 10 min read
On this page
- What WordPress already handles, and what it doesn't
- Step 1: Check the settings that can hide your site from Google
- Step 2: Pick one SEO plugin, not three
- Step 3: Write titles, meta descriptions and headings that earn the click
- Step 4: Submit your sitemap and connect Google Search Console
- Step 5: Make the site fast enough to pass Core Web Vitals
- Step 6: Add structured data and internal links
- Step 7: Get WordPress ready for AI search
- Step 8: Keep security, mobile and accessibility in shape
- Check your WordPress SEO from wp-admin
- Next steps
WordPress SEO is mostly about not breaking what WordPress already does well, then filling a few gaps. Core WordPress gives you an XML sitemap, clean URLs, lazy-loaded images and canonical tags on posts. It doesn't give you control over meta descriptions or structured data. Get a handful of settings right, add one SEO plugin, keep the site fast, then check the result with an audit instead of guessing.
The steps below are in order of impact. The first one can make the difference between being in Google and not being there at all.
What WordPress already handles, and what it doesn't
A fresh WordPress install is in better shape for search than most guides admit.
| Built into core | What it does for SEO |
|---|---|
XML sitemap at /wp-sitemap.xml |
Lists your posts, pages, categories and authors so search engines can find them |
| Virtual robots.txt | Generated on the fly, with a Sitemap: line pointing at the core sitemap |
| Pretty permalinks | Readable URLs such as /blue-widgets/ once you switch them on |
| Responsive images | Serves smaller image sizes to smaller screens |
| Native lazy loading | Adds loading="lazy" to images, while leaving the first large image to load straight away |
| Canonical tags on posts and pages | Tells search engines which URL is the main version of a single post or page |
| Old slug redirects | If you change a post's URL slug, the old URL redirects to the new one |
Recent versions also add speculative loading, which prefetches a page the visitor is likely to open next (Perfmatters explains how it works).
What core leaves out:
- Meta descriptions. There is no field for them.
- Title control. Your theme outputs something like "Post title – Site name", with no way to change it per page.
- Canonicals on listing pages. Core only adds a canonical tag on single posts and pages (the
rel_canonicalreference). The home page, categories and paginated archives get none. - Structured data. Core adds no schema markup to speak of.
- A redirect manager for anything beyond changed slugs.
Those gaps are what an SEO plugin is for. Before installing one, check the settings that can hide the site entirely.
Step 1: Check the settings that can hide your site from Google
Search engine visibility
Go to Settings > Reading and make sure Discourage search engines from indexing this site is unticked. Developers often tick it while building a site and forget it at launch.
When it's ticked, WordPress doesn't block crawlers in robots.txt. It adds a noindex tag to every page and removes the core sitemap (WordPress core announcement; wp_robots_no_robots reference). Google can still visit, but it is told to drop every page.
One more check: open yoursite.com/robots.txt. If there is a real robots.txt file in the site's root folder, it overrides WordPress's virtual one and may still contain a Disallow: / left over from development (mySites.guru). The default virtual file looks like this:
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Sitemap: https://example.com/wp-sitemap.xml
Permalinks
Under Settings > Permalinks, choose Post name. URLs like /?p=123 tell people and search engines nothing. If the site is already established, don't change the structure on a whim: every URL moves, and you need redirects from the old ones.
One version of your domain
Under Settings > General, the WordPress Address and Site Address should both start with https:// and use the same choice of www or no www. The other versions (http://, or www if you chose without) should redirect to it. Your host can usually set that up.
Thin archive pages
WordPress creates pages you may never have meant to publish:
- Attachment pages. Each uploaded image can get its own near-empty page. New installs have had these switched off for some time, but older sites often still have them. All three main SEO plugins have a setting to redirect them to the file or the parent post.
- Tag archives. Ten tags used once each make ten thin pages. Either use tags consistently or set tag archives to
noindexin your SEO plugin. - Author archives. On a single-author site, the author archive duplicates the blog page. Turn it off or
noindexit.
Step 2: Pick one SEO plugin, not three
Yoast SEO, Rank Math and All in One SEO (AIOSEO) all fill the gaps above. On their free versions:
| Feature (free version) | Yoast SEO | Rank Math | AIOSEO |
|---|---|---|---|
| Title and meta templates, per-page overrides | Yes | Yes | Yes |
| XML sitemap (replaces the core one) | Yes | Yes | Yes |
| Automatic schema | Yes | Yes, with more types to choose | Yes |
| Redirect manager | Paid | Yes | Paid |
| Breadcrumbs | Yes | Yes | Yes |
| llms.txt file | Yes | Yes | Yes |
Free and paid lines move, so check each plugin's own feature page before you decide. For most small sites, any of the three is fine. Pick the one whose settings you find clearest, and switch off modules you won't use.
What matters more is running only one. Two SEO plugins means two <title> tags, two meta descriptions, two sitemaps and two schema graphs, sometimes with different canonicals. That leaves Google guessing which signal to trust. If you switch plugins, use the new plugin's import tool, then deactivate and delete the old one.
You might not need one at all if the site is a handful of pages and your theme or host already gives you title and description fields. Most sites with a blog will want one.
Step 3: Write titles, meta descriptions and headings that earn the click
Titles
Set a default template in your SEO plugin, such as Post title | Site name, then override it on pages that matter. The override lives in the plugin's panel in the editor. Google's title link guidance asks for a unique, descriptive, concise title on every page, without keyword stuffing or repeated boilerplate. Google can rewrite titles it finds unhelpful, so a clear one is more likely to be shown as written.
Meta descriptions
Write a short summary of what the page gives the reader. Google sets no character limit. It cuts snippets to fit the screen and often writes its own from the page text. Put the useful part first and make each description unique. A product page might read: "Hand-thrown stoneware mugs in six glazes, dishwasher safe, made to order in Bristol."
One H1 per page
Your theme normally prints the post title as the H1, the main heading. Start your own headings in the body at H2. Two common ways to end up with a second H1:
- In a block theme, someone adds a Heading block set to H1 at the top of the content.
- A page builder's hero section uses H1 for a slogan.
View the page source and search for <h1 to count them.
Image alt text
In Media > Library, select an image and fill in Alternative Text. Describe what the image shows in context: "Blue ceramic mug on an oak table", not "mug1" or a list of keywords. It helps screen reader users and tells search engines what the image is.
Step 4: Submit your sitemap and connect Google Search Console
Once an SEO plugin is active, it turns off /wp-sitemap.xml and serves its own. Submit the plugin's sitemap (its settings show the URL), not the core one. Submitting both just creates noise.
To connect Google Search Console:
- Add a Domain property and verify it with the DNS TXT record Google gives you, at your domain registrar. This covers every version of the site.
- Or add a URL prefix property and paste the HTML tag into your SEO plugin's verification field.
- Go to Sitemaps and submit the plugin's sitemap URL.
Then check the Pages report every few weeks. The reasons to watch are "Excluded by 'noindex' tag" on pages you want indexed, "Duplicate without user-selected canonical", and "Crawled - currently not indexed". That last one often means a page is too thin or too similar to another.
Step 5: Make the site fast enough to pass Core Web Vitals
Core Web Vitals are Google's three page experience measures. A page passes when, at the 75th percentile of visits, Largest Contentful Paint (LCP, main content loading) is 2.5 seconds or less, Interaction to Next Paint (INP, response to clicks and taps) is 200 milliseconds or less, and Cumulative Layout Shift (CLS, content jumping around) is 0.1 or less (web.dev).
On WordPress, the biggest levers are, roughly in order:
- Hosting and PHP version. Cheap shared hosting is often the slowest part. Run a PHP version WordPress supports, ideally the one on its requirements page. Your host's control panel usually lets you switch.
- A page cache. Many hosts include one. Otherwise, use a caching plugin, and only one.
- Images. Upload images at the size they're shown, in WebP or AVIF where your setup supports it.
- Theme and page builder. Heavy multipurpose themes and builders load lots of CSS and JavaScript on every page. A lightweight theme or a block theme is usually faster.
- Plugins and unused JavaScript. It's what each plugin loads on the front end that counts, not how many you have. Remove plugins you don't use, especially sliders, popups and chat widgets.
Our guide to testing Core Web Vitals covers the tools and how to read field data against lab data.
Step 6: Add structured data and internal links
Structured data
Structured data (schema) is code that tells search engines what a page is about. Your SEO plugin adds the basics automatically: Organization or Person, WebSite, WebPage, Article on posts and BreadcrumbList. Add more only where it fits the page:
- Product on product pages. WooCommerce adds product markup itself, and SEO plugins extend it.
- FAQ on pages with real questions and answers. Google now shows FAQ rich results only for a small set of authoritative sites, but the markup still helps search engines and AI assistants read the page.
Test pages with Google's Rich Results Test.
Internal links
Internal links help search engines find pages and judge which ones matter. When you publish a post, open two or three older related posts and link to the new one with descriptive anchor text. In the block editor, select the text, press Ctrl+K (Cmd+K on a Mac) and type to search your own posts.
An orphan page is one that no other page links to. Compare your sitemap with the pages you link to, or let a crawler find them. Fix or remove broken links as you go: they waste crawls and frustrate visitors.
Step 7: Get WordPress ready for AI search
Older WordPress guides skip this, but it now decides whether ChatGPT, Claude, Perplexity and Google's AI Overviews can read and quote your pages.
- Let AI crawlers in. Check robots.txt for rules against GPTBot, OAI-SearchBot, ClaudeBot or PerplexityBot. Then check the layers above WordPress: CDN bot settings (Cloudflare has an option to block AI bots, so check what it is set to), host-level bot blocking and security plugins. Our guide to allowing AI crawlers in robots.txt lists the user agents and the rules to use.
- Add an llms.txt file. llms.txt is a short Markdown file that points AI assistants to your key pages. Use your SEO plugin's option, or create one with the free llms.txt generator and upload it to the site root. What llms.txt is, and whether AI reads it covers the evidence.
- Make content render without JavaScript. Most AI crawlers don't run JavaScript. Standard WordPress posts are fine, but content loaded by tabs, sliders or some page builder widgets may be invisible to them. See what AI crawlers see.
- Answer early. Put a direct two- or three-sentence answer near the top of each post, under a heading that matches the question.
The free AEO and GEO checker runs these checks on any page: AI crawler access, content without JavaScript, llms.txt, entity markup, FAQ markup and answer blocks.
Step 8: Keep security, mobile and accessibility in shape
- HTTPS and mixed content. After moving to HTTPS, old image and script URLs that start with
http://cause mixed content warnings. Search the database for them, or use your host's tool. - Updates. Keep core, themes and plugins current; out-of-date plugins are a common way sites get hacked. On the Plugins screen you can turn on auto-updates for each plugin.
- Security headers. Headers such as
Strict-Transport-SecurityandX-Content-Type-Optionsare usually set at the host or in.htaccessrather than in WordPress. - Mobile. Use Preview in the block editor to switch between desktop, tablet and mobile, then run Lighthouse in Chrome's DevTools on the live page. How to test mobile now covers the options.
- Accessibility. Check text contrast against the background and give every meaningful image alt text. Both help visitors, and both show up in audits.
Check your WordPress SEO from wp-admin
After a round of changes, you want to know whether they worked and what to fix next. An SEO audit scores the site out of 100 across eight weighted areas: Performance, Content Quality, Technical, Mobile, Security, Accessibility, Social and AEO. It ranks every fix by the points it adds. Start at the top of that list rather than the easiest item. Every check and weight is on the methodology page.
To do this without leaving WordPress, the seoscore WordPress plugin shows the site's score and ranked fixes in wp-admin. It audits each page as you edit it and can apply approved SEO titles, meta descriptions and image alt text. It's a checker and fixer rather than another settings layer, so it sits alongside whichever SEO plugin you kept.
Two more features help keep things on track:
- The SEO agent works through your audits every week. It proposes fixes such as titles, alt text, headings, structured data and internal links, and finds broken links. Nothing changes until you approve it.
- Automatic audits, on Starter and up with a free trial, re-audit the site weekly or daily and email you when the score drops. A plugin update that breaks something shows up without anyone having to check.
Next steps
- Untick Discourage search engines, set permalinks to Post name and confirm your HTTPS domain today.
- Keep one SEO plugin, set title templates, and
noindexor redirect thin archives. - Submit the plugin's sitemap in Search Console and look at the Pages report.
- Fix the slowest part of your stack, usually hosting, caching or images.
- Check AI crawler access and add llms.txt.
- Run an audit and work down the fixes in order of points.
Questions people ask
Is WordPress good for SEO?
Yes. It produces clean HTML, readable URLs and a sitemap out of the box, and it gives you full control over content and structure. Where WordPress sites struggle is usually speed and settings left wrong, not the platform itself.
Do I need Yoast to rank on WordPress?
No. Yoast is one good option, but Rank Math and All in One SEO do the same core jobs. What matters is having one SEO plugin set up properly, not which brand it is.
Does my WordPress theme affect SEO?
Yes, mainly through speed, heading structure and mobile layout. A heavy theme can slow every page and add duplicate H1s. A lightweight or block theme makes the other steps easier.
How many WordPress plugins are too many?
There is no fixed number. One plugin that loads large scripts on every page does more harm than twenty small ones that only work in the admin. Remove what you don't use and watch what each plugin loads on the front end.
How long does WordPress SEO take to show results?
Fixing a blocking setting such as a stray noindex can show within days of Google recrawling the site. New content on a young site usually takes weeks to months to rank, depending on competition and how many other sites link to yours.
Sources
- How to use Speculative Loading to prerender pages in WordPress perfmatters.io
- Changes to prevent search engines indexing sites. make.wordpress.org
- WordPress Discourage Search Engines Setting mysites.guru
- developers.google.com/search/docs/appearance/title-link developers.google.com
- developers.google.com/search/docs/appearance/snippet developers.google.com
- search.google.com/search-console search.google.com
- web.dev/articles/vitals web.dev
- wordpress.org/about/requirements/ wordpress.org
- search.google.com/test/rich-results search.google.com
seoscore
Your score inside WordPress
See your score and fixes in wp-admin, page by page.
See the WordPress plugin