Inventory
List current URLs, navigation, content, assets, forms, integrations, analytics, domain access, hosting access, and source ownership.
US decision guide / Redesign
Should you redesign or rebuild your small business website?
Redesign when the current structure and technical foundation can support the next offer. Rebuild when navigation, templates, code, access, or ownership limits make meaningful changes harder than replacing the foundation. Audit the current website before choosing either route.
Last reviewed: · Reviewed by Kacper Rękawek, founder
01 / Decision table
Redesign what works. Rebuild what blocks the work.
The label should follow evidence from the current website, not a preference for a particular platform or visual style.
| Area | Evidence for redesign | Evidence for rebuild |
|---|---|---|
| Offer and content | The core information is accurate and can be reorganized. | The website is built around an offer or audience the business no longer serves. |
| Navigation and templates | The structure can support the required pages and next actions. | The existing structure forces confusing navigation, duplicated pages, or fragile layouts. |
| Code and platform | The foundation is maintainable and supports the approved scope. | Required changes depend on workarounds or inaccessible, obsolete, or unowned code. |
| Access and ownership | The business controls its domain, hosting, source, and required accounts. | Missing access or unclear ownership prevents a responsible update and handoff. |
| Migration and SEO | Most useful URLs and page purposes can stay stable. | New structure requires URL mapping, redirects, metadata review, and a controlled migration. |
02 / Warning signs
Look for decision problems, not an arbitrary website age.
A website can look dated and still have a sound foundation. A newer website can still block inquiries, ownership, or search migration.
- Visitors cannot quickly identify the offer, audience, or next action.
- Navigation reflects old services or splits one decision across conflicting pages.
- Routine content changes break layouts or require fragile workarounds.
- Forms, mobile behavior, or key accessibility paths fail during ordinary use.
- The business lacks clear access to the domain, hosting, source, analytics, or integrations.
- Important URLs need to change, but no redirect or migration map exists.
03 / Audit
Build the decision from an inventory.
An audit does not need an invented score. It needs a complete record of what exists, what matters, what is missing, and what the new scope requires.
Preserve
Identify useful page intent, content, URLs, brand assets, and operational connections that should survive the change.
Decide
Separate content, visual, structural, and technical changes, then choose redesign, selective rebuild, or full rebuild.
Verify
Define checks for navigation, forms, mobile behavior, accessibility, metadata, canonicals, redirects, analytics, and the sitemap.
04 / Migration and SEO
Protect useful URLs and make every change explicit.
A rebuild can change the technical foundation without discarding useful search context. The migration plan should be written before launch, then verified against the deployed website.
- Inventory every current public URL and identify its new destination.
- Keep useful URLs stable when their purpose and structure still fit.
- Plan redirects for changed or removed URLs before deployment.
- Review titles, descriptions, canonicals, structured data, and internal links.
- Verify forms, analytics, robots directives, and the XML sitemap after launch.
- Record limitations instead of promising rankings, traffic, or business results.
05 / FAQ
Website redesign questions.
These answers define a decision process without inventing timelines, rankings, results, or a universal redesign price.
What is the difference between redesign and rebuild?
A redesign improves the visible experience while keeping enough of the current foundation. A rebuild replaces structural or technical parts that cannot support the required change. The right choice depends on current code, content, ownership, integrations, URLs, and the approved scope.
Can a redesign keep the current content?
Existing copy, brand assets, photography, and product knowledge can be reused when they remain accurate and available for the approved brief. An audit should label what stays, what needs revision, and what is missing before the project scope is confirmed.
Do website URLs need to change?
Not necessarily. Useful URLs should remain stable when the page purpose and structure still fit. When a URL must change, the migration plan should map the old address to the correct new destination and update internal links, canonicals, and the sitemap.
How should SEO be handled during redesign?
A redesign should inventory search-critical pages before changes, preserve useful page intent and content, plan redirects for changed URLs, review metadata and canonicals, and validate internal links and the sitemap. FastLanding does not promise rankings or invented traffic results.
What should a website audit include?
A practical audit should cover current URLs, navigation, content, brand assets, forms, integrations, analytics, domain and hosting access, source ownership, mobile behavior, accessibility, and technical SEO. The audit should separate facts, risks, missing access, and optional improvements.
Can a redesign keep the current platform?
Yes, when the current platform, code, access, and ownership can support the approved scope without fragile workarounds. When the foundation blocks required changes or cannot be maintained responsibly, rebuilding selected parts or the whole website can be the clearer decision.
How much does a FastLanding redesign cost?
FastLanding's published US launch price is $3,900 for one defined website sprint. A redesign or rebuild label alone does not set the price; the written scope and dependencies do.
How long does a website redesign take?
There is no universal timeline on this page. Timing depends on the approved scope, available materials, migration requirements, integrations, and review pace. FastLanding states the start window and milestones in the written proposal instead of publishing an unsupported deadline.
Project fit
Start with the current website and the decision it must support.
Share the URL, offer, audience, known problems, required integrations, available assets, and what must remain under your control.