How Much Does a WordPress Website Cost?
What a WordPress website really costs: US market ranges, our starting rates, the six cost drivers, an illustrative budget, quote tips and cheap-quote red flags.
Marcus Adeyemi
In the US market, a professionally built WordPress website typically costs $6,000 – $20,000 for a small marketing site, $20,000 – $75,000 for a business site with real integrations and a migration, and $75,000+ for a large or complex build. Where your project lands in those ranges depends far more on the number of unique templates, content readiness, integrations and migration than on the fact that it runs on WordPress.
That is the short answer to the question of WordPress website cost. The longer answer matters because WordPress is a platform, not a price point. The same software sits underneath a one-page site assembled from an off-the-shelf theme and a multi-language business platform with custom blocks, custom post types and a CRM integration. Quotes for "a WordPress site" can therefore differ by an order of magnitude and both be honest, because they describe different jobs.
This guide is for business owners, marketing leads and in-house teams who need a budget they can defend. It covers the pricing models you will meet and what each includes, how market ranges compare with our published starting rates, what actually drives the cost, an illustrative budget built from those figures, how to get a quote you can rely on, the red flags in cheap quotes, and how to budget for the site over the years after launch.
Pricing models for WordPress websites and what each includes
Before comparing numbers, make sure you are comparing the same kind of number. WordPress work is sold in a few distinct ways, and each one moves risk between you and the supplier differently.
- Fixed-price project One price for an agreed scope: templates, content, integrations, testing and launch. Scope changes are priced separately.
- Landing page or microsite One page or a handful, built accessible and fast, on a CMS you can edit. Our starting rate is from $4,800 per project.
- Marketing site A set of templates, real content, real integrations and a migration. Our starting rate is from $18,000 per project.
- Retained engineering A developer on your stack for an agreed share of each month. Our starting rate is from $145 per hour.
- Time and materials Billed for hours used against an estimate. Flexible, but the total is only known at the end.
- Phased build Discovery priced first, then the build quoted from what discovery found. Slower to start, far fewer surprises.
Fixed-price projects
A fixed-price project suits most marketing sites. The supplier carries the risk of the build taking longer than planned; you carry the risk of changing your mind. What makes a fixed price trustworthy is the scope document behind it: a list of templates, the integrations by name, the number of pages to migrate, the accessibility target, the browsers and devices tested, and what "launch" includes. A fixed price with a one-paragraph scope is not really fixed. Our article on what is included in a website design project lists the parts a complete scope should name.
Landing pages and microsites
If you need one page or a handful, for a campaign, a product launch or an event, a full site is often the wrong purchase. Our landing page or microsite work starts from $4,800 per project, with a published turnaround of 3–5 weeks. That covers a small number of pages built accessible and fast on a CMS your team can actually edit. If you are unsure which you need, landing page vs full website walks through the decision.
Marketing sites
This is the usual shape of a WordPress project: a set of templates, real content, real integrations and a migration from whatever came before. Our marketing site work starts from $18,000 per project, with a published turnaround of 8–12 weeks. The starting figure assumes a typical scope; more templates, more integrations or a large migration raise it.
Retained engineering
Retained engineering puts a developer on your WordPress stack for an agreed share of each month, starting from $145 per hour, with a published start within 2 weeks. It suits teams that already have a site and need continuous improvement: new blocks, performance work, plugin updates, integrations and fixes. It is also a sensible way to handle the months after a launch, when a new site always turns up a list of small changes.
Time and materials, and phased builds
Time and materials is honest when the scope genuinely cannot be known in advance, such as untangling an old site with undocumented customizations. Its weakness is that you carry all the risk of overruns, so it needs a cap, a weekly burn report and a clear definition of done. A phased build separates discovery from the build: you pay for discovery, receive a real specification, and then get a fixed quote for the build. For anything beyond a small site, it is often the best way to get an accurate number.
WordPress website cost: market ranges vs our starting rates
The table below sets reviewed US market ranges alongside our published starting rates. The market ranges describe what a professionally built site of each size typically costs. Our figures are starting prices, not guaranteed totals: a quote turns them into one number for your scope.
| Project type | Typical US market range | Our starting rate | Published turnaround | What it usually covers |
|---|---|---|---|---|
| Landing page or microsite | Not separately ranged | From $4,800 per project | 3–5 weeks | One page or a handful, accessible and fast, on an editable CMS |
| Small marketing site | $6,000 – $20,000 | Marketing site from $18,000 per project | 8–12 weeks | Five to fifteen pages, a handful of templates, a usable CMS, accessible and fast |
| Business site with systems | $20,000 – $75,000 | Quoted from scope | Quoted from scope | Custom templates, real integrations, structured content, a migration and a proper testing pass |
| Large or complex build | $75,000+ | Quoted from scope | Quoted from scope | Multi-language, complex integrations, design systems, or a site that is the product |
| Ongoing development | Not separately ranged | Retained engineering from $145 per hour | Start within 2 weeks | A developer on your stack for an agreed share of each month |
How to read the ranges
The ranges sit edge to edge, and projects move between them by complexity. A small marketing site with five pages, three templates and no integrations sits at the low end of $6,000 – $20,000. A fifteen-page site with more templates and a careful accessibility pass sits near the top, and a site that adds a CRM, a booking system and a migration crosses into the $20,000 – $75,000 band even if it has few pages. The labels describe complexity, not page count.
Our marketing site starting rate of $18,000 falls within the upper part of the small marketing site range and just below the business site range. That reflects what our starting scope includes: real content, real integrations and a migration, which is closer to the "business site with systems" description than to a brochure site. For a broader view that is not specific to WordPress, see how much a website costs.
What drives the cost of a WordPress site
Six factors move the price more than anything else. None of them is specific to WordPress, but each has a WordPress-specific shape worth understanding.
1. Number of unique templates
A fifty-page site with six templates is a much smaller job than a twelve-page site with eleven. Count layouts, not pages. In WordPress terms, a template is a distinct page layout: the home page, a service page, a case study, a blog post, a team profile, a location page. Each needs design, block or theme development, responsive testing and content entry rules. Once a template exists, adding pages that use it is mostly content work.
How those templates are built matters too. A block-based build gives editors flexible, reusable sections; a set of rigid page templates is quicker to build but harder to extend. Our guide to WordPress block development decisions covers the trade-offs, and structured content such as case studies, team members or locations is usually best modeled as custom post types, explained in getting WordPress custom post types right.
2. Content readiness
A site with copy and images ready moves at roughly twice the speed of one where content is written during the build. This is the single most underestimated driver. Developers can build templates without final content, but they cannot finish them: layouts change when real headlines are longer than the placeholder, when a service needs a table nobody planned for, or when photography arrives in the wrong proportions. If content will be written during the project, budget for it explicitly and expect the schedule to reflect it.
3. Integrations
A CRM, a booking system, a payment gateway, a legacy inventory feed: each one is a separate contract with somebody else's API and somebody else's outage. WordPress has plugins for many common integrations, and a good plugin can save real time. But every integration still needs configuration, data mapping, error handling, testing against the live service, and a plan for what the site does when the other system is down. Custom integrations with older or in-house systems cost more because there is no plugin and often little documentation.
4. Accessibility target
Meeting WCAG 2.1 AA from the start adds modestly to design and build. Retrofitting it later costs several times more. In practice, building to that target means color contrast checked at the design stage, keyboard navigation and visible focus states on every interactive element, proper heading structure in templates, form labels and error messages, and blocks that do not let editors create inaccessible content by accident. Themes marketed as accessible are a starting point, not a guarantee; the finished site, with its content and plugins, is what needs testing.
5. Migration
Moving a thousand existing pages, preserving their URLs and their formatting, is its own project with its own risks. Migration involves mapping old content types to new ones, cleaning formatting pasted in over years, moving media, building a redirect map for every URL that changes, and checking that nothing important was lost. It can be scripted, done by hand, or a mix of both, and the choice depends on how consistent the old content is. What a website content migration costs goes into the detail.
6. Who maintains it
Building something you can edit safely costs more up front than building something only we can change. It is almost always the cheaper of the two over three years. A site your team can update without calling a developer needs well-designed blocks, sensible restrictions, clear field labels and some training. A site that only a developer can change is cheaper to launch and then bills you for every edit afterward.
Myth: WordPress is free, so a WordPress website should be cheap.
Reality: The software is open source, but the cost of a site is design, templates, content, integrations, accessibility, migration and testing. Those costs are the same kind of work whichever CMS you choose, and they are what the ranges above describe.
How the time is spent, phase by phase
Cost follows time, so it helps to know where the time goes. A WordPress project typically runs through five phases. The durations below are the ranges for each phase; they vary with scope and do not simply add up to a fixed project length, because phases overlap and smaller projects sit at the short end of each range.
| Phase | Typical duration | What happens | What moves it |
|---|---|---|---|
| Discovery | 1–2 weeks | Goals, audiences, content inventory, integrations, technical constraints | How quickly stakeholders are available |
| Content and structure | 2–4 weeks, and this is the one that slips | Sitemap, content model, page outlines, copy and image sourcing | Content readiness and approvals |
| Design | 3–6 weeks | Design direction, template designs, component library | Number of templates and review rounds |
| Build | 4–12 weeks depending on template count | Theme and blocks, custom post types, integrations, content entry | Template count and integrations |
| Testing and launch | 1–3 weeks, plus the redirect map | Cross-browser and device testing, accessibility checks, performance, redirects, go-live | Migration size and fix list |
Content and structure is the phase that slips, and it is the one the client controls most. If you want to protect both the budget and the date, the most effective thing you can do is have content decisions made, and ideally content written, before design is finished. For more on schedules, see how long it takes to build a website.
An illustrative WordPress budget, built from published figures
The following example is illustrative. The company and its needs are hypothetical, and the figures are our published starting rates, not a quote. A real quote could be higher once scope is defined.
Imagine a professional services firm that needs a new marketing site on WordPress to replace an old one, a separate campaign microsite for a product launch later in the year, and ongoing development help after launch. The site has a modest number of templates, a CRM form integration and a migration of existing articles.
| Line item | Basis | Starting figure |
|---|---|---|
| Marketing site | From $18,000 per project | $18,000 |
| Campaign microsite | Landing page or microsite from $4,800 per project | $4,800 |
| Retained engineering, first year | From $145 per hour, assuming 10 hours a month for 12 months (120 hours; the hours are an illustrative assumption) | $17,400 |
| First-year starting total | Sum of the three lines | $40,200 |
The arithmetic: 10 hours a month for 12 months is 120 hours, and 120 hours at $145 is $17,400. Adding $18,000 for the marketing site and $4,800 for the microsite gives $22,800, and adding the $17,400 of retained engineering gives $40,200. That is a starting figure for the first year, not a ceiling.
What would push it up
If the discovery phase found that the firm needed eleven templates rather than six, that the CRM integration had to sync data both ways, or that the migration covered a thousand pages rather than a few dozen, the marketing site line would rise from its starting point. If the firm chose to write content during the build rather than before, the schedule would lengthen, which usually raises cost too. Each of these is one of the six drivers above.
What would bring it down
Having copy and images ready before the build, keeping the template count low, launching with fewer integrations and adding them later through retained engineering, and reusing the marketing site's blocks for the microsite would all hold the budget closer to the starting figures. The microsite in particular gets cheaper to build when it can reuse components that already exist.
How this compares with the market
The site itself, at a starting $18,000, sits inside the small marketing site range of $6,000 – $20,000 and just below the business site range of $20,000 – $75,000. With a real integration and a migration, the final quote for the site could reasonably land in the business site band. That is not a surprise to budget for; it is what those ranges describe.
How to get an accurate WordPress quote
An accurate quote is mostly the product of an accurate brief. Suppliers price uncertainty, so the more you pin down, the narrower and more reliable the number becomes.
- List the templates, not the pages. Walk through your current site and your plans, and write down each distinct layout. Note how many pages will use each.
- Name every integration. List each system the site must connect to (CRM, booking, payments, inventory, analytics, email), with the product name and what data moves in which direction.
- Describe your content status honestly. Say which content is written and approved, which exists but needs editing, and which does not exist yet. Say who will write it.
- Quantify the migration. Give the number of existing pages and posts, the content types, and whether URLs must be preserved. Export a sitemap if you can.
- State the accessibility target. Name WCAG 2.1 AA if that is what you need, so it is built in and priced from the start.
- Say who will maintain the site. Explain who edits content day to day, how technical they are, and whether you want ongoing development support.
- Ask for the quote itemized by phase. A breakdown across discovery, content and structure, design, build, and testing and launch shows where the effort is and makes quotes comparable.
- Ask what is excluded. Content writing, photography, hosting, premium plugin licenses, training and post-launch support are common exclusions. Get them in writing.
When comparing quotes, line them up against the same scope. A quote that is much lower than the others has usually left something out, and the exclusions list will tell you what. Our web design and development page explains how we scope and quote WordPress work.
Red flags in cheap WordPress quotes
A low price is not automatically a bad sign. A small site with few templates, ready content and no integrations genuinely costs less. The problem is a low price for a large scope, which usually means the missing work will reappear later as change requests, overruns or a site you cannot maintain.
Red flags: Be cautious when a quote shows any of the following.
- A single total with no breakdown by phase or deliverable, and no list of exclusions.
- No mention of content, migration or redirects on a project that replaces an existing site.
- A heavy multipurpose theme and a long list of plugins proposed as the whole build, with no plan for updates or conflicts.
- Integrations listed as "plugin setup" with no testing or error handling described.
- No accessibility target, or "accessible" claimed without naming a standard or a testing method.
- Admin access withheld, or the site built so that only the supplier can make changes.
- No testing phase, or testing described as "we check it on our phones."
- Unlimited revisions promised alongside a very low fixed price.
Why these matter
Each flag points to a cost that has been moved rather than removed. Missing redirects cost you search visibility after launch. A stack of overlapping plugins costs you in performance, security updates and conflicts every time something is updated. Accessibility skipped at build time costs several times more to retrofit. A site only the supplier can edit costs you every time you need a change. The cheapest quote is the one that stays cheapest over the life of the site, not on the day you sign.
WordPress-specific choices that change the price
Beyond the six general drivers, a handful of decisions particular to WordPress shape both the build cost and the running cost. They are worth settling in discovery, because changing them halfway through a build is expensive.
Off-the-shelf theme, custom theme or block theme
An off-the-shelf theme looks like a shortcut, and for a very small site it can be. The catch is that multipurpose themes carry features you will never use, which affects performance, and bending one to fit a specific design often takes longer than building the templates properly. A custom theme built around the block editor gives you exactly the templates you need and blocks your editors can use safely. It costs more to build, and it is usually the cheaper route over three years because there is less to fight against.
Page builders
Visual page builders let editors lay out pages freely. That freedom is useful for a marketing team that wants to experiment, but it tends to produce inconsistent pages, heavier markup and content that is hard to migrate later, because the layout is stored in the builder's own format. If you choose one, choose it deliberately and set rules for how it is used; if you do not need it, native blocks are usually the leaner option.
Multi-language
Running a site in more than one language on WordPress is well supported, but it multiplies content entry, testing and maintenance. Every template has to handle longer or right-to-left text, every integration has to pass the language along, and every update has to be checked in each language. This is one of the features that moves a project into the large or complex band.
Online store, memberships and logged-in areas
Adding a store, a members' area or gated content changes the character of the project. You are no longer building a site that presents information; you are building one that handles accounts, payments, emails and support questions. Scope these as systems in their own right, with their own testing, rather than as a plugin to be switched on.
Structured data and search
WordPress makes it easy to add structured data through plugins, but the best results come from templates that output accurate markup for the content they hold, such as articles, services, locations or events. Deciding this during the build is cheap; bolting it on later means revisiting every template.
Costs beyond the build
A WordPress website has running costs after launch, and a sound budget includes them. This guide does not quote specific prices for hosting, themes or plugins, because they vary widely by provider and change often, but every budget should have a line for each of the following.
- Hosting. Managed WordPress hosting, a general cloud host or your own infrastructure. The choice affects performance, security, backups and how much maintenance falls to you.
- Domain and email. Usually already in place, but worth checking who controls the domain account.
- Premium themes and plugins. Many are sold as annual licenses that need renewing to keep receiving updates. List every paid component and its renewal date.
- Updates and security. WordPress core, themes and plugins need regular updates, testing that the updates did not break anything, and monitoring.
- Integrations. The CRM, booking or payment systems your site connects to have their own subscriptions and occasionally change their APIs.
- Content and improvement. New pages, new templates, performance work and fixes. This is where retained engineering fits.
Rendering choices can also affect running costs. Caching strategy, and whether any part of the site is pre-rendered, change what hosting you need; settle those decisions during discovery so hosting is chosen for the site you are actually building.
How to budget for a WordPress site over time
The right horizon for a website budget is about three years, which is the period over which a maintainable build usually proves cheaper than one only a developer can change. Think of the budget in three layers.
Year one: build and settle
The build is the largest cost in year one, followed by a period of adjustments after launch. Every new site turns up small issues once real users and real content arrive: a form that needs another field, a template that needs a variation, a page that loads slowly on older phones. Budget for them rather than treating them as failures. Retained engineering, starting from $145 per hour, is one way to cover this without reopening the project contract.
Years two and three: maintain and improve
After launch, the steady costs are hosting, licenses, updates and a modest amount of development. The variable cost is improvement: new templates for new services, new integrations, performance and accessibility work. Teams that set aside a regular monthly allocation for improvement tend to avoid the cycle where a site is neglected until it needs a full rebuild.
Planning the next rebuild
A well-built WordPress site can be extended for years, but at some point the design, content model or integrations stop fitting the business. The costs of that rebuild are heavily shaped by the decisions made now: clean content structures and custom post types migrate easily, while content trapped in page-builder shortcodes does not. Keep an eye on migration effort as part of the long-term budget, because the content you add over the next three years is the content the next rebuild will have to move.
Verdict Budget for a WordPress website by counting templates, naming integrations, being honest about content, sizing the migration and fixing an accessibility target, then compare quotes against the same scope. Use the market ranges to sanity-check the numbers, treat our rates as starting prices, and plan the running costs over three years, not just the launch.
Is WordPress the right platform for your budget?
WordPress is a sound choice when you want an open platform, a large pool of developers, full control over hosting and a content model you can extend. It is less compelling when your team wants a fully hosted tool with no maintenance, or when the site is really an application. Platform choice changes where the cost sits more than whether there is cost: hosted builders move maintenance into a subscription, while open platforms move it into updates and development time.
If you are weighing options, compare the whole three-year picture rather than the launch price. Our comparisons of Wix vs WordPress and HubSpot CMS vs WordPress look at fit for different teams, with the same cost drivers applying whichever platform you choose. The number of templates, the integrations, content readiness, accessibility, migration and maintainability will shape your budget on any CMS.
When a lighter option is enough
If what you need is a single campaign page, a small event site or a product launch page, a landing page or microsite may do the job at a fraction of the effort of a full marketing site. If what you need is a platform for a growing content operation, sales team and integrations, it is worth investing in the full build and the maintainable editing experience that goes with it.
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.
