How to improve SEO performance on WordPress

Key takeaways

  • Check indexability before anything else: the Reading setting, X-Robots-Tag headers, robots.txt and CDN or firewall rules. A page Google cannot index cannot rank.
  • Google’s ‘good’ Core Web Vitals are LCP of 2.5 seconds or less, INP of 200 ms or less and CLS of 0.1 or less, measured on field data. Google says good scores do not guarantee top rankings.
  • The 2024 Web Almanac found only 43% of sites passed Core Web Vitals on mobile. Fix the real bottleneck, and never lazy-load the hero image.
  • Pages that already sit around positions 4 to 20 are the practitioner favourite for quick gains. Refresh them before you publish new posts.
  • Give titles, canonicals, robots directives, schema and the sitemap to one SEO plugin. On WooCommerce, keep Cart, Checkout and My Account out of every cache layer.

A WordPress site can have a green SEO plugin score, a 95 in PageSpeed Insights and a sitemap submitted to Google, and still get no search traffic. Each of those numbers measures one thing. None of them measures whether Google can index your pages, whether those pages answer what people search for, or whether real visitors get a usable page.

Better SEO performance comes from doing the work in the right order. Fix whatever stops Google from seeing the right pages. Then improve the pages that are close to ranking. Then fix the speed problems real visitors have. Measure each step before you start the next. If you have not set up the basics yet (an SEO plugin, a sitemap, permalinks), start with our step-by-step WordPress SEO setup and come back here.

What order should you fix things in?

Start with indexing and finish with measurement. Google, WordPress and WooCommerce documentation all point to the same sequence, and so do the support threads:

  1. Indexability. Public pages are not set to noindex and are not blocked.
  2. Crawling, canonicals and the sitemap. Google can find each page through normal links and knows which URL is the main one.
  3. Content and titles. The pages that matter are useful, distinct from each other and well linked.
  4. Real-user speed. Problems confirmed in field data, fixed at their source.
  5. Tested cache and plugin changes. Especially anything that touches a store checkout.
  6. Measurement. Search Console and analytics, compared against a baseline you recorded first.

No study has measured the payoff of this exact order. The logic is simple, though. Rewriting a title does nothing for a page Google has been told not to index, and a faster page does nothing for a page nobody searches for.

Make one kind of change at a time. If thirty edits go live in the same week and rankings drop in week three, you cannot tell which edit caused it.

Is Google actually allowed to index your pages?

Check this first, because it is the most common silent failure. The site looks fine to you while Google is told to stay away.

The Reading setting. Go to Settings, then Reading, and look at “Discourage search engines from indexing this site”. WordPress.org’s Reading screen documentation explains that this box asks search engines not to index the site. It does not stop visitors, so you will not notice it is on. It is often ticked during development and never unticked at launch.

Header-level noindex. A noindex can also come from an HTTP header, X-Robots-Tag: noindex. Hosts and staging tools sometimes set it. It does not appear in the page source, so view source will not show it. Open the browser’s Network tab, click the page request and read the response headers.

robots.txt. Google’s noindex documentation explains a trap here. If robots.txt blocks a URL, Google may never fetch the page, so it never sees a noindex on it. Use robots.txt to control crawling and noindex to control indexing, and do not stack them.

CDN and firewall rules. Practitioners keep reporting the same pattern: a site with excellent speed scores loses rankings because Cloudflare, a WAF rule or a bot filter is challenging Googlebot. Optimisation plugins that intermittently return 503 errors cause the same problem. To check, run URL Inspection in Search Console and use the live test. If Google cannot fetch the page, fix that before anything else.

Once the block is gone, request indexing once and then wait. Unticking the box does not make pages appear within hours, and requesting indexing again and again does not speed it up.

Which Search Console statuses matter, and which are noise?

Open Indexing, then Pages, and read the reasons, not the totals. Three statuses cause most of the confusion.

  • Discovered – currently not indexed. Google knows the URL exists but has not crawled it yet. On a new or weakly linked site, add internal links to the page and give it time.
  • Crawled – currently not indexed. Google fetched the page and decided not to index it. This usually points to quality, not a technical fault: the page is thin, duplicates another page, or nothing links to it.
  • Alternate page with proper canonical tag. Usually just information. Google found a duplicate, such as a URL with tracking parameters, and indexed the main version instead.

