Tell us what needs to change. We will help you scope it.
Start a project →Audit the current pages, preserve useful content and map every changed URL before replacing the design. The new site gets a clear editing model and a tested route back if launch needs to pause.
A redesign fits when the site still earns traffic or leads but no longer fits the business. If the current site earns nothing worth keeping, a new build is often simpler, and we will say so.
Every file is built from your current pages and data, and it lives in your accounts from the first day.
Every page scored on traffic, leads and links, with a keep, merge, rewrite or retire decision.
Traffic, conversions and top search queries recorded before anything changes, so launch has a fair comparison.
Your brand carried into tokens, type and components, with the patterns your content already depends on.
One template for every content type in the audit, so no existing page is left without a layout.
Pages, posts, media and forms moved by script, then counted and checked against the old site.
Old URL, decision, new URL and tested response for every page that moves or retires.
Content freeze, cutover steps, launch checks and a tested route back to the old site.
Daily checks on 404s, forms and index coverage for 14 days, closed with a written summary.
Drag the handle to compare the old and new versions of the Northvale concept. It is an illustrative comparison, not a client result.
Northvale Dental Group concept · Illustrative comparison, not a measured result
The current site stays live and untouched until the launch gate. Each gate ends with a written decision before the next phase starts.
| Week | Phase | What happens | Your effort | Gate |
|---|---|---|---|---|
| 1-2 | Audit | Page inventory, analytics and Search Console baseline, content decisions, new sitemap | Access to the CMS, analytics and Search Console | Keep-or-retire list approved |
| 3-5 | Design | Refreshed design system and a template for every content type in the inventory | Two 60-minute reviews a week | Templates approved |
| 6-9 | Build | Rebuild on staging, content migrated by script, redirect map written and tested | A content owner for rewrites and approvals | Staging accepted |
| 10-12 | Launch | Content freeze, cutover, redirect and form checks, then 14 days of 404 and coverage checks | Final approval, DNS access | Launch checklist green |
Before any template changes, we export every URL with its traffic, links and conversions, then decide what stays, moves or retires. Redirects, forms and tracking are tested on staging before launch, so the pages that earn their keep do not go missing.
Most redesigns keep the current platform. The audit shows whether yours can carry the new design or should be replaced as part of the project.
We rebuild the theme as blocks and keep your posts, pages, users and media in the same database.
Each plugin is kept, replaced or removed, with the reason written down before the rebuild.
Pages made in a page builder are rebuilt as blocks, so the extra markup stops slowing every page.
Products, customers, orders and apps stay in place while the new Online Store 2.0 theme is built in preview.
Each installed app is checked for its load-time cost and whether the new theme makes it unnecessary.
Test orders, discounts and analytics events are checked on the new theme before it is published.
Editors keep the WordPress admin and the content they know. Only the public front end is replaced.
Routes are generated from your existing permalinks, so most URLs do not change at all.
A large content library, or speed targets the current theme cannot meet even after a rebuild.
Redesigned templates, tokens as CSS variables, and an inventory that says which template each URL uses.
Your team gets the tested redirect map and the content decisions, not only the new screens.
Optional: we check their staging build against the approved templates and send a fix list.
Prices arrive in the written proposal. The scope depends on how much of the current site you keep.
What changes the price: number of existing pages · templates · content rewrites · URLs that change · integrations to retest · a platform change · languages.
A redesign should feel new to your customers and familiar to your editors. The pages that already work are part of the brief.
Not sure the whole site needs replacing? One of these may fit better.
Expert review, analytics and Core Web Vitals check, severity-ranked backlog.
S07Custom block themes and headless builds your marketing team can edit without calling a developer.
S14Updates on staging first, restore drills, monitoring, a monthly report.
Guides for planning a redesign that keeps what already works.
Find which server sent the 414 and stop the redirect or form that keeps growing the URL. Raise the nginx or Apache limit only for legitimate long URLs.
Tested on nginx 1.30.6 and Apache 2.4.70 (Apache Lounge Win64 build) on Windows 10 Pro with a Node.js 22.23.4 backend, and WordPress 7.1.4 on PHP 8.3 in Playground, November 11, 2026
The decisions to make before a redesign launches. Inventory, keep or remove rules, the URL map, freezes, validation and rollback, with real numbers from our own rebuild.
The line items in a redesign quote and what drives each one. Includes dated market figures with their methods and a worked example from our scoper.
A migration checklist built on the w3experts.com move from WordPress. It covers a reconciled URL inventory, a 72-row redirect map, DNS and email records, SSL, backups, launch day, rollback and a 14-day watch.
Tested on Local W3Experts build (redirect map), plus live sitemap, DNS and HTTP checks of w3experts.com with PowerShell and curl on Windows 10, November 11, 2026
The sample map records the old URL, the decision to retain or move it, the new destination and a test result. It separates content decisions from design changes so useful pages are not lost by accident.
The sample map records the old URL, the decision to retain or move it, the new destination and a test result. It separates content decisions from design changes so useful pages are not lost by accident.
You keep the agreed project files and source. This sample illustrates the handoff; it is not a client result.
We inventory pages, key user paths, available analytics and technical constraints. That baseline helps decide which content to retain, combine, rewrite or remove before design starts.
We plan URL changes and test redirects to reduce avoidable migration errors. Search rankings depend on factors beyond a redesign, so we do not promise that every position will remain unchanged.
No. Useful URLs can stay in place when the structure still makes sense. A changed URL needs a recorded destination and a tested response in the migration map.
Yes, if the platform supports the requirements. We inspect the theme, plugins and editing workflow before recommending a rebuild or a smaller change.
We compare task clarity, content hierarchy and responsive behavior against the agreed brief. Concept examples are labeled and are not presented as measured client conversion results.
We agree on backups, a content freeze, redirect checks and a rollback plan. The launch window and responsibilities are documented before changing the public site.
Most website scopes fall within six to twelve weeks. Large content inventories, new integrations or incomplete approvals can require a phased schedule.
Your team receives the approved design files, repository, accounts and publishing guidance. Ongoing maintenance is a separate care scope with stated coverage.
