BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
The Relevance Requirement for a 301 Redirect (Koray’s Rule): How Topical Match Decides Whether Your Domain Passes Equity
The relevance requirement for a 301 redirect is the topical-match threshold that decides whether ranking equity transfers from the old URL to the new one. Send a redirect to a closely related page and the signals flow. Send it to an unrelated page and Google treats the move as a soft 404, and the equity evaporates.
This is the rule the field compresses into a single sentence. Koray Tugberk Gubur made it explicit inside his semantic SEO framework: a 301 passes value only when source and target share a central entity. The honest read is that a 301 is a tactic, and like any tactic it works when done right and wastes the asset when done wrong. There is no moral question here, only a topical one.
It matters at its sharpest when an aged or expired domain is the source, because the redirect is only as good as the topical match between the domain you acquired and the page you point it at. SEO Domains operates the curated marketplace where that history is screened, so the domain feeding a relevant 301 starts from real, on-topic authority instead of a random drop.
What is the relevance requirement for a 301 redirect?
The relevance requirement for a 301 redirect is the topical-alignment threshold a source and target must clear for ranking equity to transfer. Koray Tugberk Gubur defined it through his semantic SEO framework: a permanent redirect passes signals when both pages share a central entity, and it is ignored when they do not.
A 301 redirect tells Google that one URL has permanently moved to another. Google’s own documentation states that the indexing pipeline uses the redirect as a signal that the target is the canonical page. The protocol itself is settled. What the protocol does not guarantee is that the equity behind the old URL arrives at the new one.
The protocol is not the same as the transfer
The redirect is the instruction. The equity transfer is the outcome, and the outcome depends on whether Google accepts the target as a genuine replacement for the source. When the target covers the same topic, Google reads it as a true move and consolidates the ranking signals. When the target is off-topic, Google reads the old page as effectively gone and routes nothing.
This is the distinction the relevance requirement names. The 301 is a request, not a command. Topical match is what gets the request granted.
Where Koray’s rule fits
Koray Tugberk Gubur built the Topical Authority framework, dated to 18 May 2022, around the idea that every page contributes to a topical map anchored by one central entity. Inside that framework a 301 is a canonical reassignment, so the target absorbs the source only when the source belongs to the target’s topical map. The rule turns the loose industry advice to redirect to a related page into a named precondition: shared central entity first, redirect second.
Why relevance gates whether a 301 passes equity
Relevance gates equity transfer because Google reclassifies a redirect to an unrelated page as a soft 404. John Mueller stated Google treats such redirects as soft 404s, Glenn Gabe documented it in a case study, and Ahrefs confirms an irrelevant 301 carries no advantage. The link signals never reach the target.
The soft-404 mechanism
A soft 404 is what Google calls a page that returns a success status while behaving like a missing page. When a redirect points to content that does not continue the source’s topic, Google decides the original page is gone instead of moved. It drops the source from the index and passes no equity to the target. The redirect resolves in the browser, yet it is invisible to the ranking system.
John Mueller put the principle in plain language. On redirecting dead pages to a homepage, he stated that Google will, in his words, “mostly treat them as 404s anyway (they’re soft-404s), so there’s no upside.” The same logic applies to any redirect whose target does not match the source’s subject.
The case study and the trade consensus
Glenn Gabe of GSQI published a case study titled “Proof That 301 Redirects To Less-Relevant Pages Are Seen As Soft 404s To Google.” His documentation showed redirects to less-relevant pages receiving soft 404 classification, which stripped the source URLs from the index without transferring signals. Ahrefs reaches the same conclusion in its 301 guide, stating that Google treats irrelevant 301 redirects as soft 404s, so there is no real advantage to redirecting unless the target is a similar and relevant page.
The PageRank side of the story
The relevance requirement coexists with a separate, well-documented shift. Matt Cutts of Google described the older position, that the equity dissipating through a 301 was identical to the equity dissipating through an ordinary link, which is where the long-quoted decay figure came from. Google later updated that stance, and Ahrefs reports that 30x redirects no longer lose PageRank. The two facts fit together cleanly: a relevant redirect now passes full equity, and an irrelevant one passes nothing because it never qualifies as a redirect in the ranking system’s eyes.
The honest read: a relevant 301 vs an irrelevant one
Done right, a 301 to a topically matched target consolidates full ranking equity and is a legitimate, durable move. Done wrong, a 301 to an unrelated target is treated as a soft 404, wastes the source’s authority, and on a borrowed domain raises exposure to the site reputation abuse policy. The variable is topical match, not the protocol.
A 301 redirect is neither good nor bad on its own. It is a lever, and the relevance requirement decides which way the lever moves. The two outcomes below are the same action applied to different targets.
The policy edge of getting it wrong
There is a second cost to an irrelevant redirect when the source is an aged or expired domain bought for its authority. Google announced its site reputation abuse policy in March 2024 and began enforcement with manual actions on 5 May 2024, expanding it to first-party involvement in November 2024. The policy targets content that exploits a domain’s earned reputation without topical alignment. A cross-niche 301, from a health domain into a finance page for instance, walks straight into that evaluation pathway. The penalty exposure detailed in 301 redirect risks and penalties grows the further the target drifts from the source’s topic.
Why this is an enabling rule, not a warning
The relevance requirement is not a reason to avoid 301s. It is the instruction for making them work. A redirect built on a topical match is one of the cleanest moves in SEO: it preserves authority, it consolidates signals, and it carries no policy risk because nothing about it is manipulative. The whole game is sourcing a target, or a source domain, that genuinely belongs in the same topical map. The mechanics underneath this sit in How 301 redirects work technically, and the equity question it resolves is covered in Does a 301 redirect pass SEO value.
Koray’s rule unpacked: entity, network, predicate
Koray’s rule breaks topical match into three tests. Central entity continuity asks whether both pages describe the same primary thing. Semantic content network membership asks whether they sit in the same cluster. Predicate compatibility asks whether the claims on the source extend the target without contradicting it. All three hold for a clean transfer.
Koray Tugberk Gubur frames every page as part of a topical map, and the relevance requirement is the rule for moving a page within or into that map. Three conditions sit at the core, and each one operates as a gate.
Central entity continuity
The central entity is the one thing a page is about, the subject that appears across its sections. Continuity demands that the source page’s central entity matches the target’s, either as the same entity or as a direct sub-entity inside the same hierarchy. A page about expired domain backlinks redirecting to a page about expired domains passes, because the source is a sub-entity of the target. A page about expired domains redirecting to a page about car insurance fails, because the entities do not connect.
Semantic content network membership
A semantic content network is the cluster of pages that serve one audience around one topic. Membership extends the test beyond the two pages to the neighbourhood around the target. The source belongs if it would sit naturally inside the target site’s existing topical coverage. This is why a redirect into a site that already publishes deeply on the source’s topic transfers more reliably than a redirect into a site that touches the topic once.
Predicate compatibility
Predicates are the claims a page makes about its entity, the verbs and relationships that connect subject to object. Compatibility means the source’s claims are a subset or a clean extension of the target’s, with no contradiction. A guide that says an aged domain carries inherited backlinks fits a target that explains how that authority is valued. A page making claims the target flatly contradicts breaks compatibility even when the entities match on the surface.
Passes the test (transfer holds)
Same central entity or a direct sub-entity. Source belongs in the target’s existing topical cluster. Source claims extend the target without contradiction. Google reads a genuine move and consolidates equity.
Fails the test (soft 404)
Unrelated central entity, no shared cluster, or contradicting claims. Google reads the source as gone, classifies a soft 404, and passes no equity. The redirect resolves but is ranked as nothing.
The four relevance tiers and the action for each
Relevance is a ladder, not a switch. Tier 1 is a perfect central-entity match and transfers full equity. Tier 2 is a sub-entity match and transfers a high share. Tier 3 is an adjacent topic and transfers a partial share, calling for selective redirection. Tier 4 is unrelated and calls for a 410 instead of a 301.
Treating relevance as binary loses information. A source can be a perfect match, a near match, an adjacent topic, or unrelated, and each level points to a different action. The four tiers below turn Koray’s three gates into a decision a practitioner runs before touching the redirect.
| Tier | Entity relationship | Equity read | Recommended action |
|---|---|---|---|
| Tier 1: perfect match | Same central entity, shared cluster, compatible claims | Full transfer | Implement the 301 with standard monitoring |
| Tier 2: sub-entity match | Source is a direct sub-entity of the target inside the same network | High partial transfer | Implement, then monitor ranking parity over an extended window |
| Tier 3: adjacent topic | Shared predicates but a different central entity | Reduced, uneven transfer | Redirect high-relevance URLs only, or point to the closest sub-page |
| Tier 4: unrelated | No shared central entity, no cluster overlap | Near zero, soft-404 risk | Use a 410 Gone, or hold the domain and rebuild instead |
Reading the tiers in practice
Tier 1 and Tier 2 are the green zone, where a domain-level 301 is the right move and the only question is how closely to watch the result. Tier 3 is the judgment zone, where a blanket domain redirect leaks equity and a per-URL map preserves it. Tier 4 is the stop zone, where forcing a 301 invites soft-404 treatment and, on a borrowed domain, policy scrutiny. The choice of target also interacts with the source type, which is the subject of 301 target strategy: aged-to-new vs expired-to-money.
How to measure source-target relevance, step by step
Measuring relevance is a five-step audit. Name the central entity on each side, check cluster membership, quantify keyword and content overlap, check the backlink anchor profile, then assign a tier. The audit runs before the redirect and before the purchase, so the domain you acquire already matches the page it will feed.
The tiers are only useful if you can place a real source-target pair on the ladder. This is the practical sequence for doing that, ordered so the cheapest checks gate the expensive ones. Run it as a relevance audit before you commit a redirect, and run it as acquisition diligence before you buy the source domain at all.
-
Name the central entity on both sides
Write down the one primary subject of the source page and the one primary subject of the target page. Same entity is Tier 1 territory. A direct sub-entity is Tier 2. A different but related entity is Tier 3. No connection is Tier 4. This single comparison resolves the decision in the clearest cases before any tool is opened.
The mistake: matching on surface keywords instead of entities. Two pages can share words and still describe different things, which is how an off-topic redirect slips through.
-
Check semantic content network membership
Look at what the target site already publishes. If it covers the source’s topic deeply, the source belongs in its cluster and the transfer is more reliable. If the target touches the topic once, membership is weak and the tier drops. Read the target’s topical map, not just the single landing page.
The mistake: judging the target by one page. A redirect lands inside a whole site, and Google reads the cluster, not the isolated URL.
-
Quantify keyword and content overlap
Use a content-gap or keyword-gap report in Ahrefs or Semrush to list the organic keywords both pages rank for, and read the shared inventory as a proxy for topical overlap. A high share of common ranking terms confirms the entity match. A thin overlap signals a lower tier even when the entities look aligned on paper.
The mistake: skipping the data and trusting intuition. The overlap report is the objective check that catches a mismatch the eye misses.
-
Check the backlink anchor profile of the source
Read the inbound anchors pointing at the source domain. They need to describe the same topic as the target. A source whose anchors are all about one subject, pointed at a target about a different subject, sends a mismatched signal that undercuts the redirect. This is the step where an aged domain’s real history either confirms or breaks the match, which is why buying intent peaks here: the right move is to acquire a topically matched aged domain whose profile has been screened against the target before purchase, the inventory the SEO Domains marketplace exists to supply. The metrics behind this read live in the Domain Authority & Metrics hub.
The mistake: buying on a headline authority score and ignoring what the links are about. A high score on an off-topic profile is the wrong raw material.
-
Assign the tier and choose the action
Combine the four checks into a single tier. Tier 1 and Tier 2 authorise the 301. Tier 3 routes to selective per-URL redirection. Tier 4 routes to a 410 or a rebuild. Record the verdict, because it doubles as the rationale for the acquisition and the monitoring plan once the redirect is live. The post-launch check is covered in Monitoring 301 impact in GSC.
The mistake: implementing before assigning a tier. A redirect pushed live without a relevance verdict is a guess, and a guess at Tier 4 is wasted authority.
What to do when relevance fails the threshold
When a source-target pair fails the relevance test, four options remain. Redirect only the high-relevance URLs and drop the rest. Point the source at the closest matching sub-page instead of the homepage. Return a 410 Gone for the cleanest deindex. Or hold the domain and rebuild it as its own topical authority before reconsidering.
A failed relevance check is information, not a dead end. It tells you a blanket 301 will waste the source’s authority, and it points to a better action. The four below cover every Tier 3 and Tier 4 case.
- Selective per-URL redirection. Map the few source URLs that genuinely match a target page and redirect those, then assign 410 or 404 to the rest. This preserves the equity that does match instead of drowning it in a domain-wide redirect that fails as a whole.
- Redirect to the closest sub-page. When the source has no perfect target but a deeper sub-page absorbs its topic, point the redirect there instead of at the homepage. A topical sub-page passes the relevance test that a generic homepage fails, which is why redirecting to a homepage is the single largest soft-404 trigger.
- Return a 410 Gone. For content with no topical home on the target, a 410 gives Google the cleanest deindex signal. It removes the URL faster than a 404 and avoids the soft-404 limbo a forced 301 would create.
- Hold the domain and rebuild. When the source domain carries real authority but no current match, the durable move is to rebuild it as a standalone site on its own topic, then reconsider consolidation later. The authority stays usable, and no equity is burned on a redirect that would fail.
Cross-niche pairs are the classic failure set: health to finance, local service to ecommerce, news to commercial. Each produces predictable equity loss and an anchor-profile mismatch, and each is better served by one of the four options than by a forced redirect. The scaling version of this decision, across a portfolio of source domains at once, sits in Multi-domain 301 merge: scale and limits, and the expired-domain timing question is covered in When to use a 301 from an expired domain.
Common 301 relevance mistakes: the checklist
The mistakes that waste a 301 are a short, repeatable list, and each has a relevance-based fix. They cluster around one root error: treating the redirect as a mechanical task instead of a topical decision. The checklist below pairs each mistake with why it fails the relevance test and the action that fixes it.
This table consolidates the failure modes scattered through the sections above into one scannable reference. The left column is the mistake, the centre column is why it breaks the relevance requirement, and the right column is the fix. Read top to bottom, the fixes describe a redirect built on a genuine topical match.
| The mistake | Why it fails the relevance test | The fix |
|---|---|---|
| Redirecting an unrelated page | No shared central entity, so Google reads a soft 404 and passes no equity | Confirm a shared central entity before redirecting; otherwise use a 410 |
| Redirecting everything to the homepage | A homepage rarely continues a specific page’s topic, the documented soft-404 trigger | Point each source at the closest topically matching sub-page |
| Matching on keywords, not entities | Shared words can mask different subjects, letting an off-topic redirect through | Name the central entity on both sides and compare those, not the keywords |
| Judging the target by one page | Google reads the whole cluster; weak network membership lowers the transfer | Check that the target site covers the source’s topic across its topical map |
| Buying a domain on its score alone | A high authority score on an off-topic backlink profile is the wrong raw material | Read the anchor profile and confirm the links are about the target’s topic |
| Blanket domain redirect at Tier 3 | A whole-domain 301 fails when only part of the content matches | Redirect the matching URLs selectively and drop the rest |
| Cross-niche redirect on a borrowed domain | Topical mismatch on earned authority draws site reputation abuse scrutiny | Keep the redirect inside the same niche, or rebuild the domain instead |
| Implementing before assigning a tier | A redirect with no relevance verdict is a guess that often lands at Tier 4 | Run the five-step audit and record a tier before going live |
| Skipping post-launch monitoring | A relevance miss only shows up as a ranking drop you have to catch | Track ranking parity in Search Console after the redirect goes live |
| Chaining redirects to force a match | Hops dilute the signal and add soft-404 risk at each off-topic step | Redirect once, directly, to a single topically matched target |
One pattern runs down the whole fix column. Every fix is a version of the same instruction: establish a genuine topical match before you redirect, and that match starts with the source domain itself. A domain whose history is off-topic fails the first relevance check and poisons every step after it. That is why a topically matched domain is the practical starting point, and it is the foundation the closing section returns to. The combined-signal question of pairing a redirect with a canonical is handled in 301 plus canonical: combined use.
Relevance requirement frequently asked questions
The five questions practitioners raise when source-target relevance enters a 301 decision, answered against the policy record and the entity-match logic of Koray’s rule.
Q1Does a 301 redirect to an unrelated page pass any PageRank?
An unrelated 301 transfers close to nothing. Google reclassifies the source as a soft 404, drops it from the index, and breaks the canonical chain that would have routed signals to the target. John Mueller stated Google treats these as soft 404s, and Glenn Gabe’s GSQI case study documented the same outcome on redirects to less-relevant pages.
Q2How is Koray’s rule different from Google’s general redirect guidance?
Google’s documentation recommends redirecting to an equivalent page without defining how close is close enough. Koray Tugberk Gubur supplies the threshold through three tests, central entity continuity, semantic content network membership, and predicate compatibility, turning the loose guideline into a measurable decision you can run before implementing a redirect.
Q3What is the minimum match for a safe 301 redirect?
The floor is one shared central entity or one direct sub-entity relationship between source and target. At or above that line the redirect sits in Tier 1 or Tier 2 and transfers equity. Below it the pair drops to Tier 3 or Tier 4, where the action shifts from a domain-wide 301 to selective mapping, a sub-page redirect, or a 410 Gone.
Q4Why does the site reputation abuse policy matter for a 301 decision?
Google announced the site reputation abuse policy in March 2024, enforced it with manual actions from 5 May 2024, and expanded it in November 2024. It treats topically mismatched content on earned authority as a violation. A cross-niche 301 from an aged domain into an unrelated target enters that pathway, so a relevance miss is both an equity loss and a policy exposure.
Q5When does a 410 beat a 301 for an aged domain with mismatched content?
A 410 wins when the aged domain’s content shares no central entity with any page on the target site. The 410 returns a clean deindex signal, removes the URL faster than a 404, and avoids the soft-404 limbo a forced 301 creates. Holding the domain to rebuild it on its own topic is the alternative when the authority is worth keeping.
The foundation of a relevant 301: a topically matched domain, properly vetted
Every part of the relevance requirement traces back to one variable: the topical match between the source domain and the target page. A domain whose history and backlink profile match the target is the raw material of a 301 that transfers equity. An off-topic domain fails the first relevance check no matter how the redirect is wired. Sourcing the match is the work.
Why the domain decides the redirect
A 301 cannot create relevance that the source domain does not carry. If the acquired domain’s history is about gardening and the target page is about accountancy, no redirect rule bridges that gap, because Google reads the topic, not the intent. The relevant target requirement is, in practice, a relevant source requirement: the domain you buy has to belong in the same topical map as the page it will feed.
How to source a domain that passes the relevance test
A domain that holds up as a 301 source survives a topical and profile check before money changes hands. The signals that decide the match are documented across the authority-metrics hub, and the registration-history read uses RDAP, the structured lookup that replaced WHOIS on 28 January 2025. The diligence on acquiring expired names sits in the Expired Domain Fundamentals hub.
- A backlink profile whose anchors and referring topics match the intended target, not just a high headline score.
- A registration and content history on the same subject as the target, read through RDAP and archived pages.
- Authority metrics cross-validated rather than trusted singly, so an inflated score does not hide an off-topic or spammed profile.
- A clean spam screen, since a toxic inheritance fails the relevance test and the quality test at once.
Browse topically matched aged and expired domains
The legitimate demand behind every relevance-requirement search is access to a domain whose real history matches the page it will feed. That is the product, not a redirect service 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 authority metrics, so the topical match is read before the domain is listed and priced.
