video
https://www.youtube.com/watch?v=Bn
- AI speeds research, enrichment, and first‑draft personalization — not the relationship. Use it to cut grunt work and keep humans on angles, consent, and final sends.
| Field | Why it exists |
|---|---|
| source_system | So you can audit where a contact came from |
| consent_status | Avoids legal pain and trust erosion |
| last_relevant_article | Anchors personalization to something real |
| angle_id | Ties messaging to your proof assets |
| fit_score | Keeps you from forcing bad fits |
| status | Lets you stop sequences quickly |
Bad personalization
- “Loved your recent piece! Big fan.”
- “Can I send a guest post?”
Good personalization
- “Citing your 8/29 piece on rural broadband gaps: we have county‑level adoption data you didn’t have.”
- “We can provide embargoed WA and OR figures with methodology and a 20‑minute Q&A.”
AI is your research assistant, not your spokesperson. Use it to speed targeting and drafts, then have a human own the relationship and the final send.
Fast is fine. Controlled is non‑negotiable.
We aren’t “bulk” — we only hit 5,000/day occasionally. Does that count?
Yes. Gmail says hit close to 5,000 in 24 hours to personal Gmail once and you’re classified as bulk permanently. Plan throttling and complaint controls.
Do I need one‑click unsubscribe in PR emails?
It’s required for promotional/marketing email. Transactional one‑to‑one isn’t in scope, but borderline “updates” are risky — add clear opt‑out language at minimum.
What about B2B PR in the UK — consent or not?
PECR rules differ for “corporate subscribers,” but you still need opt‑out mechanics, suppression lists, and records. Don’t spray individuals.
Did AI Overviews kill clicks — is SEO dead?
No. AIO presence varies by study and vertical. Both Google and Bing cite sources, and some publishers see traffic from those surfaces. Measure your own citations and clicks.
Is n8n affordable for this?
Cloud Starter lists about 2.5K executions/month, Pro about 10K. You’re billed per workflow run, not per step. Check pricing before you automate everything.
Are purchased media lists okay if the vendor “has consent”?
No. Consent isn’t transferable. Purchased lists are a common path to traps, complaints, and blocklists.
- Gmail Email sender guidelines (bulk thresholds, spam complaints, unsubscribe, DMARC)
- Google: Explore web with generative AI in Search (citations, controls)
- Bing Webmaster Tools: AI Performance public preview
- Muck Rack: State of Journalism 2026
- Muck Rack: Follow-up with journalists (webinar recap)
- BrightEdge: AI Overviews presence and citations
- Spamhaus: Address acquisition and consent basics
- ICO: Consent record-keeping (GDPR Art. 7)
- ICO: B2B direct marketing and PECR
- n8n Docs: HTML node
- n8n Pricing
Most PR outreach still feels like 2009 spreadsheets duct-taped to mail merges. I watched AI BROS’ new video, “This AI Workflow Makes PR & SEO Campaigns Much Faster” (https://www.youtube.com/watch?v=Bnvm9agJdZ8), and it’s worth talking about because speed without control just turns into more spam and deliverability pain 🙂

// My reaction
This still happens?
The stakes are higher now. AI Search is biased toward citable, trustworthy content with visible citations, and Gmail/Yahoo’s rules don’t care about your intentions. Gmail guidelines and Yahoo Sender Hub set the bar, and Google and Microsoft now render citations directly inside AI answers. (support.google.com)
Why this matters for SEO and PR
- AI Search is citation-hungry. If you want to show up in AI answers, you need credible, citeable pages and brand mentions that reinforce entities and claims. See how I structure that in Build Content for AI Search: answer-first, citeable, extractable. Then go check your exposure with the AI Visibility Checker. 🔗
- Email deliverability and journalist fatigue are real. Spray-and-pray gets you blocklisted fast.
- You need a single source of truth for contacts, states, and consent. No rogue sheets.
Useful context on my approach:
- Planning: SEO Strategy
- Content assets: Content Writing
- Automation backbone: n8n HTML node (field manual)
- AI visibility sanity check: AI Visibility Checker
- AI can speed research, enrichment, and first-draft personalization — not relationship. Use it to cut grunt work, then add human judgment where it counts.
The workflow I actually use
1) Define the campaign outcome and why us
- One sheet with the campaign goal, proof assets you can actually show, and the single page you want cited. If you don’t have a citeable page, build that first, otherwise you’re pushing air.
2) Build the contact index legally and cleanly 🧹
- Start with exports from media databases you already license, plus opt-in journalist lists and newsletters. Where allowed, augment with on-site author pages and mastheads, respect site terms.
- Consolidate into a master table: name, outlet, beat, region, email, source, consent flags, last-contact date.
- Use n8n to normalize names and outlets and dedupe. Keep a global do-not-contact list and enforce it on every run, no exceptions.
3) Classify and score with AI 🧠
- Task LLMs with light enrichment only: topic clusters, beat tags, historical coverage fit, and a quick-fit score from 0 to 3. No hallucinated bios, no guessing emails.
- Prompt pattern, system: “You tag journalists by topic and beat using only provided text. If unknown, return ‘unknown’. Output JSON with fields: topics[], beat, fitScore 0–3 and rationale.”
4) Create angles, then pressure-test them
- Draft 3 to 5 angles mapped to your proof assets. Each angle needs a quote, a data point, and a unique hook. If you can’t paste proof into the pitch, it’s not an angle.
- Let AI rough the skeletons, then you rewrite for truth and tone. Cut anything you can’t stand behind on a live call.
5) Personalize at scale without sounding robotic 📨
- Dynamic fields I actually use: last relevant article slug, one-sentence why-it-fits, the unique data point you’ll share, and the ask.
- Guardrail prompt, assistant: “Rewrite this 80–110 words, plain English, no flattery, reference the provided article in one clause, and propose a specific asset or expert. No emojis, no exclamation marks.”
6) Sequence and send
- Use a CRM or a sheet that tracks Status: queued → sent → replied → scheduled → covered → no. Throttle per domain. Never BCC blasts, ever.
- Two-touch max unless invited to continue. If it’s not a fit, move on and keep your rep clean.
7) Monitor and measure 🔗
- Track replies, briefings booked, earned links by page, unlinked mentions, and whether your target page starts appearing more often in AI answers.
- Add UTMs to assets you share so you can attribute downstream. If you do not tag it, you can’t claim it.
8) Post-campaign clean-up 📈
- Update contact states, enrich learned preferences, and prune bounces. Feed wins and misses back into your content roadmap and your scoring logic.
Practical fields I keep in the outreach table
| Field | Why it exists |
|---|---|
| source_system | So you can audit where a contact came from |
| consent_status | Avoids legal pain and trust erosion |
| last_relevant_article | Anchors personalization to something real |
| angle_id | Ties messaging to your proof assets |
| fit_score | Keeps you from forcing bad fits |
| status | Lets you stop sequences quickly |
Prompts and snippets that hold up under pressure
Bad personalization
- “Loved your recent piece! Big fan.”
- “Can I send a guest post?”
Good personalization
- “Citing your 8/29 piece on rural broadband gaps: we have county-level adoption data you didn’t have.”
- “We can provide embargoed WA and OR figures with methodology and a 20-minute Q&A.”
AI is your research assistant, not your spokesperson. Use it to speed targeting and drafts, then have a human own the relationship and the final send.
Risks and guardrails
- Legal and consent: respect CAN-SPAM, GDPR and PECR where relevant. Country rules differ. When unsure, don’t send. 🛑
- Accuracy: never let models invent bios, emails, or quotes. Keep model outputs in draft until reviewed.
- Brand safety: no off-brand promises, no fake urgency. If the asset isn’t ready, pause.
- Deliverability: warm domains, correct DNS, throttling, plain-text fallbacks. Keep your sending IP and domain reputation clean.
What to measure beyond links
- Quality: topical fit and the authority of the linking page, not just the domain.
- Velocity: how fast coverage starts after first sends, this ties to timing and angle strength.
- Coverage depth: are you cited, quoted, or just mentioned, score the difference.
- AI visibility: did your citeable page start surfacing in AI results for target queries, run periodic checks with the AI Visibility Checker.
Fast is fine. Controlled is non-negotiable.
Takeaway
If AI is just helping you send more email, you’re torching goodwill for short-term vanity metrics. Use it to compress research, enrichment, and first-draft work, then keep humans on angles, consent, and final sends. You’ll end up with cleaner ops, faster cycles, and coverage that compounds into links, mentions, and citations that feed traditional SEO and AI Search visibility. That’s how you win without burning your sender reputation or your relationships, and that loops straight back into better SEO, smarter GEO targeting, and tighter AI-era measurement.

// My reaction

