BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
301 Target Strategy: Aged-to-New vs Expired-to-Money, and the Four Redirect Configurations That Decide a Domain’s Equity
A 301 redirect target strategy is the decision about where to point an acquired domain’s inherited authority. The choice is not the binary that the field’s guides present. It is a grid: an aged domain or an expired domain on one axis, a new owned site or an existing money site on the other. Each of the four combinations carries a different equity range, a different relevance bar, and a different policy-risk gate.
The honest position is the one the trade press keeps circling. Done with a clean, topically matched domain and a page-to-page map, a redirect consolidates real authority and Google treats it as a normal site move. Done with an unrelated domain pointed at a money site for the link juice alone, it reads as a manipulation scheme, and the records show those plays reversing. This guide teaches the right configuration for each target, and leaves the choice to the operator.
One variable runs underneath all four cells: the quality of the domain itself. A clean profile with a real topical history is the raw material that makes a redirect hold; a junk drop is where the penalty risk starts. SEO Domains operates the curated marketplace where that raw material is screened before it is priced, so a redirect plan begins with vetted inventory instead of an unverified auction list.
What a 301 target strategy is, and why the target decides the outcome
A 301 target strategy is the plan for where an acquired domain’s link equity is sent. A 301 is a permanent server-side redirect that tells search engines a resource has moved for good, so the inherited authority of the old URL is consolidated into the new one. The target you pick, more than the redirect mechanics, decides whether that consolidation reads as a legitimate move or a manipulation pattern.
The mechanics are settled. A 301 status code signals a permanent move, and Google’s documentation states that 301 redirects are the strongest signal for telling its systems a page has a new canonical address. The depth on the signal itself lives in the pillar’s 301 redirect risks and penalties guide. What that documentation cannot decide for an operator is the target.
Why most guides stop at rebuild versus redirect
The field treats this as a two-way fork. DomCop frames it as rebuild as a standalone authority site or run a strategic 301. NameSilo and Name.com list redirect and rebuild as parallel use cases. The fork is real, and it is the right first cut. The problem is that it collapses four distinct situations into two, and the four differ in ways that change the equity and the risk.
The two axes the binary hides
The first axis is the source. An aged domain has a continuous registration and a real prior life. An expired domain dropped, sat unowned, and was re-registered, so its inherited profile carries a gap that has to be verified before it is trusted. The disambiguation between the two is covered across the Aged Domain Fundamentals hub.
The second axis is the target. A new owned site is built from scratch to match the domain, so the operator controls the relevance. An existing money site is a live property with its own topic, so the redirect has to bridge two histories that the operator did not design to align. Cross the two axes and four configurations appear, each with a different answer to the same question: how much equity transfers, and at what risk.
The four redirect configurations: source type by target type
The four configurations are aged-to-new, aged-to-money, expired-to-new, and expired-to-money. Equity transfer is highest where relevance is easiest to control and the domain history is continuous, and lowest where the operator borrows authority across a topic gap. The figures below are reasoned ranges, anchored to the consolidation principle in Google’s redirect guidance, not measured guarantees.
Read the grid top to bottom and a pattern appears. The closer the target is to a real continuation of the domain’s earned topic, the more of the inherited authority survives the move, and the lower the policy exposure. The configuration named in this page’s title, aged-to-new against expired-to-money, marks the two ends of that spread: the cleanest, fully controllable build at one end and the highest-reward, highest-exposure play at the other.
| Configuration | Reasoned equity band | Relevance bar | Primary risk gate | Best fit |
|---|---|---|---|---|
| Aged-to-new | High | High, and easy to engineer because the new site is built to match | Lowest. The site is rebuilt around the domain’s topic, so continuity is real | Building a durable, owned authority asset |
| Aged-to-money | Medium to high | Very high. Page-to-page topical match required | Medium. A topic mismatch reads as engineered consolidation | Merging a related property’s equity into a live site |
| Expired-to-new | Medium to high, once history is verified | High, and verified against the domain’s real past | Medium. A re-registration gap hides toxic inheritance until screened | Resurrecting a dropped niche property |
| Expired-to-money | Low to medium | Very high, plus a clean profile and measured pace | Highest. Borrowed authority, a topic gap, and link velocity stack together | The classic juice play, the most reward and the most exposure |
Why the bands are ranges, not numbers
No public source publishes a verified percentage of equity a 301 transfers, because the figure depends on the link profile, the relevance, and Google’s discounting in real time. Stating a precise number would be fabrication. The honest framing is directional: continuity and relevance push the transfer up, a topic gap and a re-registration gap push it down. The bands encode that direction, and the configurations rank in the order the consolidation principle predicts.
Aged-to-new: rebuilding inherited authority into an owned site
Aged-to-new points a clean aged domain at a new site built to continue its topic. It is the lowest-risk configuration because the operator controls both ends: the domain has a continuous history, and the new site is designed to match it. The trade is cost and time, since a real site has to be built and maintained instead of a redirect set and forgotten.
This is the configuration that produces an owned asset instead of a borrowed signal. WebAcquisition frames the equivalent as building a new authority site, and identifies recreating the domain’s URL structure as the move that captures the inherited backlink equity cleanly. Because the new site is built around the domain, the topical match is engineered instead of hoped for, which is what keeps the risk gate low.
When aged-to-new is the right call
The fit is a brand build that wants a head start. An aged domain with a real backlink history shortens the climb a brand-new registration faces, and the rebuilt site carries no interlinking footprint, no shared-ownership signal, and no policy exposure from a network. The diligence that separates a buildable aged domain from a liability is documented across the Aged Domain Fundamentals hub.
Expired-to-new, the close cousin
Expired-to-new runs the same play on a dropped domain. The difference is the gap. A domain that lapsed and was re-registered has an interruption in its history, and Google’s stated position is that a sufficiently different new use can stop the old links applying. That makes verification the price of admission: the domain’s real past has to be read before the rebuild commits, or the inherited authority that looked like an asset turns out to be discounted or toxic.
Expired-to-money: the classic play, its reward, and its exposure
Expired-to-money points an acquired domain straight at an existing revenue site to pass its link equity. It is the highest-reward configuration and the highest-exposure one, because three risk factors stack: authority borrowed across a topic gap, a re-registration history that can hide a penalty, and link velocity that spikes when a domain’s whole profile arrives at once.
This is the play the forums argue about. Threads on BlackHatWorld, BuilderSociety, and Reddit’s r/SEO debate redirecting expired domains to a money site precisely because it works for disciplined operators and reverses for careless ones. The honest read is that both outcomes are real, and the variable that decides which one an operator gets is discipline on the same three factors every time.
The documented upside
The clearest public account comes from Glen Allsopp’s Detailed analysis of an expired-domain SEO operation run by Suumit Shah. The reported figures are specific: roughly 28,000 US dollars per month in revenue after eight months, a total investment near 15,000 US dollars, and 3 to 5 expired domains redirected into the project, against a profile of 2,300-plus referring domains. Treat those as a single cited case study, not a template. Notably, the operator stated that the early redirects were out of niche, then moved toward relevant domains as the project matured, which is itself a tell about where the durable version of the play sits.
The documented exposure
The same source records the other side. Matt Cutts, then head of Google’s webspam team, named unrelated expired domains pointed at a site as the pattern Google watches, while acknowledging that genuine domain transfers are legitimate. The dividing line both Google voices draw is continuity. A redirect that continues a real topic is a move; a redirect that bridges a gap for the link juice is the configuration that gets discounted when the pattern is recognised. Allsopp’s own admission, that there is little world of difference between this and a private blog network, is the candid version of the same point. The detailed risk model lives in 301 redirect risks and penalties.
The relevance gate: page-to-page mapping versus the homepage red flag
Relevance is the gate that every configuration passes through, and the mechanism that enforces it is the redirect map. A page-to-page redirect that sends each old URL to its topical equivalent reads as a real move. A whole domain pointed at a homepage for the authority alone is what WebAcquisition calls a major red flag and DomCop calls the lazy approach that risks a manipulation flag.
This is the single rule every competitor agrees on, and the one this page makes operational across all four cells. The relevance bar rises as the configuration moves from new-site targets toward money-site targets, because a new site can be built to match the domain, while a money site has to absorb a history it did not design.
The four redirect targets, ranked by how they read
WebAcquisition documents the targets a redirect can point at. Ranked from the cleanest continuation to the clearest footprint, they are:
- Page-to-page map. Each old URL goes to its topical equivalent. This is the configuration Google treats as an ordinary site move, and the one the identity.digital migration checklist builds around with a URL list for permanent redirects.
- Silo or pillar page. Old URLs feed a topically aligned pillar article. A strong continuation when a one-to-one map is not available.
- Category page. A redirect into a relevant category. Weaker than a page map, defensible when the category genuinely matches the source topic.
- Homepage of an unrelated site. The whole domain forwarded to a money-site homepage for the link equity alone. This is the footprint flagged across the field, and the configuration that defines done-wrong.
The micro-site quarantine, for an unverified domain
WebAcquisition documents a middle path for a domain whose history is uncertain: rebuild it as a standalone micro-site first, let it settle, then redirect into the main property once it has proven clean. The value of the quarantine is isolation. If the domain turns out to carry a penalty, the damage stays on the micro-site and the money site is protected. It is the disciplined answer to the verification gap that defines the expired configurations.
What Google says about redirected authority, and how mismatch is read
Google’s public position is consistent across years. Redirects that continue a real site are honoured; redirects that change the use of a domain to harvest old links are discounted. The signals that mark the difference are topical continuity, the redirect map, and the registration history read through ICANN’s lookup system, now served by RDAP instead of legacy WHOIS.
Google’s early guidance, recounted in Detailed’s analysis, held that a re-registered domain would enter the index but would not get credit for pre-existing links if the use changed. Source: Detailed, expired-domain SEO.
John Mueller stated that links pointing at an old site stop applying when the new site is recognised as not the same as before. Source: Google, cited in Detailed.
Google’s March 2024 core and spam updates introduced an expired-domain-abuse policy, naming the purchase of expired domains to boost low-value content as a targeted practice. Source: Google Search Central, spam policies.
RDAP, the Registration Data Access Protocol, replaced WHOIS as the standard ICANN lookup on 28 January 2025, returning ownership and history data in a structured form that diligence reads before purchase.
The detection logic, framed as the mistakes to recognise
The way a mismatch is read is the mirror of the relevance gate. A topic gap between the redirected domain and the target, a homepage-only redirect, a registration history that does not match the claimed continuity, and a velocity spike when a domain’s whole profile lands at once are the signals that separate an engineered consolidation from a site move. Recognising those signals is the point of this section. It is the description of what done-wrong looks like, not a manual for hiding it.
How to choose and deploy a redirect target, step by step
Choosing and deploying a redirect target runs in six stages: verify the domain, classify it into one of the four configurations, build or confirm the target, map page-to-page, deploy the 301, then monitor. Each stage pairs the done-right move with the footprint that exposes a careless redirect. The sourcing stage, stage one, is the foundation the other five rest on.
The sequence below consolidates the steps the field scatters across separate guides into one ordered path. Every stage states the disciplined version and the mistake that turns the redirect into a flagged pattern.
-
Source and verify the domain: the foundation
The whole strategy stands on the raw material. The done-right move is to acquire a domain with a clean, real backlink profile and a verified history, screened before purchase. Read the registration record through RDAP, check the spam and anchor profile, and confirm the domain was not de-indexed. The metrics that separate a clean name from a junk one are documented in the Domain Authority & Metrics hub, and screened inventory sits on the SEO Domains marketplace.
The mistake: buying an unverified drop for its metric alone. A de-indexed or spam-flagged domain is a liability in every one of the four configurations, before a single redirect is set.
-
Classify into one of the four configurations
Place the domain on the grid. Aged or expired on the source axis, new owned site or existing money site on the target axis. The classification sets the equity band, the relevance bar, and the risk gate from Figure 1, which tells the operator how much continuity the next stages have to engineer.
The mistake: treating every domain as an expired-to-money juice play by default. The configuration that fits the domain and the goal is the one that holds, not the one with the loudest reputation.
-
Build or confirm the target’s topical match
For a new-site target, build the site around the domain’s earned topic so continuity is real. For a money-site target, confirm that a genuine topical bridge exists between the domain’s history and the destination’s subject. The relevance requirement is the gate the redirect has to clear.
The mistake: redirecting across a topic gap on the assumption that authority transfers regardless. An unrelated source and target is the mismatch Google’s guidance discounts.
-
Map page-to-page, not domain-to-homepage
Build a redirect map that sends each old URL to its closest topical equivalent, the way the identity.digital migration checklist builds a URL list for permanent redirects. Where a one-to-one match is missing, route to a silo or pillar page that genuinely covers the topic.
The mistake: forwarding the whole domain to one homepage. The homepage dump is the footprint the entire field flags as the lazy, manipulation-prone approach.
-
Deploy the 301 at a measured pace
Implement the permanent redirects server-side and confirm each returns a 301 status with a server-header check from more than one location. Where a profile is large, stage the redirects instead of landing the entire link graph at the target in a single day.
The mistake: a velocity spike. A domain’s whole inherited profile arriving at a money site at once is the classic unnatural-link signal that draws scrutiny.
-
Monitor in Search Console and hold the redirect
Track the target in Google Search Console for indexation and ranking movement, watch the server logs for redirect errors, and keep the 301 in place long enough for the move to settle. A permanent redirect that is removed early loses the consolidation it was set to capture.
The mistake: setting and forgetting. A redirect that is never monitored hides a broken chain or a reversal until the ranking damage is already done.
The redirect-target mistakes checklist, and the fix for each
The mistakes that turn a redirect into a flagged pattern are a short, repeatable list. Each is a footprint that signals an engineered consolidation instead of a site move, and each has a documented fix. The fixes converge on one move: start from a clean, topically matched domain and continue its real topic instead of harvesting its links. Use this as the scannable reference for recognising done-wrong.
The table consolidates the footprints scattered through the configurations, the relevance gate, and the detection section into one place. The left column is the mistake, the centre column is why it reads as manipulation, and the right column is the done-right fix.
| The mistake (footprint) | Why it reads as manipulation | The fix (done-right move) |
|---|---|---|
| Unverified or de-indexed source domain | A toxic inherited profile is already devalued in Google’s link graph | Verify history and spam profile through RDAP and a screen before purchase |
| Redirecting across a topic gap | An unrelated source and target reads as link harvesting, not continuity | Match the target to the domain’s real earned topic |
| Whole domain to a homepage | The homepage dump is the field-recognised lazy footprint | Map page-to-page, or route to a genuinely matched pillar |
| Default expired-to-money on every domain | The highest-exposure configuration applied where it does not fit | Classify the domain into the configuration that suits it |
| Velocity spike at the target | A whole profile landing at once is a classic unnatural-link signal | Stage large profiles and keep the pace human |
| No micro-site quarantine on an uncertain domain | An unverified penalty transfers straight onto the money site | Quarantine on a standalone site first, then redirect once proven clean |
| Removing the 301 early | An early-removed permanent redirect forfeits the consolidation | Hold the redirect and let the move settle before any change |
| No post-deploy monitoring | A broken chain or reversal stays hidden until rankings drop | Track indexation and server headers in Search Console |
One pattern runs down the whole fix column. The recurring move is to begin with a verified, topically relevant domain, then continue its real topic instead of harvesting its links. A domain that fails the verification row poisons every configuration that follows, because no redirect map can repair a toxic source. That is why sourcing the right raw material is the practical starting point of a redirect target strategy, not an afterthought.
301 target strategy frequently asked questions
The questions operators raise when they plan where to point an acquired domain, answered against the configuration grid, the relevance gate, and the cited public record.
Q1Is it better to redirect an expired domain to a money site or rebuild it as its own site?
It depends on the goal and the domain. Rebuilding, the new-site configuration, is the lower-risk path because the operator controls the topical match and builds an owned asset. Redirecting to a money site, the expired-to-money configuration, is the higher-reward, higher-exposure path because it borrows authority across a topic gap. The deciding variable is whether a genuine topical continuity exists between the domain and the target. Where it does not, the rebuild holds and the money-site redirect is the one that gets discounted.
Q2How much link equity does a 301 redirect pass?
No public source publishes a verified percentage, because the figure depends on the link profile, the topical relevance, and Google’s real-time discounting. Google’s documentation describes a 301 as the strongest signal that a page has moved, and continuity is what preserves the inherited authority. The honest framing is directional: a relevant, continuous move transfers a high share, and a mismatched redirect transfers little once the pattern is recognised. Any single fixed percentage stated as fact is not supportable from the record.
Q3Is redirecting an unrelated high-authority domain to a money site safe?
It is the configuration with the highest exposure. Matt Cutts named unrelated expired domains as the pattern Google watches, and John Mueller stated that links stop applying when the new use is recognised as different. A redirect that bridges an unrelated topic for the link equity alone is the done-wrong version that the record shows reversing. A redirect that continues a real, matched topic is the version Google treats as a normal site move.
Q4Is it better to map every old URL, or point the whole domain at a homepage?
Map page-to-page. Sending each old URL to its topical equivalent reads as a genuine site move, and the identity.digital migration checklist builds around exactly that URL list. Forwarding a whole domain to one homepage is the footprint WebAcquisition calls a major red flag and DomCop calls the lazy approach. Where a one-to-one match is missing, route to a silo or pillar page that genuinely covers the source topic.
Q5What is the safest configuration for using an acquired domain’s authority?
Aged-to-new. A clean aged domain with a continuous history, rebuilt into a new owned site designed to match its topic, keeps the inherited authority while giving the operator control of both ends of the relevance gate. It produces an owned asset instead of a borrowed signal, and it carries no network footprint. The expired variant runs the same play on a dropped domain, with verification of the re-registration history as the added price of admission.
The variable underneath all four cells: a clean, matched domain
Every configuration in this guide resolves to the same variable: the domain. A clean, real, topically relevant profile is the raw material that makes a redirect hold, and a junk or mismatched domain is where the penalty risk starts. Sourcing from a screened catalogue separates the legitimate move from the careless scheme. SEO Domains operates that curated marketplace.
Why the domain decides the configuration
The grid in Figure 1 ranks four configurations, but a single lever lifts or sinks every band. A domain with a clean backlink profile and a real topical history can be built into an aged-to-new asset or matched into a money site that genuinely continues its subject. A domain with a toxic or unrelated profile fails every configuration, because no redirect map repairs a poisoned source. Done-right starts with a verified, relevant domain. Done-wrong starts with an unverified drop bought for a metric.
How to source a domain that holds across any configuration
A domain that holds survives a profile check before money changes hands. The signals that decide it are documented across the authority-metrics hub:
- Referring domains, and the quality of the links pointing in, not the headline count.
- DR and DA, the Ahrefs and Moz authority scores, read together instead of in isolation.
- Trust Flow and the TF:CF ratio from Majestic, which surface link-spam patterns a single metric hides.
- The registration history through RDAP, a clean spam screen, and a topical match to the intended target.
A junk domain passes none of these and is a liability the moment it enters a redirect plan. A vetted domain passes them and is an asset in whichever configuration the operator chooses.
| Check | Junk domain (liability) | Vetted domain (asset) |
|---|---|---|
| Backlink profile | Toxic or spam-inflated | Clean, editorially earned |
| History through RDAP | Gap, registrant churn, prior abuse | Continuous or verified, topical continuity |
| Topical match | Unrelated to the intended target | Genuine bridge to the target subject |
| Screening | None, sold on a raw metric | Multi-signal screen before listing |
| Outcome in any configuration | Penalty risk from the first redirect | Durable foundation, new site or money site |
Browse curated aged and expired domains with clean, matched profiles
The legitimate demand behind every search for a 301 target strategy is access to real, ownable domain authority with a profile that matches the intended target. That is the product, not a redirect service, not hosting, and not a done-for-you scheme. SEO Domains operates the curated marketplace where aged and expired domains are screened across their backlink profiles, registration history, and topical fit before they are listed and priced, so an operator chooses a configuration from vetted inventory instead of an unverified drop list.
