Most people searching for a WordPress developer are really trying to answer two questions at once: what should this cost, and how do I avoid hiring the wrong person again. Both are answerable. WordPress still runs a large share of the web, which means the talent pool is enormous and wildly uneven. A $25 per hour freelancer and a $140 per hour developer can both call themselves the same thing and produce results that are nothing alike. Here is how the money actually breaks down, and what to check before you sign anything.
Hiring a WordPress website developer in the US typically costs $60 to $150 per hour, or $3,000 to $25,000 for a full custom build depending on page count and functionality. Small fixes run $150 to $600. Ongoing maintenance retainers usually land between $100 and $500 per month.
What does a WordPress developer actually cost?
Rates in the US vary more by engagement type than by geography. A developer in Ohio and one in New York often quote within 20 percent of each other for the same scope, because the market is remote by default. What moves the number is whether you are asking for a fix, a customization, or something built from nothing.
The ranges below reflect what agencies and experienced freelancers quote in the US market in 2026. Offshore rates run considerably lower, often $20 to $45 per hour, with the usual tradeoffs in communication overhead and code quality.
| Engagement | US hourly range | Typical project cost | Timeline |
|---|---|---|---|
| Small fixes and bug repair | $75 to $150 | $150 to $600 | 1 to 3 days |
| Theme customization (existing theme) | $60 to $120 | $1,200 to $5,000 | 1 to 3 weeks |
| Custom theme build from design | $85 to $150 | $6,000 to $25,000 | 4 to 10 weeks |
| Custom plugin development | $100 to $175 | $3,000 to $20,000 | 3 to 8 weeks |
| WooCommerce store build | $85 to $160 | $8,000 to $40,000 | 6 to 14 weeks |
| Monthly maintenance retainer | n/a | $100 to $500 per month | Ongoing |
| Speed and Core Web Vitals work | $90 to $160 | $1,500 to $6,000 | 2 to 4 weeks |
Two things distort these numbers. First, page count matters less than component count. A 30 page site built from eight reusable blocks is cheaper than a 6 page site where every page is bespoke. Second, content. If you have not written the copy, either you write it or you pay someone $75 to $200 per page to do it.
Ask every candidate to break their quote into design, build, content, and post launch support as separate lines. Quotes that arrive as one number hide where the money goes, and they are the ones that generate change order arguments in week six.
Designer, developer, or page builder installer?
These three roles get advertised under the same search terms and they are not interchangeable. Hiring the wrong one is the single most common expensive mistake we see.
A WordPress website designer works on layout, hierarchy, typography, and how the site looks and feels. They may deliver Figma files and never touch code. Good ones think about conversion paths as much as aesthetics.
A WordPress web developer writes PHP, JavaScript, and CSS. They build custom themes, extend plugins, handle database queries, and fix things that page builders cannot reach. They may have no design instinct at all, and that is fine if you already have a designer.
The third category has no formal name, so call it what it is: someone who installs a premium theme, configures Elementor or Divi, drops in stock content, and hands it over. That work has a real place. If you need a five page brochure site quickly and cheaply, it is often the right answer. The problem is when it gets sold at custom development prices, or when the resulting site accumulates 40 plugins and becomes impossible to maintain.
How to tell which one you are talking to
- Ask what happens when a plugin update breaks the layout. A builder installer says they will contact support. A developer says they will check the changelog and patch the child theme.
- Ask to see a custom post type they built and what it was for. If the answer is vague, they configure rather than build.
- Ask which page builder they use and why. "None, I write templates" and "Elementor because the client updates it themselves" are both good answers. "Whatever the theme came with" is not.
- Ask for a GitHub or Bitbucket link. Not every good freelancer has public code, but a developer who has never used version control on a client project is a real risk.
A vetting checklist that actually filters
Portfolios are the least reliable signal in this industry, because you cannot tell who did what. A shared screenshot proves nothing about whether the person built the site or swapped a logo on it. These checks are harder to fake.
- Run two or three of their live sites through PageSpeed Insights on mobile. Scores under 50 across an entire portfolio suggest they ship and leave.
- View source on a portfolio site. Count the render blocking scripts. Look for whether CSS is minified and whether images are served as WebP or AVIF.
- Ask who owns the code and the hosting account at the end. The correct answer is you, on your own accounts, with admin credentials handed over.
- Ask what their handoff includes. A staging environment, a plugin inventory with license details, and a short walkthrough recording should be standard.
- Request one reference from a client whose project went badly. Anyone with three years of experience has one. How they describe it tells you more than five glowing reviews.
- Confirm whether the quote includes revisions and how many. Two rounds per page is normal. Unlimited revisions usually means the price already absorbs the risk.
The maintenance reality of WordPress
WordPress is free to install and not free to run. This is the part that gets skipped in sales conversations, and it is where most site owners get frustrated 18 months in.
Core updates arrive several times a year. Plugin updates arrive constantly, sometimes weekly for the busier ones. Each update carries a small chance of conflicting with your theme or another plugin. That chance is small per update and meaningful across hundreds of updates a year. Security is the other half: WordPress is targeted heavily precisely because it is popular, and the overwhelming majority of successful attacks come through outdated plugins rather than core.
Then there is plugin bloat. A site that starts with eight plugins tends to reach twenty within two years, because every new requirement gets solved by installing something. Each one adds queries, scripts, and another update to track. We have seen sites where removing nine plugins and replacing them with 200 lines of theme code cut mobile load time in half.
| Maintenance item | Frequency | What it prevents |
|---|---|---|
| Core and plugin updates on staging first | Every 2 to 4 weeks | Live layout breakage |
| Offsite backups with tested restore | Daily, restore tested quarterly | Total loss after a hack |
| Plugin audit and removal | Twice a year | Speed decay, attack surface |
| Uptime and malware scanning | Continuous | Silent downtime, blacklisting |
| PHP version upgrades | Annually | Security gaps, host deprecation |
Budget $100 to $500 per month for this, or accept that you will pay a developer $600 in emergency fees the day something breaks. The retainer is cheaper and less stressful. If you are running a store or generating leads through the site, the emergency route is not really an option.
When should you not use WordPress at all?
Worth asking before you hire anyone. If your site is under ten pages, changes rarely, and needs no logged in users or complex forms, a static build or a hosted platform will cost less to own over five years. If you are selling physical products at volume, Shopify handles the payment, tax, and inventory layer better than WooCommerce does without significant development. Our Shopify development team gets a steady stream of migrations from WooCommerce stores that outgrew their plugin stack.
WordPress earns its place when you publish frequently, need editorial workflows, want non technical staff editing pages, or need custom content structures. That is a large share of businesses, which is why it is still the default. Just choose it deliberately rather than by inertia.
Before requesting quotes, write down every page type your site needs and every action a visitor should be able to take. Two pages of that document will get you more accurate bids than an hour long discovery call, and it makes comparing three proposals straightforward instead of guesswork.
How to structure the engagement
Fixed price works for well defined scopes: a marketing site, a theme rebuild, a migration. Hourly works for open ended work where the requirements will shift, like a product site with an unclear roadmap. Retainers work once the site is live and needs steady attention.
- Start with a paid discovery, typically $500 to $2,500, that produces a sitemap, functionality list, and firm quote. Anyone unwilling to charge for discovery is guessing at your scope.
- Split payment into three or four milestones tied to deliverables, not dates. Design approved, templates built, content loaded, launched.
- Insist on a staging URL from week one so you can watch progress instead of waiting for a reveal.
- Agree on a defect window, usually 30 days post launch, where bugs are fixed at no cost.
- Move to a maintenance agreement before launch day, not after the first problem.
If your requirement sits at the smaller end, a straightforward marketing site with strong copy and a clear conversion path, our website design and development team handles that as a fixed scope package. And if the goal of the site is lead generation rather than presence, spend part of the budget on conversion optimization instead of adding pages nobody reads.
Frequently asked questions
How much does it cost to hire a WordPress developer in the US?
US WordPress developers typically charge $60 to $150 per hour. Small fixes cost $150 to $600, theme customization runs $1,200 to $5,000, and a custom theme build from a design usually falls between $6,000 and $25,000. WooCommerce stores start around $8,000 and can exceed $40,000 once you add custom checkout logic or ERP integrations. Offshore rates are lower, often $20 to $45 per hour, with more coordination overhead.
What is the difference between a WordPress designer and a WordPress developer?
A WordPress designer handles layout, typography, hierarchy, and visual direction, often delivering Figma files without writing any code. A WordPress developer writes PHP, JavaScript, and CSS to build custom themes, extend plugins, and solve problems a page builder cannot reach. Most projects above $8,000 need both. Below that, one hybrid person is usually enough, but confirm which half of the skill set is genuinely strong.
Do I need ongoing WordPress maintenance after launch?
Yes. WordPress core updates several times a year and plugins update far more often, with each update carrying a small risk of conflict with your theme. A workable baseline is updates applied on staging every two to four weeks, daily offsite backups with a tested restore, continuous malware scanning, and a plugin audit twice a year. Budget $100 to $500 per month. Skipping it means paying emergency rates later.
How long does it take to build a WordPress website?
A five page brochure site on a customized theme takes one to three weeks. A custom theme built from an approved design usually takes four to ten weeks. WooCommerce stores run six to fourteen weeks depending on catalog size and integrations. The biggest delay in almost every project is content. Sites sit waiting on client copy and photography far more often than they wait on code, so start writing early.
Is it safe to hire a freelance WordPress developer instead of an agency?
Freelancers are often better value for defined scopes under $10,000, provided you own the hosting and domain accounts and receive all code and credentials at handoff. The main risk is availability. One person gets sick, takes on other work, or stops replying, and you have no backup. Agencies cost more but carry redundancy and documented process. If the site drives meaningful revenue, that redundancy usually pays for itself.
Should I use a page builder like Elementor or a custom theme?
Use a page builder when non-technical staff need to edit pages regularly and the design is fairly conventional. Use a custom theme when performance matters, the design is distinctive, or you need content structures a builder cannot model cleanly. Builders add CSS and JavaScript weight that shows up in Core Web Vitals, especially on mobile. Block themes with reusable patterns sit between the two and suit most marketing sites well.
The takeaway
Hiring well here comes down to two decisions: matching the role to the work, and paying for maintenance before you need it. If your project is a marketing site with clear pages and a conversion goal, a strong generalist at $70 to $110 per hour will serve you better than a specialist at $160. If it involves custom data structures, integrations, or a store, pay for the specialist and expect the timeline to double. Either way, own your accounts and keep the plugin count honest.