A website redesign gets easier when the important decisions happen before the first layout review. Otherwise, a conversation about the homepage can turn into a surprise investigation into who owns the domain.
Use this website redesign checklist to organize the business decisions, content, access, and testing your project needs. You’ll give your designer a clearer brief, make quotes easier to compare, and reduce the number of things discovered five minutes before launch.
1. Define what the new website needs to accomplish
Write down the main customer action you want the site to support, such as requesting an estimate, booking an appointment, buying a product, or calling the business. Identify who should take that action and what they need to understand first.
Record the current problems in specific terms. “People can’t find our service area” gives your team something to solve. “The website feels old” needs a little more investigation.
Review existing traffic and inquiries, then choose a few measurements to track after launch. Our website lead-generation checklist can help identify problems worth carrying into the brief.
2. Inventory the pages and decide what stays
Make a list of current pages and their URLs. Mark each one to keep, improve, combine, or retire. Include service pages, contact details, downloadable documents, and landing pages used in advertising.
Check which pages already attract useful visitors or support sales conversations. Preserve their valuable information even if the design changes.
Agree on the new page list before comparing proposals. A five-page project can become a twenty-page project surprisingly quickly when every service suddenly needs its own home. Identify those needs while you can still adjust the scope.
3. Collect content and assign an owner
Gather your current logo files, brand colors, business information, service descriptions, approved testimonials, and good-quality photographs. Confirm you have permission to use the images and quotes.
Choose photos that show the business customers will actually encounter. Replace old team portraits, retired products, and project examples that no longer reflect your work.
Assign responsibility for every missing item and agree on a deadline. Decide who writes the copy, who checks factual details, and who has final approval. Use one shared folder and agree on filenames before you get to “final final newest.”

4. Confirm access and define the project scope
Identify who controls the domain registration, hosting, website administration, business email, analytics, and connected services. Arrange account access through secure invitations where available.
Keep ownership and billing responsibilities clear. Your developer should know which systems must continue working when the new website goes live, especially email.
Ask proposals to specify the pages, copywriting, image sourcing, forms, integrations, revision rounds, launch work, and training included. Clarify what would require a separate quote. Gravity Junction’s web design service is a starting point for discussing your project’s requirements.
5. Plan forms, bookings, and follow-up
List every action a visitor can take and where the information should go. That includes contact forms, appointment requests, email sign-ups, phone links, and online purchases.
Decide who receives each inquiry and what confirmation the customer sees. If information goes into a CRM, identify the required fields and who will check that connection.
Keep form questions useful and labels visible. The W3C’s guidance on labeling form fields explains how associating each label with its field helps people use the form. Include clear error messages and test the complete submission process.
6. Give existing search traffic a place to land
Before URLs change, assign someone to map important old addresses to their appropriate new destinations. Include links used in ads, emails, directory listings, and downloadable materials.
Google’s site-move guidance recommends permanent redirects for moved URLs. Send visitors to the page that best matches the one they were looking for.
Ask the launch team to check internal links, confirm public pages are eligible for indexing, and review the sitemap in Search Console. If the development site used a noindex setting, make sure the intended public pages launch without it. Put these tasks in the project plan and name the person who will verify them.
7. Review the website on real devices
Read the main pages on a phone, tablet, and computer. Open the menu, follow the primary button, check phone links, and submit clearly labeled tests through every form.
Look for clipped headings, tiny text, awkward image crops, overlapping elements, and controls that are difficult to tap. Try keyboard navigation through the menu and forms, and ask your developer to check contrast, image alternatives, and accessible labels.
Ask someone outside the project to try a real customer task, such as finding a service and requesting an appointment. Record the page, device, and issue in one shared list so the team can reproduce the problem.

8. Agree on launch and ongoing care
Name the person who approves launch and the person who performs it. Confirm the backup and recovery plan, the timing of domain changes if needed, and who handles urgent issues.
After launch, repeat the contact and booking tests, confirm notifications arrive, and check that analytics records expected activity. Decide who owns updates, backups, troubleshooting, and future content changes.
Our website support page explains the help available to Gravity Junction hosting clients. Review ongoing responsibilities before the project closes.
Bring a useful brief to the first conversation
Start with a page list, your main business goal, known problems, available content, and someone who can make final decisions. Those details give the project a workable foundation.
Ready to put your checklist to use? Tell Gravity Junction what your new website needs to accomplish.




