Should You Move Your Site to an Aged Domain?

This is the option almost nobody considers. Instead of pointing an aged domain at your site, you move your site onto the aged domain and make it your primary name.

It is right occasionally and wrong most of the time. Right when the aged domain is a materially better name than the one you have and you are early enough that the switch is cheap. Wrong when the plan is to inherit the old domain's links, because a migration does not stack two link profiles into one: it moves yours, and whatever the old domain had was earned for a different site that no longer exists. The risk in this project is the migration, not the domain, and migrations go wrong in ways that cost more than any name is worth.

When is it worth doing?

Three cases where the answer is often yes.

The name is genuinely better and you are early. A two-word .com against the hyphenated or misspelled thing you launched with, before you have printed anything, and while your traffic is small enough that losing some of it temporarily does not matter. The name is a twenty-year asset; the migration cost is one-off.

You are reclaiming your own history. You rebranded, let the old domain lapse, somebody dropped it, and now you can have it back. Here the old links really do point at your company, and Google's site move guidance is written for exactly this.

The domain is the category name in your market. Rare, expensive, and when it happens the naming benefit outruns any SEO argument.

Three cases where the answer is no.

You want the old domain's backlinks. Moving your site does not merge two profiles. The old domain's inbound links point at URLs from the old site, and unless you can serve matching content at those paths they resolve to nothing useful. If the old links are the goal, redirecting the aged domain at your site does the same job for an hour of work and no risk.

Your current domain has real equity. If you rank, have brand searches and years of citations, you are proposing to spend that to buy a nicer name. Sometimes correct. Rarely.

You cannot dedicate weeks to it. A half-finished migration is the worst state available.

What actually transfers?

Google gives you one tool for this and documents its limits clearly. The Change of Address tool in Search Console "tells Google to emphasize crawling and indexing your new site over crawling your old site. It also forwards various signals from the old site to the new site."

Three constraints on it:

• You must be an owner of both properties in Search Console, under the same account, and both must be domain-level properties rather than path-level ones.
• Google maintains the forwarding "for 180 days after you start migration in Search Console".
• After that window, in Google's words, "Google does not recognize any relationship between the old and new sites".

The tool is a signal, not the mechanism. The mechanism is your redirects, which is why Google advises keeping them "for as long as possible, generally at least 1 year". A hundred and eighty days of Search Console assistance sitting on top of permanent server-side 301s is the correct arrangement.

What does not transfer is the aged domain's own history in any automatic sense. You are not inheriting its rankings. What you get is a domain whose name other people have referenced, and the value of that shows up over time and only if the subject fits.

How to do the move

Nine steps. Do them in order and do not compress steps 1 to 3.

1. Crawl your current site and export every indexable URL. This list is the migration. Everything else is bookkeeping.
2. Build a one-to-one redirect map from every old URL to its equivalent on the new domain. Google's guidance is explicit that if there is not a one-to-one match, "try to make sure that every page on your old site is at least redirected to a new page with similar content". Do not map anything to the homepage by default.
3. Check what the aged domain already has pointing at it. Run the backlink checker on it and note which old URLs hold the referring domains. Where you can serve something genuinely equivalent at those paths, do. Where you cannot, let them 404 rather than inventing a destination.
4. Stand the new site up on the aged domain with the full content, correct canonicals pointing at the new URLs, HTTPS, and a fresh robots.txt that allows the search crawlers. A domain that has been parked has been serving a parking page to every crawler that visited it.
5. Verify both properties in Search Console and read the manual actions report on the aged domain before you move anything onto it.
6. Switch on the 301s from the old domain, server-side, permanent, no chains.
7. Submit the Change of Address in Search Console, then submit the new sitemap.
8. Update everything that is not a redirect: analytics, ad accounts, email, social profiles, app store listings, invoices, your Google Business Profile, and every partner who links to you. The partner links are the ones people forget and the ones that matter, because a 301 chain that later breaks loses them.
9. Hold the old domain indefinitely and keep the redirects running. Letting it lapse hands the redirect target to whoever registers it next, which is the failure described in the brand protection guide.

Expect a dip in traffic for weeks. Expect recovery to be gradual rather than clean. John Mueller has said of domains with a past that "Sometimes it just takes a lot of time for the old state of a domain to be shaken off", speaking on Reddit in September 2025, and he added there is "nothing manual that you can / need to do here". Patience is the whole intervention.

What it costs

The migration itself, in engineering time. A traffic dip of unpredictable size and duration. Every printed or embedded reference to the old name. Email addresses your customers have saved. Two domain renewals forever rather than one.

Against that, one better name. Decide whether that trade is worth it before you look at any metric on the aged domain, because the metrics are the part most likely to talk you into a move you should not make.

Using the Revised directory for this

Shortlist for the name first and the numbers second, which is the reverse of how the directory is usually used.

Listings publish the mask at the name's true length, with its first letter, final word and hyphens visible, so you can judge shape and readability before spending a reveal. Use the estimated-value band as a proxy for how a name reads commercially, alongside the Basics filters for your TLD.

Then check the two things that decide whether the move is defensible. Under History, require real age and a long archived record: a domain that was a live site for a decade is a different asset from one registered in 2009 and parked since. Under Quality, use the referring-domain band, a minimum Agent Citability score and the spam signal. Agent Citability is our published measurement of how deeply a domain is referenced by the sources answer engines cite; it ships as versioned releases and a score can fall between them, so treat it as evidence rather than a valuation.

Read the Linked by column before anything else. For a migration, subject fit is not a nice-to-have. You are going to be this domain, and if its references were about an unrelated subject they will not help you and the mismatch is the thing Google's expired domain abuse policy describes.

Aged domain versus new domain covers the choice for a site that has not launched yet, which is a much easier version of this decision. What to do with an expired domain compares all six options.

FAQ

Will moving to an aged domain improve my rankings? Not by itself, and there is no published evidence that it does. You move your own site's signals to a new address and take on migration risk. Any benefit from the domain's history depends on the subject matching and shows up slowly.

How long does a site migration take to recover? Weeks to months, with no guarantee about the level it recovers to. Google forwards signals through the Change of Address tool for 180 days, and advises keeping redirects for at least a year.

Can I merge the aged domain's backlinks with my own? No. You can serve equivalent content at the old URLs that hold those links so they resolve to something useful, which is the closest thing available. There is no merge.

Do I need the Change of Address tool? It helps and it is free, but it requires owning both properties in Search Console at domain level. The redirects do the actual work.

Should I keep the old domain? Yes, indefinitely. Keep the redirects live and renew it. Letting it drop hands your redirect source to a stranger.

Is it safer to just redirect the aged domain to my current site? Almost always, yes. It captures whatever the old links are worth for an hour of work and no migration risk. Move only when the name itself is the reason.