Expired domain abuse — when a bought domain's legacy authority becomes the liability

You acquired a domain with an established backlink profile — a defunct local newspaper, a shuttered SaaS, a lapsed nonprofit — and rebuilt it with programmatic content in a completely different niche. For six to ten weeks it ranked far above what a fresh domain could earn, riding residual link equity and historical trust. Then, typically anchored to a spam-update rollout (Google named expired domain abuse as one of three new spam policies in the March 5, 2024 spam update, which finished rolling out on April 19, 2024 after 44 days), rankings collapse across the new template set while the legacy pages Google still remembers behave inconsistently. In Search Console you may see a manual action citing 'Expired domain abuse', or — more often — silent algorithmic suppression: impressions on the new content fall to near zero, the cached authority signals stop transferring, and third-party trackers show the domain reverting to the visibility its new content alone would merit.

Repurposing a domain's legacy authority for content unrelated to its history

The core violation. Google compares the topical and link-graph fingerprint of the domain's archived history against its current content. When a former photography-equipment blog reappears as a payday-loan directory, the inherited backlinks point at a subject the current pages never cover, and the mismatch reads as an attempt to launder authority rather than earn it.

Skipping the new-domain trust ramp by migrating a programmatic template set onto an aged shell

Some operators move an entire /city/{service} grid onto a purchased domain specifically to bypass the months of slow trust-building a fresh domain endures. The template itself may already be borderline thin or doorway-shaped; layering it onto borrowed authority accelerates the ranking but also concentrates every scaled-content and doorway signal onto a domain now under expired-domain scrutiny.

Funnelling equity through a 301 redirect from an unrelated expired domain

Rather than rebuilding on the old domain, the operator 301-redirects a topically-unrelated expired domain into a money site to pass PageRank. Google discounts redirects whose source and target share no topical or link-graph continuity, and a cluster of such redirects pointing into one host is itself a spam signal.

1. 1

   Pull the domain's history in the Wayback Machine and record its former primary topic, then compare it against your current content's primary topic — a categorical mismatch is the single strongest expired-domain-abuse signal.

2. 2

   Export the referring domains from your backlink tool and label each by the subject it links about; if the majority of legacy links are topically unrelated to your current pages, the inherited authority is the liability, not the asset.

3. 3

   Run pseolint's host-section-divergence rule to quantify how far the new content section diverges from any legacy section still on the host across links, topic, template, and authorship.

4. 4

   Audit every 301 redirect pointing into the domain and verify the source domain's former topic matches the target — discount or remove redirects with no topical continuity.

5. 5

   Check Search Console → Manual actions for an explicit 'Expired domain abuse' citation, and the Security & Manual Actions history for prior enforcement on the domain before you acquired it.

6. 6

   Measure the unique, substantive value of the new pages independent of the domain's authority — if the same content on a fresh domain would not rank, the authority is doing work the content cannot sustain, which is exactly what the policy targets.

pseolint findings most strongly correlated with this pattern.

Kestrelbank Analytics acquired a lapsed personal-finance newsletter domain with 1,900 referring domains built over a decade of genuine editorial coverage, and rebuilt it as a 4,200-page directory of crypto-exchange comparisons — a topic the newsletter had never touched. For nine weeks the directory ranked in the top five for mid-tail exchange queries, far above its content quality, on the strength of the finance-newsletter backlinks. When the March 2024 spam update finished rolling out, Google's expired-domain classifier scored the crypto directory against the newsletter's archived history, found no topical or link-graph continuity, and suppressed the entire new template set; visibility fell 94% in eleven days. There was no recovery path that preserved the play — the value was always the borrowed authority, which the policy is designed to neutralize. The domain was eventually rebuilt around genuine, independently-linkable exchange-security research authored under a named analyst, at which point it began earning the rankings its own content merited.

Recovery from expired domain abuse is harder than most demotions because the play's entire value — the borrowed authority — is exactly what Google has decided to stop crediting. If the content on the new domain is genuinely useful and merely topically discontinuous with the domain's past, the path is to rebuild topical and editorial continuity: publish substantive, independently-linkable content in the domain's actual current subject, add named authorship and E-E-A-T signals, and let Google recrawl and re-fingerprint the domain over one to two core-update cycles (typically 60 to 120 days). If the content only ever ranked because of the inherited authority, there is no recovery that preserves the original strategy — treat the domain as a fresh property and earn rankings its own content can sustain. Removing topically-unrelated 301 redirects into the domain should be immediate; that signal is discounted quickly once the redirects are gone.