Technical
Why WordPress Still Matters in 2025
A client asked me to rebuild their WordPress site in React because 'WordPress is old.' I asked them three questions, kept them on WordPress, and saved them $15,000 in development costs. Here is my reasoning and when WordPress is still the right choice.
The Numbers
WordPress powers 43% of the web. That number is not shrinking. There is a reason for this dominance: WordPress solves the content management problem better than custom code for most businesses. Not all businesses. Most businesses.
Your client probably does not need a React application. They need to update their own content without calling a developer, add blog posts and pages, manage contact forms, and not pay $200/month for hosting. WordPress does all of this out of the box.
When WordPress Wins
Use WordPress when:
- The client needs to edit content: WordPress admin is intuitive for non-technical users. No training required for basic content updates.
- The project is content-heavy: Blog, portfolio, news site, documentation, company pages
- Budget is limited: WordPress themes and plugins reduce development time from weeks to days
- SEO matters: WordPress has mature SEO tooling with Yoast, RankMath, built-in sitemaps, and schema markup support
Custom React App:
Build time: 4-8 weeks | Cost: $10-25K | Client edits: needs developer
WordPress:
Build time: 1-2 weeks | Cost: $2-5K | Client edits: self-serviceThe Block Editor Changed Everything
The Gutenberg block editor turned WordPress from a blog tool into a proper page builder. Clients can drag and drop content blocks, create complex layouts without code, reuse custom block patterns across pages, and preview changes before publishing. The editing experience is now competitive with dedicated page builders like Webflow and Squarespace.
The Agentic Angle
Here is what makes WordPress exciting in the AI era: I use Claude Code to build custom WordPress themes and plugins. The agent reads the WordPress documentation, understands the hooks and filters system, and generates production-ready PHP code.
Building a custom WordPress theme used to take a week of careful PHP and CSS work. With agentic development, I can build a production-ready theme in a single day. The agent handles the boilerplate while I focus on design decisions and client requirements.
When to Go Custom
WordPress is wrong when you need:
- Real-time features (chat, live updates, collaborative editing)
- Complex application logic (CRM, ERP, inventory management)
- High-performance APIs consumed by mobile apps
- Custom user interfaces that do not fit the WordPress admin model
For everything else, start with WordPress. Your client will thank you for the lower cost, the faster delivery, and the ability to manage their own content without developer involvement.
See the WordPress Developer Resources for theme and plugin development guides.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read