Fix by cause, not URL by URL. Group the excluded pages by reason, fix one group, then export the report again. Do not remove noindex from archives you excluded on purpose. Whether thin tag archives belong in the index is a judgment call, and how tag archives affect SEO walks through it.

Are your links, canonicals and sitemap working together?

Google finds pages mainly by following links. A sitemap only helps. Google’s link best practices ask for ordinary <a href> links with descriptive anchor text. Links that only appear after a JavaScript click may never be crawled. Every page you want to rank should be linked from at least one other page, ideally one that already gets traffic.

The sitemap is a list of hints. Learn WordPress puts it plainly: a sitemap helps search engines find your content but does not boost rankings by itself. It should list only canonical URLs. If a page is missing from Yoast’s sitemap, check whether it is set to noindex, has a canonical pointing elsewhere, or redirects. Those are the reasons Yoast’s help pages list.

For duplicates, choose the main URL. Then redirect the copies to it or point them at it with rel="canonical". Do not use robots.txt or noindex to pick a canonical. A canonical tag is a hint, and Google can choose a different URL anyway.

Give every SEO output to one system. Two plugins, or a theme plus a plugin, both writing titles, meta descriptions or sitemaps is a common self-inflicted problem. Support threads show the symptoms: “Duplicate meta descriptions” warnings, or a sitemap error that says “XML declaration allowed only at the start of the document” because something prints output before the XML. If you switch SEO plugins, migrate the custom titles and descriptions before you deactivate the old one. One Reddit user removed Yoast first and lost traffic along with the fields.

Never change URLs without a redirect map. A redesign or a permalink change with no redirects turns pages that earn traffic into 404s. Map every old URL to its closest new one before launch. Our guide to redirecting a page without losing traffic covers the mechanics.

Which pages should you improve first?

Improve the pages that already nearly rank, before you write new ones. Practitioners agree on this more than on any other tactic. There is no controlled study behind it, but the reasoning holds: those pages are already indexed and already showing up in results.

  1. In Search Console, go to Performance, open the Pages or Queries tab, and filter average position to roughly 4 to 20.
  2. Sort by impressions. Pages with high impressions and low clicks are your shortlist.
  3. For each page, list the queries it appears for that the text does not actually answer. Add a section for each one, with a heading in the reader’s words and the answer in the first two sentences.
  4. Replace stale facts, prices and screenshots.
  5. Add internal links to the page from related pages that get traffic.
  6. If the page gets impressions but few clicks, rewrite the title so it says plainly what the page delivers. Compare “Drain Cleaning | Acme Plumbing” with “Same-Day Drain Cleaning in Austin | Acme Plumbing”.
  7. Request indexing once, note the date, and leave the page alone for a few weeks.

Publishing more is not the fix. One r/Wordpress owner had 148 articles, 36 of them written in a single month, and almost no traffic. Replies told him a bigger hosting plan would not change that. Where several pages target the same intent, merge them into one stronger page and redirect the others to it.

Keep titles and alt text specific rather than stuffed with keywords. Google may rewrite titles and write its own snippets from the page content anyway. For decorative images, empty alt text (alt="") is correct.

How much does speed matter for SEO performance?

Speed counts, but less than most audits suggest. Google’s Core Web Vitals documentation sets “good” at Largest Contentful Paint of 2.5 seconds or less, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of real visits. Google’s page experience guidance also says good scores do not guarantee top rankings. Practitioners report raising PageSpeed from the 50s to 90+ and seeing no real change in search traffic.

Use the Core Web Vitals report in Search Console, which is real-visitor data, to decide whether you have a problem. Use Lighthouse only to work out why. The 2024 Web Almanac found that 43% of sites had good Core Web Vitals on mobile and 54% on desktop, so failing on mobile is normal. It is still worth fixing, for visitors and conversions as much as for rankings.

MetricUsual WordPress causeFixTrap
LCPOversized hero image, found lateResize and compress it, and keep it in the initial HTMLLazy-loading the hero, or preloading several images that compete for bandwidth
INPLong JavaScript tasks from plugins and trackersRemove or defer scripts that load on pages that never use themAssuming minify-and-combine fixed responsiveness
CLSImages and embeds without dimensions, late bannersSet width and height, and reserve space for ads and noticesReserving so much space that it leaves blank gaps

