You migrated from old.com to new.com. Set up 301 redirects. New domain is serving. But Search Console’s old property still tracks the old domain only — it doesn’t know about the move. Or you added the new domain as a property and it’s empty even though new URLs are getting crawled. The misconception: GSC properties are not magically tied to your “site”; they’re tied to specific URL prefixes or domain authorities. Historical data stays in the old property — it doesn’t transfer.
The fix is a three-part process: add the new property, file a Change of Address in the old property, keep both properties active for months.
Common causes
Ordered by hit rate, highest first.
1. New domain not added as a property
You moved DNS but never added new.com to Search Console. New property doesn’t exist; new URLs accumulate orphaned data in Google’s index without anywhere for you to see them.
How to spot it: Search Console → property selector. If only old.com listed, add new.
2. Property type mismatch
You added a URL-prefix property for https://new.com/ but your site also serves https://www.new.com/. The property only tracks one prefix; you lose visibility into the other.
How to spot it: GSC property settings → type. If URL-prefix, consider switching to Domain property (covers all subdomains and protocols).
3. Domain ownership not verified for new domain
You added the property but skipped verification (DNS TXT record). Property shows but no data flows.
How to spot it: GSC → property → if “Not verified” banner shows, complete verification.
4. Change of Address tool not used
The Change of Address tool tells Google “site moved from X to Y.” Without it, Google’s consolidation is slower and possibly incomplete.
How to spot it: Old property → Settings → Change of address. If “No change of address” set, you skipped this step.
5. Bilingual or i18n sub-properties forgotten
You have new.com/en/ and new.com/zh/. If using URL-prefix properties, you need one per locale or use a Domain property for the whole new.com.
How to spot it: Performance per locale not showing as expected. Use Domain property to capture everything.
6. Historical data accidentally lost in migration
You deleted old property “to clean up” — historical data is gone. GSC doesn’t have an undelete.
How to spot it: Property gone from list. Recovery: not possible. Export data before deleting properties.
Shortest path to fix
Step 1: Add new domain as Domain property
GSC → Add property → “Domain” (not URL-prefix) → enter new.com (no https://, no www.).
Verify via DNS TXT record (provided by GSC). The TXT goes at apex; verification confirms ownership of all subdomains and protocols.
Step 2: Submit new sitemap
In new property → Sitemaps → enter sitemap.xml (relative path).
Confirm crawl. Within hours, URLs should start appearing in Pages report.
Step 3: Use Change of Address in OLD property
OLD property → Settings → Change of address → “Change to a new site” → select new property.
Requirements:
- Both properties verified
- Sitewide 301 from old to new
- Robots.txt not blocking either
GSC announces the move to Google’s indexing pipeline.
Step 4: Keep old property for 6+ months
Old property continues to receive data while:
- External backlinks still hit old URLs → redirected → counted in new
- Lingering old-URL impressions in SERP
Export old property’s data periodically for archive.
Step 5: Monitor both
For weeks/months after migration:
- Old property: should see traffic decreasing as Google moves to new
- New property: traffic increasing
- Watch for old URLs returning 404 instead of 301 in old property’s Pages report
Step 6: After 12 months, decide about old property
After a year, old property’s data is largely historical. You can:
- Keep it indefinitely (free, no harm) for historical reference
- Export and delete
Don’t delete before exporting if you might want historical analysis.
When this is not on you
GSC historical data does not transfer. Export the old property’s data before deactivating, and keep both properties active for monitoring during migration.
Easy to misdiagnose as
People think adding the new domain “moves” data from the old property. It doesn’t. Historical data stays where it was logged. Only the new property accumulates new data.
Prevention
- Always use Domain properties (not URL-prefix) for new domains — covers all subdomains and protocols.
- Keep old GSC properties for archive after migrations; never delete during transition.
- Use Change of Address tool the day you switch domains.
- Export GSC data quarterly as backup; data older than 16 months is partially purged.
FAQ
- Does Change of Address work for major migrations? Yes, but only for full-domain moves with sitewide 301s. Not for partial migrations or subdirectory moves.
- Can I merge two properties? No — keep both, query each separately.