What Should I Check Before Redesigning a Website?
Before you launch a redesign, make sure you have a solid baseline of current performance, a complete inventory of every indexable page, and a detailed plan for preserving SEO signals. In short, you need to know what you have, what will change, and how you’ll protect rankings throughout the transition. This article serves as a website redesign checklist to guide you through each phase.
Why Do Website Redesigns Often Lose Traffic?
A redesign can unintentionally drop traffic when critical SEO elements are altered or omitted. The most common culprits are:
| Issue | How It Affects SEO | Typical Oversight |
|---|---|---|
| URL changes without 301 redirects | Link equity and search‑engine signals built into the old URL are lost, leading to drops in rankings. | Forgetting to map every old URL to its new counterpart. |
| Removing or rewriting high‑performing content | Pages that already rank for valuable queries disappear from the index, causing immediate traffic loss. | Assuming the new design will automatically improve content without auditing existing pages. |
| Staging site left “noindex” or password‑protected | If the “noindex” tag is copied to the live site, search engines cannot crawl the new pages. | Using the same robots.txt file from staging on production. |
| Slower template or unoptimized assets | Page‑speed signals such as Core Web Vitals deteriorate, which can lower rankings. | Not testing the new design against the site’s speed goals. |
| Missing meta data or structured data | Title tags, meta descriptions, and schema markup that helped pages rank are gone, reducing click‑through rates and rich‑result eligibility. | Relying on the CMS to auto‑populate these fields without verification. |
Understanding these pitfalls helps you build a website redesign checklist that explicitly addresses each risk.
What Should I Do Before Starting a Redesign?
- Define Business and SEO Goals
- Clarify the primary purpose of the redesign (e.g., higher conversions, brand refresh, better performance).
- Set measurable SEO objectives such as maintaining current organic traffic, preserving top‑10 rankings, or improving Core Web Vitals.
- Capture a Baseline Report
- Export top‑performing pages, queries, and conversion paths from Google Search Console.
- Pull traffic, bounce rate, and goal‑completion data from Google Analytics for the same period.
- Save these reports; they become the benchmark for post‑launch comparison.
- Run a Full Crawl of the Existing Site
- Use a crawling tool (e.g., Screaming Frog, Sitebulb) to generate a list of every indexable URL, its status code, and existing meta data.
- Export the internal link graph and any structured‑data markup detected.
- This crawl will serve as the source for your content and URL inventory.
How Do I Build a Complete Content and URL Inventory?
- Export All Indexable URLs
- Include columns for current traffic, ranking positions, and conversion metrics.
- Flag URLs that receive the most clicks or generate the highest revenue.
- Decide the Fate of Each Page
- Keep – Pages that rank well and align with the new design.
- Merge – Consolidate thin or duplicate pages into a stronger, single resource.
- Remove – Outdated content that no longer serves user intent.
- Create a URL‑Mapping Spreadsheet
- Column A: Old URL
- Column B: New URL (or “Redirect to” if the page will be removed)
- Column C: Reason for change (keep, merge, remove)
- Column D: Notes on canonical tags or special redirects (e.g., 301 vs. 302).
Having this map ready ensures that every redirect can be implemented accurately on launch day.
How Can I Develop the Redesign on a Staging Site Without Getting Indexed?
- Block All Crawlers
- Add a
User-agent: *block withDisallow: /in a robots.txt file placed at the root of the staging environment. - Alternatively, set a
<meta name="robots" content="noindex, nofollow">tag on every staging page.
- Password‑Protect the Staging Domain
- Use HTTP authentication or a CMS‑level login requirement. Search engines cannot pass the login prompt, keeping the site hidden.
- Verify the Block Is Not Carried Over
- Before moving to production, run a URL Inspection in Google Search Console for a sample page on the staging URL. It should return “Blocked by robots.txt” or “No index tag found.”
- Ensure the staging robots.txt file is not copied to the live server during deployment.
- Test Staging Visibility
- Attempt to fetch a staging URL with a tool like
curlwithout authentication; you should receive a 401/403 response or a “noindex” header.
By keeping the staging site invisible, you avoid premature indexing that could confuse search engines with duplicate content.
Which SEO Elements Must Be Carried Over to the New Site?
| Element | Why It Matters | How to Preserve |
|---|---|---|
| Title tags & meta descriptions | Directly influence click‑through rates and relevance signals. | Export from the crawl and import into the new CMS template. |
| Headings (H1‑H6) and on‑page copy | Provide context for both users and crawlers. | Copy unchanged content verbatim; only rewrite when necessary for clarity. |
| Structured data (schema.org) | Enables rich results and improves SERP visibility. | Export JSON‑LD snippets and re‑inject them into the new page templates. |
| Canonical tags | Prevent duplicate‑content issues during migration. | Keep the same canonical URLs unless the page is removed; update if the URL changes. |
| Image alt text | Supports accessibility and image search. | Preserve alt attributes during media migration. |
| Internal links | Distribute link equity throughout the site. | Use the URL‑mapping sheet to update any hard‑coded links to their new destinations. |
For a deeper dive on the on‑page items you need to carry over, see our SEO checklist.
What Is the Pre‑Launch SEO Checklist?
- Redirect Verification
- Implement every 301 redirect from the URL‑mapping spreadsheet.
- Test each redirect with a tool like
curl -Ito confirm a 301 status and correct destination.
- Robots.txt & XML Sitemap
- Review the live robots.txt to ensure only intended sections are blocked.
- Generate a fresh XML sitemap that includes every new URL and excludes any “noindex” pages.
- Analytics & Tracking
- Confirm that the Google Analytics tracking code and any event tags are present on all templates.
- Verify that Google Search Console verification tags are still valid after the domain move (if applicable).
- Mobile Layout & Speed
- Run the new design through the mobile-friendly checks to catch viewport or tap‑target issues.
- Test page speed with Lighthouse or PageSpeed Insights; address any Core Web Vitals that fall below recommended thresholds.
- Broken Link Scan
- Use a crawler to detect any 404s or broken external links introduced during migration.
- Fix or redirect broken links before the site goes live.
- Content Review
- Double‑check that all title tags, meta descriptions, and structured data from the old site appear on the new pages.
- Hosting Considerations
- If the redesign includes a new server, review the choosing web hosting guide to ensure the environment meets performance and security needs.
What Are the Essential Launch‑Day Tasks?
| Task | How to Execute |
|---|---|
| Remove staging blocks | Delete the noindex meta tag, robots.txt disallow rules, and any password protection from the production server. |
| Submit the final XML sitemap | Go to Google Search Console → Sitemaps and submit the new sitemap URL. |
| Spot‑check critical redirects | Manually test a sample of high‑traffic pages to confirm they redirect correctly and preserve link equity. |
| Validate analytics & conversion tracking | Use the Real‑Time reports in Google Analytics to confirm pageviews and event fires on the live site. |
| Confirm canonical tags | Inspect a few pages with the URL Inspection tool to ensure the canonical points to the live URL, not the staging version. |
| Monitor server logs | Keep an eye on HTTP 404 and 500 responses during the first few hours; address any unexpected errors immediately. |
These actions help you transition smoothly while keeping search engines and users on the right path.
How Should I Monitor the Site After It Goes Live?
- Indexing & Crawl Errors
- In Google Search Console, review the Coverage report daily for new 404s, soft 404s, or “Submitted URL not found” errors.
- Fix any issues by updating redirects or restoring missing pages.
- Rankings & Click‑Through Data
- Compare current impressions, clicks, and average positions for your top queries against the baseline captured before the redesign.
- Look for any sudden drops; investigate whether they correlate with missing redirects or altered content.
- Core Web Vitals & Performance
- Track LCP, FID, and CLS metrics in the Core Web Vitals report.
- If values dip, identify the offending resources (large images, third‑party scripts) and optimize them.
- Conversion Funnels
- Use Google Analytics to monitor goal completions, form submissions, and e‑commerce transactions.
- Ensure that conversion rates are at least on par with the pre‑redesign baseline; investigate any declines.
- Backlink Health
- Check a backlink monitoring tool for any lost inbound links that still point to old URLs.
- If you find such links, consider reaching out to webmasters to update the target URL.
Regular monitoring during the first several weeks gives you enough data to confirm that the redesign has preserved SEO equity and to act quickly on any anomalies.
Next Step
If you’d rather have experts handle the redesign, migration, and SEO safeguards for you, contact us to discuss a full‑service website redesign that includes redirects, content migration, and performance optimization.