Home/Blog/ Web Design/ Website Redesign Checklist: 27 Things to…
Web Design

Website Redesign Checklist: 27 Things to Fix Before Launch

Website Redesign Checklist: 27 Things to Fix Before Launch

Half of all website redesigns cause organic traffic to drop. Not slightly, but by 20 to 60% in the first 90 days. The reason is almost always the same: a launch checklist that prioritised design and content over the technical SEO plumbing.

This is the 27-point pre-launch checklist our team runs on every Australian website we redesign. Use it and you protect your rankings while improving every other metric.

Quick Answer

A website redesign checklist covers technical SEO (301 redirects, sitemap, robots.txt, schema), content (meta tags, internal links, image alt text), performance (Core Web Vitals, hosting, CDN), tracking (GA4, Search Console, conversion goals), legal (privacy policy, cookies, accessibility) and design (mobile responsive, browser testing, brand consistency).

Key Takeaways

  • The single biggest cause of post-launch traffic loss is missing or broken 301 redirects from old URLs to new.
  • Most Australian redesigns forget at least 5 items on this list, especially around tracking and legal.
  • The pre-launch checklist takes 2 to 5 days to execute properly; do not compress this stage.
  • Post-launch monitoring for 14 days is non-negotiable.
  • Treat the redesign as a migration, not a rebuild.
Website wireframe sketches on a tablet

Before You Start: The 3 Things to Do 4 Weeks Out

  1. Crawl the existing site with Screaming Frog or Sitebulb. Export every URL, title, meta, H1, status code, inbound link count. This is your baseline.
  2. Pull current organic traffic and rankings from Search Console and your rank tracker. Export at the URL level.
  3. Document every existing 301 redirect in the current .htaccess or server config.

Section 1: Technical SEO (Items 1 to 8)

1. 301 redirects from every old URL to the closest matching new URL. This is the item that causes most post-launch traffic loss, and the failure mode is rarely a missing redirect file. It is redirects that point to a page that then redirects again, redirects to the homepage instead of the equivalent page, or redirects that were written against the staging domain. Export the old URL list from your baseline crawl, map every URL that has either traffic or an inbound link, and test the full list with a crawler in list mode before launch, not after.

2. Robots.txt allows crawling of the new site. The staging Disallow: / rule shipping to production is one of the most common and most damaging launch errors in the industry, and it can go unnoticed for weeks because the site looks perfectly normal to visitors. Check the live file within minutes of go-live.

3. Noindex tags removed from production templates. The WordPress setting under Settings, Reading that discourages search engines is the usual culprit, along with template-level meta robots tags left over from development. Check a rendered page source rather than trusting the CMS setting alone, because a plugin or theme can inject its own.

4. XML sitemap updated and submitted to Search Console. It should contain only canonical, indexable, 200-status URLs. A sitemap full of redirects and 404s slows discovery of the pages you actually want crawled and muddies your coverage reporting for weeks.

5. Internal linking preserved or improved. Redesigns routinely strip out contextual body links in favour of cleaner-looking pages, which quietly removes the internal link equity that was holding up your best-ranking URLs. Compare inbound internal link counts per URL against your pre-launch crawl and make sure no important page has lost its links.

6. Schema markup implemented for all key pages (LocalBusiness, Organisation, BreadcrumbList, FAQ, Article, Product, Service).

7. Canonical tags correct on every page, self-referencing by default, and pointing at the HTTPS non-staging version. Watch for canonicals hard-coded to the staging domain, which is a common way to hand your rankings to a URL nobody can reach.

8. SSL valid and HTTPS forced sitewide.

Our web design and development team ships every Australian build with all 8 items verified before go-live.

Section 2: Content and On-Page (Items 9 to 14)

9. Meta titles and descriptions hand-written for every public URL rather than auto-generated from a template. Keep titles under 60 characters and descriptions under 155 so they are not truncated. Auto-generated metadata is the single most common reason a technically clean redesign still loses click-through rate, because the new titles read like a sitemap rather than a search result.

10. H1 tags present, unique and relevant on every page, and only one visible H1 per page. Check the rendered output rather than the editor, because many themes output a second H1 in a hero block or a hidden page-header element on top of the one in your content.

11. Image alt text on every meaningful image, describing what the image shows rather than repeating the target keyword. Decorative images should carry an empty alt attribute so screen readers skip them. This is both an accessibility requirement and a small, cheap source of image search traffic that most redesigns discard.

12. Internal links updated to new URL structure.

13. All blog and resource content migrated and reformatted.

14. A custom 404 page that returns a genuine 404 status code and helps the visitor recover, with search, a link to the main service pages and a link home. Confirm it does not return a 200 status, because soft 404s let broken URLs sit in the index indefinitely.

Section 3: Performance and Hosting (Items 15 to 19)

15. Core Web Vitals all in the green on mobile (LCP under 2.5s, INP under 200ms, CLS under 0.1).

16. Image optimisation across the site (WebP or AVIF, properly sized, lazy-loaded).

17. CDN configured with Australian edge nodes (Cloudflare, Bunny, Fastly).

18. Hosting can handle expected launch traffic.

19. Backups configured and tested (UpdraftPlus, BlogVault, ManageWP).

Section 4: Tracking and Analytics (Items 20 to 23)

20. GA4 installed and verified firing across the site.

21. Search Console verified for the new domain or property.

22. Conversion goals and events configured.

