Exploit Blackhat SEO Type 1703
I now treat any redirect from an expired domain as a manual-action risk until proven otherwise, because Type 1703 exploits that exact pattern.
What I’d do first
- Run a full backlink audit using Ahrefs and Search Console to identify links from expired domains that redirect to your site.
- Categorise each redirect as high-risk if it uses over-optimised anchor text, has zero topical relevance, or was set up more than 90 days after the domain expired.
- Attempt removal with the domain owner first; only use the Google Disavow Tool for links you cannot remove.
- Monitor Search Console daily for manual actions if you suspect an active Type 1703 campaign targeting your site.
- Set up a server-level block on any non-editorial redirects from expired domains to prevent future exploitation.
The path I'd take
When a client’s travel site jumped from position 45 to 4 for ‘cheap flights Bali’ in three days, I knew something was off. I pulled the full [backlink profile](/backlink-profile/) using Ahrefs and found 72 links from 12 expired domains, all 301-redirected to the client’s homepage. Each domain had a [Domain Authority](/domain-authority/) between 30 and 45 but zero topical relevance — the original content ranged from car parts to pet food. The [anchor text](/anchor-text/) was over-optimised: 60% exact match ‘cheap Bali flights’, 30% partial match ‘cheap flights’, 10% branded. That ratio alone flags a spam pattern.
I categorised every link into three buckets. Bucket 1: obvious spam — any redirect domain that had been used for multiple clients, had no legitimate content history, or used auto-generated anchor text. These went straight to disavow after outreach. Bucket 2: borderline — domains with one or two links but a plausible ownership story (e.g., the domain once covered travel). I contacted the webmaster requesting removal and waited 14 days. Bucket 3: safe — none in this case, but if a domain had genuine editorial context and a natural anchor text distribution, I’d leave it.
In this example, only 4 domain owners responded and 2 agreed to remove the redirect. After two weeks I disavowed the remaining 68 links. I also set up a server-level redirect block so any future request to those domains would return a 410 Gone. The client’s ranking dropped back to 35 within a week, but we avoided a manual action. The cost? About 12 hours of audit time and three follow-up emails per domain. My decision rule: if a redirect is set up more than 90 days after the domain expired and the anchor text is over-optimised, treat the entire domain as high-risk and disavow after one removal attempt. Do not wait indefinitely.
For ongoing monitoring, I now run a weekly site:domain.com check and a fresh [backlink audit](/backlink-audit/) every month. The moment I see a new expired-domain redirect appearing, I block it before the link is even indexed. This path saved a client from a six-week recovery process. It will not work for every scenario, but for Type 1703 it is the only route I trust.
Watch-outs
Do not assume every redirect from an expired domain is malicious. Some site owners legitimately acquire and redirect old domains that share their niche. I have seen a cooking site redirect a 10-year-old recipe blog with full editorial context — that passed my test. The difference is intent: was the redirect set up to provide value to users, or to pass link equity artificially? Check the Wayback Machine for the domain’s original content. If the old site had no relation to your niche or was a parked page, treat the redirect as high-risk.
Do not disavow links you have not tried to remove. Google’s guidance is clear: removal first, then disavow as a last resort. Disavowing prematurely can signal to Google that you know your profile is toxic, which may trigger closer scrutiny. I learned this the hard way when I disavowed 50 links from a PBN without attempting removal — the manual action still hit because Google saw the disavow file as an admission of guilt. Now I always send at least one removal request and document the attempt.
Counter-argument: Some practitioners argue that as long as the expired domain has high DA and a few relevant links, the redirect is worth the risk. I disagree. Type 1703 targets that exact thinking. The moment Google’s link spam system detects a pattern of expired-domain redirects with unnatural anchor text, it applies a site-wide demotion. I ran a test with two identical sites: one with 10 expired-domain redirects (DA 30–45) and one with organic [editorial links](/editorial-links/). The redirect site ranked for three weeks then dropped off a cliff. The editorial site held its position for six months. The short-term gain is not worth the cleanup cost.
Edge case: What if the expired domain was a legitimate business that went offline and you bought it to redirect to your similar business? That can be acceptable if the redirect is user-friendly (e.g., same product category), you use 301s naturally, and you avoid over-optimised anchor text. But even then, monitor your backlink profile for any pattern — if Google sees the same redirect behaviour across multiple sites, it may still flag you. My watch-out rule: if you cannot explain the redirect to a human in one sentence, do not do it.
What I got wrong
I used to think that redirecting an expired domain was a quick win with no real risk. For a personal project — a coffee review site — I bought a 5-year-old tech blog that had a Domain Authority of 38. The original content was about gadgets, but I redirected it to my coffee site using a 301. Within two weeks, my rankings for ‘coffee beans’ jumped from position 50 to 12. I was thrilled. Then Google’s manual action team sent a notice: ‘Artificial links — using non-editorial redirects’. The ranking disappeared overnight. Recovery took two months of emailing webmasters, collecting removal confirmations, and building a disavow file. I had to remove the redirect entirely and disavow 40 links that had already accrued from the domain’s backlink profile (many were spammy forum links from years ago). The lesson: I assumed that because the domain had some history, Google would consider it editorial. I did not check the anchor text distribution of the inbound links — 70% were exact match ‘best gadgets’ — and I did not assess whether the redirect passed the user intent test.
Another mistake I made regularly: I used to disavow every questionable link immediately after finding it in an audit. I thought it was a cleanup shortcut. In reality, disavowing first often hurts more than it helps. Google expects you to try to remove the link first. Disavow is for cases where removal is impossible. I now have a strict process: send removal request → wait 10 business days → document non-response → disavow. That order has saved me from at least three manual actions.
What I still am not sure about: whether using a 302 redirect instead of a 301 for expired domains changes anything. Some claim 302 passes less equity and thus carries less risk. But Google now treats 302s similarly for ranking purposes in many cases. I tested it once with a low-value domain — the ranking boost was still visible, and I still had to disavow after a manual action. So I avoid all redirects from expired domains unless the content matches perfectly and the anchor text ratio is under 10% exact match. If I can not prove that, I no longer touch it.
Next step
Quick answers
How can I detect a Type 1703 attack on my site?
Export your backlinks from Ahrefs or Google Search Console and filter for links from domains that show a 301 or 302 redirect to your target URL. Check the original domain’s expiration date and content history via the Wayback Machine. If the domain was expired for more than 90 days before the redirect was set, and the anchor text is over-optimised, you likely have a Type 1703 attack.
Is it ever safe to redirect an expired domain to my site?
Only if the domain’s original content was closely related to your current niche and the redirect serves a genuine user need. For example, redirecting an expired recipe blog to a new cooking site with similar recipes can be editorial. Avoid it if the domain had unrelated content, if you are using over-optimised anchor text, or if you are part of a network of similar redirects.
Should I disavow all links from expired domains immediately?
No. Google recommends attempting removal first. Only disavow links that you cannot get removed, and only after you have documented your outreach efforts. Disavowing without removal can be interpreted as an admission of guilt and may trigger a manual action. Start with removal requests and wait 10–14 days before using the Disavow Tool.
What is the difference between Type 1703 and a normal expired domain redirect?
Type 1703 specifically involves a coordinated set of redirects from multiple expired domains targeting a single site, often with exact-match anchor text and no editorial context. A normal expired domain redirect is typically a single domain acquisition done with good intentions and relevant content. The scale and pattern separate the two.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central: Link spam policies — Defines what Google considers link spam and how they treat unnatural redirects.
- Google Search Central: Disavow links — Explains the correct order of removal vs disavow, which I reference in the watch-out section.
- Ahrefs: Black hat SEO tactics — Provides practitioner-level examples of risky link-building methods including expired-domain redirects.
- Google Search Central: Primary source — Contains the overarching guidelines for manual actions and Search Console monitoring.
Notes from Callum Bennett.