docs(marketing): add backlink outreach target list for Chrome DevTools MCP campaign
Action 6 prep — outreach target list (Tier 1-3), email template, priority order, monitoring plan. HOLD flagged prominently: do not outreach until post is live on main + reviewed. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
07464b7b6d
commit
08057cf59b
@ -0,0 +1,92 @@
|
||||
# Backlink Outreach Targets
|
||||
## Chrome DevTools MCP SEO Campaign — Action 6 Prep
|
||||
**Status:** TARGET LIST — do NOT outreach until post is live + reviewed by Marketing Lead
|
||||
**Post URL:** /blog/browser-automation-ai-agents-mcp (pending push + publish)
|
||||
|
||||
---
|
||||
|
||||
## Tier 1 — High-DR, Topic-Relevant (Priority Outreach)
|
||||
|
||||
| Site | Type | Why relevant | Contact / Format |
|
||||
|---|---|---|---|
|
||||
| modelcontextprotocol.io | MCP official docs | Primary backlink, topical authority on MCP | GitHub PR or Discussion |
|
||||
| chrome-developer-tools.github.io | CDP official docs | Primary backlink, CDP authority | GitHub PR or doc suggestion |
|
||||
| langchain.com/blog | LangChain blog | They cover MCP integrations, have published similar posts | Guest post or tip submission |
|
||||
| python.langchain.com | LangChain Python blog | Their audience is exactly our target reader | Blog syndication tip |
|
||||
| crewai.com/blog | CrewAI blog | CrewAI users want better browser tools — natural fit | Guest post or contribution |
|
||||
| news.ycombinator.com | Hacker News | Show HN potential when post goes live | Submit when published |
|
||||
| dev.to (mcp tag) | Community blog | Active MCP discussion, many articles tagged MCP | Share link + short description |
|
||||
| reddit.com/r/LocalLLama | Community | High-intent developer audience for AI agent tooling | Share link |
|
||||
| reddit.com/r/MachineLearning | Community | Relevant for AI agent + tool use discussion | Share link |
|
||||
|
||||
---
|
||||
|
||||
## Tier 2 — Developer Communities & Newsletters
|
||||
|
||||
| Site | Type | Why relevant | Contact / Format |
|
||||
|---|---|---|---|
|
||||
| pycoders.com | Weekly Python newsletter | Python developers building AI agents | Submit via their form |
|
||||
| pythonweekly.com | Weekly newsletter | Python developers | Submit link |
|
||||
| javascriptweekly.com | Weekly newsletter | JS developers (CDP is JS-adjacent) | Submit link |
|
||||
| tl;dr.tech | Daily newsletter | Developers, covers AI/ML tools | Submit link |
|
||||
| Bytes.dev | JS/TS weekly | Relevant for MCP JS implementations | Submit link |
|
||||
| discord.gg/langchain | LangChain Discord | Active community, share link in browser-automation channel | Post in their Discord |
|
||||
| discord.gg/crewai | CrewAI Discord | Share in tools/plugins channel | Post in their Discord |
|
||||
|
||||
---
|
||||
|
||||
## Tier 3 — SEO / Link-Building Contextual
|
||||
|
||||
| Site | Type | Why relevant | DR / Notes |
|
||||
|---|---|---|---|
|
||||
| github.com/sponsors | GitHub | Many MCP repos — open PRs linking to tutorials | Contribute to relevant MCP repos |
|
||||
| stackprinter | Stack Overflow | Answer questions about MCP browser automation with a link | Be helpful first, link naturally |
|
||||
| semgrep.dev | Security/tooling blog | CDP is a security-relevant protocol — code scanning angle | Pitch guest post on MCP security |
|
||||
|
||||
---
|
||||
|
||||
## Outreach Email Template
|
||||
|
||||
**Subject:** Tutorial: AI Browser Automation with MCP + Chrome DevTools (thought it might fit [publication])
|
||||
|
||||
Hi [Name],
|
||||
|
||||
I came across [their post on X] and found it useful for [reason].
|
||||
|
||||
I recently published a tutorial on giving AI agents a real browser using MCP + Chrome DevTools Protocol — no Puppeteer, no SaaS dependency. It covers:
|
||||
- How MCP gives AI models typed browser tool calls
|
||||
- A full Python code example (end-to-end competitor research agent)
|
||||
- Infrastructure comparison (custom Playwright vs SaaS browser APIs vs Molecule AI + MCP)
|
||||
|
||||
[Post URL + UTM]
|
||||
|
||||
Happy to do a follow-up on a specific angle if useful — e.g. security scanning with CDP, or integrating with [their tool].
|
||||
|
||||
[Your name]
|
||||
|
||||
---
|
||||
|
||||
## Outreach Priority Order
|
||||
|
||||
1. **Day 1 of outreach:** Hacker News, Reddit r/LocalLLama, dev.to
|
||||
2. **Day 2–3:** LangChain blog tips, Python Weekly, Pycoders
|
||||
3. **Week 2:** MCP GitHub, CDP docs PR, Semgrep guest post
|
||||
4. **Week 3:** Stack Overflow answers (build reputation first, then link)
|
||||
|
||||
**DO NOT outreach until:**
|
||||
- Post is pushed to `main` and live at the final URL
|
||||
- Marketing Lead or PMM has reviewed and approved the final version
|
||||
- UTM parameters are confirmed
|
||||
|
||||
---
|
||||
|
||||
## Monitoring After Outreach
|
||||
|
||||
Track acquired backlinks with:
|
||||
- Google Search Console → Links → External links (check weekly)
|
||||
- Ahrefs/Moz if available
|
||||
- GitHub stars/watchers on molecule-core repo (correlation signal only)
|
||||
|
||||
---
|
||||
|
||||
*Last updated: 2026-04-20 by Content Marketer*
|
||||
Loading…
Reference in New Issue
Block a user