23. Server-side tracking implemented, which is now close to essential rather than optional. Browser-based tracking loses a material share of conversions to ad blockers, iOS privacy features and cookie restrictions, and that loss falls hardest on exactly the paid campaigns you are trying to optimise.

Our Australian SEO services include analytics implementation and review as standard.

Section 5: Legal and Accessibility (Items 24 to 27)

24. Privacy Policy compliant with Australian Privacy Act 1988.

25. Terms and Conditions and Returns Policy current.

26. Cookie consent banner (where required).

27. Accessibility baseline (WCAG 2.1 AA). Use axe DevTools or WAVE to scan.

Post-Launch: The 14-Day Monitoring Routine

Day 0 (launch day): submit new sitemap to Search Console; resubmit critical pages via URL Inspection; verify GA4 is firing; manually test 20 critical URLs.

Days 1 to 3: check Search Console for crawl errors daily; watch GA4 for traffic drops; test 10 more URLs randomly; monitor uptime.

Days 4 to 7: compare organic traffic and ranking to the pre-launch baseline; fix any 404s or redirect chains immediately; check Core Web Vitals field data.

Days 8 to 14: run a full Screaming Frog crawl, compare to pre-launch; submit new pages for indexing; re-check conversion goals.

How to Build a Redirect Map That Actually Works

The redirect map is the single most important artefact of a redesign, and most of them are built badly. A workable process:

  1. Start from data, not the sitemap. Combine your crawl export with Search Console URLs from the last 12 months and your top URLs by inbound links. Pages with no traffic today may still hold links that carry value.
  2. Map to the closest equivalent, never to the homepage. A bulk redirect to the homepage is treated as a soft 404 and passes almost nothing. If there is genuinely no equivalent page, redirect to the most relevant category or service page.
  3. One hop only. Old URL to final new URL, directly. Chains of two or three redirects dilute value and slow crawling, and they accumulate silently as a site ages.
  4. Keep the old redirects. If the current site already redirects URLs from a previous migration, those rules must survive. Dropping them breaks a chain that may go back years.
  5. Test in list mode before launch. Run the full old URL list through a crawler against staging and check every status code and destination. Fix everything that is not a single 301 to a 200.

If Traffic Drops After Launch, Diagnose in This Order

Some fluctuation in the first fortnight is normal as Google recrawls. A sustained drop beyond about 10% needs investigation, and the order matters because the cheapest checks catch the most common causes.

  1. Check robots.txt and meta robots on live pages. This catches the majority of catastrophic drops.
  2. Crawl the old URL list and look for 404s, redirect chains and redirects to the homepage.
  3. Compare indexed page counts in Search Console before and after, and read the Page Indexing report for new exclusion reasons.
  4. Compare titles and H1s against the baseline crawl. A templated rewrite can cost significant click-through rate without touching rankings.
  5. Check Core Web Vitals field data, which lags by 28 days, and server response times under real traffic.
  6. Only then look at content changes and internal linking. This is the slowest to diagnose and the least likely single cause.

Who Signs Off What

Redesigns fail on ownership as often as on technique. Before launch, put a name against each section rather than leaving it with the vague collective of the project.

SectionOwnerSign-off evidence
Technical SEOSEO leadCrawl export with all redirects at 301 to 200
Content and on-pageContent leadMetadata sheet, one row per URL
PerformanceDeveloperLab and field Core Web Vitals results on mobile
TrackingAnalytics ownerTest conversion recorded end to end
Legal and accessibilityBusiness ownerPolicy pages live, accessibility scan report

FAQ

How long does a website redesign take in Australia?

Most Australian SMB redesigns take 8 to 16 weeks from kickoff to launch. Discovery and content usually take longer than the build itself, and content is the stage that slips most often because it depends on input from people whose main job is something else. Add 2 to 5 days at the end purely for the pre-launch checklist and do not let that time be absorbed by design revisions.

Will a redesign hurt my SEO?

It can, if the checklist is skipped. Done properly, a redesign should hold or slightly improve organic traffic in the first 90 days.

How much does a redesign cost in Australia?

Full agency redesigns typically cost $8,000 to $30,000 in Australia, while a visual refresh on the existing structure costs $2,000 to $6,000. The deciding factor is usually whether the URL structure and templates change. If they do, you are running a migration and should budget for the SEO work that comes with one.

Can I do a redesign without losing rankings?

Yes, if every item on this checklist is verified, especially 301 redirects, robots.txt, noindex removal, and internal linking.

Should I launch on a Friday?

No. Launch Tuesday or Wednesday morning, so that your developer, SEO and analytics people are all available for the 48 hours when problems actually surface. Friday launches mean small issues sit undiscovered over a weekend, and by Monday they have been crawled and indexed. Avoid launching immediately before a public holiday or a peak trading period for the same reason.

What’s the most-missed item?

Server-side tracking is missed on the large majority of Australian SMB redesigns, and schema markup on most of them. The most damaging miss, though, is smaller and duller: redirects that were tested against staging and never re-tested against production. It looks complete on the checklist and fails silently on launch day.

Conclusion

Every item on this 27-point checklist is a guardrail that has caught a real problem on a real Australian project. Sign off each item with the person responsible. Hold the launch date if any item is incomplete. Book a free 30-minute strategy session and we will scope the project to protect your existing organic traffic.

Related reading

Ready to Grow Your Organic Traffic?

Let VYRO build and execute the right SEO strategy for your business - from local to international.

Get a Free SEO Audit Explore Our Services
VYRO Web
Typically replies instantly
👋 Hi there! How can we help you grow your business today?
Choose a topic