Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from repo
Analyze website backlink profiles to assess domain authority and identify link-building opportunities
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
references/outreach-templates.md
1# Outreach Templates23Copy-start templates for link building. Personalize every email, lead with the recipient's value, keep the first note to 100-150 words, make one clear ask, use a real domain email, and never attach files in the first email.45## Operating Rules67| Rule | Do | Avoid |8|------|----|-------|9| Personalization | Mention a specific article, section, quote, or page | Generic "love your site" openers |10| Ask | One request per email | Combining guest post, link swap, and product pitch |11| Sequence | Initial, follow-up after 5-7 days, final after day 14 | More follow-ups after a decline |12| Sender | Real person at `[email protected]` | Free-mail aliases for cold outreach |13| Compliance | Honest reason, clear identity, easy opt-out | Fake "Re:", misleading claims, link-exchange language |1415## Template Matrix1617| Use Case | Subject | Opening Proof | Core Ask |18|----------|---------|---------------|----------|19| Broken link | `Found a broken link on your [topic] page` | `I noticed [broken URL/anchor] in [section] returns 404.` | `Would [your URL] work as a replacement?` |20| Guest post | `Guest post idea: [title]` | `Your recent [article] covered [specific angle].` | `Would this outline fit your readers?` |21| Resource page | `Resource for your [topic] page` | `Your [topic] resource page is organized around [section].` | `Consider adding [resource] to [specific section].` |22| Unlinked mention | `Thanks for mentioning [brand]` | `You mentioned [brand] in [article/context].` | `Could you link that mention to [URL]?` |23| Digital PR | `New data: [headline stat]` | `[Study] found [surprising finding].` | `This may fit your coverage of [beat].` |24| Source request | `[Source request] Re: [query]` | `[Name], [title], can speak to [topic].` | `Use the quote/data below if helpful.` |25| Skyscraper | `Updated resource on [topic]` | `You link to [older competitor resource].` | `If useful, swap to this updated version.` |26| Relationship-only | `Loved your piece on [topic]` | `The section on [specific point] helped us [outcome].` | No ask; start relationship. |2728## Base Email Shape2930```text31Hi [Name],3233I was reading [specific page/article] and noticed [specific observation].3435[One sentence of value: broken link, useful resource, original data, quote, or relevant angle.]3637[One clear ask tied to their reader benefit.]3839No pressure either way. Thanks for the useful work on [topic].4041[Name]42```4344## Scenario Starters4546### Broken Link4748```text49I noticed the link to [description] in [section] returns a 404.50We recently published [resource] covering [overlap]. It may work as a replacement: [URL].51Either way, wanted to flag the broken link.52```5354### Guest Post5556```text57I'd like to contribute:58Title: [proposed title]59Angle: [unique POV]60Reader value: [why their audience cares]61Samples: [URL 1], [URL 2]62Would this be a fit?63```6465### Digital PR / Research6667```text68We just published [study] and found [headline stat].69Key findings: [finding 1]; [finding 2]; [finding 3].70Full report: [URL]. Happy to provide quotes or raw cuts.71```7273### HARO / Source Request7475```text76Source: [name], [title], [company]77Credentials: [why credible]78Response: [2-3 concise paragraphs]79Key quote: "[one standalone quote]"80Available at [email/phone].81```8283## Follow-Up Sequence8485| Email | Timing | Message |86|-------|--------|---------|87| Initial | Day 0 | Make the ask |88| Follow-up 1 | Day 5-7 | `Just bumping this in case it got buried. [one-sentence reminder].` |89| Follow-up 2 | Day 14 | `Last follow-up. Feel free to bookmark [URL] if useful later.` |90| Stop | After FU2 | Move to a 3-6 month re-engagement list with a new angle |9192## Response Handling9394| Response | Reply Pattern |95|----------|---------------|96| They'll add link | Thank them; provide exact URL and preferred anchor if requested |97| They want guest post | Send title, outline, target length, delivery date, and ask for guidelines |98| Noncommittal | Acknowledge; offer to help as a future source |99| Decline | Thank them once; do not argue or follow up again |100| No response | Do not mention the non-response next time; use a new angle |101102## Subject Line Guardrails103104Use: specific topic, article title, stat, or resource. Keep under 60 characters.105106Avoid: `Link exchange opportunity`, `SEO partnership`, `I'd love a backlink`, fake `Re:`, all caps, vague "quick question" subjects.107