Website Redesign Checklist for Business Owners

Most redesign projects don’t fail because of bad design. They fail because someone forgot to set up redirects, or the contact form silently broke, or Google got locked out of the new site for three weeks. This checklist is built to prevent exactly that.

The Website Redesign Checklist Starts Before You Touch Anything

Before a single page gets moved or rebuilt, you need a content inventory. That means pulling a list of every URL on your current site, not just the pages in your nav. Tools like Screaming Frog (free up to 500 URLs) can crawl your site and export every live page in a few minutes. Save that spreadsheet. You’ll need it when you map redirects later.

While you’re at it, note which pages actually drive traffic. Pull 90 days of data from Google Analytics or Search Console and sort by sessions. If your /services/hvac-repair page gets 400 visits a month, that URL needs to either stay the same in the redesign or redirect perfectly to the new one. Killing high-traffic URLs without redirects is one of the most common ways businesses lose search rankings after a redesign.

Also back up your current site completely before any work starts. Hosting providers have varying backup policies, and some don’t retain more than a week. Download a full copy of your files and database and store it somewhere you control.

Content and Copy: What to Keep, What to Cut, What to Rewrite

A redesign is a good time to audit your content honestly. Pages that haven’t been updated in three years, service descriptions that no longer match what you offer, staff bios for people who left, all of that needs a decision: update it, redirect it to something relevant, or delete it and let it 404 cleanly.

For pages you’re keeping, verify the copy is accurate. Phone numbers, addresses, service areas, hours, pricing, all of it. These details live on your site for years and go stale faster than you’d think. If you’ve changed your service radius or added a new offering since the last redesign, now’s the time to reflect that.

Make sure every page has a unique title tag and meta description written before launch. These don’t need to be long. They need to be accurate and specific. “Plumbing Repair in Grand Rapids, MI | Kowalski Plumbing” is better than “Home” every single time.

The Technical Checks That Actually Matter

Redirects deserve their own section in any website redesign checklist because they’re where things quietly break. Every old URL that’s changing needs a 301 redirect pointing to the closest matching new URL. Don’t redirect everything to your homepage. Google treats that as a soft 404 and it tells visitors nothing. Map old URLs to their logical new equivalents.

Forms are the other thing that breaks constantly during redesigns. Contact forms, quote request forms, newsletter signups, all of them need to be tested with a real submission after the new site goes live. Not just a visual check. Actually submit the form and confirm the email arrives. Check that any confirmation messages or auto-replies fire correctly too.

SSL should be active on the new domain before launch. If your site loads over HTTP instead of HTTPS, modern browsers flag it immediately and it affects search rankings. Most hosts provision SSL automatically now, but verify it yourself before you point DNS anywhere.

Check your robots.txt file. During development, sites are often set to block search engines so Google doesn’t index a half-built site. That’s correct practice, but you need to remove that block before launch. Forgetting this is surprisingly common and can leave your site invisible to search engines for weeks.

A Real Example: Indiana Photo Booth

When we redesigned Indiana Photo Booth, a photo booth rental company based in Indianapolis, the old site had several service pages at URLs that didn’t match the new site architecture. The old structure used generic page IDs. The new one used clean, descriptive URLs like /photo-booth-rental-indianapolis.

We mapped every old URL to its new equivalent before launch day and loaded the redirects before DNS switched. When the new site went live, any existing links or bookmarks pointing to old pages followed cleanly to the right destinations. Search Console showed zero coverage drops in the weeks after launch. That’s what proper redirect handling looks like in practice.

The site also had a quote request form that needed to route to a new email address. We tested it three times across different devices before calling the project done. One of those tests revealed the mobile keyboard was triggering a layout bug that blocked the submit button on certain screen sizes. Caught it, fixed it, done.

DNS, Hosting, and Go-Live Day

DNS changes take time to propagate, usually between 30 minutes and 48 hours depending on the registrar and TTL settings. If you lower your TTL to something like 300 seconds (five minutes) a day or two before launch, the switch happens much faster when you’re ready.

On launch day, go through the site on multiple devices and browsers. Chrome, Safari, Firefox, an Android phone, an iPhone. Check that images load, fonts render, pages scroll correctly, and the mobile navigation works. This takes about 20 minutes and catches the things that only appear on real devices.

Set up Google Search Console on the new site if it wasn’t already there, verify ownership, and submit your XML sitemap. This tells Google where to find all your pages and speeds up indexing. You can also use the URL Inspection tool to request indexing on your most important pages manually right after launch.

Post-Launch: What to Monitor in the First 30 Days

Analytics is your signal that things are working. Confirm Google Analytics (or whatever you’re using) is firing correctly on the new site before you close out the project. Check the real-time view while clicking around the new site. If you see sessions, the tracking is live. If you don’t, something broke during migration.

Monitor Google Search Console’s Coverage report over the first two weeks. You’re looking for a spike in 404 errors, which would indicate redirects that got missed, or a drop in indexed pages, which might mean a crawling issue. Neither of these is catastrophic if you catch them early, but both get worse the longer they sit.

Accessibility is worth a quick check too. Run the new site through a tool like WAVE or Google’s Lighthouse. You’re looking for missing alt text on images, low color contrast, or form fields without labels. These issues affect both users and search engines. They’re also usually quick fixes when caught early.

How Web Lift Up Handles All of This

This checklist covers a lot of ground, and it can feel like a project in itself before the actual redesign even starts. That’s part of why we built Web Lift Up the way we did.

For a flat $499, we handle the full redesign, including the audit, the redirect mapping, the SEO foundation with proper metadata and structured data, form testing, and launch. The whole thing runs seven days start to finish. Day one is the audit, days two through four are building your demo, days five and six are revisions, and day seven is launch. You see a working demo before you pay anything.

You own the code, the content, and your domain when we’re done. No retainer, no platform lock-in, no monthly fee attached to the redesign itself. If you want social media management after launch, that’s available as an add-on at $250 per month, but it’s never required.

If you’ve got a redesign coming up and want someone who’s already run this checklist on real projects, reach out at [email protected].