web.dev’s LCP guide is explicit that the main image should not be lazy-loaded. Optimising pictures in WordPress covers the image side in detail.

Before you install a speed plugin, check what your host already caches. A caching plugin on top of server caching often adds conflicts rather than speed. To find the actual bottleneck, deactivate extensions one at a time on a staging copy and retest, then try a default theme. Speeding up a WordPress site safely goes through that process.

On WooCommerce, test caching on the checkout. WooCommerce’s documentation tells you to exclude Cart, Checkout and My Account from page and edge caching. Exclude them in every layer: plugin, host and CDN. Purge everything, then test both as a logged-out visitor and as a shopper with items in the cart. A cached checkout leads to stale prices, an endless spinner, or one customer seeing another’s session.

How do you know whether it worked?

Record a baseline before each change: impressions, clicks, average position and conversions for the pages you are about to touch. Then compare the same pages, not site-wide totals. Technical fixes usually show after Google recrawls, often within days to a few weeks. Content improvements take weeks to months. Nobody can promise a timetable, and anyone who guarantees rankings is selling something.

Read the numbers in combination. Rising impressions with flat clicks means people see the page but don’t choose it, which points to the title, the snippet, or an AI answer above it. Rising clicks with flat leads means the page attracts the wrong intent. Track the business outcome, such as enquiries, calls or orders, alongside the search numbers.

If traffic drops after a rebuild, check redirects and indexing before you blame seasonality. Comparing year on year in Search Console usually settles it.

How does this work change when an agent does it?

Most of this work is diagnosis, followed by a small edit: a title, a redirect, a noindex flag, a link. The edit takes minutes. For a business owner without a web team, the slow part is the queue: finding someone, explaining the problem, waiting for the slot, and checking that it was actually done.

Example request: “Our drain cleaning page sits around position 9 with lots of impressions and few clicks. Rewrite its SEO title and meta description to match ‘same-day drain cleaning in Austin’, add a link to it from the services section on the homepage, and tell me what changed.”

SiteSelf would find the page, read its current title and description in your SEO plugin, and tell you what it is about to change and whether the change can be undone. Then it would make the edits on the live site. Afterwards it fetches the changed pages, checks that the new title tag and the link actually render, and reports back in chat. What it did is recorded. This work needs only the SiteSelf Connector plugin from the WordPress.org directory. Speed and caching work, such as server cache rules or code changes, needs hosting (SSH) access.

The limits are worth knowing. The agent does not read Search Console yet, so you bring the numbers. It does not watch rankings afterwards, and nothing runs unless you ask for it. Pages owned by Elementor, Divi or Beaver Builder are refused at the moment of work, with the reason. The SEO fixes through chat page shows what is in scope, and the pricing page explains how credits work.

Frequently asked questions

Does installing an SEO plugin improve rankings?

No. Yoast SEO, Rank Math and All in One SEO give you controls for titles, canonicals, sitemaps and schema. Rankings come from what you do with those controls and from the content itself. Run only one, so you don’t get duplicate tags.

Will a better hosting plan increase my traffic?

Only if speed or reliability is the actual problem. A host change can cut load times sharply, but it does nothing for pages that are blocked from indexing, thin, or not matched to what people search for. Check indexing and content first.

Is a 90+ PageSpeed score worth paying for?

Pay to fix problems that show up in Search Console’s Core Web Vitals report, which uses real-visitor data. Pushing a lab score from 80 to 95 rarely moves rankings, and adding a new tracking script can undo it the following week.

Should I change permalinks on an established site?

Only with a good reason and a redirect for every old URL, tested before launch. Without redirects, pages that already earn traffic turn into 404s and lose their history. Test structural changes on a WordPress staging site first.

Does structured data get me rich results?

It makes a page eligible for them, not guaranteed to get them. On WooCommerce, the price and availability in the markup must match what the page shows. Validate with the Rich Results Test, and avoid adding a second schema plugin on top of the one you already run.

What should I ask for if I hire someone for SEO?

Ask for a baseline before work starts, a list of the specific pages and fixes covered, who will make the changes, and how results will be checked. Make sure you keep ownership of your accounts and files. Be wary of guaranteed rankings and cheap link packages.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *