Redirecting an Aged Domain So Its Link Equity Transfers

You bought a domain with a real history. Twelve years of archived pages, ninety referring domains, a handful of links from publications you would never get a reply from today. The domain sits in your account and does nothing. The obvious move is to redirect it at your existing site and let the authority flow downhill.

That works, but only under conditions most people skip. A redirect is a request, not a transfer. Google decides whether to honor it, and the decision turns almost entirely on whether the destination is a credible replacement for what the old URL used to be. Get that wrong and you have not lost 20% of the value. You have lost all of it, and the redirect sits there returning a 301 to nobody in particular.

What Actually Transfers Through a Redirect

Links point at names. When a university library linked to oldsite.com/research/water-quality in 2014, that link is still an instruction to visit that exact URL. It does not know or care that the domain changed hands.

A 301 tells Google the URL has permanently moved. Google's documentation puts it plainly: with a permanent redirect, "Googlebot follows the redirect, and the indexing pipeline uses the redirect as a signal that the redirect target should be canonical."¹ The canonicalization docs add why that matters, describing consolidation as the way search engines merge "the signals they have for the individual URLs (such as links to them) into a single, preferred URL."²

So the mechanism is real. It is also not lossy in the way the folklore suggests. The "301s pass 85% of link juice" figure floating around SEO blogs traces back to guidance Google retired years ago. Gary Illyes, then on Google's search team, stated in July 2016 that "30x redirects don't lose PageRank anymore," and Google has not walked that back since.³

Which means the risk is not decay. It is rejection. Either Google accepts the redirect and folds the old URL's signals into your page, or it decides the redirect is not a genuine move and drops the whole thing. There is very little middle ground.

The Domain Authority Myth

One thing that definitely does not transfer is a score. Domain Authority, Domain Rating, and Authority Score are third-party estimates calculated by Moz, Ahrefs, and Semrush respectively. Google does not read them. When you redirect a DA 45 domain into your site, your site does not become DA 45. What happens is that those tools eventually notice the old domain's backlinks now resolve to your pages, and they recompute your score from that. The links moved. The number followed. Our guide to domain authority covers why that distinction matters when you are pricing a domain.

Judge an acquisition on the referring domains themselves, not the composite score sitting on top of them.

Google's Rules, Stated Exactly

In March 2024 Google added expired domain abuse to its spam policies. The definition is short:

Expired domain abuse is where an expired domain name is purchased and repurposed primarily to manipulate Search rankings by hosting content that provides little to no value to users.⁴

The policy page lists three examples: affiliate content on a site previously used by a government agency, commercial medical products sold on a site previously used by a non-profit medical charity, and casino content on a former elementary school site.⁴ The pattern is a mismatch between what the domain was and what it became, combined with content nobody would seek out on its own.

The announcement post is more useful than the policy page, because it says what is allowed:

Expired domain abuse isn't something people accidentally do. It's a practice employed by people who hope to rank well in Search with low-value content by using the past reputation of a domain name. These domains are generally not intended for visitors to find them in any other way but through search engines. It's fine to use an old domain name for a new, original site that's designed to serve people first.⁵

Read the last line twice. Google is not prohibiting the use of aged domains. It is prohibiting the use of aged domains as a delivery vehicle for content that exists only to catch search traffic.

Two details are worth knowing. First, the link spam section of the same policy page covers buying and selling links for ranking purposes and does not mention expired domains at all.⁶ Acquiring a domain is not treated as buying links, because the publishers who linked to it were never paid. Google handles the domain case under its own policy.

Second, expired domain abuse does not appear as an issue type in Search Console's manual actions report.⁷ Enforcement is largely algorithmic. You will usually not get a notice. You will just get nothing.

The Test You Can Actually Apply

Strip the policy down and it asks one question: would this domain still be pointed here if it had no history?

If you acquired a domain because its old audience overlaps yours, its archived pages covered subjects you cover, and its links come from sites you would be pleased to be cited by, you pass. If the only reason the domain is in your account is the metric attached to it, and the destination has nothing to do with what the domain used to be, you are describing the practice Google named.

Redirects Face a Second Gate

Here is the part most guides miss. The spam policy is written about hosting content on a repurposed domain. A redirect does not host anything, so the policy is not the mechanism that stops it. Something else is.

When Googlebot follows a redirect, the indexing pipeline compares what the old URL was about with what the destination delivers. If the destination is not a plausible replacement, Google treats the redirect as a soft 404 and the signals go nowhere. Glenn Gabe documented this in a 2016 case study across several client migrations, where Search Console began issuing soft 404 warnings for redirected URLs within weeks of launch, and rankings for those URLs fell rather than consolidating. He cites John Mueller's explanation directly: redirects to the homepage or to non-relevant pages can be treated as soft 404s, and Google eventually drops the source URLs from the index entirely.⁸

So there are two independent gates. The policy gate asks whether your intent is legitimate. The relevance gate asks whether the redirect is technically believable. Blanket-redirecting an unrelated domain at your homepage fails both, which is why it is the single most common way this goes wrong.

Step 1: Find Out Which Pages Earned the Links

Before you write a single rule, work out where the authority actually sits. On a domain with ninety referring domains, it is common for six or seven old URLs to hold most of the value and for the homepage to hold surprisingly little.

You want three things:

• The URLs that were linked, not just the count of links. A referring domain total tells you nothing about where to point anything.
• The archived content at those URLs, so you know what each linking page was endorsing.
• The anchor text, which tells you what the linking sites thought the page was about.

Listings on Revised show referring domains and archived history before purchase, so much of this is visible while you are still deciding. For a domain you already hold, the free domain report pulls the same profile. Either way, do this before you commit to a destination, not after.

Check the archive for character too. A domain that ran as a regional trade publication for a decade and then went dark is a different asset from one that changed subject three times and spent two years parked. John Mueller noted in September 2025 that a domain carries an internal state that takes time to shed, adding that "sometimes it just takes a lot of time for the old state of a domain to be shaken off (sometimes that's also the case when it was parked for a while)."⁹ Parking history is not fatal, but it is a reason to expect a slower response.

Step 2: Build a Page-Level Map

This is where the work is, and it is the difference between a redirect that compounds and one that evaporates.

Pull the domain's historical URL list from the Internet Archive's CDX API, which the Internet Archive documents publicly:¹⁰

https://web.archive.org/cdx/search/cdx?url=example.com&matchType=domain&fl=original,timestamp,statuscode&collapse=urlkey&limit=5000

That returns every distinct URL the archive captured. Cross-reference it against the linked URLs from step 1 and you have a shortlist, usually far shorter than the raw archive. Now assign each one a destination:

The rule is one-to-one wherever a genuine equivalent exists. Where none exists, redirect to the nearest parent rather than inventing a match, and accept that those URLs will carry less. Gabe's recommendation still holds: when there is no plausible replacement at all, a 404 is more honest than a false redirect, and it costs you nothing you were going to keep anyway.⁸

If your site has no page that could reasonably stand in for the domain's best URLs, that is the map telling you something. Either write the content first, or you have bought a domain for a destination that cannot receive it.

Step 3: Implement as Server-Side 301s

Google supports 301 and 308 as permanent redirects, and treats 302, 303, and 307 as temporary, meaning the indexing pipeline will not use them as a canonical signal.¹ For this purpose 301 is the conventional choice and 308 is equivalent in effect. Do not use 302 and then plan to switch later.

Server-side redirects are what Google calls "the best way to ensure that Google Search and people are directed to the correct page," ahead of meta refresh, with JavaScript redirects last because rendering can fail.¹ A meta refresh or JS hop on a domain whose entire value is link consolidation is not worth the risk.

