WordPress Development
WordPress runs a substantial share of the web because it works, and gets blamed for what is done to it. A site that is slow, hacked or impossible to rank is nearly always carrying a bought theme, a stack of plugins and years without maintenance. We build WordPress sites properly, rescue ones that are not, and say so when it is the wrong tool.
What is included
- A review of what you have and whether WordPress is right for the job
- A bespoke theme, or a clean rebuild of the one you have, with no page-builder dependency
- A plugin list where each plugin has a stated reason to be there
- Security hardening, backups and an update routine set up before launch
- SEO configuration: permalinks, titles, archives, sitemaps, redirects and structured data
On this page
- What does a WordPress development agency do, and who needs one?
- Should you buy a WordPress theme, use a page builder or have a bespoke theme built?
- How do you stop plugin sprawl on a WordPress site?
- What does keeping a WordPress site secure involve?
- What makes a WordPress site fast, and what makes it slow?
- Is WordPress good for SEO?
- What does WordPress SEO configuration cover?
- Which WordPress archives and default URLs should be indexed?
- What does a WordPress SEO consultant do that a plugin cannot?
- Do you need multisite or headless WordPress?
- How do you move to WordPress, or off it, without losing rankings?
- When is WordPress the wrong choice?
- How do you choose a WordPress development agency or WordPress developer?
What does a WordPress development agency do, and who needs one?
A WordPress development agency builds, rebuilds and looks after business websites on WordPress. The work covers the theme, the plugins, the editing experience, security and updates, speed, and the search configuration that decides what Google sees. It is for businesses that want a site their own team can edit, and that will still work well in two years.
Not every business needs one. A simple brochure site on a well-made bought theme, kept updated by someone careful, can run for years. The point at which an agency earns its fee is usually when the site has become slow or fragile, when a page builder has trapped the design, when plugins have piled up with no record of why, or when the site is about to be rebuilt or moved.
We do this as part of our broader website development work, which also covers headless and custom builds. We are based in Oldbury in the West Midlands, and the work is done remotely. That breadth is why we can tell you honestly that WordPress is right, or that it is not.
Should you buy a WordPress theme, use a page builder or have a bespoke theme built?
Buy a theme for a simple site you will rarely change, use a page builder if your team must lay out pages itself and you accept the speed cost, and commission a bespoke theme when speed, a distinct design and clean editing matter. The table sets the four routes side by side.
| Route | What it is | Choose it if | Watch for |
|---|---|---|---|
| Bought theme | A ready-made theme from a marketplace, installed and configured with your content and brand. | The site is simple, the layout is close to what you want, and you will not change it much. | Dozens of features and scripts you do not use, loaded anyway. Updates depend on the seller continuing to support it. |
| Theme plus page builder | A theme combined with a visual page-building plugin so non-developers can lay out pages freely. | Your team needs to design new pages without a developer and you can accept slower pages. | Heavy markup and scripts on every page, and a design that lives in the builder, so leaving it means rebuilding the site. |
| Child theme of a bought theme | A small layer of your own code on top of a bought theme, so your changes survive its updates. | A bought theme is nearly right and needs a few targeted changes. | You still inherit the parent theme's weight and its dependence on one seller. |
| Bespoke theme | A theme built for your design and content, with fields and layouts designed for the people who will edit it. | Speed, a distinct design and a clean, unbreakable editing experience matter, and the budget supports it. | A larger build. It pays back through speed and control, but a simple site may never recoup it. See WordPress or a custom build. |
How do you stop plugin sprawl on a WordPress site?
Make every plugin justify itself: what it does, who maintains it, what it loads and what it costs. Remove duplicates, replace small plugins with a few lines of code, and keep a written list. Sprawl is not a number of plugins; it is plugins nobody can explain.
- What does it do that the theme or WordPress cannot? Many plugins exist to add a single button, a banner or a snippet. That is a few lines of code in a bespoke theme and no extra thing to update.
- Who maintains it, and when did they last release? An abandoned plugin is the commonest route into a compromised site. Check the last update, the support activity and whether it works with the current version of WordPress.
- What does it load, and where? Some plugins add scripts and styles to every page, even where they are not used. Check the effect on speed before and after installing.
- Does it duplicate another plugin? Two SEO plugins, two caching plugins or two form plugins create conflicts, duplicate markup and wasted weight. Pick one.
- What does it cost to keep? Many carry an annual licence. A plugin that saves a day once and costs a licence forever is worse value than it looks.
- Can the site survive without it? If removing it breaks content, the content has become dependent on the plugin. That is lock-in, so find out before you rely on it.
- Is the list written down? Keep a record of each plugin, why it is installed and who decided. When a plugin is deactivated, delete it, and check it has left no tables or scripts behind.
- Test updates away from the live site. A staging copy catches the update that breaks a form before your customers do, which belongs to ordinary website care.
What does keeping a WordPress site secure involve?
Security on WordPress is a routine, not a product: update core, themes and plugins promptly, remove what you do not use, protect admin access, keep tested backups, and monitor. Most compromised sites were running something outdated. The table shows where each risk sits and what the routine is.
| Area | What goes wrong | The routine |
|---|---|---|
| Plugins and themes | Outdated or abandoned code with known weaknesses, which automated scanners look for across the web. | Apply updates on a schedule, remove anything unused, and replace plugins that are no longer maintained. |
| WordPress core | Running an old version. By default WordPress applies minor security releases itself, but major versions need attention. | Keep core current, and test major releases on staging before applying them. |
| Admin access | Weak or reused passwords, a username that is easy to guess, and no second factor on accounts that can change anything. | Strong unique passwords, two-factor authentication, limited login attempts, and only as many administrators as are needed. |
| File permissions and editing | A compromised account used to edit theme or plugin files directly from the admin. | Turn off in-dashboard file editing, restrict file permissions and keep code in version control. |
| Backups | A backup that was never restored, or that sits on the same server as the site it is meant to protect. | Automated backups stored elsewhere, with a restore actually tested so you know it works. |
| Hosting | A shared server where one neglected site can affect others, or a host that does not patch its own software. | Choose hosting for isolation and maintenance, not only price. Keep the account in your name. |
| Monitoring | A site that has been quietly defaced or redirected for weeks before anyone notices. | Uptime and change monitoring, so a problem is seen quickly. A monthly care plan is one way to buy this. |
What makes a WordPress site fast, and what makes it slow?
A WordPress site is fast when the host, the theme, the plugins and the images are each light and cached, and slow when any one of them is not. Most slow sites are slow for two or three findable reasons, and each is fixable without a redesign.
- The theme and page builder. A bespoke theme loads only what each page uses. A theme with a page builder often loads large scripts and style sheets on every page, which is the single biggest difference between good and bad WordPress performance.
- Plugins. Each can add code to every page. Audit what loads, remove what is unnecessary, and replace small plugins with targeted code.
- Hosting and caching. A cheap shared host with no page caching rebuilds each page on every request. Good hosting, page caching and an object cache where it helps keep the server quick to start answering.
- Images. WordPress produces several sizes and adds lazy loading to images by default, but the theme decides whether the right size is used. Upload sensibly sized originals and serve modern formats.
- Fonts, sliders and embeds. A slider that loads every slide up front, several font files and a video embedded above the fold all cost time before anything is readable.
- Third-party tags. Chat, consent, analytics and advertising pixels share the browser's main thread and slow how quickly the page reacts.
- Measure what visitors get. Field data in Search Console reflects real devices. What the Core Web Vitals measure explains the targets, and the deeper fixes sit with technical SEO work.
Is WordPress good for SEO?
Yes, when it is configured properly. WordPress produces clean, crawlable pages, lets you edit titles, descriptions, headings and redirects, and creates a sitemap and canonical tags for you or through a plugin. A well-built WordPress site can rank as well as any other. The problems come from defaults left alone and from what is added later.
The defaults are generous. WordPress makes archive pages for categories, tags, authors and dates, creates search result pages, and can serve the same content at more than one address. None is wrong, but each is a page you did not write and may not want indexed. Add two SEO plugins that both output titles and markup, a slow theme and a page builder that hides headings in generic containers, and the site fights its own SEO.
That is why WordPress SEO is configuration and template work rather than a purchase. We treat it as part of the build, within the wider SEO service: decide what should exist, set the platform to produce it, and check what Google actually crawls. A plugin gives you fields. Deciding what goes in them, and which pages should exist, is the job.
The point
We treat it as part of the build, within the wider SEO service: decide what should exist, set the platform to produce it, and check what Google actually crawls.
What does WordPress SEO configuration cover?
It covers permalink structure, title and heading templates, which archives are indexed, canonical tags, XML sitemaps, redirects, structured data, internal linking and speed, set up deliberately in the theme and one SEO plugin. The aim is that every page Google can reach is one you meant to publish.
- Permalinks. Use a readable structure such as the post name, decided before content is loaded. Changing it later changes every URL and needs a redirect for each.
- Titles and headings. Titles should come from a template and be editable per page, with one clear heading per page. A page builder can hide the heading in a generic block, so check the rendered source.
- Archives and taxonomies. Decide what to do with category, tag, author, date and attachment pages, covered in the table below. The default is not always right.
- Canonical tags and duplicate paths. Confirm that each page declares one preferred address, that www and non-www, http and https, and trailing-slash variants all resolve to it, and that pagination behaves.
- Sitemaps. WordPress can generate a sitemap itself. An SEO plugin can replace it. Use one, make sure it lists only what you want indexed, and submit it in Search Console.
- Redirects. Record every redirect, keep chains short, and make a redirect when a URL changes. A tidy redirect map matters most when a site is replaced.
- Structured data. Output one clear set from the theme or one plugin, matching the page. Two sources produce conflicting markup.
- Internal links and breadcrumbs. Build them as ordinary links in the templates so every page is reachable from a menu or a parent, and so the content that matters is easy to find.
- Search settings and noindex. Keep internal search results, thin tag pages and staging copies out of the index. Make sure the live site is not set to discourage search engines, a setting left on after launch more often than anyone admits.
Which WordPress archives and default URLs should be indexed?
Index your pages, posts and the few archives that have real content. Keep out internal search results, date archives, thin tag pages and attachment pages. Author archives depend on whether the site has more than one author. The table gives the usual treatment for each default WordPress URL type.
| URL type | Usual treatment | Why |
|---|---|---|
| Pages and posts | Indexable, with a self-referencing canonical | These are the content you wrote and want found. |
| Category archives | Indexable if they have an introduction and a sensible set of posts; otherwise noindex | A category page can be a useful landing page, but only when it offers more than a list of titles. |
| Tag archives | Usually noindex, or removed if tags are not used | Tags multiply quickly, each with a few posts, and overlap with the categories they sit beside. |
| Author archives | Noindex on a single-author site; indexable if authors are real contributors with profiles | On a one-author site the author page duplicates the blog. It can also reveal a login username. |
| Date archives | Noindex | They list the same posts by month or year, add no new content and create many thin pages. |
| Attachment pages | Redirect to the parent post or the file, depending on version and settings | A page that exists only to show one image is thin and competes with the post it belongs to. |
| Internal search results | Noindex and kept out of crawling | Results are unbounded and thin, and crawlers do not need to submit searches. |
| Paginated archives | Each page has its own URL and canonical, reachable by ordinary links | Pointing every page at page one hides the posts that sit on later pages. |
| Feeds and comment pages | Left out of the index; comment pagination avoided or controlled | They repeat content already on the page and are not designed to be landing pages. |
What does a WordPress SEO consultant do that a plugin cannot?
A WordPress SEO consultant decides what a plugin cannot: which pages should exist, which archives should be indexed, how the URLs should be structured, what to fix first and why. A plugin gives you fields and switches. It does not know your business, your content or which of your pages deserve to rank.
In practice the consultant reads the site the way a crawler does, compares what is indexed with what should be, and turns the differences into specific changes: a redirect map, an archive rule, a corrected heading template, a plugin removed. If those changes need building, they have to be made in the theme or the configuration, which is why it helps if the person advising can also edit the code.
Whether you need advice alone or advice plus the build is a real question. If you have developers, an advisory consultancy may be enough. If you do not, work with an agency that can make the changes, and judge the people involved on specifics, as set out in how to choose a web development company.
The point
Whether you need advice alone or advice plus the build is a real question.
Do you need multisite or headless WordPress?
Most business sites need neither. Multisite runs several sites from one WordPress install, and headless uses WordPress only to manage content while a separate front end displays it. Both are real options for particular situations, and both add cost and complexity that a standard site does not carry.
Headless is something we cover in website development, where a headless content system sits behind a React or Next.js front end where performance or complexity justifies the extra cost to build and maintain. WordPress can play the content role in that arrangement. It is justified less often than it is sold, because you then maintain two systems and rebuild some of what a theme gives you for free, including preview, search markup and plugin behaviour.
Multisite appears in our work as part of a custom build, scoped individually. If your need is several sites that share a design, a shared set of users or a single administration point, tell us what the sites are for and we will say whether multisite is the right shape or whether separate installs are simpler. Do not choose either to look modern. Choose it because a standard site cannot do the job.
The point
Multisite appears in our work as part of a custom build, scoped individually.
How do you move to WordPress, or off it, without losing rankings?
Map every URL before anything moves, redirect each old address with a 301, carry across the content that was ranking, and check indexation afterwards. The platform matters less than the redirect map. The same discipline applies whether you are arriving on WordPress or leaving it.
- Export the real URL list. Use the live sitemap, a crawl and Search Console rather than memory. Include old posts, images that earn links and low-traffic pages.
- Decide the new structure on purpose. Set the permalink structure and page hierarchy before loading content. Do not let defaults decide it.
- Redirect everything. One 301 for each old URL to its closest equivalent, not everything to the homepage. Test on staging and again at launch, using the method in website migration SEO.
- Keep the content that ranks. A redesign tempts you to trim the copy. Compare what the old pages said with what the new templates will say.
- Move forms, tracking and integrations. Forms, analytics, tag setups and connections to other systems are often forgotten, and they fail silently.
- Take a full backup first, in both directions. Before the move, make a complete copy of the old site and database, tested, so you have somewhere to go back to.
- Leaving WordPress deliberately. If you are moving to a custom build, export the content in a form that can be read outside WordPress and keep the URL structure unless you have a reason to change it.
- Check search afterwards. Watch indexation, errors and traffic against the baseline. A short dip is normal; a lasting fall means something was missed.
When is WordPress the wrong choice?
WordPress is the wrong choice when the site is really an application, when unusual integration would mean fighting the platform, when plugin overhead costs you at scale, or when security rules demand a smaller attack surface. For most content-led business sites it is a sensible foundation.
- The site is an application. Logins, dashboards, per-user data and complex workflows are better served by a web application build than by a stack of plugins.
- Unusual integration. When the website needs deep two-way connection with a stock, production or booking system, you may be better off with custom code, since you will be fighting plugins that do not quite fit.
- A shop with complicated commerce. WooCommerce is capable, but if a hosted platform suits your catalogue better, building on Shopify instead is worth comparing before you commit.
- You will not maintain it. WordPress needs updates and attention. If nobody will look after it, it will become a liability, and the right answer may be a simpler site or a care plan.
- Strict security or performance requirements. A custom build has a smaller attack surface and loads only what it needs. The cost is a larger build and a narrower pool of developers.
- A site that will never change. A small static site may not need a content management system at all.
- You want no maintenance at all. Hosted platforms exist for people who would rather pay a fee than think about updates. That is a legitimate choice, with trade-offs in control.
How do you choose a WordPress development agency or WordPress developer?
Ask what theme they will build, how they choose plugins, who handles updates and security, how they set up SEO, and what you will own at the end. Ask to see the plugin list from a real project. An agency that cannot answer in specifics is selling a design, not a maintainable site.
- Bespoke or bought? Ask what the theme will be built on, and whether the design lives in a page builder you cannot leave.
- How do you choose plugins? You want a short, justified list and a developer willing to write small features as code, not someone who answers every request with an install.
- Who updates it afterwards? Updates, backups and monitoring either happen or they do not. Find out who is responsible and what it costs, before launch.
- How is SEO set up? Look for decisions about permalinks, archives, redirects and markup made during the build, not promised later.
- What will you own? The code, the content, the domain, hosting and analytics should all be in your name, with no buyout fee. Ask exactly what is transferred.
- What have they built? Our own delivery record is international rather than UK-based, and the projects we have built show what we have made, without rankings we cannot promise.
- Does the arrangement suit the job? A freelancer, an agency and an in-house hire fail in different ways, and how to weigh them is worth reading before you decide.
- What does it cost? Page count, copy and images, how bespoke the design is, the number of integrations and how settled the requirements are decide the build, and hosting, paid plugins and care sit on top. We publish no prices and scope each job after looking at it, so tell us what the site must do and we will say whether WordPress is the right foundation.
What WordPress Development covers
Not a menu to pick from. Most projects use some of this and ignore the rest, and the scope conversation is mostly about working out which half you actually need.
Bespoke WordPress themes
A theme built for your design and your content, with only the code the site needs, instead of a bought theme with hundreds of options you will never use.
Theme and page-builder rescue
Moving a site off a heavy page builder or a theme nobody can update, keeping the content and the URLs while replacing what makes it slow and fragile.
Plugin review and replacement
Auditing what is installed, what each plugin does, who maintains it and what it costs the site, then removing, replacing or writing code for the ones that do not earn their place.
Editing experience
A back end your own team can use without calling a developer: sensible fields, reusable blocks and layouts that cannot be broken by a stray click.
Security and update discipline
Hardened admin access, a routine for core, theme and plugin updates, backups that have been restored in practice, and monitoring through a care plan if you want one.
Performance work
Finding what slows a WordPress site, whether the host, the theme, the plugins or the images, and fixing it without a redesign where possible.
WordPress SEO configuration
Permalinks, titles, archives, canonical tags, sitemaps, redirects and structured data set up deliberately and checked against what Google actually crawls.
WooCommerce and integrations
Online stores on WordPress and connections to the CRM, booking or accounting systems behind the site, built on the same disciplined theme.
Why this is worth doing properly
Advice that can end in “not WordPress”
We build on WordPress and on custom stacks. If your site is really an application, or has requirements WordPress would fight, we say so before you pay for the wrong foundation.
Bespoke themes, not page-builder bloat
A theme written for your design loads only what each page uses. That is where most of the speed difference between a good WordPress site and a bad one comes from.
A short, justified plugin list
Each plugin is another thing to update, another thing to secure and another source of slowness. We keep the ones that do real work and write the rest as small amounts of code.
SEO set up in the platform
Most WordPress SEO problems are configuration problems: archives, duplicate paths, conflicting plugins. Because we build the theme, fixing them means changing the source, not adding another plugin.
You own the site
On final payment the code, the content and every account are yours, with no buyout fee and nothing only we can maintain. Anyone competent can pick the site up.
What you are handed, and who this suits
Deliverables
- A written recommendation on whether WordPress is the right foundation
- A bespoke theme built on a staging site you can review
- A documented plugin list: what each does, why it is there, who maintains it
- A security and update set-up with backups restorable in practice
- WordPress SEO configuration: permalinks, archives, titles, sitemaps and markup
- A redirect map from your old URLs where the site is being replaced
- Performance fixes covering images, caching, scripts and the theme
- Training, written documentation, the repository and every account in your name
Everything on that list is yours on final payment, in your own company's accounts — the handover is written into the contract, not offered as a favour at the end.
Usually a fit for
- Businesses whose WordPress site has become slow, fragile or frightening to update
- Teams stuck on a page builder or a bought theme that nobody can change cleanly
- Companies that want to edit their own content without calling a developer
- Owners with a site that has dozens of plugins and no record of why
- Businesses moving to WordPress, or off it, who cannot afford to lose their rankings
- Organisations that have found out they do not own their own theme, code or accounts
Built with
- WordPress with custom themes
- PHP and the WordPress theme API
- Custom fields and reusable content blocks
- WooCommerce
- REST and GraphQL APIs for integrations
- Schema.org structured data in JSON-LD
- Google Search Console
- Google Analytics 4
- XML sitemaps and robots.txt
- 301 redirect mapping
Chosen per project, not per fashion. If your team already runs something else and can maintain it, that usually wins.
Ask what this would involve for youFour gates, and you sign off at each one
Every stage ends with something you can read and approve — audit and plan, theme and structure, build and configure, launch and look after. Nothing moves to the next stage until you say so.
- 01
Audit and plan
We review the site or the brief: what it needs to do, who edits it, what plugins and integrations exist, and what search currently sees. We then say whether WordPress fits and what we would change.
- 02
Theme and structure
Page types, fields, navigation, URL patterns and the plugin list are agreed in writing before development starts, so the theme is built around your content, not the other way round.
- 03
Build and configure
The theme, the editing experience, security, performance and SEO settings are built on a staging site you can look at throughout, then tested across browsers, devices and a crawl.
- 04
Launch and look after
Launch with redirects and tracking live and everything handed over to you. After that the site is yours to run, or we keep it updated, backed up and monitored on a care plan.
Frequently Asked Questions
What does a WordPress development agency do?
It builds, rebuilds and looks after websites on WordPress: the theme, the plugins, the editing experience, security, speed and search settings. A good one also tells you when WordPress is wrong for the job, and hands over the code and accounts at the end.
Is WordPress good for SEO?
Yes, when it is configured properly. It produces clean pages, lets you edit titles, descriptions and redirects, and handles sitemaps and canonical tags. The problems come from defaults left alone: archive pages, duplicate paths, two SEO plugins fighting, and slow themes. Good WordPress SEO is mostly configuration and template discipline, not a plugin purchase.
What do WordPress SEO services include?
Permalink and URL structure, title and heading templates, decisions on which archives are indexed, canonical tags, XML sitemaps, redirects, structured data and speed, plus the content and internal linking around them. On WordPress much of that sits in the theme and one SEO plugin.
Do I need a WordPress SEO consultant?
Only if the decisions are beyond what your team can make. A plugin gives you fields to fill in; a consultant decides which archives to index, how to restructure the URLs and what to fix first. If you also need the changes built, work with an agency that edits the theme.
Should I buy a theme, use a page builder or have a bespoke theme built?
A bought theme suits a simple site you will change little. A page builder suits a team that needs to lay out pages themselves, at a cost in speed. A bespoke theme suits a site where speed, a distinct design and clean editing matter. It costs more to build and gives the most control.
How many plugins is too many on a WordPress site?
There is no magic number. The test is whether each plugin does something the site needs, is actively maintained, and does not duplicate another. Twenty well-chosen plugins can be safer than five abandoned ones. If nobody can say why a plugin is installed, it is a candidate for removal.
Is WordPress secure?
The core software is actively maintained. Most compromised sites were running outdated plugins or themes, weak passwords or no backups. A WordPress site with a short plugin list, updates applied on a routine, hardened admin access and tested backups is not a soft target. An unmaintained one is.
Can you take over a WordPress site another developer built?
Usually. We start by reviewing the theme, the plugins, the hosting and the state of updates, and whether it is cheaper to repair or rebuild. Sometimes the honest answer is a rebuild. We will show you the reasoning and the content and URL plan, so rankings are carried across.
When should I not use WordPress?
When the site is really an application with logins and per-user data, when unusual integration would mean fighting the platform, or when strict security or performance demands a smaller attack surface. For those, a custom build is cleaner. Our WordPress or custom build comparison sets out how to decide.
What decides the cost of a WordPress build?
Page count, whether you supply the copy and images, how bespoke the design is, how many integrations the site needs, and how settled the requirements are before we start. A rescue of an existing site is scoped differently from a new build. We scope each job after reviewing it. What a website costs in the UK sets out the drivers.
Let's Build Something That Matters.
Tell us what you're trying to achieve and we'll help you find the right solution.