Website Renovation Cost and Timeline: What Affects Scope

The short version #

A renovation quote isn't really a number. It's a function of seven variables: page count, design depth, CMS choice, languages, content migration, SEO preservation, and integrations. Every project goes through six phases (audit, information architecture, design, build, content, QA and launch), and skipping one phase always shows up later somewhere else. "Just reskin it" sounds cheap and almost never is, because the messy URLs and stale plugins underneath are what actually cost real money. If budget is tight, ship an MVP first: home page, three service pages, one or two cases, then add depth from there. Three common tiers we see in the market: a light fix at $7K–$11K and 4–6 weeks, a standard rebuild at $17K–$35K and 8–12 weeks, a growth-grade site at $42K–$85K and 12–20 weeks. The comparison table at the bottom is the version you can take into your next vendor meeting.

A client called last month and opened with "how much for a new site?" There's no honest answer to that question, in the same way there's no honest answer to "how much to renovate a house?" The actual situation, once we got into it: a 2018 WordPress build, six-second homepage on mobile, a contact form nobody had checked in nine months, twenty blog posts in mixed Chinese-English, and nobody still at the company had Search Console access. You can reskin it for $4K and end up at the same place six months later, because the foundation didn't change. Or you can do everything that needs doing and the number lands closer to $80K. Neither answer is wrong. Which one is right depends on what they're actually trying to fix.

This piece is the framework we use to figure that out, written so you can hold your own when the next vendor sends a quote.

Cost variables #

1. Pages #

Page count is the baseline. A standard service-business site usually has a homepage, three to six service or product pages, an About page, a case studies index, individual case study pages, a blog index, blog posts, a contact page, and the legal trio (privacy, cookies, terms). That's typically twelve to fifteen distinct templates.

The variable is whether case studies and blog posts share a layout. If your cases need data charts, embedded video, and custom hero treatments, each one becomes its own template. If they're text with a few images, you reuse one. Each additional language multiplies content effort by 1.3–1.5 (not 2, because the structure carries over), but it nearly doubles QA time. Every navigation state, every form validation message, every dynamic string gets checked twice.

2. Design #

Three depths:

• Theme-based: grab a ThemeForest or Elementor template, swap colors and logo. Visual coherence suffers. Two weeks. The cheap part is real; the price is that six months in, your team starts saying "this doesn't look like us."
• Semi-custom: a small design system, custom homepage and key service pages, common templates for everything else. The right answer for maybe 80% of mid-market companies.
• Full custom: every page designed individually, custom illustrations, motion, custom typefaces. Design alone runs 30–40% of project cost. Worth it when brand is a top-three priority for the business.

Designers price by the day. Mid-level UI designers in our region are $300–$500 per day. A full custom site usually takes one designer 15–25 working days.

3. CMS #

WordPress is still the most economical answer for small and mid-sized companies, especially those exporting overseas. It's open source, the ecosystem is deep, and external help is easy to find. The hidden cost is what happens after launch (plugin updates, security patches, performance tuning), which most people underestimate.

Hosted options like Webflow and Framer ship faster and almost run themselves, but monthly fees add up and customization hits a ceiling early. Good fit for content-heavy brand sites that don't need deep backend integration.

A headless setup — Strapi, Contentful, or Sanity paired with Next.js or Nuxt — costs roughly 1.5–2x WordPress upfront. In exchange you get better performance, finer SEO control, and cleaner integration with whatever ERP or CRM you already run. We default to this when the brief says "this site has to talk to our internal systems."

For the actual decision tree, see WordPress vs Custom Website vs Shopify.

4. Languages #

The most common mistake is translating an existing site instead of rewriting for the new audience. Buyers in Berlin or São Paulo can smell machine translation in two sentences, and the conversion damage is real. Genuine localization means rewriting copy, reordering case studies, and picking local keywords. Each additional language runs roughly 60–80% of the primary language's content budget, plus one to two weeks of extra QA.

