Failure mode: treating 410 like 404

Failure mode: treating 410 like 404
Mistake: you batch 404 and 410 together. 410 = "gone, intentionally." The owner deleted it on purpose and likely won't relink. Wasted outreach slots.
Fix triage:
— 1. Split status codes into separate buckets at crawl time.
— 2. 404 (not found) → primary outreach queue, high priority.
— 3. 410 (gone) → low-priority queue; only pursue if the linking page is high-value and the topic is evergreen.
— 4. Add a note field: "intentional removal — lead with why your resource is the natural successor."
— 5. QA gate: cap 410 outreach at 15% of any batch.
Automation: status-code routing in your crawl export filter.
Definition of done: 404 and 410 never share an outreach batch.