What a website change should cost
By Ismael · Reviewed
A website change should cost what its evidence work and reversible delivery cost: a written scope, a URL and content inventory, a tested change set and a rollback path. SiteBienfait prices from a written estimate rather than a package. Google Search Central, updated 2026-06-05, advises that an audit should give realistic estimates of improvement and of the work involved.
What drives the cost of a website change?
Five inputs, and each one is countable. The number of live URLs determines the inventory and mapping work. The number of distinct templates determines the build work. The amount of content that has to move determines the migration work. The number of integrations — forms, booking, payments, analytics — determines the testing work. The measurement plan determines how long the work has to be monitored before anyone can call it finished.
A change that touches three templates on a twenty-page site is a different job from a change that touches thirty templates on four hundred pages. The estimate should make that difference visible, line by line, rather than presenting one number that could describe either.
What should a written estimate contain?
Deliverables named as artefacts. A URL inventory. A redirect map with one row per old URL. A preview link. A report against the SEO contract. A rollback plan. Dates for each gate, and a named approver. Assumptions and exclusions, written down: what is included in the count of pages, what happens when a page needs new copy, and who supplies the content.
Google Search Central, updated 2026-06-05, describes the expectation from the client’s side: an audit should give realistic estimates of improvement and an estimate of the work involved. That is the shape an estimate should follow. Any figure without a matching scope is a guess with a price.
Why is the cheapest change often the most expensive?
Because skipped work reappears later as a repair. Google Search Central, updated 2026-08-20, documents what a URL change requires: a mapping from old URLs to new ones, redirects in place, canonical tags updated, a sitemap submitted, both properties monitored. A change that skips the mapping and the redirects saves effort once and creates a recovery project.
The same page recommends splitting a move into smaller steps and changing one thing at a time, because a combined change makes the cause of a fluctuation impossible to isolate. Sequencing is not overhead; it is what makes the result diagnosable.
What should never be paid for?
Three things. A promised search position, because no provider controls the ranking systems and Google Search Central, updated 2026-06-05, states that Google never accepts money to include or rank sites. A report that cannot be traced to work that was performed. And a change that cannot be rolled back, because the site owner then carries all of the risk and none of the control.
The same guidance recommends asking any provider for previous work, for how success will be measured, and for a clear account of every change made to the site. Those questions are a better price test than a percentage discount.
How is the estimate checked against the invoice?
Map each invoice line to the estimate line it came from, and each one to an artefact that can be opened: the redirect map file, the preview URL, the contract report, the deployment record. If a line cannot be matched to an artefact, it is not necessarily wrong, but it is the first thing to ask about.
Then check the change itself. A change set should show what changed, not only that something changed. That is also what makes the monthly cost comparable between providers: the same scope should produce the same countable deliverables.
SiteBienfait’s build route publishes the scope of a change as a written estimate with the artefacts listed. The redirect map checker is part of how that scope is checked, since the URL mapping is one of the deliverables a quote either includes or does not. The website migration SEO checklist lists the full set of artefacts a move should produce, which is a practical way to compare two estimates for the same job.
Sources
- Google Search Central, Do you need an SEO?, last updated 2026-06-05.
- Google Search Central, Move a site with URL changes, last updated 2026-08-20.
- Google Search Central, Guidance on third-party SEO tools and advice, last updated 2026-06-05.
Questions
01 What drives the cost of a website change?
Scope that needs evidence: the number of URLs, templates, content migrations, redirects, integrations and measurement steps. Each one adds verification work, and a written estimate should name them rather than hide them in a single figure.
02 What should a written estimate include?
The deliverables, the assumptions, the exclusions, the dates and the approval points. Google Search Central, updated 2026-06-05, says an audit should give realistic estimates of improvement and an estimate of the work involved.
03 Should a website change be priced by the hour or fixed?
Either can work if the scope is written down. What matters is that the same document lists the artefacts: URL inventory, redirect map, preview, SEO contract report and rollback plan, so the invoice can be checked against it.
04 What should never be paid for?
Promised rankings, promised traffic and reports that cannot be traced to work performed. Google Search Central, updated 2026-06-05, notes that Google never accepts money to include or rank sites, and advises against anyone promising a specific search position.