How Much Do Small Website Updates Cost?
You need a few changes to your website. Nothing dramatic: a new employee, a different phone number, a service page that needs updating. Then someone asks for your budget, and you realize you have no idea what those changes should cost.
The honest answer is that small website jobs are priced by the work behind the change, not the number of words or buttons you can see. Changing an address in one well-built template is different from tracking it down in six page builders, a footer widget, and an old contact form.
You do not need to become a developer to buy this work sensibly. You need a clear request, an understandable estimate, and a way to keep surprises from becoming an invoice.
What the hourly rate actually tells you
An hourly rate is useful, but it is only half the price. The other half is the time needed to investigate, make the change, test it, and put it live.
At Web Dev Handyman, the standard rate is $120 per hour in USD, billed in 15-minute increments. A quarter hour is $30. There is no required monthly retainer, and small jobs are welcome. The scope and estimated work are discussed before billable work begins.
That is one pricing model, not a universal industry rule. For context, Codeable publishes recommended specialist rates of $80–$120 per hour, with its own platform fee structure. Other providers sell fixed tasks or prepaid blocks. Compare the scope and terms as well as the headline number.
Some useful budget examples
Here is what the math looks like at $120 per hour. These are planning examples, not quotes or promises about how long your site will take.
- 15–30 minutes: $30–$60. A straightforward text or image change when the location is known and access is ready.
- One to three hours: $120–$360. A small group of content changes, a contained layout repair, or investigation and correction of a relatively simple issue.
- A new page or a more involved repair: scope it first. Design, copy, forms, integrations, and the condition of the existing site can change the estimate substantially.
The same visible task can land in a different category depending on the website. “Fix the form” might mean correcting a recipient address. It might mean tracing a script conflict and an email delivery problem. Anyone giving a guaranteed price without knowing the issue is making assumptions somewhere.
Why the small things sometimes take longer
A developer usually needs to understand where the change belongs before editing it. Is the footer controlled by a theme file, a plugin, a widget, or the page editor? Does the same component appear across the site? Will an update overwrite a direct edit?
Access can add friction too. An expired invitation, missing hosting login, or unknown plugin license can stall a task that would otherwise be straightforward. Gathering those details before work starts is one of the easiest ways to keep a small job small.
Testing is also part of the work. A button can look right on a laptop and wrap badly on a phone. A changed email address can appear correctly on the page while the form still sends to the old inbox. A useful fix covers the behavior, not just the screenshot.
Send a request a developer can actually estimate
“The site needs some love” is relatable. It is also difficult to price. A short, specific list is much more useful.
Include the exact page address, what is happening now, and what should happen instead. A screenshot helps for layout issues. For an intermittent problem, include the device and browser you were using. If there is a real deadline, say so.
You do not need to diagnose the cause. “On my iPhone, the submit button disappears below the message box” is a good request. “It is probably a JavaScript race condition” is unnecessary unless you have evidence.
Keep passwords out of the initial contact message. Once the work is scoped, access can be arranged through an appropriate invitation or another secure method.
Agree on what happens if the scope changes
Some jobs reveal a second problem. The important thing is having a decision point before the second problem becomes additional work.
Ask what the estimate includes, whether investigation is billable, and when the developer will check back if more time is needed. For an unfamiliar issue, a capped first investigation can make sense: use an agreed amount of time to identify the cause, then decide on the repair.
A good estimate explains assumptions. It should not pretend the condition of an unseen website is already known.
Bundle related changes without building a giant project
If you have five content edits, send them together. One organized request makes it easier to identify shared templates, test related pages, and avoid repeated setup. That does not mean you need to save up six months of problems before asking for help.
Prioritize anything affecting inquiries first. A broken form matters more than a slightly dated team photo. An incorrect service area matters more than a decorative animation. Spend where the change helps a visitor take the next step.
For the current rate and how work is scoped, visit the website development pricing page. If your list is ready, see the kinds of small website updates I handle and send it over. A clear to-do list is a perfectly good place to start.