rampstackco/claude-skills / skills/seo-offpage
seo-offpage
VerifiedPlan and execute off-page SEO including link building, digital PR, brand mentions, citation building, and external authority signals. Use this skill whenever the user wants to build backlinks, plan a digital PR campaign, list local citations, run guest post outreach, develop linkable assets, recover lost links, or audit a backlink profile for risk. Triggers on link building, backlinks, digital PR, brand mentions, citation building, guest post, outreach, linkable asset, broken link building, HARO, podcast outreach, off-page SEO, anchor text, link velocity, toxic backlinks, disavow. Also triggers when the user is trying to grow domain authority or earn coverage.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 352 B |
| SKILL.md | skill md | 7.9 KB |
| references/linkable-assets-guide.md | markdown | 11.4 KB |
| references/outreach-templates.md | markdown | 6.0 KB |
references/outreach-templates.md
View on GitHub# Outreach Templates
Templates for the most common off-page outreach scenarios. Personalize every send. The templates are scaffolding, not ready-to-fire copy.
A few rules across all templates:
- Subject lines under 60 characters
- First line never says "I love your blog" or any variant
- One specific reference to their actual work (not a generic compliment)
- One clear ask
- One reason it benefits them, not you
- Sign with a real name and link to a real profile
- Plain text, no formatting, no images, no tracking pixels
---
## Guest post pitch
**Subject:** [Topic] for [their site name]?
Hi [first name],
I just read your piece on [specific article, published Date] and noticed [specific observation about an angle they did not cover, or a question their piece raised but did not answer].
I write about [your topic area] and I think the gap there could become a strong follow-up. Working title: "[Specific working title]." It would cover:
- [Specific point 1]
- [Specific point 2]
- [Specific point 3]
I can have a draft to you in two weeks. Recent samples of my writing:
- [URL 1]
- [URL 2]
If this is not a fit, no worries. Let me know either way.
Thanks,
[Name]
[Title and where you write]
---
## Expert quote / source pitch
**Subject:** Expert source on [topic] for your [piece type]
Hi [first name],
I saw your request for sources on [topic] via [HARO / Twitter / their site].
Quick credentials: [one sentence on why you're qualified - title, years, specific work]. Happy to provide a quote, full interview, or background on:
- [Specific angle 1]
- [Specific angle 2]
- [Specific angle 3]
Available for a quick reply via email today, or a call this week.
[Name]
[Title]
[Profile / portfolio link]
---
## Broken link outreach
**Subject:** Broken link on your [page topic] page
Hi [first name],
I was reading your [page name] page (great resource) and noticed the link to [specific old URL] is broken - the destination returns a 404.
I run [your site] and we have a piece on the same topic that might be a relevant replacement: [your URL]. It covers [specific overlap with what the broken link was for].
No pressure either way. Just wanted to flag the broken link.
[Name]
---
## Podcast pitch
**Subject:** [Specific topic angle] for [show name]?
Hi [first name],
I have been listening to [show name] for [time period]. The recent episode with [guest name] on [topic] resonated because [specific reason].
I would love to come on and talk about [specific topic angle]. Why this is a fit for your audience:
- [Specific angle 1]
- [Specific angle 2]
- [What I bring that other guests have not covered]
Past appearances:
- [Show name] - [topic] - [link]
- [Show name] - [topic] - [link]
If the topic resonates, I can send a one-page brief with sample questions.
[Name]
[Title]
[Headshot / bio link]
---
## Resource page link request
**Subject:** Resource for your [page topic] roundup
Hi [first name],
Your [page name] page is one of the better roundups I have seen on [topic]. I noticed it includes [example resource they list].
I run [site] and recently published [your URL], which covers [specific angle]. A few reasons it might earn a spot in the list:
- [Differentiator 1: e.g., original data, more detail, recently updated]
- [Differentiator 2]
If it is a fit, I would be grateful for the inclusion. If not, completely understood.
[Name]
---
## Linkable asset announcement
**Subject:** New [asset type] on [topic]
Hi [first name],
We just published [asset type, e.g., "an interactive calculator", "a 50-source benchmark study", "a free template"] on [topic]: [URL].
The reason I am sending it your way: [specific reason this person or publication would care - their audience overlap, a stated interest, a recent piece they wrote].
Three things that make it different from existing resources:
1. [Specific differentiator]
2. [Specific differentiator]
3. [Specific differentiator]
If it is useful for your readers, I would love a mention. Either way, I would value your read of it.
[Name]
---
## Citation / mention reclamation
When your brand is mentioned online but not linked to.
**Subject:** Quick note on the [piece] you published
Hi [first name],
Thanks for mentioning [your brand] in your [piece title, with link]. Genuinely appreciated.
Quick request: would you be open to linking the mention back to [your URL]? Helps your readers find us, and helps us track the reach of the piece.
No worries if it is not your editorial standard to add links retroactively.
Thanks,
[Name]
---
## Partnership pitch (low-key)
**Subject:** [Brand] x [their brand]?
Hi [first name],
I run [your brand]. We share an audience with [their brand] - both serving [audience description].
A few low-effort ways we could collaborate:
1. [Specific idea: e.g., cross-promote in newsletters, swap quotes for content, co-host a webinar]
2. [Specific idea]
3. [Specific idea]
If any resonate, I would love a 20-minute call to figure out the simplest version we could ship in 30 days.
[Name]
[Title]
[Site]
---
## Universal don'ts
- Do not start with "Hope you are doing well."
- Do not call yourself a "fellow [profession]" unless you actually know them.
- Do not say "I'll keep this brief" and then write 600 words.
- Do not attach files in cold outreach.
- Do not follow up more than twice. Three+ follow-ups damage reputation.
- Do not use subject lines like "Quick question" or "Re: [topic]" if it is not actually a reply.
- Do not include phrases like "value-add," "synergy," or "leverage."
- Do not pitch yourself as the expert in their field. They are.
---
## Personalization checklist
Before sending any outreach:
- [ ] Used their first name correctly (spelled right)
- [ ] Referenced specific recent work of theirs (not from 5 years ago)
- [ ] Stated the ask clearly in the first 3 lines
- [ ] Gave them a reason to say yes that benefits them
- [ ] Plain text, no HTML, no images, no tracking pixel
- [ ] Subject line under 60 characters and not deceptive
- [ ] Signature includes real credentials and a way to verify the sender
If any are missing, do not send.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |