For non-technical stakeholders, choosing a WordPress agency can feel like guesswork.

Most agencies sound convincing. Many have polished portfolios. Pricing varies wildly. And without a technical background, it is difficult to separate genuine engineering expertise from surface-level competence.

That gap matters.

The technical decisions made early in a WordPress project shape everything that follows: performance, scalability, security, editorial experience, and long-term cost. Two sites can look identical at launch and behave completely differently six months later.

We’re here to help you spot that difference.

Why technical depth matters more than you think

At a glance, most WordPress builds look similar. Under the surface, they rarely are.

Less experienced agencies tend to optimise for speed of delivery. That often means leaning heavily on page builders, stacking plugins, or introducing custom code that bypasses WordPress conventions. It works, until it doesn’t.

What that usually leads to:

• performance that degrades as the site grows
• updates that break critical functionality
• security exposure through poorly maintained dependencies
• rising maintenance costs over time
• difficulty integrating with other systems
• less editorial flexibility and creativity
• developer support is required for simple content or design updates

More mature teams take a different approach. They build with WordPress, understand its capabilities and are close to its evolving roadmap. They make fewer shortcuts early on, so you aren’t paying for them later.

The difference is rarely visible in a demo. It becomes obvious in ownership.

WordPress core alignment and contribution

A simple way to gauge technical maturity is to look at how an agency relates to WordPress itself.

WordPress isn’t static. It evolves continuously through an open-source community. Agencies that stay close to core benefit from that evolution. Agencies that fight it tend to carry increasing technical debt.

You are looking for alignment, not reinvention.

Strong signals include a preference for native functionality, a clear awareness of upcoming changes, and an absence of unnecessary abstraction layers. The best teams will also contribute back, whether that’s to core or the wider ecosystem. The Five for the Future pledge database is a great resource for checking which organisations have made a commitment to contribute regularly.

That contribution matters. It’s one thing to use WordPress; it’s another to help shape it.

If you are not sure how to assess this, ask directly:

• Do you contribute to WordPress?
• How do you stay aligned with core updates?
• Where have you deliberately chosen core over custom?

Clarity and intent are more important than perfect answers. There’s got to be an obvious culture of contributing from the top down.

Modern WordPress: Full Site Editing and the block editor

WordPress has changed significantly. Not every agency has kept up.

The block editor and Full Site Editing represent a shift towards a more flexible, system-driven way of building sites. They’re more than new tool: they change how content teams work and how sites evolve.

Some agencies still default to older approaches. Classic themes. Heavy page builders. Layered abstractions that make simple things harder than they should be.

That’s not always wrong, but it should always be a conscious choice.

A technically strong agency will be comfortable explaining where modern WordPress fits, where it does not, and why.

In practice, that usually means:

• They treat the block editor as the foundation, not an add-on.
• They understand block-based theming and where Full Site Editing is appropriate.
• They create custom blocks when it adds value, not as a default.
• They think about the editor experience as carefully as the front end.

If those points are missing from the conversation, that tells you something.

Code quality and engineering standards

You don’t need to read code to understand whether an agency takes engineering seriously.

You just need to listen to how they describe their work.

Teams with strong engineering practices tend to talk about process with confidence and specificity. They can explain how things are built, tested, and maintained without resorting to jargon or hand-waving.

Look for evidence of discipline.

Version control is standard. Code is reviewed. Deployments are structured, not manual. There is a clear approach to testing, even if it is pragmatic.

Just as importantly, they can connect those practices to outcomes.

Performance is considered from the start, not retrofitted. Accessibility is treated as a requirement, not an enhancement. Security is built in, not patched on.

If the answers feel vague or overly simplified, they probably are.

Questions to ask in a pitch or discovery meeting

You don’t need technical knowledge to ask effective questions. You just need to focus on how decisions are made.

A few well-placed questions can reveal a lot:

• How do you decide what should be custom versus using existing WordPress functionality?
• What does a well-architected WordPress project look like to you?
• How do you approach performance from the start of a project?
• What technical mistakes do you see most often in WordPress builds?
• How do you ensure the site is maintainable over time?

Then listen carefully.

Strong agencies will talk about trade-offs. They will explain why, not just what. And they will connect technical decisions back to business outcomes without being prompted.

Personability and working relationship

Technical capability matters. But so does what it is like to actually work with the team.

Most enterprise WordPress projects are not short engagements. They involve ongoing collaboration, trade-offs, and moments where clarity matters more than speed. The relationship you have with the agency will shape that experience just as much as their technical decisions.

It is worth asking a simpler question alongside everything else: can you see yourself working closely with these people?

Trust is a useful proxy here.

Do they listen carefully to your brief and reflect it back with clarity? Do they explain their thinking in a way that makes sense, without defaulting to jargon? When something is complex, do they simplify it or hide behind it?

The strongest teams are able to translate technical decisions into clear, practical implications. They bring you into the process rather than keeping you at a distance.

There is also a more human dimension to consider.

Is the conversation easy, or does it feel strained? Do they challenge you constructively, or simply agree? Can they navigate ambiguity without creating confusion?

These signals matter because they compound over time.

A technically strong agency that communicates poorly can make a project feel difficult. A truly effective partner will make the process feel structured, collaborative, and, importantly, manageable.

That does not mean every interaction needs to be effortless. But it should feel like a working relationship you would be comfortable relying on.

Red flags to watch for

Some warning signs are easy to miss if you are not looking for them.

Over-reliance on page builders without a clear reason is one. So is solving simple problems with large numbers of plugins. Proprietary frameworks that lock you in should raise questions immediately.

Pay attention to tone as well as content.

If an agency dismisses WordPress core, avoids discussing the block editor, or struggles to explain their decisions in plain language, that is usually a signal of weak foundations.

Equally, if there is no clear story around updates, maintenance, or long-term ownership, you should assume it has not been thought through.

Making a confident decision

You don’t need to become an expert to evaluate one.

The best WordPress agencies are capable, but also intentional. They align with the platform, invest in good engineering practices, and build with the long term in mind.

Just as importantly, they can explain all of that clearly.

If you focus on those signals, you move the conversation away from surface-level comparisons and towards something more meaningful.

That is where the real differences are.

The post Evaluating the Technical Skills of a WordPress Agency appeared first on Human Made.

At WP:26, Human Made’s virtual event exploring the future of WordPress, we asked a simple question:

What patterns are shaping the web in 2026?

To help answer that, Chris Reynolds, Senior Developer Advocate at Pantheon, stepped back from the day-to-day tooling conversations and looked at the bigger picture.

While many discussions about the future of the web focus on disruption, Chris framed the moment differently.

The web isn’t being replaced. It’s accelerating.

AI is speeding up how teams build and publish. Expectations around digital experiences continue to rise. And organisations are under increasing pressure to deliver faster, smarter, and more resilient platforms.

The question isn’t whether the web is changing. It’s how platforms and teams adapt to keep up.

The web is speeding up

One of the key themes Chris explored was the pace of change.

AI tools are dramatically lowering the friction involved in creating, editing, and shipping digital content. Teams that once spent hours drafting, revising, and formatting can now iterate much faster.

But that speed comes with new challenges.

When publishing cycles accelerate, the surrounding systems also need to keep up. Infrastructure, workflows, governance, and editorial processes all need to scale alongside the tools themselves.

It’s not enough to move quickly. Platforms need to support sustained velocity.

Rising expectations for digital experiences

At the same time, user expectations continue to climb.

Audiences expect fast websites. Accessible interfaces. Consistent experiences across devices. And increasingly, they expect content to be relevant and personalised in real time.

These expectations aren’t new, but they are becoming non-negotiable.

For organisations operating at scale, this means the bar for digital platforms keeps rising.

Sites must perform well under heavy traffic. Content needs to be delivered quickly across multiple channels. Editorial teams need workflows that allow them to publish at speed without sacrificing quality.

In other words, the web isn’t just bigger. It’s more demanding.

Why adaptability matters more than disruption

Chris offered a useful reframing of the current moment. Instead of focusing on disruption, he emphasised resilience.

Platforms that succeed over the next decade won’t necessarily be the ones chasing every new trend. They’ll be the ones capable of evolving steadily as the ecosystem changes around them.

That means:

• supporting new technologies as they emerge
• integrating with an expanding ecosystem of tools
• adapting workflows without forcing organisations to rebuild everything from scratch

This kind of adaptability is often overlooked when people talk about digital transformation. But in practice, it’s what determines whether platforms can survive long-term.

WordPress and the long game

That perspective makes WordPress particularly interesting.

For more than two decades, the platform has evolved alongside the web itself. From blogging tool to full-scale CMS, and now increasingly into a flexible application platform.

Throughout those changes, its core strength has remained the same: adaptability.

WordPress doesn’t require organisations to abandon their workflows every time the industry shifts. Instead, teams can evolve their platforms gradually, integrating new capabilities while maintaining the stability they rely on.

That ability to change without constant reinvention is something many organisations are rediscovering as the pace of digital innovation accelerates.

