MISTAKE: Publishing community-submitted codes with no decay logic

MISTAKE: Publishing community-submitted codes with no decay logic
User-submitted codes are great inventory and a brutal liability — they go stale, they're sometimes single-use codes one person already burned, and a page full of 'success: 0%' codes drags your whole domain's trust score down with users and with the AI engines now ranking deal sites by reliability.
The fix: Treat every submitted code as guilty until verified. Auto-expire community codes after X days without a confirmed success, sort by recent success rate not recency, and visibly retire anything below a threshold. Show the upvote/downvote and last-worked timestamp so the user judges with you.
Why it matters: Community codes can be your edge over feed-only competitors — but only if your decay logic is more aggressive than your users' optimism.