Are You Sick of AI Deepfakes and Slop? A Field Manual for Writers Who Still Do the Work
Your feed is drowning in content that looks real, reads passable, and adds nothing. It's not your imagination. The volume advantage of AI, bot amplification, and celebrity ghostwriting is overwhelming platforms. Writers who put in the hours are getting buried.
This is a practical playbook to protect your career, grow despite the noise, and build a body of work that algorithms can't counterfeit.
What Changed (And Why Your Metrics Fell Off a Cliff)
Algorithms reward volume, recency, and engagement velocity. Slop shops can post 10-20 times a day. Bot networks fake the early boost. Celebrities arrive with PR engines and teams. The result: the feed tilts toward scale, not substance.
Quality still wins, but it needs structure. You can't out-spam a machine. You can out-proof it.
Build a Moat Machines Can't Fake
- Proof-of-work in public: Show your sources, timelines, draft notes, and corrections. Screenshots, field photos, annotated PDFs. AIs can mimic tone; they can't fake your receipts.
- Specificity over generalities: Names, places, timestamps, primary docs, interviews. Vague writing is where slop hides.
- Signature voice: Short, punchy lines mixed with occasional long, rhythmic sentences. Add stance. Risk saying something clear instead of hedging every point.
- Original reporting rituals: One call, one FOIA, one transcript pull, or one on-the-ground observation per piece. Even a small, true detail changes everything.
Own the Relationship With Readers
- Email list health: Clean inactive subs quarterly, segment by interest, and ask for replies to train deliverability. Set SPF/DKIM/DMARC with your sender domain.
- Cross-channel redundancy: Mirror your posts to your site, RSS, and a second channel you control. Don't let one platform hold your income hostage.
- Community > virality: Weekly office hours, comment prompts, AMAs. Depth beats reach. Ten people who reply are worth a thousand who skim.
Spot and Counter Deepfakes
- Reader education: Post a short guide on your site: how you verify media, how you correct errors, and how you handle AI use.
- Basic checks: Reverse image search, check audio artifacts, confirm with a second source, and watch for uncanny consistency across a creator's "voice."
- Link readers to help: Share practical guidance on scam detection from the FTC: How to avoid a scam.
Your Public AI Policy (Use It Without Becoming Slop)
- Acceptable use: research leads, outline options, headline drafts, and first-pass summaries.
- Non-negotiables: all quotes verified, claims sourced, final draft rewritten in your voice, personal experience added, and links to primary material.
- Audit trail: keep a notes file listing sources, interviews, and what AI touched. A one-sentence disclosure builds trust.
If you want a curated jump-start on ethical tooling and workflow prompts for writers, browse a vetted set of options here: AI tools for copywriting.
A Quick Reader-Facing Checklist to Sniff Out Slop
- Voice: lots of platitudes, no stance, and the same safe phrasing across posts.
- Sources: generic links, no primary docs, no names, no timestamps.
- Speed: 10+ posts a day with identical structure and rhythm.
- Engagement pattern: sudden spikes from unknown accounts; comments that say nothing specific about the piece.
Monetization That Survives Algorithm Swings
- Mixed model: memberships + paid research notes + workshops + aligned sponsors. One income stream is fragile.
- Value ladder: free weekly briefing, paid monthly deep-dive, quarterly cohort or workshop. Make the upgrade path obvious.
- Trust-first sponsors: take fewer, disclose standards, and include your own testing notes.
Distribution Without Selling Your Soul
- 1-2 flagship pieces a week: heavy on original insight and evidence.
- 3-5 light posts: source dumps, notes, behind-the-scenes updates.
- Repurpose smartly: pull 5-7 quotes into short posts, one chart for social, a 60-90 second audio summary for your feed.
Operational Hygiene for Writers
- Source database: a simple spreadsheet of experts, documents, and contacts with tags.
- Corrections log: public page with timestamps. Credibility compounds.
- Template bank: pitch email, interview request, data request, follow-up, and correction note. Speed without sloppiness.
- Monthly review: which pieces drove replies, new subs, and paid upgrades. Replicate what your best readers vote for with their time.
What to Tell Your Readers (Copy-Paste Friendly)
- Reply to one email a week. It trains deliverability and shapes coverage.
- Whitelist the sender address and drag it to Primary.
- Share one post that changed your mind with a colleague.
- Upgrade if the work saves you time or money. If not, keep the free tier and stick around.
A Simple Weekly System
- Monday: pick one question only you can answer; line up one source or dataset.
- Tuesday: interview, collect receipts, write the bones.
- Wednesday: draft, insert proof, cut 20% of fluff.
- Thursday: publish the flagship; ship 3 quotes to social; send a short reader prompt.
- Friday: community session or AMA; log corrections and notes.
- Weekend: light post: what you're tracking next week.
Final Word
You can't out-post bots or outspend celebrities. You can outlast them with proof, voice, and a direct line to readers. Keep your work grounded in specifics. Show your process. Build your own channels. Ask for help clearly and often.
The feed favors noise. Readers favor trust. Give them a reason to stay.
Your membership also unlocks:
