How much does a professional website cost in 2026?
From creation and content to hosting and support: understand professional website pricing, compare quotes, and plan for post-launch costs effectively.
Sur cette page6 sections
You are looking for the price of a website and you find everything: a few hundred euros, a subscription, a quote for several thousand. Everyone talks about a "professional website", but no one seems to be selling the same thing.
It is not just a question of an expensive or cheap provider. A site that presents your services, a site that takes payments, and a site that organises your bookings can look quite similar. What they need to do behind the scenes is not.
To discuss the price, I therefore prefer to start with a day in your business. What do you want to avoid doing manually? What should the customer be able to find or request? And what happens once they have clicked?
In the third case, rules must be defined: duration, capacity, exceptional closures, failed payments, cancellations, modifications. This functionality then needs to be built and tested, including when things do not go as planned.
We are not just pricing a button. We are pricing what it involves in your organisation. Similarly, ten presentation pages can be simpler to build than a single management screen. This is why bespoke is not just for large companies, but it also cannot be reduced to a price per page.
One quote might state "five pages included" while expecting you to provide all the text and images. Another might include the consultations necessary to produce this content. These are not two ways of billing for exactly the same work.
You then have to count what continues: domain, hosting, external services, maintenance, then the planned content and follow-up. Some contracts group these elements into a subscription. Others only cover a part and leave the rest to be purchased or managed elsewhere.
I would separate the budget into three lines: creation, recurring costs, and future developments. This avoids comparing an entry price to an offer that already includes long-term support.
Support benchmarks are also very broad: approximately €80 to €250 excl. VAT per month for a first level, €200 to €500 for more extensive support, and €400 to €1,000 or more for a more demanding business tool. They should not be automatically added to every post: you must read what is included in the offer.
If you have a defined budget, the most useful thing is to say so and look for what can be built properly with it. We can sometimes start with a manually validated request before developing full availability management. The service works, you learn from its use, then you invest where repetition justifies automation.
For hosting, the price alone does not say what is covered. Does a backup exist? Who can restore it? Who monitors incidents? Is your email included? These answers must appear somewhere, especially if your business depends on the site.
SEO follow-up also requires a scope. Correctly preparing pages at launch is not the same service as producing articles every month, analysing requests, and evolving content. The phrase "SEO included" does not let you know what will actually be done.
The problem is not WordPress itself, nor AI itself. It is not knowing what was built, what dependencies exist, and who will be able to take over the project. A poorly organised bespoke site can be as difficult to maintain as a poorly assembled CMS.
The question of maintenance therefore belongs to the price discussion, not to a conversation put off until later. You are buying a tool that will live with the company, not just the screenshots from delivery day.
Then ask how you will modify a service after delivery, who will intervene in the event of a breakdown, and what costs will be added if an external service becomes necessary. Finally, have it clarified what you can recover if you change providers.
At Cadarsir, I want this discussion to lead to a clear scope, with a creation adapted to the activity and defined support. The goal is not to make you buy the biggest project. It is to build something you will actually use, and that we can evolve without starting the discussion from scratch every year.
It is not just a question of an expensive or cheap provider. A site that presents your services, a site that takes payments, and a site that organises your bookings can look quite similar. What they need to do behind the scenes is not.
To discuss the price, I therefore prefer to start with a day in your business. What do you want to avoid doing manually? What should the customer be able to find or request? And what happens once they have clicked?
The small feature that changes the whole quote
"I want a booking button." It is a short request. It could mean a simple link to your current tool, a form that you accept manually, or a system that calculates availability and takes a deposit.In the third case, rules must be defined: duration, capacity, exceptional closures, failed payments, cancellations, modifications. This functionality then needs to be built and tested, including when things do not go as planned.
We are not just pricing a button. We are pricing what it involves in your organisation. Similarly, ten presentation pages can be simpler to build than a single management screen. This is why bespoke is not just for large companies, but it also cannot be reduced to a price per page.
A creation price is not yet the website budget
Before going live, there is scoping, page organisation, text, visuals, design, development, and testing. These tasks can be grouped into one offer or appear separately. The important thing is to know who is doing them.One quote might state "five pages included" while expecting you to provide all the text and images. Another might include the consultations necessary to produce this content. These are not two ways of billing for exactly the same work.
You then have to count what continues: domain, hosting, external services, maintenance, then the planned content and follow-up. Some contracts group these elements into a subscription. Others only cover a part and leave the rest to be purchased or managed elsewhere.
I would separate the budget into three lines: creation, recurring costs, and future developments. This avoids comparing an entry price to an offer that already includes long-term support.
Benchmarks, not a price that guesses your project
To give an idea, here are three creation benchmarks, expressed in euros excluding VAT:- Approximately €2,000 to €5,000 excl. VAT to present an activity and facilitate contacts.
- Approximately €4,000 to €10,000 excl. VAT for a site with more refined sales journeys and adapted integrations.
- Approximately €10,000 to €25,000 excl. VAT, or more, for business processes, private areas, or more complex connections.
Support benchmarks are also very broad: approximately €80 to €250 excl. VAT per month for a first level, €200 to €500 for more extensive support, and €400 to €1,000 or more for a more demanding business tool. They should not be automatically added to every post: you must read what is included in the offer.
If you have a defined budget, the most useful thing is to say so and look for what can be built properly with it. We can sometimes start with a manually validated request before developing full availability management. The service works, you learn from its use, then you invest where repetition justifies automation.
What costs little can still be important
The domain often represents a small line in the budget. Yet it remains your company's address on the web. Look at its renewal, its owner, and account access, not just the first-year promotion. France Num explains these points.For hosting, the price alone does not say what is covered. Does a backup exist? Who can restore it? Who monitors incidents? Is your email included? These answers must appear somewhere, especially if your business depends on the site.
SEO follow-up also requires a scope. Correctly preparing pages at launch is not the same service as producing articles every month, analysing requests, and evolving content. The phrase "SEO included" does not let you know what will actually be done.
The cheapest site to deliver is not always the cheapest to keep
Tools, extensions, or generated code can be assembled quickly. This does not yet say how long a modification will take, nor what will need to be checked after an update.The problem is not WordPress itself, nor AI itself. It is not knowing what was built, what dependencies exist, and who will be able to take over the project. A poorly organised bespoke site can be as difficult to maintain as a poorly assembled CMS.
The question of maintenance therefore belongs to the price discussion, not to a conversation put off until later. You are buying a tool that will live with the company, not just the screenshots from delivery day.
Comparing two quotes by describing the same need
Take your main action: requesting a quote, booking, buying, or publishing a project. For each offer, ask what happens from start to finish, what you need to provide, and what remains your responsibility.Then ask how you will modify a service after delivery, who will intervene in the event of a breakdown, and what costs will be added if an external service becomes necessary. Finally, have it clarified what you can recover if you change providers.
At Cadarsir, I want this discussion to lead to a clear scope, with a creation adapted to the activity and defined support. The goal is not to make you buy the biggest project. It is to build something you will actually use, and that we can evolve without starting the discussion from scratch every year.
