Plugin audit and reduction
What each plugin loads, on which pages, and whether two of them do the same job. Removal is usually the biggest single win available, and it is the one an agency paid to add things rarely proposes.
WordPress will let you do almost anything, which is the problem. A plugin for every job, a page builder that turns a paragraph into forty nested divs, and archive pages generating thin duplicates nobody asked for. The fix is nearly always removing things and editing the theme, not installing one more plugin to manage the last one.
Thanks, that’s with us.
A senior engineer reads every enquiry and will reply as soon as they can.
Book a time that suits you, or send a message on WhatsApp.
2020
Building since
1,000+
Clients served
UK
Registered company
4.6/5
Rated on Clutch
Quick answer
Less keyword work than people expect and far more removal. An SEO plugin such as Yoast or Rank Math handles titles, descriptions, canonicals and sitemaps competently, and once it is configured there is little left to gain there. The problems that remain are structural, and a plugin cannot fix them because the plugin is often part of them.
The first is weight. Every plugin adds queries, scripts and styles, usually on every page whether that page needs them or not. A site with thirty plugins and a page builder is routinely shipping several hundred kilobytes of CSS and JavaScript that nothing on screen uses, and that lands directly on Core Web Vitals on mobile.
The second is accidental pages. WordPress generates category, tag, author, date and attachment archives by default. Most sites need a couple of these and publish all of them, producing thin near-duplicates that compete with the posts they list and consume crawl attention that deeper pages need.
The third is markup. Page builders wrap content in deep nested containers, which is not fatal but makes the main content harder to isolate and bloats the DOM. Fixing these means working in the theme, in a staging environment, with the ability to roll back. It is development work, not configuration.
What we do
Eight areas, most needing theme and staging access. The audit says which are costing you rather than selling you all eight.
What each plugin loads, on which pages, and whether two of them do the same job. Removal is usually the biggest single win available, and it is the one an agency paid to add things rarely proposes.
Largest Contentful Paint and interaction delay measured on mobile with your real plugin stack in place. We separate what is the theme, what is the builder, what is the plugins and what is your hosting, because the fixes differ.
Deciding which of the category, tag, author, date and attachment archives earn their place. Most sites should index a few and remove the rest, rather than publishing every permutation WordPress offers by default.
Elementor, Divi and WPBakery produce deeply nested containers and load their full asset bundle site-wide. We scope what loads where and flatten the structure so the main content is easy to isolate.
Schema emitted from template code so it tracks the content and survives plugin changes, rather than depending on a plugin whose output shifts with every update and quietly stops validating.
Categories and tags used as a structure rather than as a dumping ground, with related content and breadcrumbs built into the templates so authority reaches deep pages instead of pooling on the home page.
Clear answers on the page, structured data that confirms them, and independent sources that corroborate your claims, so an assistant assembling a shortlist can quote you with confidence.
Product and category templates, faceted URLs and crawl budget on WooCommerce stores, plus redirect mapping when a site moves platform or restructures, covering the long tail rather than only the top pages.
The gap
What a typical WordPress SEO engagement does, against what is actually holding the site back.
Green lights in your SEO plugin and still no traffic?
That is the most common way this starts. Those indicators measure whether you filled in the fields, not whether the page can compete. The audit tells you what is actually capping the site, which on WordPress is usually weight, thin archives or a mismatch between the pages you have and the questions people ask.
In practice
Six recurring patterns. These describe what we see across engagements, not named client projects.
Sliders, form builders, popups, social widgets and two analytics tools all loading on pages that use none of them. The theme is frequently fine. The stack in front of it is what pushes mobile performance below the threshold.
A site with four hundred tags, most used once, each generating an indexable page with one excerpt on it. They dilute crawl attention and occasionally outrank the article itself, which is the worst of both outcomes.
A caching plugin installed, then another added when the first appeared not to work, with the host's own layer underneath. Usually the result is stale pages and inconsistent behaviour rather than speed.
Page builder output loading its complete CSS and JavaScript bundle on every page including ones built in the plain editor. Scoping what loads where often recovers more than any content change would.
Structured data produced by a plugin, then broken by an update, so rich results quietly disappeared months ago and nobody noticed. Moving it into the theme means it tracks the content and survives the next update.
A permalink structure changed or a category renamed, with no redirect map, so every accumulated link to the old URLs now lands on a 404. Recoverable, and far cheaper to plan before the change than to reconstruct afterwards.
How we work
Nothing touches your live site until it has been seen working on staging, and every change can be rolled back.
A crawl set against what Search Console reports as indexed, mobile performance with your real plugin stack, structured data validation, archive and taxonomy review, and a check on whether AI assistants can find and quote you.
Each finding gets an estimate of what fixing it is worth against what it costs. Items where those do not justify each other are written down and not done. You see the whole list, including what we recommend leaving alone.
Changes made on staging so you can see them against your real content first. Plugin reduction, theme edits, archive decisions, structured data and internal linking. Deployed when you approve, with a rollback available.
Before and after from your own Search Console on the queries the work targeted, plus Core Web Vitals on mobile. Where something did not do what we expected, we say so and say what we are doing instead.
Clear scope · Regular demos · Full handover
Honest fit
WordPress SEO pays when the site is capable and something structural is capping it. Sometimes neither is true.
What you are buying
Three shapes of engagement. The audit is free and carries no obligation to take either of the others.
| Free audit | Fix and deploy | Ongoing WordPress partner | |
|---|---|---|---|
| You get | Findings ranked, in writing | Theme and config changes deployed | Continuous diagnosis, content and fixing |
| Access needed | None | Staging and theme | Part of your release process |
| Plugin stack | Audited and measured | Reduced and reconfigured | Reviewed as plugins are added |
| Structured data | Validated | Moved into the theme | Maintained through updates |
| Commercial shape | Free, no obligation | Fixed scope, from £2,500 | Monthly retainer, from £1,500 a month |
| Best when | You do not know where the ceiling is | You know the problem and need it fixed | Search is a primary channel |
Sectors
Sectors that run on WordPress and where search is a real route to enquiry.
FAQ
What people ask before commissioning work. If yours is not here, put it in the form.
Still have a question?
Ask us directly. A senior engineer reads every question.
Ask about your projectYes. It gives you control over URLs, titles, markup and templates, which many platforms do not. The weakness is that it also lets you install anything, so most WordPress SEO problems are self-inflicted through plugins and page builders rather than caused by the platform.
One of them, configured once. Both handle titles, descriptions, canonicals and sitemaps perfectly well and there is little to choose between them. What neither can do is reduce your plugin weight, fix archive duplication or change your templates, which is where the real constraints usually sit.
Not if it is done properly. We audit what each one actually does, test removals on staging against your real content, and deploy with a rollback available. Some plugins are load-bearing and stay; the point is to find out which rather than guess.
Some categories usually yes, most tags usually no. A tag used once generates a page with a single excerpt that competes with the article it links to. The decision should be deliberate per archive type rather than left at whatever WordPress produced by default.
Normally a monthly retainer, from £1,500 a month, because content, links and technical health need continuous work. Some sites genuinely need a one-off fix instead, from £2,500. The right figure depends on the size of the site and the competition, which the free audit establishes first.
Usually not. Most of the cost comes from loading the builder's full asset bundle on every page including ones that do not use it. Scoping what loads where recovers most of the performance without rebuilding pages your team is comfortable editing.
We can audit without it and hand findings to your developers. But most WordPress constraints live in the theme and the plugin stack, so configuration-only access limits us to the SEO plugin's fields. We will say upfront if that makes the engagement poor value.
Yes. WooCommerce adds product and category templates, faceted URLs and crawl budget questions on top of the usual WordPress work. If the store is the main part of the site, our ecommerce SEO page covers the catalogue side in more depth.
Map the redirects before you change anything, covering the long tail and not only the top pages. Permalink changes without a redirect map are one of the most reliable ways to lose years of accumulated links, and it is far cheaper to plan than to recover.
That page is about building, rescuing and speeding up WordPress sites as development work. This one is about making an existing site rank: plugin weight, archives, templates and structured data. Plenty of clients need one without the other.
Start here
A senior engineer reads every enquiry and comes back with questions, a realistic view of the work, and an honest opinion on whether search is the right channel for you at all.
Thanks, that’s with us.
A senior engineer reads every enquiry and will reply as soon as they can.
Book a time that suits you, or send a message on WhatsApp.