Key takeaways
- Good WordPress SEO services pay for judgement and fixes: what to index, how templates and archives behave, site structure, speed, redirects and content.
- WordPress already creates an XML sitemap at /wp-sitemap.xml, so “sitemap creation” alone is not a paid line item.
- One tick box in WordPress can ask search engines not to index the whole site. Checking it is part of any audit, not a service in itself.
- Installing and configuring an SEO plugin is an hour of setup. It is not an SEO strategy and shouldn’t be billed as one.
- Ask for every line in a proposal to name a deliverable you can check, and for the hours behind it.
Most WordPress SEO services I am asked to review cost more than they should, not because the price is high but because a large part of the scope is work WordPress or a free plugin already does. A sitemap, a plugin install, a few title templates. Those things matter, but they take an hour, and they are not the reason a site ranks or doesn’t.
I have worked in SEO and digital marketing for more than 16 years, and WordPress is one of the platforms I work on most. This article is the scope sheet I would want a client to hold up against any proposal, mine included: what should be in it, what shouldn’t, and what a small business can sensibly buy on a small budget.
Why WordPress SEO services are easy to oversell
WordPress makes the basics easy. That is good for site owners and convenient for anyone selling SEO, because the easy parts look impressive on a proposal. “XML sitemap setup”, “SEO plugin configuration” and “search engine submission” can fill half a page and describe very little work.
The hard parts are less visible. They are decisions: which pages should be indexed, which archives create thin or duplicate pages, how the theme builds titles and headings, whether the templates are fast enough on mobile, and how the site’s structure leads people and Google to the pages that make money. Those decisions are what you hire an expert for.
A plugin can carry out an SEO decision. It can’t make one.
What WordPress already does without paying anyone
Before you pay for a line item, check whether WordPress or a free plugin already covers it.
XML sitemaps. Since version 5.5, WordPress core includes sitemaps. The core team’s announcement of XML sitemaps in WordPress 5.5 says WordPress exposes a sitemap index at /wp-sitemap.xml, covering public post types and taxonomies, author archives and the homepage, with a maximum of 2,000 entries per sitemap (a limit that can be changed with a filter). SEO plugins often replace it with their own. Google’s page on building and submitting a sitemap says that if you use a CMS, it has likely already made a sitemap available to search engines, and that submitting one is “merely a hint” that doesn’t guarantee Google will use it.
The search engine visibility setting. WordPress has a box labelled “Discourage search engines from indexing this site”. The WordPress Reading Settings documentation says that since version 5.3 it adds a noindex, nofollow robots meta tag to the site’s head, and that “it is up to search engines to honor your request”. The same 5.5 announcement says core sitemaps are disabled when this option is on. Sites launched from a staging copy with that box still ticked are one of the first things I check.
Titles, meta descriptions and basic schema. Free SEO plugins give you fields and templates for these. Filling them in well is work. Turning the plugin on is not.
The WordPress SEO services scope sheet: what should be in it
Here is what I expect a WordPress SEO engagement to cover, and what each item should produce. Not every site needs every item, but every item on a proposal should look like one of these.
| Scope item | What the work involves | Deliverable you can check |
|---|---|---|
| Indexing review | Which URLs Google indexes and which it shouldn’t (tags, author archives, attachment pages, parameters, staging copies) | A list of URL groups with a keep, noindex or remove decision for each |
| Templates and theme | How the theme outputs titles, headings, canonicals, pagination and structured data | Tickets for your developer, with the template file and the fix |
| Site structure | Menus, categories, internal links and the path to money pages | A proposed structure and a list of internal links to add |
| Speed and Core Web Vitals | Heavy themes, page builders, unoptimised images, script bloat | Measured issues per template and the fixes in priority order |
| Redirects and migrations | URL changes, HTTP to HTTPS, domain moves, redesigns | A redirect map and a pre-launch and post-launch checklist |
| Content mapping | Matching searches to pages, finding gaps and overlaps | A keyword-to-page map with pages to create, merge or improve |
| Plugin review | Overlapping SEO, cache and redirect plugins that conflict | A list of what to keep, remove or reconfigure, and why |
| Measurement | Search Console, analytics and a ranking baseline | Access set up under your ownership, and a short list of figures to watch |
For most sites this starts with a WordPress SEO audit, because the audit is what tells you which rows matter on your site. If the audit finds the site structure is the real problem, our page on SEO website structure explains what that work involves.
Speed is a scope item, not a plugin
Speed belongs in the scope because WordPress themes and page builders are a common cause of slow pages. Google’s web.dev guide to Core Web Vitals gives the thresholds for a good experience: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads, on mobile and desktop separately.
A caching plugin can help. It won’t fix a theme that loads every script on every page. A good scope says which templates fail, why, and what will change.
What shouldn’t be in the scope (or shouldn’t cost much)
These are the line items I most often see padded. Some are fine as part of a larger job. None of them should be the job.
Line items to question in a WordPress SEO proposal
- “SEO plugin installation and configuration” sold as a separate package.
- “XML sitemap creation” when WordPress or the plugin already produces one.
- “Submission to Google” or to hundreds of search engines. A sitemap submission in Search Console takes minutes, and Google calls it a hint.
- Bulk link packages priced by the number of links.
- Auto-generated tag or location pages created to target more keywords.
- A monthly report with rankings and no list of what was changed.
- Stacking speed plugins without measuring before and after.
If a proposal is mostly made of these, you are paying for setup, not SEO. Ask what is left when you take them out.
WordPress SEO services for small business: what a small budget should buy
A small business doesn’t need every row of the scope sheet every month. With a small budget I would spend it in this order:
- A one-off audit. It finds the problems that block everything else: a noindex left on, duplicate archives, a slow theme, broken redirects.
- The fixes from that audit. Often your own developer can make them if the tickets are clear. You pay the consultant for the decisions and the review, not for the typing.
- A short content plan. A handful of pages that match what your customers search for, and improvements to the pages that already get impressions.
- A check after the changes. Rankings and Search Console data before and after, so you can see whether it worked.
After that, ongoing work only makes sense if there is a plan behind it. Paying a monthly fee for “maintenance” with no list of changes is the most common waste I see on small WordPress sites.
SEO services for a WordPress website: how to read a proposal
When you have quotes in front of you, run each one through four questions:
- Is every line a deliverable? “Ongoing optimisation” isn’t. “A redirect map for every URL that changes in the redesign” is, and you can check it line by line.
- Are the hours stated? If a plugin setup is billed as a day’s work, ask what happens during the day.
- Who makes the changes, and where? Changes should be tested on staging where possible, and you should get a written list of everything changed on the live site.
- What access is needed? A WordPress account with the lowest role that allows the work, named to the person using it, removed at the end. Our article on contract terms when one person holds the keys to your site covers access and ownership in more detail.
If your project includes a redesign or a move to a new domain, plan the SEO checks before launch, not after. Record your rankings before launch and check the same keywords again after it, so you can see what the move changed.
A quick test for any proposal
Strip out everything WordPress or a free plugin does on its own. If what is left is a clear list of decisions, fixes and checks, the proposal is about SEO. If almost nothing is left, it is about setup.
How I scope WordPress SEO work
I charge by the hour, with no fixed packages. A WordPress engagement with me usually starts with an audit and a ranked list of fixes, written as tickets your developer can act on. If your team can make the changes, I review them. If you need hands-on help, we agree the hours first. You keep ownership of the site, Search Console and analytics throughout. Our WordPress SEO consulting page explains how that works in more detail.
And if your WordPress site is in good shape and the plugin is doing its job, I will tell you that too.
FAQ
What do WordPress SEO services include?
Good WordPress SEO services cover indexing decisions, theme and template fixes, site structure and internal links, speed, redirects, content mapping, plugin conflicts and measurement. Each item should come with a deliverable you can check, such as a list of URL decisions or developer tickets.
Do I need SEO services for a WordPress website if I already use an SEO plugin?
A plugin gives you the controls, not the decisions. It won’t tell you which archives to noindex, why a template is slow or which pages are missing. If your site is small and you are comfortable with the basics, you may not need much help. If traffic is falling or a redesign is coming, an audit is worth it.
Are WordPress SEO services for small business worth the cost?
They are when the money goes to an audit and the fixes it finds, not to setup work WordPress already does. Start with a one-off audit and a clear list of changes, then decide whether ongoing work is needed.
Does WordPress create a sitemap automatically?
Yes. Since WordPress 5.5, core creates a sitemap index at /wp-sitemap.xml, and SEO plugins often replace it with their own. Core sitemaps are switched off if the “Discourage search engines from indexing this site” option is ticked.
Should I pay for “submission to Google”?
No. You can submit your sitemap in Search Console yourself in a few minutes, and Google describes a sitemap as a hint, not a guarantee of crawling. To ask Google to look at a single page, use the URL Inspection tool in Search Console.
If you have a WordPress SEO proposal in front of you and want to know which lines are real work, send it over and talk it through with me.
Eugen Platon · SEO consultant with 16+ years in SEO and digital marketing · free 10-minute first call