When you hire a WordPress developer, you are not just buying a website. You are choosing who will hold the keys to your domain, hosting and code, and who you will call when something breaks at 9pm on a Friday. A good choice saves you years of hassle; a poor one can cost you a rebuild.

This guide helps you work out what kind of help you need, where to look, the 12 questions worth asking, and the red flags to watch for. I am a WordPress developer myself, so I have tried to keep it fair: these are the questions I would want a client to ask me.

Concept illustration of a website wireframe panel and a checklist panel joined by a glowing handshake symbol
A clear brief and a clear agreement do most of the work of a good hire.

Do You Need a WordPress Developer, Designer or Both?

The titles overlap, so start with the job, not the label.

Three-column comparison of what a WordPress designer, a developer, or both cover on a project
Match the skills to the work you actually need done.

If your site already looks right but is slow, broken, hacked or missing a feature, you need a developer. If it works but looks dated and does not convert, start with design.

Where to Find Good WordPress Developers

Freelancer or agency? Both can be right. I compare them honestly in freelance WordPress developer vs agency.

12 Questions to Ask Before You Hire a WordPress Developer

Good answers are specific, calm and free of jargon. Vague answers are a signal to dig deeper.

Checklist of 12 questions to ask a WordPress developer before hiring, from similar projects to post-launch support
Print this and take it into your first call.
  1. Can you show me similar sites you've built, and what was your part? Ask for live links.
  2. Will you use a custom theme, a block theme or a page builder, and why? Each has trade-offs for speed, editing and future changes.
  3. Do you work on a staging site? Changes should be tested away from the live site.
  4. How do you handle backups during the build and after launch?
  5. Which plugins will you use, and why each one? Fewer, well-maintained plugins are a good sign.
  6. How do you secure a site? Listen for updates, strong logins, least-privilege user roles and backups, not just "we install a security plugin".
  7. How will you measure speed? A good answer mentions Core Web Vitals or real-user data, not only a single test score.
  8. Who will own the code, the domain, the hosting and the accounts? The answer should be "you".
  9. How are changes and extras priced? Ask how scope changes are agreed.
  10. What does handover include? Logins, documentation, training, and the source code for anything custom.
  11. What support do you offer after launch, and how fast do you respond to an emergency?
  12. Who else works on the project? Subcontractors are fine, as long as you know.

For technical projects, it is reasonable to ask whether they follow the WordPress Coding Standards. WordPress describes these as a baseline that makes code readable and easier for anyone to modify later, which matters if you ever change developer.

Red Flags in Proposals and Portfolios

Two-column list of red flags in WordPress developer proposals and portfolios
One red flag is a question to ask. Several together is a reason to walk away.

Who Should Own the Hosting, Domain and Code?

You should. Even if your developer manages things day to day, the accounts should be in your business's name, with your developer added as a user.

Concept illustration of three keys on a ring representing the domain, hosting and code
Domain, hosting and code: three sets of keys you should always hold.

How to Write a Brief They Can Quote On

The clearer your brief, the more accurate and comparable the quotes. Include:

I'll publish a fuller template soon in how to write a website brief for your developer. If you are wondering about timescales, see how long it takes to build a WordPress site.

Contracts, Handover and Support After Launch

A short, clear agreement protects both sides. Look for:

Tip: ask how the developer runs a project from start to finish. A clear process, like the one in my WordPress development process, is usually a better sign than a long list of features.

Frequently Asked Questions

What should I ask before hiring a WordPress developer?

Ask about similar projects and their exact role, their approach to themes and plugins, staging and backups, security, speed measurement, ownership of code and accounts, pricing for changes, handover and support after launch.

Should I hire a freelance WordPress developer or an agency?

It depends on the project. Freelancers often offer direct contact and flexibility; agencies can offer a wider team and more cover. The questions in this guide apply to both.

Who should own my WordPress hosting and domain?

Your business should. Register the domain and hosting in your name and add your developer as a user, so you keep control if you ever change developer.

How can I check a WordPress developer's portfolio?

Open the live sites, check they load quickly and work on mobile, and ask the developer what they personally built on each one. Ask to speak to a past client if possible.

Is a cheap WordPress developer a bad idea?

Not necessarily, but compare like for like. A lower quote may leave out testing, backups, security or support. Ask what is included, and what is not, before deciding on price.

Final Thoughts

To hire a WordPress developer well, be clear about the job, ask the 12 questions, watch for red flags and keep ownership of everything important. The right developer will welcome those questions, because they make the project smoother for both of you.

If you'd like to talk through a project, you can see how I work on my WordPress developer page, and bring these questions with you.

Ask specific questions, own your accounts, and agree the scope before work starts.

Official References

Sources checked on 29 October 2026: