A Website Redesign Checklist for Nashville Businesses

A redesign should improve the site without resetting the domain. Preserve valuable URLs, metadata, content, internal links, backlinks, analytics, structured data, and conversion paths before changing visual design or technology.

Established Nashville businesses may have decades of service, portfolio, location, blog, pricing, PDF, and campaign URLs. The current sitemap shows what the website publishes now—not everything Google, customers, and other sites remember. This checklist supports our Nashville web design and website redesign process.

Why website redesigns lose rankings and leads

• Old URLs disappear or redirect to irrelevant pages.
• High-performing copy is shortened for visual reasons.
• Titles, descriptions, canonicals, headings, and structured data are dropped.
• Navigation and internal links stop reinforcing important pages.
• Robots directives or staging controls reach production.
• JavaScript hides content or makes crawling dependent on rendering.
• Forms, phone tracking, CRM delivery, or analytics events break.
• Performance declines under larger images, fonts, animations, and scripts.
• Multiple major changes launch together without a baseline or rollback path.

Never assume the current sitemap represents the historical URL inventory of an established domain.Atomic Design

Phase 1: build the historical URL inventory

1. Crawl every accessible hostname, protocol, subdomain, and known legacy folder.
2. Export all CMS pages, posts, media, products, categories, tags, authors, and custom content types.
3. Export Search Console pages and queries across the longest available period.
4. Export analytics landing pages, conversions, and revenue.
5. Collect every URL from current and historical XML sitemaps and RSS feeds.
6. Pull backlinks and referring domains, including links to 3xx and 4xx URLs.
7. Search web archives for old navigation, services, work, locations, blog, and pricing pages.
8. Inspect server files, deployment history, redirect rules, and prior repositories when available.
9. Search Google and Bing for indexed domain URLs and legacy filename patterns.
10. Crawl internal links, canonicals, hreflang, structured-data URLs, PDFs, images, and downloadable assets.

Merge and deduplicate the sources. For every URL, record status, title, traffic, conversions, queries, backlinks, content topic, intended replacement, and action: keep, improve, consolidate, redirect, or deliberately retire.

Phase 2: plan before visual design

Set measurable baselines

Capture organic clicks, impressions, rankings, conversions, form completion, calls, revenue, Core Web Vitals, indexed pages, crawl errors, and backlink counts. Save screenshots and exports so post-launch changes can be diagnosed.

Assign one owner to each search intent

Map commercial and informational queries to specific pages. Do not create separate pages for minor keyword variations. Preserve strong owners and add support pages only when the intent is meaningfully different.

Approve the redirect map before development ends

Keep URLs unchanged when possible. When a move is necessary, use one permanent redirect to the closest equivalent page. Avoid chains, loops, blanket homepage redirects, and redirects to a merely convenient parent.

Separate redesign goals from migration risk

Changing domain, CMS, URLs, content, navigation, branding, tracking, and hosting simultaneously makes diagnosis difficult. Reduce unnecessary change and stage high-risk decisions when possible.

Phase 3: build and migration checklist

• Block staging with authentication or noindex, but maintain a written step to remove production blocks.
• Match production URL behavior in staging, including trailing slashes, case, hostnames, and query handling.
• Generate the new sitemap from canonical indexable URLs only.
• Test 301 rules against the full historical inventory, not a small sample.
• Validate accessibility using keyboard, screen-reader, contrast, label, focus, zoom, and reduced-motion checks.
• Preserve domain and DNS control; reduce TTL before planned DNS changes.
• Create complete backups and a documented rollback procedure.

Phase 4: launch-day checklist

1. Freeze content and configuration changes during the release window.
2. Capture final backups and export the old redirects, DNS, and analytics settings.
3. Deploy during a monitored low-risk period with technical and business owners available.
4. Remove staging noindex, authentication, and crawler blocks from production.
5. Test the preferred HTTPS hostname, www/non-www behavior, trailing slashes, and certificates.
6. Crawl the production site and compare indexable URLs, titles, canonicals, headings, links, and status codes.
7. Test high-value historical URLs and every redirect category.
8. Submit real forms from desktop and mobile and verify inbox/CRM delivery.
9. Confirm analytics, consent, calls, forms, purchases, and other conversion events.
10. Validate robots.txt and submit the new XML sitemap in Search Console.
11. Use URL Inspection on representative commercial, location, blog, and redirected URLs.
12. Check structured data with Google’s Rich Results Test and fix critical errors.

Phase 5: monitor after launch

First 72 hours

Watch server errors, form delivery, analytics, robots, sitemaps, redirects, canonicals, crawl logs, uptime, performance, and Search Console indexing signals. Repair systemic problems before cosmetic issues.

First four weeks

Compare organic clicks, impressions, position, indexed pages, conversions, and landing-page behavior against the baseline. Inspect lost queries and links page by page. Keep a migration change log.

First three months

Continue monitoring redirect hits, 404s, soft 404s, excluded pages, Core Web Vitals, rankings, conversions, and backlink destinations. Improve pages based on evidence rather than reversing the entire redesign after normal short-term volatility.

Keep redirects indefinitely when old URLs still receive links or traffic. Do not remove them merely because the launch is complete.

Nashville redesign questions

Will a redesign always reduce traffic?

No. A well-planned redesign can preserve and improve visibility. Risk rises when URLs, content, links, metadata, performance, and crawl controls change without inventory and validation.

Should every old URL redirect?

Every valuable or linked URL needs a deliberate decision. Redirect to a close equivalent when one exists. A true dead end with no value may return 404 or 410 rather than misleading users.

Can we change the domain during the redesign?

Yes, but it adds substantial risk. Avoid combining a domain move with unnecessary URL and content changes, and follow Google’s site-move guidance precisely.

How long should migration monitoring continue?

Monitor intensively for at least three months and retain redirects much longer. Large or historically complex domains require ongoing checks.

Primary guidance

This checklist follows Google Search Central guidance for site moves with URL changes, sitemap submission, crawler access, canonicals, and structured data. It also incorporates Atomic Design’s requirement to search historical sources before changing any established URL.

Continue planning your Nashville website

• Nashville website cost guide
• How to choose a Nashville web design company