Custom websites start at $5,000. Every project receives a written scope, fixed price, and timeline before work begins. Final pricing depends on page inventory, content, integrations, migration requirements, and custom functionality.
That starting price describes custom production work, not a theme swap. A responsible redesign preserves useful search history, analytics, content, domains, and operational connections while changing the positioning, buying path, interface, and code that no longer work.
Why redesign estimates differ
Two websites with the same number of pages can require very different releases.
One may have ten approved pages, no organic traffic, and a simple contact form. The other may have ten page templates generating hundreds of indexed URLs, years of performance history, several marketing integrations, multilingual content, and forms that route leads into different teams.
The page count looks similar. The migration and business risk do not.
How Routeless prices a redesign
The written scope accounts for:
- The page and template inventory.
- Positioning, writing, and content production.
- Search, analytics, and redirect migration.
- Intake, booking, payment, CRM, or other integrations.
- Custom interfaces and customer workflows.
- Testing, launch, and post-launch responsibilities.
See the current public language on the pricing page.
The inventory comes before design
Start by listing what exists:
- Public URLs and their purpose.
- Search impressions, visits, conversions, and backlinks where available.
- Content that remains accurate.
- Forms, scripts, analytics, CRM, calendars, payments, and embedded tools.
- Domains, subdomains, redirects, and campaign pages.
- Legal, accessibility, and consent requirements.
- Owners for hosting, DNS, source code, analytics, and third-party accounts.
Without an inventory, a redesign team can remove a page that quietly earns qualified traffic, break a form that feeds an operating queue, or publish two URLs competing for the same intent.
Positioning and information architecture
An established business redesign is often triggered by a story problem before a visual one. The company has expanded, changed buyers, added a higher-value service, or outgrown language written years earlier.
Positioning work determines:
- Who the primary buyer is.
- Which problems the business is equipped to solve.
- Which services deserve their own commercial pages.
- What evidence supports each offer.
- Which visitors should be filtered out.
- What action belongs on each page.
Information architecture turns those decisions into page ownership. It should be settled before high-fidelity design, because navigation and layout cannot resolve overlapping offers.
Content is a major scope driver
“We will provide the copy” only reduces scope when the content is approved, complete, and structured for the new pages.
Redesign content work may include interviews, message development, page outlines, writing, editing, proof collection, image selection, migration, metadata, schema, and stakeholder review.
Large review groups increase schedule risk. Name one content owner and one final approver before writing begins.
Search migration and redirects
Changing a URL does not automatically destroy rankings, but careless migrations make it easy.
A search-safe redesign should include:
- A complete current URL inventory.
- A decision to keep, merge, redirect, remove, or noindex each URL.
- One canonical owner for each search intent.
- Direct permanent redirects without chains.
- Preserved metadata and content where they remain useful.
- Updated internal links, canonicals, structured data, and sitemaps.
- Pre-launch and post-launch crawl comparison.
- Search Console monitoring against a dated baseline.
The goal is not to preserve every old page. It is to preserve useful authority and make deliberate changes visible.
Integrations and customer workflows
A basic form is inexpensive. A reliable customer workflow requires more decisions:
- Which questions qualify the request?
- Where does the record go?
- How are duplicates handled?
- Who gets notified?
- What happens when delivery fails?
- Does the visitor book, pay, upload, or create an account?
- Which source and campaign data must follow the record?
Verify external systems before including them in a fixed estimate. A vendor logo is not evidence that production access or the required API behavior exists.
Design and frontend development
Custom design cost depends on the number of distinct decisions, not only the number of pages.
A service detail page may be reusable across ten services. An interactive inventory explorer, comparison tool, bilingual buying path, or complex proof gallery may need its own behavior, data, responsive states, and accessibility testing.
The build should define reusable components without forcing genuinely different content into one generic template.
Accessibility, performance, and analytics
These belong in the release:
- Keyboard access and visible focus.
- Semantic headings, labels, and landmarks.
- Meaningful image alternatives.
- Responsive behavior at realistic widths.
- Performance budgets and optimized media.
- Analytics events tied to the buyer journey.
- Consent behavior where required.
- Error and success states for every form.
Retrofitting these after launch is usually more expensive and less reliable than including them in acceptance criteria.
Launch and post-launch monitoring
A redesign is not finished when the new homepage appears.
The launch plan should cover DNS and hosting ownership, redirects, analytics validation, form delivery, integrations, sitemaps, canonical tags, structured data, error monitoring, and rollback responsibilities.
Compare post-launch behavior with the recorded baseline. Search traffic and conversion can fluctuate for reasons unrelated to the redesign, so publish measured observations with dates rather than claiming causation too early.
When a focused release is enough
Do not redesign the whole website when the actual problem is:
- One unclear service page.
- A broken mobile inquiry path.
- Missing proof.
- Poor form routing.
- A slow media-heavy template.
- An unsupported integration.
- An outdated visual system that can be improved without migration.
A focused release can produce evidence for the larger decision while reducing risk.
Use the Website Budget Estimator to identify which conditions push your project into a connected-workflow range.
Frequently asked questions
How long does a website redesign take?
The project timeline is included in the written scope before work begins. Page inventory, stakeholder review, integrations, and migration requirements determine that timeline.
Should we keep our current CMS?
Keep it when the team can own and maintain it, it supports the required design and workflow, and its performance and security are acceptable. Replatform when ownership, capability, or operating cost justifies the migration risk.
Is SEO included in a redesign?
Search foundations should be: URL inventory, redirects, page ownership, metadata, canonicals, structured data, internal links, sitemap updates, analytics, and launch monitoring. Ongoing content or promotion is a separate decision.
Who owns the finished website?
The client owns the domain, production code, accounts, content, and data defined in the agreement.
Need a responsible plan for this redesign? Share the current website and what needs to change. Routeless will return a written scope, fixed price, and timeline.
Discuss my redesign View the case studyAuthor: Eric Provencio · Reviewed: September 3, 2026 · Buyer stage: commercial-evaluation
Methodology: Scope factors reflect the inventory, migration, integration, and release controls required for established sites; custom websites start at $5,000 and receive a written fixed price.
Primary intent: website redesign cost