A client discovered their old domain still pointed to their outdated website two years after launching a new site. Here's why this happens, why it matters, and how to fix it with 301 redirects.
What you'll learn
- How businesses end up with duplicate websites on old domains
- What 301 redirects are and how they work
- Why duplicate websites hurt SEO and brand consistency
- How to find old domains you might have forgotten about
- Steps to properly redirect old domains to your current site
- What to tell web developers when switching providers
The quick version
When companies change web developers or rebrand, old domains often get forgotten. These domains continue showing outdated websites, confusing customers and splitting SEO value. The fix is straightforward: 301 redirects. But first you need to know the problem exists.
Check right now
Do you own multiple domains? Visit each one in a private browsing window. You might be surprised what you find.
What happened (and why it's more common than you think)
A former client contacted us this week with a problem. They had two domains for their business—the original domain they'd used for years, and a newer domain with a slightly different format. Both pointed to the same website initially.
Two years ago, they hired a new web developer to build a completely new site. The developer built it on the newer domain. The new site launched. Everyone celebrated. Business continued.
But nobody touched the old domain. It still pointed to the old hosting account. The old website stayed live. For two years.
They discovered this only when a customer mentioned seeing outdated information on their website. The customer had found the old domain through a Google search and didn't realize it wasn't the current site.
How this happens
This situation is surprisingly common. Here's the typical sequence:
Company starts with one domain. Years pass. They acquire or create additional domains (different formats, misspellings, old brand names). All domains point to the same site initially, so everything works.
Company decides to redesign their website. They hire a new developer or agency. The new team asks "what domain should we use?" The company gives them one domain—usually whichever seems primary.
The new site launches on that domain. The new developer never asks about other domains because they don't know they exist. The old team never mentions them because they assumed everything would transfer automatically.
Old domains continue pointing to old hosting. Old websites stay live. Nobody notices until someone accidentally finds them.
The real problem: This isn't anyone's fault exactly. The old developer didn't manage domains they didn't know about. The new developer can't redirect domains they weren't told exist. The company assumed website migration meant ALL domains. Nobody had a complete picture.
Why having duplicate websites actually matters
Google sees duplicate content as a problem
When the same content (or nearly the same content) exists on multiple domains, Google must choose which version to rank. This splits your SEO authority between domains instead of concentrating it on one site.
Google may also view duplicate content as manipulative if it appears you're trying to dominate search results with multiple copies of the same site. Even unintentional duplication can trigger ranking penalties.
You're essentially competing against yourself. Some keywords might rank your new site. Others might rank your old site. Neither performs as well as they would if all authority concentrated on one domain.
Customers see outdated information
Old websites show old services, old pricing, old team members, old contact information. Customers might call disconnected phone numbers. Email outdated addresses. Make decisions based on information that's no longer accurate.
Some customers find the old site and assume you're out of business because it looks neglected. Others find both sites and don't know which to trust. Neither scenario helps business.
Brand inconsistency confuses people
Your new website reflects your current brand positioning, messaging, and design. Your old website doesn't. Having both active creates inconsistent brand presentation.
Customers might see the old site first and form impressions based on outdated branding. Potential hires might visit the old site and think your company looks different than it actually is. Partners might question which site represents current capabilities.
You're paying for hosting you don't need
Old websites usually mean old hosting accounts you're still paying for. These accounts serve no purpose beyond keeping outdated content live. That's money wasted on a problem rather than invested in solutions.
How to fix it: 301 redirects explained
What a 301 redirect actually does
A 301 redirect is a permanent redirect from one URL to another. When someone visits the old domain, the server automatically sends them to your current domain. The visitor never sees the old site. They land on your current site instead.
For search engines, a 301 redirect transfers most of the old domain's SEO value to the new domain. It tells Google "this content permanently moved here." Rankings, authority, and inbound links transfer to the new location.
How to set up redirects properly
Contact whoever manages your old domain and hosting. This might be your IT department, your old web developer, or your domain registrar. You need access to the hosting control panel or DNS settings.
Set up 301 redirects from the old domain to your current domain. The simplest approach redirects everything: olddomain.com → currentdomain.com. Anyone visiting any page on the old domain lands on your current homepage.
The better approach redirects matching pages: olddomain.com/services → currentdomain.com/services. This preserves the user's intent and passes more SEO value. But it requires knowing which old pages correspond to which new pages.
Test the redirects. Visit your old domain in a private browsing window. You should land on your current site immediately. Check a few different old URLs to ensure the redirects work correctly.
What to do with the old domain after redirects are in place
Keep paying for the old domain for at least 6-12 months while redirects do their work. This ensures anyone with bookmarks, links, or old marketing materials still reaches your current site.
Monitor traffic to make sure redirects function correctly. Check Google Search Console for both domains to see if the old domain's rankings transfer to the new domain.
After 6-12 months of successful redirects, you can decide whether to keep the old domain. If it still receives traffic or has inbound links, keep it. If it's truly dormant, you can let it expire. But maintain redirects as long as you own both domains.
Should you keep old domains forever? If the old domain gets meaningful traffic, has quality inbound links, or might be confused with your brand, keep it permanently with redirects in place. If you used it for email, keep it so you don't miss messages. Otherwise, after 12+ months of redirects, you can let it expire to save annual registration fees.
How to prevent this when switching web developers
This problem is preventable with clear communication between outgoing developers, incoming developers, and the business.
What to tell your new web developer
Provide a complete list of all domains you own or have used. Don't assume they'll figure it out. They won't. List every domain variation, misspelling, old brand name, and alternate format.
Clarify which domain should be primary. If you want everything redirected to one main domain, say so explicitly. Don't assume it's obvious which domain matters most.
Ask them to set up redirects from all other domains to the primary domain. Make this a deliverable in the project scope, not an afterthought discovered months later.
What to ask about domain management
Request a checklist of all domains, hosting accounts, and credentials they're managing. You should have a clear record of what they're handling and what they're not.
Confirm what happens to old hosting accounts. Are they being cancelled? Left active? Redirected? Don't leave this ambiguous.
Get login credentials for all accounts involved. You should be able to access your domain registrar, hosting, and any services even if you prefer the developer handle day-to-day management.
Check for yourself
After the new site launches, personally visit every domain you own in a private browsing window. See what loads. If it's not your current site redirecting properly, something got missed.
Search for your business name in Google. Look at which domains appear in results. If old domains rank for your brand name, set up redirects immediately.
Not sure about your domain setup?
We can audit your domains, set up proper redirects, and make sure old websites aren't confusing customers or hurting SEO.
Frequently asked questions
What is a 301 redirect?
A 301 redirect is a permanent redirect from one URL to another. When someone visits the old URL, the server automatically sends them to the new URL. For search engines, a 301 redirect transfers most of the old page's SEO value to the new page. It tells both users and search engines that the content has permanently moved.
Why does having duplicate websites hurt SEO?
Google sees duplicate content as a quality issue. When the same content exists on multiple domains, Google must choose which version to rank. This splits your SEO authority between domains instead of concentrating it. Google may also penalize sites for duplicate content if it appears manipulative. You're competing against yourself instead of competitors.
How do I know if I have old domains still pointing to old websites?
Check your domain registrar account to see all domains you own. Visit each domain in a private browsing window to see what loads. Check Google Search Console for all properties associated with your domains. Search for your business name in Google to see which domains appear in results. Ask your IT team or previous web developers what domains were used.
What should I do if I find an old domain still showing an old website?
Set up 301 redirects from the old domain to your current domain. Redirect the homepage to your new homepage, and ideally redirect matching pages to their new equivalents. Update any places where the old domain appears (business listings, social media, email signatures). Monitor for a few weeks to ensure redirects work correctly. Consider letting the old domain expire if you no longer need it, but only after redirects have been in place for several months.
Should I keep paying for old domains?
If the old domain still gets traffic or has inbound links, keep it and redirect it to your current domain. If you've used it for email or business communications, keep it to avoid missing messages. If it's a common misspelling of your current domain, keeping it prevents competitors from buying it. Otherwise, after proper redirects are in place for 6-12 months, you can let it expire.
What should I tell a new web developer when switching?
Give them a complete list of all domains you own or have used. Clarify which domain should be primary. Ask them to set up redirects from all other domains to the primary domain. Request a checklist of all domains, hosting accounts, and credentials they're managing. Ensure they understand what should happen to old domains and old website content.