A broader view of where the web is heading

Chris’ session offered an important reminder that while individual technologies may come and go, the underlying patterns shaping the web are remarkably consistent.

In 2026, the web continues to grow more connected. More interactive. More intelligent.

And organisations that succeed will be the ones building platforms that can evolve alongside those changes rather than constantly chasing them.

That perspective helped anchor the wider conversations throughout WP:26.

Across discussions about AI, accessibility, and enterprise publishing, one theme kept emerging: the future of the web won’t be defined by a single technology shift, but rather by platforms that can adapt to many of them.

And that’s a challenge the WordPress ecosystem has been quietly preparing for a long time.

Check out the rest of the WP:26 sessions to find out what the web has in store for enterprise teams in 2026.

The post The shape of the web in 2026 appeared first on Human Made.

Most conversations about AI in CMS platforms start in the wrong place.

They focus on features. Content generators. Chatbots bolted into sidebars. Assistive tools that demo well but rarely change how work actually happens. These additions feel modern, but they do not compound. They live in isolation, disconnected from the systems that organisations rely on day to day.

The defining shift for WordPress in 2026 is not a single AI feature at all. It’s the foundation being laid to enable thousands, or millions, of intelligent capabilities over time.

This is the moment where WordPress begins to move from CMS to agentic platform.

Why point features fall short

Most proprietary platforms are still treating AI as an add on. Each feature is designed, shipped, and monetised independently. A writing assistant here. A chatbot there. Useful in isolation, but operationally shallow.

The problem is not ambition. It’s architecture.

Without a shared, machine readable understanding of what a platform can actually do, AI tools are limited to suggestion rather than execution. They can recommend actions, but they cannot reliably take them. And without governance baked in, they remain risky to automate at scale.

WordPress is taking a different approach.

The Abilities API changes the model

At the centre of this shift is the Abilities API.

Rather than hard coding intelligence into individual features, the Abilities API allows plugins to declare what they are capable of doing in a standardised, machine readable way. Create content. Process an order. Publish a campaign. These are no longer implied behaviours buried in code. They are explicit capabilities that machines can discover and understand.

This applies to the entire ecosystem, including custom plugins built by teams themselves.

Once exposed, these abilities can be executed by AI agents. That might happen inside WordPress, or through external automation tools such as n8n. The important change is that WordPress is no longer just a system that humans operate through an interface. It becomes a system that agents can operate directly.

This is how a CMS quietly starts to resemble an operating system for digital work.

Governance without shortcuts

One of the most important details in this design is what does not change.

When agents create, update, or publish content, they do so using the same permissions and governance models as human users. There are no back doors. No elevated privileges. Automation respects the same rules as people.

This matters far more than flashy AI demos. It is what makes agentic workflows viable in enterprise environments, where trust, auditability, and control are non negotiable.

It also opens the door to a future where traditional user interfaces are no longer required for many tasks. Content can be created, updated, and distributed programmatically, without losing oversight.

MCP closes the loop

The Model Context Protocol completes this picture.

MCP allows AI models to connect to WordPress as a server, grounding conversations and actions in real site data and user granted capabilities. Instead of relying on vague prompts or disconnected tools, agents operate with context that actually reflects the state of the system.

This approach aligns closely with how enterprises already think about AI. Rather than being locked into opaque credit based models, organisations increasingly demand flexibility. Bring your own key. Bring your own model. Azure OpenAI today. AWS Bedrock tomorrow.

Open source enables this by default.

The ecosystem advantage

The real differentiator, however, is not any single API or protocol. It it’s scale.

WordPress has a plugin ecosystem of more than 60,000 extensions. Once those plugins can declare their abilities in a standard way, they become part of a shared agentic environment. Each new capability increases the value of the whole.

Proprietary vendors can compete on individual features. They can build impressive demos. What they cannot replicate is this kind of network effect.

What WordPress offers out of the box, when agent enabled, is structurally impossible for closed platforms or smaller ecosystems to match.

A different kind of AI platform

WordPress is not reselling generic AI wrappers at a markup. It is building the substrate those tools would need to actually matter.

This is not about replacing editors or developers. It is about changing how work flows through systems. From manual interaction to orchestration. From features to capabilities. From interfaces to agents that can act safely at scale.

That is the real shift underway.

To be clear, WordPress in 2026 isn’t becoming an AI powered CMS. Rather, it’s becoming an agentic platform, with an ecosystem advantage that compounds over time.

The post WordPress: From CMS to agentic platform appeared first on Human Made.