5. Migration #

Existing content, URLs, images, cases, and form data don't migrate themselves. The traps we've seen, in rough order of how much they hurt:

• Old URLs without 301 redirects — traffic drops 30–40% in the first week and recovery takes months.
• Hardcoded image paths in old posts — every image 404s after launch.
• Form submissions never exported — months of warm leads gone.
• robots.txt set to Disallow: / on staging and forgotten at launch — the entire site disappears from Google for whatever stretch you don't notice.

Bad migration outranks bad design as a project killer. Detailed playbooks: Website Content Migration Checklist and How to Preserve SEO During a Website Rebuild.

6. SEO #

If the existing site has organic traffic, the rebuild needs an SEO preservation plan: a URL mapping table, 301 redirects, structured data, sitemap submission, and a Search Console comparison against pre-launch baselines. The technical lead and the SEO owner co-own this, usually 5–15 working days of focused work.

If the existing site has no meaningful organic traffic, you can skip preservation but you still need to lay a clean baseline — titles, descriptions, schema, internal links, performance budget all configured. See Technical SEO Baseline for a New or Rebuilt Website.

7. Integrations #

Where do form submissions go — Google Sheet, HubSpot, Salesforce, your own CRM? Should the WhatsApp button preload a message? Do you want X or LinkedIn feeds embedded? Does the CEO want a daily conversion email? None of these integrations is hard alone, but together they routinely take 20–30% of build time. If they aren't listed at kickoff, they get added in week six and the budget warps.

Project phases #

A renovation project, regardless of size, runs through six phases. The size only changes how long each one takes:

1. Audit (1–2 weeks): inventory the existing site — pages, traffic, keywords, lead sources, tech stack, performance baseline. The phase that gets skipped most often, and the one whose absence breaks every later decision. Method: Complete Website Renovation Audit Checklist.
2. Information architecture (1 week): which pages live in the new site, how navigation works, what URL structure looks like, where breadcrumbs go.
3. Design (2–4 weeks): every template designed and signed off.
4. Build (3–6 weeks): front end, back end, CMS configuration, form integrations, performance tuning.
5. Content (parallel with build): copy, case studies, images, video. English and any second language written separately, not translated.
6. QA and launch (1–2 weeks): device matrix, browser matrix, performance load tests, SEO checklist, soft launch, then the actual cutover.

Cut any phase in half and the savings reappear as cost in another phase. Our most painful client skipped audit; in build week four we discovered 200+ external backlinks pointing to product pages that had been deleted three years ago. Every redirect had to be planned from scratch and the timeline slipped two weeks.

The reskin trap #

"We just want a fresh coat of paint, the content stays" is one of the most common ways a renovation goes sideways. It sounds small, but underneath there are usually three things going on:

• The CEO doesn't like the visual but can't say why.
• Sales thinks the homepage "doesn't punch" but isn't sure if it's copy, structure, or both.
• Engineering knows the site is slow but doesn't want to smuggle technical-debt cleanup into a "design refresh."

Reskin without rebuild, and all three problems come back in three months wearing new fonts. Our advice: either commit to a real surface-level refresh (homepage and brand colors only, two to three weeks, tightly scoped) or commit to a full rebuild. The middle ground is where projects die.

Ship MVP first #

If budget or timeline is tight, the cleanest play is an MVP launch with iteration:

• Wave 1 (4–6 weeks): homepage, three core service pages, About, Contact, one or two case studies, baseline SEO. Mobile speed has to be solid, the contact form has to actually work, and the WhatsApp button has to open with the right message.
• Wave 2 (4–8 weeks post-launch): blog module, expanded case studies, glossary, additional language if needed.
• Wave 3 (2–4 months post-launch): site search, reviews, deep CRM integration, A/B testing infrastructure.

The reason for waves is data. By the time you plan wave 2, you know which service pages get traffic, which countries bounce hardest, where the form drops people. Wave 2 stops being guesswork.

