Hiring a WordPress developer for a US business costs about $15 to $28 an hour on Upwork (median $20), $80 to $120 an hour on Codeable, a vetted WordPress platform, and $100 to $149 an hour on average at a US web development company, according to Clutch. But the rate tells you less than six simple checks do. Does the developer work on staging, keep code in Git, measure Core Web Vitals, pick plugins carefully, know your page builder, and hand you full ownership of the code and accounts?
I'm Mohit Goyal, a WordPress developer in Gurugram, India. In 4+ years I've shipped 100+ sites for clients in India, the UK and the US. This is how I'd hire if I were in your seat.
How much does it cost to hire a WordPress developer in the US?
Anywhere from $15 an hour on an open marketplace to $250+ an hour at a WordPress agency. The hiring route moves the price far more than WordPress itself does. Clutch's pricing guide found that hourly rates barely change by tech stack. Location, team size and experience are what move them.
| Hiring route | Typical rate | Source |
|---|---|---|
| Open marketplace (Upwork) | $15–$28/hr, median $20 | Upwork |
| Experienced independent developer | Most land between $60 and $130/hr | FreshySites |
| Vetted WordPress platform (Codeable) | $80–$120/hr, 17.5% service fee included | Codeable |
| US web development company | $100–$149/hr on average | Clutch |
| WordPress agency | $100–$250+/hr, or $5,000–$55,000+ per fixed project | Codeable |
| In-house web developer | Annual salary plus benefits; see the current median pay | BLS |
Two notes on that table. Upwork's figures cover its global talent pool, so the low median reflects a lot of offshore developers, not US freelancers. And the same Clutch guide puts India-based web development companies at under $25 an hour on average. That gap is why so many US and UK firms look offshore. My post on outsourcing web development to India is written for UK firms, but most of it applies to US buyers too.
Don't compare hourly rates on their own. A developer who charges less but needs three times the hours isn't cheaper. Neither is one who leaves you a site you have to rebuild in a year. Write one scope, send it to every candidate and compare fixed quotes. If you don't have a scope yet, the free Project Scope Generator on my site turns a two-line idea into a structured one you can send out.
Should you hire a freelancer, an agency or a marketplace developer?
Go with an agency for large builds with many stakeholders, a senior freelancer for focused builds where you want direct contact, and an open-marketplace developer only if you can vet code yourself. Each route puts the risk somewhere different.
- Open marketplaces like Upwork are the cheapest, but you do all the technical vetting. If you can't read code, that's a real risk.
- Vetted platforms like Codeable screen developers and give you one fixed estimate. You pay for that screening through the platform fee.
- Agencies bring a project manager, QA and designers. Useful on big builds with lots of people signing off, but you're paying for the overhead.
- A senior freelancer, hired directly, means you talk to the person writing the code. The risk is a single point of failure, so ask who covers holidays, illness or a sudden rush.
I'm in that last group. When a project needs design, a mobile app or Shopify, I bring in partners I trust, and I stay your single point of contact.
Can a WordPress developer in India work with US hours?
Yes. East Coast mornings overlap with Indian evenings, and West Coast teams mostly work through written updates. India Standard Time is UTC+5:30 with no daylight saving. US clocks change twice a year, so the gap shifts with them (check exact times on timeanddate.com).
| US time zone | Gap in summer (DST) | Gap in winter | 9am your time is |
|---|---|---|---|
| Eastern | India 9h 30m ahead | 10h 30m ahead | 6:30pm / 7:30pm IST |
| Central | 10h 30m ahead | 11h 30m ahead | 7:30pm / 8:30pm IST |
| Mountain | 11h 30m ahead | 12h 30m ahead | 8:30pm / 9:30pm IST |
| Pacific | 12h 30m ahead | 13h 30m ahead | 9:30pm / 10:30pm IST |
Arizona is the exception: most of the state doesn't observe daylight saving, so it stays on Mountain Standard Time all year, 12h 30m behind India.
On the East Coast, your morning is the developer's evening, which is plenty for a short call. On the West Coast, live overlap falls late at night in India, so most of the work runs on written updates. That works well: you review the staging site in your afternoon and leave feedback. The developer works on it during the Indian day, and the fixes are waiting for you when you sit down the next morning.
Settle a few things up front: a fixed weekly call window, a written update at the end of each working day, and one shared task board so feedback doesn't get buried in email. Schedule the launch for a time when you're both awake, and have the developer on hand for the first few hours after it goes live.
What should you check before you hire a WordPress developer?
Check six things: staging, Git, Core Web Vitals, plugin choices, page-builder experience and ownership of the code and accounts. Between them, they catch most bad hires. Ask about each one on the first call.
1. Do they build on a staging site?
Nobody should be editing your live WordPress site directly. Ask how they set up staging, how changes get to production, and what happens to WooCommerce orders or form entries that land on the live site during the build. If the answer is vague, that's a red flag.
2. Is the code in Git, in a repository you own?
Custom themes, child themes and custom plugins belong in a Git repository under your organization on GitHub or GitLab, not on the developer's laptop. Page-builder layouts live in the WordPress database, which Git doesn't cover, so also ask how they back those up and export them.
3. Do they measure Core Web Vitals?
Google's "good" thresholds are LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1, according to web.dev. Ask for before-and-after PageSpeed Insights reports from past projects, and write passing scores into the deliverables. Run your current site through PageSpeed Insights before the first call so you know where it fails today. Paste that report into my free Page Speed Fix Planner and you'll get a plain-English list of what's failing and why.
4. How do they choose plugins?
Ask for the planned plugin list with a reason for each one. Good developers use fewer plugins, pick ones that are actively maintained, and know when one small custom plugin beats three generic ones. I maintain two plugins on WordPress.org: HTTP Security Header, with 1,000+ active installs, and Geo Targeting for Bricks Builder. Keeping them working through WordPress updates taught me what to look for in other people's plugins, and I run that same test before any plugin goes on a client site.
5. Do they actually know your page builder?
Bricks, Elementor and Oxygen work very differently. Being good at one doesn't make someone good at another. Ask for live sites built in your builder, and ask how they set up global classes and templates so your team can edit pages without breaking the design. Not sure which builder to use? My comparison of Bricks, Elementor and Oxygen walks through the trade-offs, but if your team already knows one, that's usually the right pick.
6. Who owns the code and the accounts?
Under US copyright law, a contractor's work only counts as a "work made for hire" in limited categories, and only with a written agreement. See the US Copyright Office's Circular 30. The safe route is a written assignment of copyright in the contract, taking effect on final payment. Get a lawyer to check the wording.
Keep every account in your name
Register the domain, hosting, Stripe, GA4 and premium licenses such as Bricks or Elementor Pro in your company's name, and give the developer user access. If they disappear, you still have everything.
If you're already locked out by a past developer, my guide on how to take back your WordPress site when a developer disappears covers the steps.
On paperwork, a foreign contractor usually gives a US business a Form W-8BEN instead of a W-9. Confirm the details with your accountant.
What proof should a WordPress developer show you?
Live sites, at least one case study that explains a problem and how it was solved, and ideally a past client you can talk to. Screenshots don't count. Here's what I point people to:
- 100+ sites in 4+ years, built on Bricks Builder, Elementor and Oxygen, plus custom themes and WooCommerce.
- Ravens Ait: a WordPress and Bricks Builder site for a Thames island venue, with 20+ event pages, Stripe bookings and HubSpot forms. I built it while delivering client sites remotely for a London agency, working across the UK–India time gap.
- Nortek LED: a WooCommerce store built pixel-perfect from Figma on a custom Oxygen Builder theme, with product filters and an optimized checkout. Post-launch analytics showed a 30% increase in average session duration, a 20% uplift in conversion rate and 35% faster load times.
- Two WordPress.org plugins that anyone can install, read and review.
What should you ask on the first call?
Cover live work in your builder, staging, Git, Core Web Vitals, plugins, working hours, ownership and post-launch support. These are the questions I'd ask:
- Can I see three live sites you built in my page builder?
- How do you set up staging, and how do changes reach the live site?
- Will the code be in a Git repository my company owns?
- What Core Web Vitals scores will the site hit at launch, and how will you prove it?
- Which plugins will you install, and why each one?
- When can we talk live each week, and how will you send written updates?
- Does the contract assign the copyright to us, and are all accounts in our name?
- What happens after launch: is there a bug-fix window, and a maintenance retainer if we want one?
Someone who knows their job answers these without much thought. If a candidate dodges the staging, Git or ownership questions, move on, however low the rate is.
Ready to brief a WordPress developer?
Write down what the site needs to do, which builder your team prefers and your launch date. Then book a 20-minute discovery call and I'll go through the scope with you, including how we'd split working hours across our time zones. If you want to see how I build on each builder first, have a look at my WordPress websites on Bricks, Elementor and Oxygen service page.