Watch the chain length. Googlebot follows up to 10 hops, but Google's own advice is to redirect to the final destination directly and, where that is impossible, to keep chains to "no more than 3 and fewer than 5."¹¹ Chains appear more easily than people expect on acquired domains, because the old URL often redirects to your destination, which then redirects from HTTP to HTTPS, then from non-www to www. Three hops before anyone has done anything wrong. Point the rules at the final canonical URL, protocol and subdomain included.

For the mechanics of DNS records, hosts, and verifying the status code, see pointing your new domain somewhere useful.

One tool you will not need: Search Console's Change of Address. That is for moving an entire site from one domain to another, and it requires you to own both properties. Google explicitly excludes partial moves, telling you to use redirects and sitemaps instead.¹² Folding an acquired domain into an existing site is not a change of address.

Step 4: Watch the Right Four Signals

Give it a few weeks, then check these in Search Console for the destination property:

1. Page indexing, "Page with redirect." Your old URLs should appear here. Google describes the status as a non-canonical URL that redirects elsewhere and will not itself be indexed.¹³ That is the correct outcome. It means the redirect was seen and accepted.
2. Soft 404. Old URLs showing up here instead is the failure mode from earlier. The redirect is being ignored. Revisit the mapping and tighten the relevance.
3. The Links report. Referring domains from the acquired domain should start appearing against your destination pages over the following weeks. This is the clearest confirmation that consolidation happened.
4. Manual actions. Rarely relevant, since enforcement here is algorithmic, but it costs nothing to look. A manual action means a human reviewer found a policy violation, and clearing one means fixing it and filing a reconsideration request, reviewed over days to weeks.⁷

Run rank tracking on the destination pages alongside, though it moves slowest of the four.

Timeline, and How Long to Keep the Redirects

Google processes moves on a per-URL basis, meaning Googlebot has to crawl every old URL at least once before its signals move. Google's site move guidance says small and medium sites typically take several weeks for most pages to transition, with larger sites taking considerably longer.¹¹ For a domain with a few dozen linked URLs, expect the bulk of the effect inside four to eight weeks, with ranking changes trailing behind indexation.

On duration, Google's instruction is "keep the redirects for as long as possible, generally at least 1 year."¹¹ Treat one year as the floor, not the plan. The domain is delivered to your account and renewing it is cheap relative to what you paid. Dropping it later hands the links back to whoever registers it next, and every URL you consolidated reverts to a dead end.

The Four Mistakes That Cost the Most

• Blanket-redirecting every old URL to your homepage. Fails the relevance gate, produces soft 404s, and consolidates nothing. This is the default configuration on most registrar forwarding settings, which is why it is so common.
• Choosing a destination with no topical connection. A domain that was a gardening publication does not belong pointed at a SaaS product, however good the links look. Both gates reject it.
• Leaving chains in place. Every extra hop is latency for users and an opportunity for something to break. Rewrite the rules to hit the final URL.
• Letting the domain lapse after the boost arrives. The consolidation lasts exactly as long as the redirect does.

What to Expect

A well-mapped redirect from a domain with genuine authority links usually shows up as a modest, durable lift on the specific pages that received the mapped URLs, not a site-wide jump. Pages that inherited three links from established publishers behave like pages that earned three links from established publishers, because that is now what they are. If the domain's links were thin or came from sites that have since decayed, the redirect will faithfully transfer very little, which is an argument for auditing the profile before purchase rather than after.

The version of this that works is unglamorous: a domain whose subject overlaps yours, a map of maybe fifteen URLs to fifteen real destinations, server-side 301s to canonical targets, and a renewal reminder set for the next decade. The version that fails is a single wildcard rule pointed at a homepage. The gap between them is an afternoon of work.

Start with the archive. It tells you what the domain was, and that determines everything else.

Related

If the domain earned deep links you would rather resolve than forward, the alternative to mapping them is putting a site back on the domain: same paths, new content, no redirect in the middle. See rebuilding the site on a domain you bought.

Sources