Yuvraj Raulji | WordPress consulting
Built deliberately, with a real content model and a caching strategy, WordPress runs marketing sites and publishing operations at a cost no other platform matches. Built by accumulation, it becomes forty plugins and a security incident. The difference is almost always decisions made in the first month by someone who was in a hurry.
Direct answer
WordPress consulting is advice on the decisions that determine whether a site stays workable: how content should be modelled rather than dumped into page builders, whether the theme should be block-based or classic, which plugins are load-bearing and which are technical debt with a subscription, how hosting and caching should be arranged, and whether a requirement is worth a custom plugin or belongs off the shelf. The most valuable output is usually a content model, because that is the decision everything else inherits and the one nobody made deliberately.
Best suited for
- A site that has become slow to change
- Content trapped in page builders nobody can restructure
- Deciding between a rebuild and a rescue
- Planning a site that has to last five years
What this page is not
This page is about the site: content, templates, plugins, hosting and how the whole thing is put together. If there is a store on it and the question is the catalogue, the checkout or the commerce plugin stack, that is WooCommerce rather than WordPress.
The problem
The symptom as the person carrying it would describe it, and the part that shows up in the numbers rather than in the ticket queue.
The content has no model, only pages
What it costs
Everything is a page built in an editor, so nothing can be listed, filtered, reused or moved. Every new requirement becomes a manual rebuild, and the archive gets less useful as it grows.
The page builder became the architecture
What it costs
Layout, content and styling are fused in the database. Redesigning means re-entering the content, and leaving the builder is priced as a full rebuild because it effectively is one.
Forty plugins, and nobody chose them together
What it costs
Overlapping features, abandoned authors, and a combination that defines the site's real behaviour. Each update is a risk nobody can size, so updates get deferred and the exposure compounds.
Nobody can say whether to rebuild or rescue
What it costs
The decision is made by whoever is most frustrated. Rebuilding a site whose problem is its content model just recreates the problem with better typography.
Approach
In this order, and the order is the opinion. Most of what goes wrong on this kind of engagement is a step taken before the one it depends on.
Start from what gets published
Who publishes, how often, what kinds of thing, and what has to be reusable or listable. This is the input to the content model, and it is the step that gets replaced by a design conversation.
Model the content properly
Post types, taxonomies, fields and blocks, so content is structured data rather than markup in a database. Everything that follows, templates, search, feeds, reuse, an eventual headless front end, depends on this being right.
Read the plugin stack as a system
What is load-bearing, what overlaps, what is abandoned, and what nothing uses. On WordPress the plugin list quietly becomes the architecture, so it deserves reviewing as one.
Decide custom against off-the-shelf
Build where the requirement is specific to the organisation; buy where it is not. A bought plugin bent into an unusual shape becomes the thing that blocks every future update.
Answer rebuild or rescue directly
With the reasoning attached. A rescue is often possible and much cheaper, and a rebuild that does not fix the content model will produce the same site again in three years.
Scope
Content architecture
Post types and taxonomiesCustom fieldsBlock and pattern designReuse and listing strategy
Build decisions
Block theme against classicPage builder exitCustom plugin against off-the-shelfMultisite fit
Review
Plugin stack auditTheme and template reviewHosting and caching readRebuild or rescue assessment
Planning
Phasing and sequencingEditorial workflow designOwnership modelSecond opinion on a proposal
Proof
A content-led brand platform built for discovery and enquiry, which is the shape of site this work applies to.
Web platform · Manufacturing
Engineering manufacturer platform
A modern engineering brand platform built for discovery and enquiry.
Web platformTechnical SEOContent
3x traffic growth and 45% better engagement
Outcome
A content model the site can grow into
Structured content is what makes a site listable, reusable, searchable and eventually headless. It is the decision with the longest reach and the one most often skipped in favour of choosing a theme.
A rescue instead of a rebuild, where that is honest
Many sites described as needing a rebuild need a content model, a plugin cull and a caching fix. That is a fraction of the cost, and recommending it is the point of independent advice.
No measured figure is quoted here. None of the six builds on the work record is published as a WordPress case, though the record includes custom builds, bespoke themes, plugin development and production provisioning on AWS. Borrowing a number from the Magento work would be dishonest.
Questions
- Should we use a page builder?
- For a small site with one or two editors, they earn their place. For a site that has to last, they fuse layout, content and styling in the database, which means a redesign becomes a re-entry of every page. Native blocks with a designed pattern library get most of the flexibility without that trap.
- How many plugins should a WordPress site have?
- The count matters less than what each does and who maintains it. Thirty well-chosen plugins can be healthier than twelve where two overlap and one has been abandoned for years. The question worth asking is which could be removed today without anyone noticing.
- Should we rebuild or fix what we have?
- Fix it if the content model is sound and the problems are performance, plugins or templates, which is more often the case than agencies suggest. Rebuild when the content is trapped in a structure that cannot be restructured, because that is the one problem a rescue cannot solve.
- Is WordPress still a serious choice?
- For content-led sites and publishing operations, yes, and the cost comparison is not close. Its reputation problems come from how easy it is to assemble badly rather than from its ceiling. Built deliberately it runs large publishing operations, and it can be run headless where the front end needs its own release cycle.
- Do we need custom development or will plugins do?
- Plugins for anything generic, custom for anything that encodes how your organisation actually works. The failure mode is buying a plugin for a specific requirement and configuring it into a shape its author never intended, which is where the update risk comes from.
Next step
Describe what is actually in front of you and we will work out whether this is the right piece of work before anyone scopes it. That conversation is usually shorter than people expect, and it occasionally ends with me saying you do not need the project.