You've changed a WordPress theme, added a few plugins, published content regularly, and still watched organic traffic flatten or fall. Perhaps a WooCommerce rebuild has left product pages competing with category archives, or Search Console is showing URLs you never intended Google to index. Hiring a WordPress SEO expert can fix those problems, but only if you assess the person's WordPress and implementation skills rather than accepting a generic rankings pitch.
The right consultant can inspect templates, plugins, taxonomies, server behaviour, accessibility and measurement. The wrong one can add another SEO plugin, produce a polished PDF and leave your site with the same structural problems. I'm Will, a senior SEO and website consultant, and I've worked both as the person being hired and alongside businesses hiring SEO support. This is how I'd test a candidate before giving them access to a live WordPress site.
Table of Contents
- What a WordPress SEO Expert Actually Does
- The Four Skill Buckets to Test Before You Hire
- Pre-Hire Checks You Can Run This Week
- Interview Questions That Expose Real Depth
- “Our mobile LCP is poor on product pages. What do you inspect first?”
- “Would you choose Yoast, Rank Math or SEOPress?”
- “How would you reorganise a WooCommerce catalogue with messy attributes?”
- “Search Console shows a manual action. What do you do?”
- “How would you migrate this WordPress site without losing rankings?”
- Red Flags I Have Learned to Walk Away From
- Engagement Models and How to Choose One
- Your First 30 Days With a New Expert
What a WordPress SEO Expert Actually Does
A WooCommerce store loses traffic after a theme switch. The homepage still looks fine, products still appear in the admin area and the SEO plugin still shows reassuring indicators. Yet the new templates have changed headings, image sizes, canonical output and internal links. A capable WordPress SEO expert doesn't start by rewriting blog posts. They trace what changed in the WordPress stack and connect those changes to crawling, indexing, usability and commercial pages.
The role has four practical workstreams:
- Technical auditing, inside
wp-admin, the rendered HTML, crawl tools and, where available, server logs. - On-page implementation, in the block editor, Classic Editor or builders such as Elementor.
- Content and information architecture, using the site's categories, tags, taxonomies and WooCommerce attributes.
- Off-page development, including relevant link prospecting and digital PR rather than indiscriminate link buying.
That combination separates a WordPress specialist from a generalist who happens to have worked on WordPress. The specialist understands how a theme creates template output, how plugins can duplicate metadata or schema, and how a builder can add front-end weight that affects real page experience. They can also explain the trade-off between making a change in a plugin setting and fixing the underlying template or development issue.
Practical rule: Ask the candidate to name the exact WordPress objects, templates or plugins they'd inspect first. “I'd improve the SEO” tells you nothing. “I'd compare the single-product template, archive output, canonical tags and generated sitemap before changing settings” shows a workable process.
The platform matters because WordPress has a substantial UK footprint. Multiple 2026 technology reports place the UK among the top three countries globally by number of WordPress sites and estimate roughly 1.3 to 1.4 million UK WordPress websites, while one UK-focused report estimates about 45% CMS market share and around 4.5 million active WordPress websites. The estimates vary by methodology, but the scale explains why WordPress SEO remains foundational for UK businesses, especially content-heavy and ecommerce sites. (WordPress statistics and market context)
If you're assessing the wider digital marketing skill set alongside SEO, EmailScout's guide to digital marketing jobs provides useful context. For the WordPress hire itself, I'd also expect a candidate to understand the practical work described in WordPress SEO services, including technical fixes, on-page changes and measurement.
The Four Skill Buckets to Test Before You Hire
A CV can show that someone has used WordPress. It can't prove that they understand the consequences of changing a theme, activating a second schema source or flattening a WooCommerce taxonomy. I'd test four distinct abilities, each with a small task the candidate can complete or talk through.
Technical WordPress SEO
Give the candidate a representative page and ask them to inspect the raw HTML, rendered output and a mobile Lighthouse run. They should identify whether the title, canonical, headings, structured data and links come from the theme, an SEO plugin or custom code. They should also distinguish a genuine performance issue from a cosmetic score concern.
Core Web Vitals provide concrete thresholds: LCP should be 2.5 seconds or faster, INP 200 milliseconds or faster, and CLS 0.1 or lower. A page or origin passes when the 75th percentile for all three metrics is in the good range. (Google Core Web Vitals thresholds explained)
Ask what they'd test before recommending a new host. A useful answer may cover above-the-fold images, render-blocking assets, font loading, third-party scripts, page caching, builder output and template-level fixes. A weak answer only recommends a speed plugin.
On-page SEO and schema
Ask the candidate to prepare a title, meta description, heading structure and schema approach for a sample page using your chosen plugin. They should know the difference between what Yoast, Rank Math or SEOPress controls and what must be fixed in the page template.
The test should include a deliberate trap: activate or show output from two systems and ask how they'd prevent duplicate schema. A competent consultant won't treat a green plugin indicator as proof that the page is optimised. They'll check visible content, generated markup and whether the structured data describes what users can see.
Content and information architecture
Use a blog with a crowded category and tag structure, or a WooCommerce catalogue with inconsistent product attributes. Ask the candidate to explain which archives should exist, which should be consolidated or noindexed, and how internal links would support important pages.
For a blog with 500 posts, the task isn't to add more tags. It's to map search intent, identify useful parent and child categories, deal with thin or overlapping archives and preserve valuable URLs during changes. For WooCommerce, the candidate should understand that attributes can create useful filtered experiences or uncontrolled URL combinations, depending on how they're configured.
Analytics and reporting
Ask them to explain how they'd configure Search Console for a subdomain, track meaningful GA4 events without loading an unnecessarily large plugin and reconcile index data with WordPress-generated URLs. Google's Page indexing report shows indexed and non-indexed URL counts and gives reasons pages couldn't be indexed, making it central to this exercise. (Google Page indexing report)
A candidate with the depth you need should be comfortable working through the technical SEO consultant skill set in plain language. They should tell you what they'll measure, why it matters and what action follows from each finding.
Pre-Hire Checks You Can Run This Week
You don't need to be a developer to test whether a candidate can think clearly. You need a controlled process that gives them enough access to reason about your site, without giving away the keys before you've agreed the work.
Start with a limited audit
Request a paid or written sample audit of your own site, capped at one to two hours of their time. Ask for a concise document that names affected URLs or templates, explains the likely cause and separates urgent fixes from worthwhile improvements.
A useful sample might identify that product pages inherit the wrong canonical, that a builder loads unnecessary assets site-wide or that a category archive is competing with a guide. A weak sample will list generic advice about keywords, backlinks and page speed without showing where the issue exists.
Inspect their own footprint
Search for the consultant's name and the services they claim to provide. Review their website's source code, mobile experience, titles, internal links and indexable pages. You're not demanding perfection, but you are looking for evidence that they apply careful standards to their own property.
Then arrange a live diagnostic. Share a screen in Search Console or PageSpeed Insights and ask the candidate to narrate what they see, what they'd verify and what they'd do next. Their reasoning matters more than whether they instantly recognise every report.
Speak to references about outcomes
Ask previous clients what changed during the engagement, which work was implemented and what stopped working after the contract ended. “They were lovely” is useful only as a character reference. You need to know whether the consultant delivered clear recommendations, worked with developers and tied activity to organic clicks, indexed pages or qualified traffic.
| Step | Action | Pass / Fail Signal |
|---|---|---|
| 1 | Request a limited sample audit | Pass: specific URLs, templates and causes. Fail: generic slides |
| 2 | Review the consultant's own site | Pass: credible technical hygiene. Fail: obvious unresolved basics |
| 3 | Run a live Search Console or PageSpeed session | Pass: explains evidence and next actions. Fail: reads scores without diagnosis |
| 4 | Contact references | Pass: clear delivery and business outcomes. Fail: only vague praise |
| 5 | Protect access and payment | Pass: signed scope and staged payment. Fail: full upfront payment or early admin access |
Never pay the full fee upfront. Don't hand over administrator credentials before a signed scope, and don't waive a practical trial just because someone says they're too senior for homework. Senior people should be able to explain how they work.
Interview Questions That Expose Real Depth
Generic questions produce memorised answers. Ask for a scenario, then keep probing until the candidate has to make a decision with incomplete information.
“Our mobile LCP is poor on product pages. What do you inspect first?”
A strong answer starts with field data, template comparison and the largest content element, then considers image delivery, theme output, caching, fonts, third-party scripts and hosting. They'll discuss trade-offs, such as whether an image CDN is enough or whether the product template itself needs simplification.
A vague answer recommends image compression and a caching plugin. Walk away if the candidate promises a fixed score without asking for access to the site, templates or real-user data.
“Would you choose Yoast, Rank Math or SEOPress?”
There's no universally correct plugin. A capable consultant asks what's already installed, what functionality the site needs, whether developers rely on existing hooks and how migration would be tested. They should also look for duplicated metadata, sitemaps or schema before adding anything.
A poor answer treats one plugin as a ranking lever. The plugin can help manage output, but it doesn't replace decisions about page purpose, content, links or templates.
“How would you reorganise a WooCommerce catalogue with messy attributes?”
Look for a distinction between products, categories, attributes, filters and landing pages. The candidate should protect useful indexable pages, control combinations that offer no search value and map redirects before changing slugs.
If they suggest deleting a category because “categories are duplicate content”, ask what happens to its links, rankings and user journeys. An answer that ignores URL preservation is a serious concern.
“Search Console shows a manual action. What do you do?”
A competent person will identify the type of action, inspect affected pages and links, document the remediation and use the reconsideration process only after the underlying issue is addressed. They won't promise immediate recovery.
A vague answer says they'll “submit the site to Google”. Walk away if they blame an algorithm update without reading the notice or reviewing the relevant pages.
“How would you migrate this WordPress site without losing rankings?”
The answer should cover URL mapping, staging controls, redirects, canonicals, XML sitemaps, internal links, robots directives, analytics, Search Console monitoring and rollback planning. They should test representative templates, not only the homepage.
“Tell me what you'd leave unchanged during the migration.” A thoughtful answer recognises that unnecessary design, taxonomy and URL changes increase risk. A showy answer proposes changing everything at once.
Red Flags I Have Learned to Walk Away From
The clearest warning sign is a ranking guarantee. No consultant controls Google's algorithm, competitors, search demand or every implementation dependency. A promise of page-one rankings by a fixed date is a sales device, not a responsible forecast.
Vague scope creates a different problem. If the proposal says “optimise the website” without naming templates, plugins, deliverables, owners and review points, you won't know what you're paying for. WordPress projects need specificity because a change to one template can affect hundreds of pages.
Watch the delivery model
Some agencies present a senior consultant during the sales call, then transfer the work to someone you've never met. Ask who will audit the site, who will implement changes and who will attend reviews. If those answers change after signing, reconsider the arrangement.
Refusal to use Search Console or inspect hosting and development constraints can also hide weak foundations. A consultant doesn't need unrestricted access to everything, but they do need enough evidence to diagnose the site properly.
Treat link schemes and misleading schema seriously
Private blog networks and paid links presented as guaranteed authority create avoidable risk. A manual action can affect visibility and take substantial remediation work to resolve. The consultant should explain how they assess relevance, editorial control and link risk.
Schema must match visible page content. Product, review, organisation and FAQ markup shouldn't be added just because a plugin makes it easy. If the candidate recommends structured data that users can't find on the page, ask them to justify it. If they can't, don't approve the change.
Accessibility belongs in this assessment. A UK-focused summary of the WebAIM Million 2026 analysis describes widespread detectable WCAG failures and worsening accessibility across home pages. Another recent audit found 95.9% of the top one million homepages failed WCAG 2 checks, while a 2025 sample of WordPress pages averaged 50 detectable errors per page. (UK accessibility statistics and audit context)
A serious WordPress SEO expert should address semantic headings, alt text, form labels, keyboard navigation and clean redirects and canonicals. These issues affect whether people can use the site, and they can sit alongside technical search problems rather than being treated as a separate nice-to-have.
Engagement Models and How to Choose One
The payment model influences the work. A project fee encourages a defined outcome, a retainer supports iteration and an hourly arrangement preserves flexibility. Performance-based pricing sounds aligned, but it often encourages short-term tactics that don't suit WordPress sites requiring careful technical, content and development work.
| Engagement Model | Typical Price Range | Accountability | Best Fit | Watch Out For |
|---|---|---|---|---|
| Project-based | Agreed fixed scope | Deliverables, dates and acceptance criteria | Technical audits, migrations and WooCommerce restructuring | Scope gaps and expensive change requests |
| Monthly retainer | Agreed recurring fee | Ongoing priorities and reporting | Content, link earning and iterative optimisation | Work drifting into vague activity |
| Hourly consultancy | Agreed hourly rate | Time and advice delivered | Small businesses and ad-hoc decisions | Paying for diagnosis without implementation |
| Performance-based | Outcome-linked arrangement | Target metrics or commercial results | Limited situations with reliable measurement | Short-term tactics and disputed attribution |
A project-based engagement suits a company planning a migration or a one-off technical audit. Make the deliverables tangible: crawl analysis, redirect map, template recommendations, implementation support and post-launch checks.
A monthly retainer works when the business can keep publishing, developing and reviewing changes. It needs a backlog, owners and a definition of what the consultant will deliver each month. Without that, a recurring meeting can replace meaningful work.
Hourly consultancy fits an early-stage UK startup that has developers in-house and needs experienced direction at key points. It can also suit a small site that needs occasional reviews rather than a full programme.
Performance-based arrangements rarely fit an established ecommerce site where technical changes, content improvements and search demand interact over time. If an agency needs confidential delivery under its own brand, white-label SEO for agencies is a separate model to assess, with clear boundaries around client contact, reporting and implementation responsibility.
Your First 30 Days With a New Expert
Treat the first month as an evaluation period with deliverables, not a waiting room for rankings. By the end of the first week, you should have a technical baseline covering crawling, index coverage, Core Web Vitals, current schema, major templates and known plugin dependencies.
Google advises checking the Page indexing report monthly and whenever a site undergoes major changes, such as publishing substantial content or blocking parts of the site from crawling. (Google guidance on monitoring indexing) That makes index monitoring part of normal operating practice, not an emergency response after traffic disappears.
During the second week, expect the first practical changes, often technical fixes and on-page rewrites. The consultant should show what changed, which URLs or templates were affected and how the change was validated. By weeks three and four, judge delivery cadence, communication and movement in meaningful measures such as organic clicks, indexed pages and qualified traffic, rather than isolated ranking screenshots.
Use this short checklist:
- Baseline: Do you have crawl, indexing, performance and schema evidence?
- Priorities: Does the backlog explain impact, effort, owner and date?
- Implementation: Has the first work shipped, or are you still reviewing slides?
- Measurement: Can the consultant connect changes to Search Console and analytics data?
- Communication: Do you understand what happened without translating jargon?
If the work isn't landing, raise specific issues in writing. Ask which agreed deliverables are incomplete, what evidence supports the recommendations and what will be delivered next. A clean exit is better than another month of hoping when the consultant avoids evidence, misses agreed work or keeps changing the definition of success.
For a practical discussion of how a new expert should report and prioritise work, this video offers a useful additional format:
Sibley Digital provides senior technical, on-page and content-led SEO for WordPress sites, with implementation and reporting tied to Search Console and real website changes. Visit Sibley Digital to discuss a WordPress audit, rebuild or ongoing SEO programme with Will.