The questions to ask a WordPress developer before hiring are the ones that show how they build, not only what they have built: who will own the code, how you will edit the site, how many plugins they use and why, how they handle speed, security and SEO, and what happens after launch. A portfolio shows you the result. These questions show you what you will be living with for the next five years.
I have been on the answering side of these questions for twelve years and more than 150 sites. Here are the twelve I would ask, and what a good answer sounds like.
About the build
1. Will you build from a theme, or from scratch?
Neither answer is wrong on its own, but you should know which you are getting. A good answer explains the choice for your project. A $59 theme with your logo on it is fine for some businesses and a trap for others, especially if the theme bundles a dozen features you will never use.
2. How many plugins will the site use, and why each one?
Listen for a developer who can name what each plugin does and why it earned its place. “Whatever it needs” is not an answer. Every plugin is code that runs on your site, needs updates and can conflict with the others. I wrote about the cost of a bloated stack in why your WordPress site is slow.
3. Can I edit the site myself without breaking it?
You want to hear about global colors and fonts, templates for repeating layouts, and real widgets instead of hard-coded sections, followed by a walkthrough at handover. If every change needs the developer, the site was built for them, not for you. Here is how I approach it: Elementor website design your team can edit.
4. Where will my business data live?
If the site will store bookings, leads, applications or orders, ask how. A developer who has thought about it will talk about database design and keeping that data fast as it grows. The details are in custom post types vs custom tables.
About ownership and money
5. Who owns the code and the accounts?
You should. The domain, the hosting, the site and any custom code should be in your name or handed over to you. A developer who keeps the keys keeps your business on a leash. I cover what to check when a project ends in WordPress security best practices.
6. Do you bill hourly or by milestone?
Both can work. What matters is that the scope is clear, progress is visible and you know what happens when the plan changes. I work either way and prefer hourly: we agree on a rate and weekly hours, and if I go over to hit my own goals for the week, you do not pay for the extra.
7. How are payments protected?
Through a platform like Upwork, the money is held until you approve the work, every message and file stays in one place, and you can see the developer’s verified work history. That protection runs both ways, which is why I take projects through Upwork.
About quality
8. How do you make the site fast?
A good answer mentions image sizes and formats, loading only what each page needs, caching, and testing with real tools. Ask what Core Web Vitals scores their recent sites get. My Core Web Vitals fix list shows what to look for.
9. How do you handle security?
Listen for updates, least-privilege accounts, two-factor sign-in, off-server backups and secure custom code. A developer who knows the official WordPress hardening guide will recognize every item. “We install a security plugin” on its own is a weak answer.
10. What is your approach to SEO?
Be careful with anyone who promises page one or talks only about installing an SEO plugin. A real answer covers site structure, page content that answers real questions, speed, structured data and redirects if you are replacing an old site. I explain why plugins alone do not rank sites on my SEO Illusion page, and how answers matter now in answer engine optimization.
About after launch
11. What happens when something breaks after launch?
Ask how long they support the work, how fast they respond, and what changes cost later. Every plugin I deliver comes with six months of updates and small features, free tweaks under five hours, a discounted rate for bigger changes, and free security updates.
12. Can you show me a project like mine, and what changed for that client?
Results beat screenshots. A good developer can tell you what the client’s problem was, what they built and what changed afterward, like leads per day or hours saved. You can see how I present mine on my work page.
Red flags
- They want admin access and ownership kept in their own accounts.
- They cannot explain why a plugin is on the list.
- They guarantee rankings.
- They go quiet about what happens after launch.
- The quote has no scope, only a number.
Frequently asked questions
Should I hire a freelancer or an agency for a WordPress site?
Both can do great work. A freelancer usually means working directly with the person building your site, often at a lower cost. An agency can cover more roles at once. Ask both sets of questions above either way.
How do I check a WordPress developer’s work?
Visit live sites they built, not only screenshots. Test them on your phone, run them through PageSpeed Insights, and ask the developer what they did on each one.
Is it safe to hire a WordPress developer on Upwork?
It is one of the safer ways to start, because payments are protected and the work history is verified. Read the reviews closely and start with a clear scope.
