Published 30 Oct 2026
Website Redesign Checklist 2026: From Planning to Post-Launch
Plan your website redesign from first audit to post-launch. A practical checklist to protect SEO and backlinks, coordinate design and development, test everything, and launch without losing leads.
Tags
Post content
A website redesign checklist is a step-by-step plan to replace or improve an existing website without losing what already works. It covers nine phases: planning, auditing, goal setting and URL mapping, content, design, development, pre-launch testing, launch, and post-launch monitoring. Following it protects your search rankings, backlinks, leads, and integrations while you improve the experience.
Your website is likely your most valuable marketing asset. In Webflow’s 2025 State of the Website report, 91% of 500 surveyed marketing leaders said their website drives more revenue than any other marketing channel. A redesign that breaks forms, loses search traffic, or deletes high-value pages puts that revenue at risk.
This guide is for business owners and marketing teams working with freelancers, an agency, or an internal team. Each phase ends with a checklist you can copy into your project tracker.
Key takeaways
- Audit before you design. Record what already brings traffic, links, and leads so you protect it.
- Map every old URL to a new one, and use 301 redirects for anything that moves.
- Keep your staging site hidden from search engines, then remove those blocks on launch day.
- Expect a short dip in rankings after launch, and monitor for at least three months.
- Judge success by business results against your baseline, not by how the new design looks.
What Is a Website Redesign?
A website redesign is a planned update to an existing website’s appearance, structure, content, or functionality. It can be as small as new page templates or as large as a complete rebuild on a new platform.
The goal is always to solve a business or user problem, such as explaining services more clearly, simplifying checkout, improving mobile usability, or making the site easier to manage.
Website Refresh vs Redesign vs Rebuild
| Type | What changes | Example | SEO risk |
| Refresh | Visual style and copy; structure stays the same | New fonts, colors, images and updated text | Low |
| Redesign | Navigation, page structure, layouts and key journeys | New menu, merged service pages, new homepage flow | Medium |
| Rebuild | Underlying code, CMS or platform | Moving from a custom PHP site to WordPress | High |
A platform change or domain change adds a separate migration workstream. Neither is required just because your website needs a new look.
Why Do Businesses Redesign Their Websites?
Businesses redesign when the current website no longer supports their audience, operations, or growth goals. The most common reasons are:
- The business has changed. New services, products, or markets are missing or poorly explained.
- Visitors struggle to understand the offer. Key explanations, comparisons or proof are missing.
- Customer journeys create friction. Navigation, enquiry forms, bookings or checkout take too much effort.
- The brand looks inconsistent. Pages use different messages, layouts, or visual styles.
- Publishing is difficult. Simple updates need a developer.
- The technology holds you back. Plugins are outdated, features are hard to add, or integrations keep breaking.
Define the improvement you want before collecting design inspiration. “Help buyers compare our three service packages” gives a designer a clearer task than “make the website more modern.”
Signs You Need a Website Redesign
Consider a redesign when problems affect several parts of the site or keep coming back after small fixes. Look for evidence like this:
- Mobile visitors struggle to complete key tasks like booking or checkout.
- Sales or support teams keep answering questions the website should already answer.
- Navigation hides important services or products.
- Engagement drops on high-intent pages such as services or pricing.
- Content and templates no longer match how you sell today.
- Your CMS makes routine publishing slow or depends on a developer.
- The site runs on unsupported themes, plugins, or code.
When Targeted Fixes Are Enough
One weak metric does not justify a rebuild. Fewer enquiries can come from tracking errors, lower traffic quality, pricing or seasonal demand. A broken form, oversized images, outdated copy or one confusing landing page usually needs a focused fix, not a full redesign.
Ask what needs structural change and what can be repaired inside the existing website. The answer tells you whether you need targeted fixes, a partial redesign, or a full rebuild.
Website Redesign Checklist at a Glance
| Phase | Key tasks | Output |
| 1. Planning | Define the problem, scope, budget, roles and milestones | Project brief |
| 2. Audit | Inventory pages, benchmark KPIs, audit SEO, backlinks and UX | Baseline report |
| 3. Goals and structure | Set goals, plan sitemap, map keywords and URLs | Sitemap and redirect map |
| 4. Content | Decide what to keep, rewrite, merge or remove | Approved content |
| 5. Design | Wireframes, prototypes, visual system, accessibility | Approved designs |
| 6. Development | Build on staging, integrations, redirects, performance | Working staging site |
| 7. Pre-launch testing | Content, journeys, devices, SEO and tracking checks | Launch approval |
| 8. Launch | Backup, deploy, verify, submit sitemap | Verified live site |
| 9. Post-launch | Monitor errors, rankings, backlinks and conversions | Improvement backlog |
Some phases overlap. Content work, for example, starts before final design and continues during development. What matters is resolving dependencies before they become expensive.
Phase 1: Website Redesign Planning Checklist
Planning sets what the project includes, who decides, and what resources you have.
Define the Problem, Audience and Scope
Write down why the redesign is happening now, who the website serves, which visitor actions matter most, what is failing, and which pages, templates, and features are in scope and out of scope.
Count templates, not just pages. Twenty service pages using one layout are far less work than twenty individually designed pages.
Review Your Brand Guidelines
Share your logo files, colors, fonts, tone of voice, and messaging with everyone on the project. If your brand is changing at the same time, finish the brand decisions before design starts, or the redesign will be built on moving targets.
Set Budget, Ownership and Milestones
Include design, development, content, migration, testing, and post-launch support in the budget. List recurring costs separately, such as hosting, premium plugins, software and maintenance.
Confirm that your business owns and can access the domain, hosting, CMS, and key third-party accounts. Name a project lead, content owner, designer, developer, SEO reviewer, and final approver, and let one person collect all feedback.
Phase 1 checklist
| Task | Done |
| Problem, audience and main visitor actions written down | ☐ |
| Pages, templates and features in scope and out of scope listed | ☐ |
| Brand guidelines shared with the whole team | ☐ |
| Budget covers design, build, content, migration, testing and support | ☐ |
| Domain, hosting and CMS access confirmed under your ownership | ☐ |
| Roles, approver and milestones agreed | ☐ |
Phase 2: Audit the Current Website and Benchmark KPIs
The audit shows what to improve and what must survive the redesign. Save this data before anything changes, because you cannot measure success without a baseline.
Inventory Every Page and Asset
Collect URLs from your CMS, XML sitemap, Google Analytics 4 (GA4), Google Search Console, and a full crawl with a tool such as Screaming Frog. Include service and product pages, blog posts, landing pages, location and language versions, PDFs, forms and account areas. Record each page’s purpose, owner, and importance.
Benchmark Your KPIs
Export at least 12 months of data where possible, so seasonality is covered:
- Traffic by channel and landing page (GA4)
- Search queries, clicks, impressions and average position (Search Console)
- Leads, bookings, sales and conversion rates for key journeys
- Core Web Vitals and page speed for mobile and desktop (PageSpeed Insights)
- Number of indexed pages and existing crawl errors
Check that tracking works correctly before you treat any number as a baseline. For a full process, follow our guide on how to audit a website for SEO.
Audit Your Backlinks
Backlinks are links from other websites to yours. They carry authority and referral traffic, and they are easy to lose in a redesign. Link loss is already common: an Ahrefs study of more than 2 million websites found that at least 66.5% of links to the sampled sites had rotted since 2013. A redesign that changes URLs without redirects adds to that loss.
Use Ahrefs, Semrush, or the Links report in Search Console to find your most-linked pages. Keep their URLs unchanged where possible, and plan a 301 redirect for any that must move.
Research Real User Problems
Analytics show what happens; users explain why. Combine:
- Heatmaps and session recordings with tools such as Microsoft Clarity or Hotjar
- Short surveys asking visitors what they came for and what was missing.
- Customer reviews and support tickets that mention the website
- Sales team feedback on questions prospects ask before buying.
A high exit rate is not always a problem. A visitor who leaves after finding your phone number succeeded; one who abandons a broken checkout did not.
Document Technology and Integrations
List every system the website relies on: hosting, CMS, plugins, booking tools, CRM, email notifications, payment providers, analytics, and external feeds. Record what each one does and where its data goes.
Phase 2 checklist
| Task | Done |
| Full URL inventory from CMS, sitemap, GA4, Search Console and a crawl | ☐ |
| 12 months of traffic, search and conversion data exported | ☐ |
| Core Web Vitals and speed recorded for key templates | ☐ |
| Most-linked pages identified with a backlink tool | ☐ |
| User research collected (heatmaps, surveys, reviews, sales feedback) | ☐ |
| All integrations and data flows documented | ☐ |
Phase 3: Set Goals, Plan the Structure and Map URLs
This phase turns audit findings into decisions about the new website.
Set Measurable Goals
For each goal, record the current number, the target, and how you will measure it. For example:
- Increase qualified enquiries from service pages by 20% within six months.
- Reduce drop-off in the booking flow.
- Cut the time staff spends publishing updates.
Agree when you will review results. Design approval and business performance are separate milestones.
Study Competitors and References
Review how competitors explain their offer, organize information, and handle key decisions. Note what works and why. A clear comparison layout is a useful reference; copying another company’s wording or design is not.
Plan the Sitemap and User Journeys
Create the new sitemap with main navigation groups, parent and supporting pages, key entry pages, and the next step on each priority page. Use labels your customers understand, not internal department names.
Map Keywords and URLs
Assign each important search intent to one page, keep existing pages that already rank, and avoid two pages targeting the same query.
Then build a redirect map: a spreadsheet listing every old URL and what happens to it (keep, update, merge, move, or remove). Every moved page needs a 301 redirect to its most relevant new page. Pages removed with no replacement should return a proper 404 or 410 status rather than redirecting everything to the homepage.
Confirm the Platform Decision
Only change your CMS if it solves a defined problem, such as editing limits, missing integrations, or high running costs. A new platform adds migration risk and cost.
Phase 3 checklist
| Task | Done |
| Goals with current baseline, target and review date | ☐ |
| Competitor and reference review completed | ☐ |
| New sitemap and key user journeys approved | ☐ |
| Keyword-to-page map with no overlapping targets | ☐ |
| Redirect map covering every existing URL | ☐ |
| Platform decision confirmed with clear reasons | ☐ |
Phase 4: Content Preparation and Migration Checklist
Content needs its own plan, owners, and deadlines. Leaving it until the end causes delays and forces layouts to fit content they were never designed for.
Decide What to Keep, Improve, Merge, or Remove
Review pages one by one. Low traffic alone is not a reason to delete a page; it may serve existing customers, support a niche service, or hold backlinks. Merge thin or duplicate pages into stronger ones, and redirect the old URLs.
Write Page Briefs and Final Copy
For each priority page, define the audience, purpose, questions to answer, proof needed, main call to action, internal links, writer, and approver. Review designs with real copy, because placeholder text hides problems with length and hierarchy. If you need help, website and landing page copywriters can rewrite key pages.
Prepare Media and Downloads
Gather logos, photos, videos, illustrations, and PDFs. Confirm usage rights, formats, file sizes, and alt text. Assign someone to supply missing assets instead of assuming the developer will.
Validate Migrated Content
Check that old content fits the new CMS fields: headings, links, metadata, product details, authors, dates, and structured data. For large migrations, compare item counts as well as spot-checking pages.
Phase 4 checklist
| Task | Done |
| Keep, improve, merge or remove decision for every page | ☐ |
| Briefs and approved copy for all priority pages | ☐ |
| Images, videos and files collected with rights and alt text | ☐ |
| Metadata and structured data carried over | ☐ |
| Migrated content checked against the original | ☐ |
Phase 5: UX and Website Design Checklist
Design should make the approved content and journeys easier to use. Test structure before polishing visuals.
Create Wireframes and Prototypes
Wireframe each key page type, then build clickable prototypes in a tool such as Figma for core journeys: finding a service, sending an enquiry, booking or buying. Include error and confirmation states, not just the happy path.
Define a Consistent Visual System
Agree on typography, colors, spacing, buttons, forms, and reusable components. Test them with real content, including long product names and detailed specifications. Experienced UI/UX designers usually build this as a component library so the site stays consistent as it grows.
Design for Mobile and Accessibility
Design mobile layouts first for key pages, with readable text, large tap targets, and simple forms. Aim for WCAG 2.2 Level AA, the widely used accessibility standard: sufficient color contrast, visible focus states, keyboard navigation, clear labels, and helpful error messages. Use tools such as WAVE for automated checks, then test manually.
Test With Real Users
Give a few representative users realistic tasks and watch where they hesitate. Fix those problems before development scales across every template.
Phase 5 checklist
| Task | Done |
| Wireframes for every key page type | ☐ |
| Clickable prototypes for core journeys, including errors | ☐ |
| Visual system and reusable components approved | ☐ |
| Mobile layouts and WCAG 2.2 AA checks completed | ☐ |
| User testing findings fixed | ☐ |
Phase 6: Development and Integration Checklist
Development turns approved designs into a working, manageable website.
Build on a Protected Staging Site
Build and test on a staging site that search engines cannot index. The safest method is password protection. Mirror the live environment as closely as possible, so test results match real conditions.
Build Templates and Editing Controls
Build reusable templates and CMS fields so your team can update content without breaking layouts. Confirm editors can do routine tasks themselves before launch.
Connect Features and Integrations
Set up forms, search, filters, bookings, payments, accounts, and external systems. Test where the data actually goes. A success message on screen does not prove the enquiry reached the right inbox or CRM.
Implement Redirects and Technical SEO
Apply the redirect map with 301 redirects, update internal links to the new URLs, and set correct canonical tags, title tags, meta descriptions, and XML sitemap entries. Google’s guide to site moves with URL changes recommends direct, one-step redirects and careful monitoring.
Build Performance In From the Start
Optimize images, fonts, scripts, and caching during development, not after launch. Target Google’s “good” Core Web Vitals thresholds:
| Metric | Measures | Good score |
| Largest Contentful Paint (LCP) | Loading speed | 2.5 seconds or less |
| Interaction to Next Paint (INP) | Responsiveness | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Visual stability | 0.1 or less |
Our website speed optimization checklist covers the most common fixes. Also install analytics events for key conversions and keep using the same GA4 property so historical data stays comparable.
Phase 6 checklist
| Task | Done |
| Staging site password-protected and hidden from search engines | ☐ |
| Templates and CMS editing tested by your team | ☐ |
| Forms and integrations deliver data to the right place | ☐ |
| 301 redirects, internal links, canonicals and sitemap updated | ☐ |
| Core Web Vitals targets met on key templates | ☐ |
| Analytics events set up in the existing GA4 property | ☐ |
Phase 7: Pre-Launch Website Redesign Checklist
Pre-launch testing compares the finished build with the approved scope. Log every defect, fix it, and retest.
Review Content and Presentation
Check approved copy, accurate contact details, prices and product information, working images and downloads, and that no placeholder text or staging URLs remain.
Test Every Important Journey
Test navigation, search, forms, checkout, payment failures, logins, password resets, and bookings, with valid and invalid inputs. Confirm that notifications, CRM records, and confirmation emails arrive.
Check Devices, Accessibility and Speed
Test the browsers and devices your audience actually uses. Tools such as BrowserStack help cover devices you do not own. Check keyboard navigation and run speed tests on several templates, not just the homepage.
Validate SEO and Tracking
Crawl the staging site to check redirects, status codes, titles, meta descriptions, canonicals, and internal links. Confirm conversion events fire once, consent banners work, and no tracking is duplicated.
Agree on Launch Approval and Rollback Plan
Document which checks must pass, which minor issues can wait, who approves launch, who fixes urgent problems, how to restore the backup, and what would trigger a rollback.
Phase 7 checklist
| Task | Done |
| Content, prices and contact details verified | ☐ |
| All key journeys tested end to end | ☐ |
| Devices, browsers, accessibility and speed checked | ☐ |
| Staging crawl shows correct redirects and metadata | ☐ |
| Tracking verified with no duplicates | ☐ |
| Launch approver and rollback plan agreed | ☐ |
Phase 8: Launch-Day Checklist
Even after successful staging tests, hosting, DNS, caching, and live integrations can behave differently in production.
Back Up and Sync Data
Take a full backup of the old site. For ecommerce sites, plan how to carry over orders, stock, and customer records created after the staging copy was made. Freeze content changes during the launch window.
Deploy and Remove Search Engine Blocks
Deploy the new site, then immediately confirm that password protection, noindex tags, and robots.txt disallow rules from staging are removed. Forgetting this step is one of the most damaging redesign mistakes, because it can remove the whole site from search results.
Verify the Live Site
Check HTTPS, key pages, redirects, and status codes. Submit a real enquiry or test order and confirm it arrives everywhere it should. Check key pages on mobile and desktop.
Tell Search Engines and Record the Launch
Submit the new XML sitemap in Google Search Console and Bing Webmaster Tools. If the domain changed, use the Change of Address tool in Search Console. Add an annotation in your analytics with the launch date, so future reports show exactly when the change happened.
Phase 8 checklist
| Task | Done |
| Full backup of the old site saved | ☐ |
| Orders, stock and customer data synced (ecommerce) | ☐ |
| Staging password, noindex and robots.txt blocks removed | ☐ |
| Live redirects, HTTPS and key journeys verified | ☐ |
| XML sitemap submitted; Change of Address used if domain changed | ☐ |
| Launch date annotated in analytics | ☐ |
Phase 9: Post-Launch Monitoring and Optimization
A redesign is judged by results against your baseline, not by how the new site looks.
Monitor Functionality First
In the first days, watch enquiry delivery, orders, bookings, uptime, and integration errors. Fix broken journeys before cosmetic issues.
Watch Search Performance Closely
Check Search Console daily for the first two weeks for crawl errors, 404s, and indexing problems, then weekly. A short ranking dip is normal while Google processes changes. Google notes that a medium-sized site can take a few weeks for most pages to move in its index, and larger sites take longer. Keep redirects in place for at least one year.
Recheck Your Backlinks
Confirm that your most-linked pages resolve correctly. For important links pointing to removed URLs, add redirects or ask the linking site to update the link.
Compare KPIs Over Fair Periods
Compare traffic, conversions, and lead quality with the same period before launch, accounting for seasonality and campaigns. Launch-week numbers rarely tell the full story.
Improve, Then Maintain
Use feedback and behavior data to improve navigation, copy, forms, and calls to action, one change at a time so you can see what worked. Then agree who owns updates, backups, security, and monitoring. Our guide on what website maintenance includes and costs explains what to plan for.
Phase 9 checklist
| Task | Done |
| Forms, orders and integrations monitored daily in week one | ☐ |
| Search Console checked for errors and indexing issues | ☐ |
| Most-linked pages and backlinks verified | ☐ |
| KPIs compared with the pre-launch baseline | ☐ |
| Improvement backlog created | ☐ |
| Maintenance owner and plan agreed | ☐ |
Redesigning a WordPress Website: Extra Checklist
WordPress powers a large share of business websites, and redesigning one has a few specific risks.
- Theme vs page builder: decide whether you are switching themes, rebuilding with a page builder or the block editor, or building a custom theme. Each has different migration work.
- Use a child theme or custom theme: never edit a parent theme directly, or updates will wipe your changes.
- Audit plugins: remove unused plugins and replace outdated or unsupported ones. Fewer plugins means better speed and security.
- Build on staging: many hosts offer one-click staging. Copy the live site, redesign there, and keep it protected.
- Check the “Discourage search engines” setting: under Settings, then Reading, this box is often ticked on staging. Make sure it is unticked after launch.
- Keep permalinks: changing the permalink structure changes every URL and needs a full redirect map.
- WooCommerce stores: plan how to sync orders, customers, and stock between staging and live, and test checkout and payment gateways thoroughly.
- Back up before every major step, including the database.
If you do not have in-house WordPress skills, read our guide on how to hire a WordPress developer online, or browse WordPress specialists and WooCommerce developers on Osdire.
Will a Website Redesign Hurt Your SEO?
A redesign does not have to hurt SEO, but it often does when URLs change without redirects, content is removed, or staging blocks stay live. Most losses come from avoidable mistakes:
- Missing or incorrect 301 redirects
- Deleting pages that ranked or had backlinks
- Changing title tags and content on ranking pages all at once
- Leaving noindex or robots.txt blocks after launch
- Slower page speed on the new design
- Broken internal links and navigation that hides key pages
If you follow the audit, URL mapping, pre-launch and launch steps above, a temporary dip usually recovers within weeks. If you are changing your domain, CMS, and design at the same time, consider bringing in an SEO specialist. Our guide on hiring an SEO expert explains what to check.
How Long Does a Website Redesign Take?
Timelines depend on site size, content readiness, custom features, and how quickly decisions are approved. These are planning estimates for typical business websites, not guarantees:
| Project type | Typical timeline |
| Refresh of a small site (under 10 pages) | 2 to 4 weeks |
| Redesign of a business website (10 to 50 pages) | 6 to 12 weeks |
| Ecommerce redesign or rebuild with migration | 3 to 6 months |
| Large site or platform change with integrations | 6 months or more |
Content delays and slow feedback are the most common reasons projects run late. For more detail, see how long it takes to build a business website.
How Much Does a Website Redesign Cost?
Cost depends on scope more than anything else. The main factors are:
- Number of unique templates and pages
- How much content needs writing or migrating
- Custom features and integrations
- Platform or domain changes
- Accessibility and testing requirements
- Who does the work: freelancer, agency, or in-house team
- Post-launch support and maintenance
Ask for a phased estimate that lists assumptions and exclusions, and compare quotes against the same brief. A cheaper quote that leaves out content migration, redirects, or testing does not cover the same work. For typical rates, see how much it costs to hire a web developer.
Should You Hire a Web Designer or a Web Developer for a Redesign?
It depends on what is changing:
| If your redesign mainly involves… | Hire |
| New look, layouts, branding and user experience | A web designer or UI/UX designer |
| New features, integrations, CMS or platform changes | A web developer |
| Both visual and technical changes | Both, or one professional skilled in design and development |
| Protecting rankings during URL or platform changes | Add an SEO specialist |
Many small business redesigns need a designer for layouts and a developer to build them. On a platform like WordPress, some freelancers handle both. Browse web designers for the visual work and web developers for the build.
Where Should You Get Your Website Redesigned?
Choose the delivery model based on the skills and coordination your project needs.
- DIY or internal team: suits businesses with the right skills and time. Website builders simplify the build, but planning, content, redirects, and testing still need owners.
- Freelance specialists: suit focused redesigns with a clear scope. Match skills to the work, because design, development, copywriting, and technical SEO are different jobs.
- An agency: suits large projects that need many disciplines and central project management. Confirm who actually does the work and what stays your responsibility.
On Osdire, you can browse freelancer profiles when you know the skills you need, or post a project brief describing your current website, goals, pages, features, and deliverables. Before hiring, check our list of red flags when hiring a web developer, and if your project includes moving hosts or platforms, consider a backup and migration specialist.
Common Website Redesign Mistakes to Avoid
- Designing before diagnosing: know what is failing before choosing layouts.
- Deleting content without checking its value: review traffic, backlinks, and business use first.
- No content owner: assign writers, approvers, and deadlines early.
- Skipping the redirect map: plan every URL before launch, not after traffic drops.
- Approving screenshots instead of a working site: test real journeys on staging.
- Leaving staging blocks live: remove noindex, passwords, and robots.txt rules on launch day.
- Changing everything at once: separate domain, platform and brand changes where possible.
- Treating launch as the finish line: plan monitoring, fixes and maintenance from day one.
Website Redesign Brief Template
Copy these prompts into your project brief before asking for quotes. Our guide on how to write a brief for a web developer explains each section in more detail.
| Brief section | What to include |
| Business problem | What needs to improve, and the evidence |
| Audience and actions | Who uses the site and what they should do |
| Current website | URL, platform, key pages and known limits |
| Baseline | Traffic, search, conversion and speed data |
| Scope and exclusions | Pages, templates, features, integrations, languages |
| Content | What is ready, what needs writing, who supplies it |
| Migration | URLs, files, records and systems that need attention |
| Responsibilities | Who does, reviews and approves each workstream |
| Budget and milestones | One-time costs, recurring costs and key dates |
| Acceptance criteria | What must be true before the project is complete |
| Launch and support | Who deploys, monitors, fixes and maintains |
Frequently Asked Questions
What should a website redesign checklist include?
A website redesign checklist should cover planning, a full audit with KPI benchmarks, goals and URL mapping, content preparation, UX and design, development, pre-launch testing, launch-day steps, and post-launch monitoring. Each phase should have clear owners and completion evidence.
Will a website redesign affect my Google rankings?
It can, but losses are usually avoidable. Keep valuable URLs, use 301 redirects for every page that moves, carry over content and metadata, and remove staging blocks at launch. A short dip is normal while Google processes changes.
How long does a website redesign take?
A small refresh can take 2 to 4 weeks, a typical business website redesign 6 to 12 weeks, and an ecommerce or platform change 3 to 6 months or more, depending on scope, content readiness, and approval speed.
How much does a website redesign cost?
Cost depends on the number of templates, content and migration work, custom features, platform changes and who does the work. Compare itemized quotes against the same brief, and check what each quote excludes.
Should I hire a web designer or a developer for a website redesign?
Hire a designer for visual and user experience changes, a developer for features, integrations, and platform work, and both for full redesigns. Add an SEO specialist if URLs or platforms are changing.
How often should you redesign a website?
There is no fixed rule. Redesign when the site no longer reflects your business, fails on mobile, blocks publishing, or underperforms after targeted fixes. Many businesses make smaller continuous improvements instead of large redesigns every few years.
What if my current website has no reliable analytics data?
Set up GA4 and Search Console as early as possible, then build a partial baseline from search data, enquiry records, sales data, and customer feedback. Document the gaps instead of presenting estimates as measured performance.
Does a website redesign require a new domain?
No. Most redesigns keep the existing domain. Only change it for a separate business reason, and treat it as an additional migration with its own redirects and Search Console steps.
Should I change my brand, domain, and CMS in the same project?
Only if necessary. Each change adds risk. Separating them, or adding clear checkpoints between them, makes problems easier to find and fix.
How long should I keep 301 redirects after a redesign?
Keep them for at least one year, and longer if old URLs still receive traffic or backlinks. Removing redirects too early can lose rankings and referral traffic.
