A website redesign checklist is a phase-by-phase list of tasks that keeps a new site from losing traffic, leads or usability. In 2026 it should cover nine phases: set goals and KPIs, inventory your content, plan the structure (including Arabic and English), design for accessibility, set a speed budget, protect URLs with redirects, rebuild analytics, then run launch QA and post-launch monitoring. Skip a phase and you usually pay for it after launch.
Below is the full checklist with a summary table you can share with your team.
Redesign, refresh or migration?#
A website redesign changes the design, structure and often the content of a site. A refresh updates visuals while keeping structure. A migration moves the site to a new platform, domain or URL structure. Many projects combine all three, which is why redesigns are risky: every change to URLs, templates or content can affect rankings. We cover the SEO side of moves in depth in our separate guide on website migration without losing SEO; this article focuses on the whole redesign project.
Phase 1: Goals and KPIs#
Start with the business problem, not the look. Write down what the new site must achieve and how you will measure it.
- Pick 3–5 KPIs: qualified form leads, WhatsApp click-to-chat taps, quote requests, calls, sales or newsletter sign-ups.
- Record a baseline: export at least the last 12 months of organic traffic, top landing pages and conversions from Google Analytics 4 and Search Console before anything changes.
- Use GA4 terminology correctly: GA4 renamed “conversions” to key events in March 2024, according to PPC Land; Google Ads conversions are now a separate object. Agree which key events count as success.
- Interview users and sales staff: ask what visitors cannot find today and which questions they repeat on WhatsApp or the phone.
Phase 2: Content inventory and audit#
A content inventory is a spreadsheet of every URL on the current site with its traffic, backlinks, conversions and owner. Crawl the site, combine the crawl with analytics data, and decide one action per page:
- Keep pages that rank, convert or attract links.
- Improve pages with potential but thin or outdated content.
- Merge overlapping pages into one stronger page.
- Remove pages with no traffic, links or business value, and redirect them to the closest relevant page.
Our website audit and performance service produces this inventory with speed and technical findings before design starts.
Phase 3: Structure and bilingual EN/AR planning#
In Jordan and the GCC, most business sites need Arabic and English. Plan both languages in the sitemap from day one, not as a later translation job.
- Use clear language folders such as
/en/and/ar/, with one equivalent page per language. - Add hreflang correctly: Google’s documentation says each language version must list itself and every other version, and “if two pages don’t both point to each other, the tags will be ignored.” Add an
x-defaultfor visitors whose language you do not serve. - Set direction in markup: the W3C advises adding
dir="rtl"to thehtmlelement of Arabic pages and not setting base direction with CSS. - Write Arabic natively: Arabic pages should target how Arabic users actually search, with their own titles and meta descriptions, not a literal translation.
- Design both layouts: mirrored navigation, icons that flip where direction matters, and Arabic fonts tested at real sizes.
Phase 4: Design and accessibility#
Accessibility is where most sites fail quietly. The WebAIM Million 2026 report found automatically detectable WCAG 2 failures on 95.9% of the top one million home pages, with an average of 56.1 errors per page. The most common were low-contrast text (83.9% of pages), missing image alt text (53.1%), missing form labels (51%) and empty links (46.3%).
Design to WCAG 2.2 level AA, which the W3C published as a Recommendation on 5 October 2023. It added nine success criteria, including Target Size (Minimum), Focus Not Obscured (Minimum), Dragging Movements and Accessible Authentication at level AA.
- Check colour contrast in the design files before development.
- Give every image meaningful alt text in both languages.
- Label every form field and make error messages clear.
- Make buttons and links large enough to tap on mobile.
- Set the correct
langattribute on every page; WebAIM found it missing on 13.5% of home pages.
Phase 5: Set a speed budget#
A speed budget is a fixed limit on page weight and loading metrics that every template must meet before launch. Set it before design, because heavy hero videos and sliders are design decisions.
- Core Web Vitals targets: according to Google’s web.dev, a good experience means Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint at or below 200 milliseconds and Cumulative Layout Shift at or below 0.1, measured at the 75th percentile of page loads.
- Page weight: the HTTP Archive Web Almanac 2025 reports a median home page of 2.56 MB on mobile and 2.86 MB on desktop. Aim to be well below the median.
- Why it matters: a study by Deloitte and 55 for Google found that a 0.1-second improvement in mobile site speed raised conversion rates by 8.4% for retail sites and 10.1% for travel sites.
- Practical rules: modern image formats, lazy-loading below the fold, few web fonts (Arabic fonts can be large), and a strict limit on third-party scripts.
Phase 6: Keep URLs and build a redirect map#
The safest redesign keeps existing URLs wherever possible. When URLs must change, build a redirect map: a two-column list of every old URL and its new equivalent. Google’s site-move guidance recommends server-side permanent redirects (301 or 308), mapping old URLs to their closest new counterparts rather than the home page, avoiding redirect chains, and keeping redirects “generally at least 1 year.” Our SEO team handles the full migration process when platforms or domains change.
Phase 7: Analytics, tracking and privacy#
- Rebuild GA4 key events for forms, WhatsApp clicks, calls and downloads on the staging site, and test them.
- Keep the same GA4 property so historical data stays comparable.
- Verify the new site in Google Search Console and submit the new XML sitemap at launch.
- Review consent: according to Clyde & Co, Jordan’s Personal Data Protection Law No. 24 of 2023, in force since 17 March 2024, generally requires prior consent that is clear, written and tied to a specific purpose, and Saudi Arabia’s PDPL has been fully enforceable since 14 September 2024. Update your privacy notice and form consent text.
Phase 8: Launch QA#
Run launch QA on staging, then again on the live site within the first hour.
- Remove staging
noindextags and check robots.txt. - Test every redirect in the map and crawl the new site for 404s and broken links.
- Submit every form in both languages and confirm emails arrive.
- Check titles, meta descriptions, canonical tags, hreflang and schema on key templates.
- Test on real phones, in Arabic and English, on Safari and Chrome.
- Confirm SSL, backups, uptime monitoring and analytics are working.
Phase 9: Post-launch monitoring#
Google’s documentation notes that for small and medium sites it can take a few weeks for most pages to move to new URLs, so expect some fluctuation. During the first weeks, check Search Console daily for crawl errors, fix new 404s, and compare traffic and key events against your baseline. After about three months, review your KPIs, survey users, and plan the next round of content improvements.
Website redesign checklist by phase#
| Phase | Key tasks | Done when |
|---|---|---|
| 1. Goals and KPIs | Define 3–5 KPIs, export 12-month baseline, list key events | KPIs signed off by management |
| 2. Content inventory | Crawl site, add traffic and links, mark keep/improve/merge/remove | Every URL has an action |
| 3. Structure and EN/AR | Sitemap for both languages, hreflang plan, RTL layout rules | Bilingual sitemap approved |
| 4. Design and accessibility | WCAG 2.2 AA checks, contrast, alt text, labels, tap targets | Designs pass accessibility review |
| 5. Speed budget | Set LCP, INP, CLS and page-weight limits per template | Staging templates meet the budget |
| 6. URLs and redirects | Keep URLs, build 301 redirect map, avoid chains | Every changed URL has a tested redirect |
| 7. Analytics and privacy | Rebuild GA4 key events, Search Console, consent text | Test events visible in GA4 |
| 8. Launch QA | Remove noindex, test forms, redirects, metadata, devices | QA list fully ticked on live site |
| 9. Post-launch | Monitor 404s, traffic, key events; review at three months | KPIs at or above baseline |
Common redesign mistakes#
- Starting with visuals before goals and content are agreed.
- Deleting old pages that still bring traffic or backlinks.
- Treating the Arabic site as a translation after the English site is finished.
- Launching without testing forms and tracking, then losing weeks of lead data.
- Adding heavy animations that push loading past the speed budget.
Planning a redesign in 2026? Consult One’s web design team in Amman runs bilingual Arabic/English redesigns for businesses in Jordan, the GCC and the USA, from content audit to post-launch monitoring. Share your current site and get a free quote with a phase-by-phase plan.
FAQ#
What should a website redesign checklist include?
A complete website redesign checklist covers goals and KPIs, a content inventory, site structure and language planning, accessible design, a speed budget, URL preservation with a redirect map, analytics and privacy setup, launch QA and post-launch monitoring. Each phase should have a clear owner and a “done when” condition so nothing is skipped before the new site goes live.
Will a website redesign hurt my SEO?
It can, but it does not have to. Rankings usually drop when URLs change without redirects, ranking pages are deleted, content is cut, or the new site is slower. Keep URLs where possible, redirect every changed URL with a 301 to its closest equivalent, preserve strong content, and monitor Search Console closely for several weeks after launch.
Should I keep the same URLs when redesigning?
Yes, wherever possible. Keeping URLs is the simplest way to protect rankings and backlinks. If the structure must change, map every old URL to its closest new page and use permanent 301 or 308 redirects. Google recommends keeping redirects in place generally for at least one year and avoiding redirect chains or sending everything to the home page.
How do I plan Arabic and English versions in a redesign?
Plan both languages in the sitemap from the start, using folders such as /en/ and /ar/ with one equivalent page per language. Add hreflang tags that point both ways, set dir=”rtl” on Arabic pages, write Arabic content natively for local search habits, and design mirrored layouts and Arabic typography alongside the English design.
What speed targets should a redesigned website meet?
Aim for Google’s “good” Core Web Vitals at the 75th percentile: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint at or below 200 milliseconds, and Cumulative Layout Shift at or below 0.1. Also set a page-weight budget well below the 2025 Web Almanac median of 2.56 MB for mobile home pages.
What should I do after launching a redesigned website?
Check Google Search Console daily in the first weeks for crawl errors and new 404s, and fix them quickly. Compare organic traffic and GA4 key events with your pre-launch baseline, confirm forms and WhatsApp links still convert, and test pages on real phones. After about three months, review KPIs and plan the next content improvements.













