Redesigning your website? An SEO checklist for New Jersey business owners
Protect valuable pages, plan redirects, and verify lead tracking before and after a redesign with this practical website launch checklist.
A redesign needs a plan for the customers and search visibility your current pages already serve. Make the URL map and launch checks part of the project before approving the new design.
The new website looks cleaner. The team likes the photography. Then someone discovers that an old service link is broken, a useful page has disappeared, or contact requests are no longer reaching the office. These are launch problems a visual review alone cannot catch.
If your New Jersey business is rebuilding its website, involve SEO and lead tracking before the design is finalized. You do not need to manage every technical detail yourself. You do need clear deliverables, an accountable launch owner, and a way to verify that existing customers can still find what they need.
1. Identify the pages that already do useful work
Ask for an inventory of the current site before pages are removed or renamed. Include service pages, location information, products, articles, and useful downloads. Add available evidence: search clicks, customer inquiries, sales, and links from other websites. Also ask your team which pages they send customers during conversations.
Give each page a decision: retain, improve, combine, or retire. A page with limited traffic might still answer an important qualification question. A high-traffic page might attract people you cannot serve. Make these decisions with business context instead of assuming that a smaller navigation menu requires deleting useful content.
2. Agree on a page-by-page URL plan
Keep useful URLs when there is no reason to change them. Where a URL changes, map the old address to its closest relevant replacement and use a permanent server-side redirect. Avoid sending every retired page to the homepage. If there is no meaningful replacement, an appropriate not-found response may be the honest result.
Google’s migration guidance also calls for updating internal links, canonical references, and sitemaps to the new URLs. Keep permanent redirects for at least a year, and preferably longer when old links still matter. Ask your developer for the mapping as a reviewable deliverable rather than a verbal assurance that redirects are handled.
3. Preserve the reasons customers choose you
A redesign can accidentally remove the details that made an old page useful. Compare the proposed page with customer questions: what is included, where is the service available, what happens next, and why should someone trust the business? Keep genuine evidence, practical explanations, and important local information.
Imagine a Morris County service company combining several pages into one short “What we do” section. The new layout might be easier to scan but fail to explain a specialist service. That is a reason to retain a dedicated page, not to fill the homepage with repeated keywords. Make each important customer journey explicit in the design review.
- Check that valuable service and product details survived the rewrite.
- Retain accurate business contact and location information.
- Preserve approved testimonials and case-study evidence with their context.
- Ensure mobile visitors can reach the same essential information.
4. Test a real customer journey before launch
Choose a few representative journeys: a new visitor requesting a quote, an existing customer finding contact details, and a shopper selecting a product if applicable. Test them on a phone and a desktop. Follow links from older emails or documents as well as the new menu.
Have the launch owner confirm that production pages are accessible to search engines, test-site restrictions have been removed where appropriate, and analytics still records the intended actions. Submit a clearly labeled test inquiry and verify both receipt and the customer confirmation. A success message alone does not establish that your team received the lead.
5. Keep someone responsible after the site goes live
Schedule a launch-day check and follow-up reviews. Look for broken pages, unexpected indexing exclusions, missing leads, and changes to important landing pages. Keep the old-to-new URL map and a dated launch log accessible to the people handling support.
Search rankings can fluctuate while Google processes a significant move. Investigate a drop with page-level evidence instead of immediately changing every title or rolling back the whole site. Compare tracking settings, redirects, availability, and content first. Your project agreement should specify who investigates issues and how urgent problems are escalated.
Your next step
- Export your current URLs and identify important customer journeys.
- Approve a retain, improve, combine, or retire decision for key pages.
- Review old-to-new URL mappings before launch.
- Verify contact delivery, mobile usability, and measurement on the new site.
- Assign a launch owner and schedule post-launch checks.