There is no single responsible price for every website redesign. Two sites with the same number of URLs can require very different work: one may need a focused interface repair, while the other needs new positioning, information architecture, CMS relationships, integrations and a controlled migration.

A useful estimate therefore starts by reducing uncertainty. It should explain what is changing, what must survive the move, which evidence and content already exist, who approves decisions and how readiness will be tested.

First decide whether the site needs repair, restructuring or replacement

The size of the intervention is the first cost driver. A repair keeps the underlying route, content and technical system and addresses a bounded problem. A restructure changes how visitors understand and navigate the offer. A full replacement rebuilds several connected layers and usually carries the largest migration responsibility.

  • Repair: the core message, route structure and CMS still work; specific usability, content or implementation problems can be isolated.
  • Restructure: visitors struggle to find the right path, content hierarchy has drifted or repeated pages compete with each other.
  • Replace: templates, responsive behavior, CMS, integrations and migration decisions are coupled tightly enough that piecemeal work creates more risk.

A provider should be able to explain why the recommended level of intervention is necessary. If every problem automatically becomes a full redesign, the estimate is not helping you make a decision.

The scope factors that usually change the estimate

1. Strategy, positioning and content readiness

A redesign costs less to define when the audience, offer, proof and page responsibilities are already clear. If the project must first reconcile several audiences, unsupported claims, missing product information or an uncertain route hierarchy, that work belongs in scope before interface production.

2. Unique page systems—not just page count

A repeated article template and twenty populated entries may be simpler than five pages that each require a unique layout and interaction model. Ask how many distinct templates, components, states and responsive behaviors the estimate covers.

3. CMS and editorial workflow

Collections, field relationships, localization, required metadata, image handling, roles and preview behavior add modelling and validation work. The important question is not whether a CMS exists, but which updates editors must make safely after handoff.

4. Integrations and operational paths

Forms, booking, CRM, analytics, consent, search, localization and product data each need an owner, access, error behavior and acceptance test. An integration that merely appears in a mockup is not yet specified.

5. Migration and search controls

A redesign of an existing site must reconcile old and new URLs, content, metadata, internal links, canonical and robots decisions, structured data, sitemaps and measurement. Google’s site-move guidance recommends preparing an accurate URL mapping, redirects and updated internal links, then monitoring the move. These controls reduce avoidable risk but do not guarantee unchanged rankings.

6. Accessibility, responsive QA and browser coverage

Accessibility is cheaper to plan throughout structure, design and development than to treat as a final overlay. Keyboard behavior, focus, contrast, heading order, reflow, images, forms and error states all affect design and validation effort.

7. Stakeholders and approval cycles

The number of decision-makers matters less than whether their responsibilities and review windows are clear. Unbounded review rounds, late legal input or unresolved content ownership can expand a project even when the interface itself is straightforward.

Three illustrative redesign scenarios

These scenarios show why labels and page counts are not enough. They are not AMS Digital prices, timelines, client cases or offers.

Focused marketing-site repair

The offer and route structure remain sound. Work concentrates on a small component set, responsive defects, content hierarchy and a limited number of templates. CMS and URLs remain mostly unchanged.

Content and interface restructure

The site serves several audiences but does not route them clearly. The project includes information architecture, revised page jobs, a design system, content decisions and a more useful CMS. Some URLs change and require mapping.

Platform and migration rebuild

The current technical system prevents routine change. The redesign includes a new content model, implementation, integrations, URL migration, analytics/consent review, launch testing and editor handoff. The migration responsibility is a substantial part of the estimate.

What a useful redesign estimate should clarify

  • The exact page and template inventory, including what is explicitly excluded.
  • Who supplies and approves copy, images, business claims, legal text and translations.
  • The CMS model, editor responsibilities and training or handoff included.
  • Each integration, its access owner and the behavior that counts as working.
  • Migration decisions for content, URLs, redirects, metadata, analytics and forms.
  • Review rounds, stakeholder responsibilities and change-control rules.
  • Responsive, accessibility, browser and launch acceptance criteria.
  • What happens after launch and which support expectations are not included.

How to reduce uncertainty before requesting a quote

Prepare the current site, a list of audience and business priorities, representative content, known integrations, expected editors, decision-makers and the reason the change matters now. You do not need to prescribe the final solution. A good first conversation should help distinguish a repair from a broader redesign and identify the evidence needed for a bounded proposal.

The best early cost question is not “What does a redesign cost?” but “Which decisions, systems and migration risks must this redesign actually resolve?”

Frequently asked questions

Does every page increase the price equally?

No. A page using an approved template is different from a page that introduces a new structure, interaction, content model or responsive state. Estimate page systems and content work separately.

Is copywriting normally included?

It should never be assumed. The scope needs to say who supplies source facts, who drafts the content, how claims are verified and who gives final approval.

Does preserving SEO add work?

Yes. Existing content, URL mapping, redirects, internal links, metadata, crawl directives, structured data and post-launch monitoring require deliberate work. This reduces migration risk without guaranteeing rankings.

Should I compare proposals only by total price?

Compare the assumptions, exclusions, page systems, content responsibility, migration controls, acceptance criteria and handoff. Two totals may describe materially different projects.