If you have the team to run this fast, our four-week rebuild sprint writeup describes exactly how a small team executes wave 1.

Three tiers #

Simplified into three tiers for budgeting purposes:

Light fix #

• Cost: $7K–$11K
• Timeline: 4–6 weeks
• Fits when: existing site's structure mostly works, real problems are speed, mobile, and visuals
• Includes: homepage redesign, performance work, mobile fixes, SEO basics, SSL/email cleanup
• Excludes: information architecture changes, content rewrite, multilingual, deep integrations

Standard rebuild #

• Cost: $17K–$35K
• Timeline: 8–12 weeks
• Fits when: the site needs to be re-thought — structure, visual, content, SEO all in scope
• Includes: full audit, IA, semi-custom design, 12–15 templates, content migration, SEO preservation plan, baseline integrations (GA4, Search Console, WhatsApp)
• Excludes: multilingual (add 30–40% per language), headless architecture, deep CRM integration

Growth-grade #

• Cost: $42K–$85K
• Timeline: 12–20 weeks
• Fits when: the site is treated as a long-term growth asset that needs blog content, multilingual, CRM integration, and testing infrastructure
• Includes: everything in standard rebuild + 2–3 languages + headless CMS + deep CRM integration + 3–6 months of post-launch content and SEO support

These are mid-market ranges. North American and European agencies typically quote 1.5–2x for comparable scope. If anyone offers a complete rebuild for $4K, they are either applying a template with no customization or planning to rack up change orders later. Both are usually worse than honest pricing.

One-off vs monthly #

Most teams celebrate launch day and then nothing happens for three months. Search Console reports go unread. No blog posts. The WhatsApp number forwards to a phone nobody answers. That's because a site isn't a delivered project; it's an operating asset. One-off builds make sense when the client has internal SEO and content people. When they don't, a monthly growth retainer usually beats a bigger upfront build. Full comparison: One-Off Website Rebuild vs Monthly Growth Service.

After launch #

Whichever tier you pick, launch day is not the end. At minimum schedule:

• Week 1: monitor 404s, indexing, mobile usability.
• Month 1: first blog post, first data review.
• Month 3: decide whether the next investment is content depth, more case studies, or backlinks.

Detailed actions in the Post-Launch Website Maintenance Checklist.

Scope comparison #

If your needs sit between two tiers — say, full-custom design but minimal integrations — that's normal. Mix and match line by line; don't force yourself into a tier just because it has a label.

FAQ #

Why do quotes vary so much? #

The same brief can come back with quotes that differ by 5–10x, and the gap is almost always in four places: whether the audit is real or skipped, whether design is templated or custom, whether SEO preservation is included, and whether post-launch maintenance is in scope. Before comparing quotes, normalize on those four lines.

How fast can it ship? #

Fastest realistic timeline is 4 weeks (light fix on a theme). Standard rebuild lands at 8–12 weeks. A full growth-grade site is 12–20 weeks. If a vendor commits to a complete rebuild in two weeks, ask hard questions — it's almost always either a template swap or a setup for later change orders.

Is renovation the same as migration? #

No. Renovation rebuilds the content and structure. Migration moves existing content to a new platform. They often happen together, but the work and the risks differ. See Website Redesign vs Rebuild vs Migration for the breakdown.

How do we protect existing SEO traffic? #

Build the URL mapping table early, configure 301s, keep the old sitemap pointing to the new sitemap during transition, and watch Search Console daily for two weeks after launch. Step-by-step: How to Preserve SEO During a Website Rebuild and Google's own site move with URL changes guidance.

Get a diagnosis #

If you're estimating a renovation budget, or you've received quotes that vary wildly and aren't sure how to read them, bring your current site, target markets, and the quotes you've already collected. We'll walk this same framework with you in a free initial review under our website rebuild service and tell you which line items are worth paying for, which ones can wait, and which ones look like a vendor charging the "doesn't-know-better" tax.