Most website redesigns are judged on launch day, when the new design looks finished. The damage shows up later: lost rankings, broken links, and visitors who cannot find a page they used last month.
A website redesign checklist should protect what the old site already earned. It should also make the top tasks easier to finish on the new site. Each step below has a done-when test, so a "mostly finished" step does not count as finished.
iShort answer
Run a redesign in five phases: plan, audit, build, launch, and monitor. Before any design work, write down the top visitor tasks, record baseline numbers, and export every URL. Sort every page into keep, rewrite, merge, or retire, then map each old URL to its new home.
Test accessibility, speed, forms, and real visitors before launch. Keep redirects for at least a year, as Google recommends.
Add AI at one step. A chatbot trained on the finished site helps visitors find content in their own words. It also shows you what the new site still fails to answer.
Each phase has a clear exit test. Finish it before moving to the next.
Plan
Write the goal, the top tasks, and the baseline numbers the new site must beat.
Audit
Export every URL. Mark each page keep, rewrite, merge, or retire. Start the redirect map.
Build
Design around tasks. Test templates for accessibility, speed, and mobile use with real visitors.
Launch
Ship redirects, remove staging blocks, submit the sitemap, and test every form.
Monitor
Fix 404s, compare against the baseline, and add AI to catch what visitors still cannot find.
95.9%
Share of the top one million home pages with detected WCAG failures in February 2026. Automated tools catch only part of the problem. A redesign needs manual testing too.
Source: WebAIM Million, 2026Key takeaways
| Question | The short answer |
|---|---|
| What is the first step? | Write down the top tasks and baseline numbers, before any design work. |
| What protects rankings? | A complete URL inventory, one-to-one redirects, retained content, and updated internal links. |
| How long do redirects stay? | As long as possible, generally at least one year, according to Google. |
| What gets tested before launch? | Accessibility, Core Web Vitals, forms, analytics, and top tasks with real visitors. |
| Where does AI fit? | One step: a chatbot such as SiteGPT, trained on the finished site, helps visitors find content. |
Does your site need a redesign or a refresh?
Start by naming the problem. A redesign costs far more than a content rewrite. It also adds risk to every URL it changes.
| What you see | Likely fix | Why |
|---|---|---|
| Copy is dated, but visitors can reach it | Content refresh | The structure works, so the pages need new words |
| The look is dated, but tasks work | Visual refresh | Templates can change while URLs stay the same |
| Visitors fail top tasks in testing | Redesign the structure | Navigation and page types are the barrier |
| The platform blocks accessibility, speed, or editing | Rebuild or replatform | Page-level fixes cannot reach the cause |
| Several departments publish conflicting pages | Redesign plus content governance | A new design alone will collect the same conflicts |
Five test participants are often enough to expose the worst barriers. Jakob Nielsen advises several small rounds with about five users each. Each fix also needs retesting (Nielsen Norman Group).
What should you do before a website redesign?
Set the goal, measure the old site, and account for every page. Decisions made here prevent most of the expensive problems later.
| Step | What to do | Done when |
|---|---|---|
| Name the goal | Pick one or two measurable outcomes, such as more completed applications or fewer repeat questions | Leadership has agreed on the numbers |
| List top tasks | Use interviews, surveys, search logs, and service questions to find what visitors must be able to do | About 10 tasks are ranked |
| Record the baseline | Save traffic, rankings, conversions, Core Web Vitals, and top pages | A dated copy exists outside the analytics tool |
| Export every URL | Combine sitemaps, server logs, analytics, and the CMS | Each URL sits on one sheet |
| Audit the content | Mark each page keep, rewrite, merge, or retire | Every row has a decision and an owner |
| Map redirects | Choose the closest new page for each old URL | No old URL with traffic or links is unmapped |
| Check accessibility | Run automated checks, then test with a keyboard and a screen reader | Known failures are logged against templates |
Nielsen Norman Group describes top tasks as the activities users must be able to do. It suggests about 10 to guide resources (NN/g). This short list settles arguments over home page space later.
The URL inventory matters most. It comes from Google's guidance on site moves. Google recommends collecting old URLs from four places: sitemaps, server logs, analytics, and the CMS. Then decide where each one should go (Google Search Central).
What should you do during design and build?
Design around the top tasks. Then run your tests on the built templates. Accessibility and speed are far cheaper to fix in a template than across a finished site.
| Step | What to do | Done when |
|---|---|---|
| Build the navigation from tasks | Label menus in visitors' words, and avoid internal department names | Test participants find top tasks without help |
| Write real content | Replace placeholder text before final design approval | Long titles and tables fit the templates |
| Set accessibility targets | Agree on a WCAG version and level, then test each template | Every template passes keyboard and screen reader checks |
| Set speed targets | Aim for LCP of 2.5 seconds or less, INP of 200 ms or less, and CLS of 0.1 or less | Key templates pass on mobile at the 75th percentile |
| Protect staging | Keep the test site behind a login or blocked from indexing | Search engines cannot reach it |
| Rebuild internal links | Point menus and body links at the new URLs | Links do not depend on redirects |
| Rebuild tracking | Recreate events, conversions, and consent settings | Test events reach analytics |
| Test with visitors | Run small rounds on top tasks, fix issues, and retest | The worst barriers have been removed |
WCAG, the Web Content Accessibility Guidelines, is the standard most accessibility rules point to. WCAG 2.2 is the current version. Some laws still name earlier versions, so confirm the one that applies to you.
The speed targets above are Google's published "good" thresholds for Core Web Vitals (web.dev). WebAIM's 2026 scan found low contrast text on 83.9% of home pages and missing form labels on 51%. Include both checks in the template review.
Regulated organizations have extra steps at this stage. Universities, hospitals and clinics, and public sector teams each have a separate guide.
What belongs on a launch day checklist?
Launch day needs a fixed order, a named owner for each step, and a rollback plan. Choose a low-traffic period with the full team available.
- Take a full backup of the old site and database.
- Put redirects live, and test a sample of top URLs.
- Remove staging noindex tags and robots.txt blocks.
- Check canonical tags and hreflang annotations against the new URLs.
- Submit the new XML sitemap in Search Console.
- Use the Change of Address tool only if the domain or subdomain changed.
- Submit each form and confirm that the message reaches a person.
- Test checkout, booking, and login paths from start to finish.
- Confirm analytics events are arriving, and annotate the launch date.
- Check top pages on a phone, and test them with a keyboard.
Use permanent server-side redirects, such as 301 or 308. Send each old URL directly to its final destination. Google warns against chains and against pointing many unrelated URLs at one page such as the home page.
What should you check after launch?
Monitor daily for the first week, then weekly until the numbers settle. Google notes that most pages on a small or medium site can take a few weeks to move. Larger sites take longer, and rankings may fluctuate in that period.
| When | Check | Action |
|---|---|---|
| Daily, first week | 404 errors, form delivery, server errors | Add missing redirects and fix failures the same day |
| Weekly, first month | Search Console coverage and top landing pages | Restore or improve content for pages that fell sharply |
| Day 30 | Baseline comparison for traffic and conversions | Separate normal fluctuation from real losses |
| Day 90 | Top task testing and accessibility recheck | Fix template issues and report results to leadership |
| One year or more | Redirect review | Keep redirects as long as possible, as Google advises |
A healthy traffic total can hide a loss. Analytics may show a healthy traffic total while a page that drove most conversions has disappeared.
Where does AI fit in a website redesign?
AI fits at one step: helping visitors find content on the new site. Add it in launch week, after redirects, core pages, and forms are working.
A redesign changes where things live. Returning visitors no longer know where pages are. A simple question can turn into a long search.
A chatbot trained on the finished site gives them another route. They ask in their own words. It answers from your pages with links to the source.
The same tool also helps the team. Questions the bot cannot answer show where the new site has a content gap.
| Route | Best job | Limit |
|---|---|---|
| Navigation | Browsing and understanding what exists | Depends on visitors recognizing your labels |
| Site search | Finding a page with known words | Returns a list, so the visitor still has to read and choose |
| Chatbot | Answering a specific question in the visitor's words | Covers only trained content, and gives one conversation instead of an overview |
Large sites sometimes need more than a chat widget. Teams comparing those options can read about enterprise site search and adding AI answers to website search.
How to add a chatbot after launch
SiteGPT is one way to complete this step. It trains on website links and sitemaps. It can also read files such as PDF and DOCX.
- Add the new sitemap after launch, so the bot reads final URLs.
- Ask it each top task as a real question, and open each source link.
- Set human escalation, so a visitor can reach your team from the chat.
- Review unanswered questions each week, then fix the page or add a custom response.
- Keep source links visible, so visitors can check where each answer came from.
Human escalation works on any SiteGPT plan. The unanswered questions panel needs the Growth plan or higher.
SiteGPT answers in a chat window. It does not produce a search results page. It takes no actions on live systems during a chat.
It can explain how to change a booking, but it cannot change one itself. It also cannot fix weak content. It answers only from what the site says.
Which redesign mistakes cost the most?
Most serious redesign losses come from a short list of skipped steps. Each one has a simple prevention step.
| Mistake | What goes wrong | Prevention |
|---|---|---|
| No URL inventory | Pages with links and traffic vanish | Export every URL before design starts |
| Redirecting everything to the home page | Visitors land away from their answer | Map each URL to its closest page |
| Deleting "thin" pages by default | Long-tail traffic disappears | Check traffic and links before retiring a page |
| Leaving noindex in place | The new site drops out of search | Make it a named launch step |
| Designing around the org chart | Visitors cannot guess where things live | Build navigation from top tasks |
| Declaring victory on launch day | Losses go unnoticed for months | Book the 30-day and 90-day reviews now |
Frequently asked questions
Planning
What should a website redesign checklist include? It should cover five phases. Plan the goals and top tasks, audit every existing URL, build and test the new templates, run launch day in a fixed order, and monitor the site for at least 90 days. The steps most often skipped are the URL inventory, the redirect map, and the after-launch comparison against the old site's numbers.
How do you know whether a site needs a redesign or a refresh? Test whether the structure is the problem. If visitors can reach their top tasks and the templates work on mobile, then rewriting pages or restyling them is usually enough. If the navigation, the content model, or the platform blocks those tasks, a redesign is justified. Run a small usability test on the current site before deciding.
How long does a website redesign take? The timeline depends on scope. There is no reliable standard. A site with few pages and no URL changes moves faster than a large site changing domains, content, and platform at once. Plan the schedule from your own page count and approval steps. Leave a buffer after launch to fix what monitoring finds.
SEO and launch
Will a website redesign hurt SEO? It can. The risk comes mostly from changed URLs, removed content, and weaker internal links. Google says rankings may fluctuate during a move and that most pages on a small to medium site can take a few weeks to move. A complete redirect map, retained content, and updated internal links reduce the damage.
How long should redirects stay in place after a redesign? Google recommends keeping them for as long as possible, generally at least one year. Redirect each old URL straight to its closest new page. Avoid chains, and avoid sending many unrelated old URLs to the home page.
Do you need the Change of Address tool for a redesign? Only when the domain or subdomain changes. Google says the tool is unnecessary for path changes, moves from HTTP to HTTPS, and switches between www and non-www on the same domain. A redesign that keeps its domain does not need it, even when many URLs change.
AI and chatbots
Where does AI fit in a website redesign? Add a chatbot trained on the new site in launch week, after redirects and core pages are done. It gives visitors who can no longer find a familiar page a way to ask for it in their own words. It also records the questions the new site failed to answer. That gives the team a list of content gaps to fix.
Can a chatbot replace site search or navigation? No. A chatbot such as SiteGPT answers in a chat window from your content and shows source links. It does not produce a search results page. It does not replace clear navigation either. Treat it as a third route for visitors who have a specific question and cannot find the page.
What happens to an existing chatbot when URLs change? It can keep old pages. On SiteGPT, auto-sync adds and refreshes pages. It never deletes content. Pages removed from the site stay in the chatbot until they are deleted from the Links List. A sitemap scan, available from the Scale plan, removes URLs that have left the sitemap. Plan this step before launch.
Sources
- Google Search Central, site moves with URL changes, for URL mapping, redirect, sitemap, timing, and Change of Address guidance
- web.dev, Web Vitals, for Core Web Vitals thresholds
- WebAIM Million 2026, for home page accessibility failure rates
- W3C, WCAG overview, for the current WCAG version
- Nielsen Norman Group, top tasks, and why you only need to test with 5 users
- SiteGPT product pages and documentation: home, pricing, keeping content up to date, widget appearance, analytics, and human support