测试站点SEO及流量优于正式站，咨询重定向及站点处置方案

Hey Eleni_M, this is such a relatable scenario when taking over a new SEO project—let’s walk through the best steps to fix this without losing all that hard-earned traffic and authority.

First: Don’t Delete the Test Site (Yet) #

The biggest mistake you could make here is hitting delete immediately. That test site has already built up trust with Google, earned backlinks, and drives real traffic—throwing that away is like leaving money on the table. Instead, 301 redirecting is almost always the optimal move.

Step 1: Audit the Test Site’s Value First #

Before setting up redirects, take an hour to map out what you’re working with:

• Pull traffic data (from Google Analytics or GSC) to see which pages are actually driving visits and rankings. Are these pages duplicates of your live site, or do they have unique content your formal site is missing?
• Check Google Search Console for the test site: Look for manual penalties, crawl errors, or any red flags (like spammy backlinks). If the test site’s success came from black hat tactics (auto-generated content, paid spam links), you’ll need to adjust your approach—but if it’s organic, lean into that authority.

Step 2: Implement 301 Permanent Redirects #

301s tell Google and users that the test site’s pages have permanently moved to your formal site, passing along most of the SEO authority. Here’s how to do it right:

• One-to-one redirects: If the test site’s URL structure matches your formal site (e.g., test-site.com/blog/post-1 → formal-site.com/blog/post-1), use server-level redirects for efficiency:
  • For Apache, add this to your .htaccess file:

    RewriteEngine On
    RewriteCond %{HTTP_HOST} ^test-yoursite\.com$ [NC]
    RewriteRule ^(.*)$ https://www.yoursite.com/$1 [L,R=301]
    

  • For Nginx, update your server block:

    server {
        listen 80;
        server_name test-yoursite.com;
        return 301 $scheme://www.yoursite.com$request_uri;
    }
    

• Unique content handling: If the test site has pages your formal site doesn’t, migrate that content to your formal site first (integrate it into existing sections or create new pages), then redirect the test URLs to the new locations. Don’t let that ranking content go to waste.
• Post-redirect checks: After setting up redirects, submit the test site’s sitemap to GSC and request a crawl. Also, monitor your formal site’s traffic and rankings over the next 2-4 weeks—you should see a gradual shift as Google transfers authority.

Why Deleting Is a Bad Idea #

• 404 errors galore: Users clicking old links to the test site will land on dead pages, leading to high bounce rates and lost conversions.
• Wasted authority: All the backlinks, crawl history, and trust the test site built will disappear, forcing you to start from scratch for your formal site.
• SEO signal confusion: Google might flag the sudden disappearance of a well-established site as suspicious, which could indirectly hurt your formal site’s rankings.

Addressing Your Note About Google Crawling the Test Site #

This is actually a good sign—it means Google is still actively paying attention to the test site. Once your 301s are live, Google will start redirecting its crawlers to your formal site automatically. If you want to speed this up, you can use GSC's "URL Inspection Tool" to request a re-crawl of key test pages, which will help Google recognize the redirects faster.

Edge Case: If the Test Site Used Black Hat Tactics #

If you discover the test site’s success came from spammy practices (e.g., keyword stuffing, PBN backlinks), proceed carefully:

1. First, set up 301 redirects to your formal site—but monitor GSC closely for any penalty warnings.
2. Disavow any spammy backlinks pointing to the test site (and check if they’re also pointing to your formal site).
3. Submit a reconsideration request to Google explaining that you’ve taken over the project and cleaned up the problematic tactics.

内容的提问来源于stack exchange，提问作者Eleni_M