If the brief is vague, the budget will be vague too. That is the first thing I would fix before anyone opens a spreadsheet and starts sounding confident.
If you are trying to estimate a website restoration or update project, the questions are usually the same: How many pages are changing? Which parts are design work versus content work? What SEO cleanup is required? How much QA is enough before launch? That is not a trick. That is the budget.
Peter Drucker is often quoted for the line, “What gets measured gets managed.” Budgeting works the same way. Google’s SEO Starter Guide explains why clear structure matters for search, the WCAG quick reference shows why accessibility needs to be part of scope, and web.dev’s Core Web Vitals guidance is a reminder that performance is not a decorative extra.
In this guide, I will break the work into plain categories, show the cost drivers behind each one, and give you a simple way to estimate a realistic budget before you ask for quotes. If you want the broader site context, start at the home page, browse the blog, read the about page, or contact us when the spreadsheet starts looking philosophical.
Why budgets go wrong
Budgets usually fail for one of three reasons. First, the scope is written in soft language: “refresh the site,” “clean things up,” “make it modern.” Those phrases are useful in a conversation and terrible in a budget. Second, the project mixes different kinds of work and pretends they cost the same. A visual redesign is not the same thing as editing 30 product pages. Third, nobody defines the finish line, so the budget keeps expanding until somebody says the words every project manager fears: “while you are in there…”
The fix is not complicated. Define the work by category, count what is actually changing, and estimate each category separately. That gives you a budget that can survive contact with reality. A rare business luxury.
Scope in plain terms
Before you estimate cost, you need a shared vocabulary. I use these definitions:
| Scope area | What it means | What usually drives cost |
|---|---|---|
| Design | Layout changes, visual system updates, template adjustments, component cleanup, and responsive behavior. | Number of templates, number of revisions, complexity of mobile behavior, and whether the work is cosmetic or structural. |
| Content | Writing, editing, rewriting, page consolidation, migration cleanup, image replacement, and metadata drafting. | Page count, uniqueness of each page, amount of new copy, and how messy the source material is. |
| SEO | Redirects, titles, meta descriptions, internal links, indexability checks, canonical handling, and search safety during launch. | Number of URLs, redirect map size, whether pages are renamed or removed, and how much technical cleanup is needed. |
| QA | Testing forms, navigation, devices, browsers, performance, broken links, and basic accessibility checks. | Number of critical journeys, number of devices, form complexity, and how many rounds of retesting are required. |
| Functionality | Anything interactive: search, filters, bookings, forms, calculators, logins, or other behavior that is more than static content. | Integration complexity, third-party services, data flow, and whether the feature already exists or needs to be built. |
If the team cannot tell you which of those buckets a task belongs to, the task is not ready for pricing. That is how estimates grow a second set of teeth.
A simple cost model
I prefer planning budgets by scope band instead of pretending every hour is interchangeable. The exact market rate will vary by region, team size, and project risk, but the shape of the budget is usually predictable.
| Category | Typical planning range | Best used when |
|---|---|---|
| Design | $1,500 to $8,000 | You are updating a small site, tuning templates, or refreshing a handful of key screens. |
| Content | $1,000 to $6,000 | You need page edits, rewrite work, metadata cleanup, or moderate migration support. |
| SEO | $750 to $5,000 | You need redirect mapping, title/meta cleanup, internal link repair, and launch checks. |
| QA | $800 to $4,500 | You want device testing, form checks, and a basic accessibility/performance pass. |
| Functionality | $1,000 to $10,000+ | You are changing forms, search, filters, booking flows, or another interactive system. |
Those ranges are not promises. They are planning guardrails. If a vendor gives you a number with no scope breakdown, what they are really selling is optimism. Optimism is charming. It is also expensive.
A useful way to think about the total is:
Total budget = base design + content workload + SEO cleanup + QA passes + contingency
I would add a contingency of 10% to 20% for any project with legacy content, broken links, or “we should just move this one thing” behavior. That last item is especially skilled at expanding into a week of work.
Page and content workload estimator
The biggest budgeting mistake is counting pages without counting uniqueness. Ten pages that all use the same template are not the same as ten pages with different layouts, custom sections, and rewritten copy.
Count these separately
- Pages to update: the total number of public pages that need attention.
- Templates: the distinct layouts that need design or build work.
- Unique sections: special blocks that only appear on one page and need custom handling.
- Copy-heavy pages: pages that need substantial rewriting rather than light edits.
- Media cleanup: image replacement, sizing, cropping, compression, and alt text.
Here is a simple workload formula I use:
Content effort score = pages × 1 + templates × 3 + unique sections × 2 + copy-heavy pages × 2 + media cleanup pages × 0.5
You do not need to worship the formula. You need it to force the conversation out of vague territory and into counts. A spreadsheet loves counts. It ignores poetry.
Example 1: small brochure site
- 8 pages total
- 2 templates
- 3 unique sections
- 4 pages need copy edits
- 6 pages need image cleanup
That is modest work, but it still involves design judgment, editorial cleanup, and QA. It is not “just a quick refresh.” Nobody serious ever says that and means it.
Example 2: mid-size service site
- 20 pages total
- 4 templates
- 8 unique sections
- 12 pages need rewriting or restructuring
- 15 pages need media updates
This is where costs begin to separate sharply by process quality. A disciplined team will map content first, then design, then QA. A less disciplined team will “see how it goes,” which is a sentence that should always be followed by a budget warning label.
SEO and migration workload estimator
SEO work during a restoration or update is mostly about continuity. Preserve what is already working, change only what needs changing, and map every changed URL on purpose. Google’s guidance on site moves with URL changes is a useful reminder that redirects and structure are not decoration. They are operational.
Scope items that affect SEO cost
- Redirect map size
- Number of page titles and meta descriptions to rewrite
- Internal links that need correction after URL changes
- Indexing checks for new or removed pages
- Canonical handling on templates and archives
- XML sitemap and robots.txt review
- Search Console verification after launch
Here is the short version: the more URLs you touch, the more SEO work you have. There is no heroic shortcut here. The search engines are not impressed by confidence.
Budget rule of thumb for SEO
- Light SEO: a small set of redirects, metadata edits, and indexing checks.
- Moderate SEO: a full URL map, internal link cleanup, title/meta rewrite work, and post-launch monitoring.
- Heavy SEO: large migration, many removed pages, significant content consolidation, and careful launch monitoring.
If the site has years of content, treat SEO like a separate workstream, not a subtask. Otherwise you will discover broken links in the way people discover plumbing problems: late and with feelings.
QA and accessibility estimator
QA is not the final checkbox. It is the part that keeps the rest of the budget from becoming a public apology. The W3C’s WCAG quick reference is a practical standard to lean on when you want accessibility checks to be concrete instead of aspirational.
What to test
- Navigation on desktop and mobile
- Contact forms, validation, and submission handling
- Buttons, links, and menu behavior
- Image loading and layout consistency
- Basic performance on key pages
- Keyboard focus and visible states
- Color contrast and readable text sizes
- 404 handling and redirect behavior
A practical QA budget usually depends on how many real user journeys need testing. A homepage-only test is cheap. A site with forms, filters, search, and multiple breakpoints is not. That is not a complaint. It is accounting.
QA cost drivers
| QA dimension | What increases effort | Planning note |
|---|---|---|
| Devices | Desktop, tablet, and mobile checks across multiple sizes. | Testing two breakpoints is not the same as testing eight. |
| Forms | Validation, error states, spam protection, and submission routing. | Every form adds a chance for the invisible thing to fail. |
| Accessibility | Keyboard focus, headings, labels, contrast, and image alt text. | Basic checks catch the worst misses before visitors do. |
| Performance | Large images, scripts, fonts, and heavy page components. | Core Web Vitals guidance is useful for prioritizing the real bottlenecks. |
Common add-ons worth pricing separately
Some work is optional in theory and non-optional in practice. If the budget does not account for these items, somebody will eventually say they “weren’t in scope,” which is budget language for surprise.
- Analytics setup: worth it when you need reliable tracking before and after launch.
- CDN or performance tuning: worth it when media-heavy pages or traffic spikes are part of the site’s reality.
- Security hardening: worth it when the site processes forms, user data, or higher-value traffic.
- Staging environment: worth it when multiple stakeholders need review before production changes go live.
- Content governance: worth it when many people will edit the site after launch and nobody wants chaos with a CMS login.
These are not luxury items. They are the difference between a site that launches and a site that starts supervising everyone else.
Budget scenarios
Once the scope is clear, I like to package estimates into three scenarios. That makes the decision easier for non-technical stakeholders and stops every conversation from becoming a custom exception.
| Scenario | Usually includes | Planning range |
|---|---|---|
| Lean | Light design adjustments, limited content edits, a small redirect set, and basic QA. | $3,000 to $7,500 |
| Standard | Template cleanup, moderate content rewriting, SEO cleanup, form testing, and multiple QA passes. | $8,000 to $20,000 |
| Comprehensive | Broader design changes, large content migration, deeper SEO work, accessibility review, and performance tuning. | $20,000 to $50,000+ |
Use the lean budget when the site is small and the changes are contained. Use the standard budget when you need a meaningful upgrade without a full rebuild. Use the comprehensive budget when the site has enough history, content, or business risk that cutting corners would be false economy.
How I would decide
- If the site has fewer than 10 pages and only a few visual edits, lean is usually enough.
- If the site has several templates, core pages, and forms, standard is the safer default.
- If the site has many indexed pages, redirects, or accessibility concerns, comprehensive starts to look sensible very quickly.
What a clean quote should include
When you ask for a quote, ask the vendor to show the estimate in the same categories you used to define scope. Design should be separated from content. SEO should be separated from QA. Functionality should be called out when it exists. That does two things: it makes comparisons possible, and it makes change requests easier to discuss later.
- Scope by category: each major bucket gets its own line item.
- Assumptions: page counts, template counts, and revision limits are written down.
- Deliverables: the proposal states what will be handed over at the end.
- Exclusions: anything not included is named before work starts.
- Review process: it explains how feedback rounds and approvals will work.
- Contingency: it explains what happens if hidden issues appear during build or launch.
If the quote does not show those pieces, the project is not really priced. It is merely dressed up to look official, which is a classic corporate pastime.
Checklist before you lock the budget
Before you approve a quote, ask these questions:
- How many pages are changing, and which ones are the highest priority?
- How many templates or unique sections need design work?
- What content will be rewritten, and what content will be kept as-is?
- Who is responsible for redirect mapping and SEO checks?
- Are metadata updates included, or priced separately?
- How many QA rounds are included before launch?
- What devices, browsers, and breakpoints will be tested?
- Are forms, analytics, and security checks included in scope?
- What counts as a change request after the estimate is approved?
- What is the contingency if hidden issues appear in legacy content or technical setup?
If those answers are not clear, the project is not ready to budget. It is ready to improvise, which is a more expensive hobby.
One more decision point matters: fixed bid versus time-and-materials. A fixed bid works best when the scope is clean, the page count is known, and the team can describe the finish line without hand gestures. Time-and-materials makes more sense when the site has hidden complexity, the content is messy, or the business is still deciding what to keep. The wrong contract shape does not just change accounting; it changes behavior. Nobody should pretend that is a small detail.
Use the checklist to force the conversation into categories, counts, and finish lines. That is where the real estimate lives.
Two examples of realistic budgeting
Example A: small service site
- 6 to 8 pages
- 2 templates
- Light copy editing
- 10 to 15 redirects
- One contact form
- One QA pass plus fix-and-retest
This type of project often lands in the lean to standard band, depending on how much cleanup is needed. The work is manageable, but only if the scope is named clearly from the start.
Example B: larger content-driven site
- 20+ pages
- Several templates and custom sections
- Content rewrites on priority pages
- Metadata updates on many URLs
- Redirect map for removed or renamed pages
- Mobile, accessibility, and performance checks
- Analytics review after launch
This kind of project usually needs standard to comprehensive pricing, because the work is not just “make it look nicer.” It is a business decision about what to preserve, what to improve, and what to stop pretending is free.
Conclusion
A realistic website restoration budget starts with scope, not with a hopeful number pulled from the air. Count pages, templates, unique sections, redirects, forms, and QA journeys. Then price each category separately and add contingency for the parts that are always more annoying than they first appear.
If you do that, you get a budget that is easier to approve, easier to defend, and much less likely to implode in week two. A remarkable achievement for a spreadsheet.
Key points to remember:
- Scope drives cost more than the word “update” ever will.
- Design, content, SEO, and QA should be priced separately.
- Count templates and unique sections, not just pages.
- Redirects and metadata work belong in the estimate, not in the margin notes.
- QA and accessibility are budget items, not optional heroics.
If you are still deciding where to start, visit the blog for related guides, read the about page for context, or contact us when you want help turning scope into a clean quote.