Most business owners hire a WordPress developer the same way they’d hire a plumber: get a few quotes, pick someone in the middle, and hope for the best.
That approach works for plumbing. It doesn’t work for web development. According to research from Requiment, 39% of software project failures trace back to poor requirements gathering, and projects with clear requirements defined before development starts are 97% more likely to succeed (Engprax). The vetting conversation you have before signing a contract matters more than most people realize.
We’ve watched hundreds of WordPress projects come through our developer directory, and the ones that go sideways almost always have the same root cause: the client didn’t know what to ask.
These ten questions won’t make you a technical expert. But they’ll help you tell the difference between a developer who knows what they’re doing and one who’s figuring it out on your dime.
1. Can You Show Me Live WordPress Sites You’ve Built?
Not screenshots. Not mockups. Live, functioning websites you can click through right now.
This is the single most important filter. A portfolio of pretty images tells you nothing about whether the sites actually work. Visit each one on your phone. Check how fast they load. Click around and see if the navigation makes sense.
You can even run them through Google’s free PageSpeed Insights tool. If a developer’s portfolio sites score below 60 on mobile, that’s a concern. If they don’t have WordPress-specific examples (just general web projects), keep looking.
Watch for portfolios where every site looks identical. That usually means the developer is reskinning the same template, not building custom work. There’s nothing wrong with using templates for certain projects, but you should know that’s what you’re getting.
2. What’s Your Development Process?
This question separates professionals from amateurs faster than anything else.
A professional WordPress developer should describe something like a three-tier workflow: a local development environment where they build and test, a staging site where you can review changes before they go live, and the production (live) site that only receives tested, approved updates.
If the answer is “I make changes directly on the live site,” that’s a red flag. Every change on a live site carries risk. A professional developer never experiments on your production environment.
Also ask about version control. “Do you use Git?” is a simple yes-or-no question that tells you a lot. Git tracks every code change, provides rollback capability if something breaks, and is standard practice for professional development. If they don’t use it, ask why.
3. How Do You Handle WordPress Security?
Vague answers here are a warning sign. “We take security seriously” means nothing without specifics.
What you want to hear: SSL implementation, user role configuration (not everyone needs admin access), regular updates to WordPress core, themes, and plugins, file permission settings, login attempt limiting, and a firewall or security plugin like Wordfence or Sucuri.
What you don’t want to hear: silence, dismissiveness, or “WordPress is pretty secure out of the box.” It’s not. A hacked WordPress site costs $150-$500+ to clean up per incident, and the reputational damage is harder to quantify.
4. Do You Build Custom or Use Page Builders and Themes?
Neither answer is automatically right or wrong. But you need to know which approach you’re paying for.
Custom theme development means code written specifically for your site. It’s more expensive ($3,000-$7,500 from a freelancer, $10,000-$30,000+ from an agency based on current pricing data) but gives you a unique, optimized site with no unnecessary code bloat.
Page builders like Elementor or Divi, paired with premium themes, are faster and cheaper to implement. But they can create performance issues and maintenance headaches down the road. As Lucid Crew’s developer hiring guide puts it, over-reliance on premium themes packed with “unnecessary features and bloated code” is a red flag.
For many small business sites, a well-implemented page builder solution is perfectly fine. For e-commerce or high-traffic sites, custom development is usually worth it. The key is knowing which one your developer plans to use and why.
5. What Happens After the Site Launches?
This is where a lot of developer relationships fall apart.
Building a WordPress site is step one. Maintaining it is step two, and it doesn’t stop. WordPress core, themes, and plugins all need regular updates. Backups need to run on schedule, security needs monitoring, and performance requires ongoing attention.
Ask specifically: Is there a warranty period after launch? (30-90 days for bug fixes is standard.) Do you offer ongoing maintenance? What does that cost? What’s your response time for emergencies?
A developer who gets vague about post-launch support is a developer who plans to move on to the next project and leave you figuring things out alone. For context on what maintenance should cost, our developer rates guide covers maintenance retainer pricing in detail.
6. How Do You Handle Revisions and Scope Changes?
Every project changes mid-stream. The question is whether there’s a process for handling that or whether it becomes a dispute.
Scope creep can bloat WordPress project budgets by 20-60% according to analysis from Elementor. A professional developer will have a change order process: you submit the request in writing, they estimate the additional cost and timeline impact, and both sides agree before work starts.
Ask how many revision rounds are included in the original quote. Two to three is standard. Beyond that, there should be a clear per-revision or hourly rate for additional changes. This protects both of you.
7. Who Owns the Code and the Site When We’re Done?
This question catches more people off guard than any other on this list.
By default, the creator retains copyright on their work unless a contract explicitly transfers it. That means without a proper work-for-hire clause, your developer could legally reuse code they wrote for your project on someone else’s site.
Make sure the contract states that all custom code, themes, plugins, and design assets transfer to you upon final payment. Also clarify who controls the hosting account, the domain registration, and the WordPress admin credentials. You should have independent access to all of these, not just access through the developer’s account.
If a developer pushes back on transferring ownership, that’s a significant concern.
8. Can You Walk Me Through a Recent Project From Start to Finish?
This is better than asking “how do you work?” because it forces a specific, verifiable answer.
Listen for a structured process: discovery or scoping phase, wireframes or design mockups, client approval before development begins, development on staging, client review, revisions, testing across devices and browsers, launch, and post-launch support.
If the answer jumps straight from “we talked about what they wanted” to “we delivered the site,” there’s no process. And 57% of failing projects are attributed to communication breakdowns according to project management data from Mosaic. Process exists to prevent that.
9. What Questions Do You Have for Me?
This might be the most revealing question of all, because you’re not looking for their answer. You’re looking for their questions.
A good developer should ask about your business goals, your target audience, your existing branding, your competitors, your timeline expectations, and your budget range. They should want to understand why you need this site, not just what pages to build.
A developer who says “just send me the content and I’ll build it” without asking deeper questions is not invested in your project’s success. They’re filling an order. And as FreelancersDev’s hiring guide notes, that’s one of the most reliable red flags in the vetting process.
10. Can You Provide Two or Three Client References?
References should be non-negotiable. And you should actually call them.
Ask previous clients three things: Did the project finish on time and on budget? How did the developer handle problems or unexpected issues? Would you hire them again?
That last question is the one that matters most. A developer can have a great portfolio and still be terrible to work with. References reveal the experience behind the deliverable.
If a developer can’t or won’t provide references, move on. There are plenty of vetted WordPress developers in your area who can.
Before You Start Asking Questions
One more thing. Before you interview a single developer, define your project as clearly as possible. What pages do you need? What functionality? What’s your realistic budget? What’s your timeline?
The clearer your brief, the more useful the developer’s answers will be. Vague projects produce vague quotes, which produce misaligned expectations. And that’s where the real problems start.
If you’re deciding between a freelancer and an agency, these same questions apply to both. The answers just look different depending on the model. Either way, the developer who gives you the most thoughtful, specific answers is usually the one worth hiring.
