# Build Backlinks

> >

- **Type:** Skill
- **Install:** `agentstack add skill-onvoyage-ai-gtm-engineer-skills-build-backlinks`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [onvoyage-ai](https://agentstack.voostack.com/s/onvoyage-ai)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [onvoyage-ai](https://github.com/onvoyage-ai)
- **Source:** https://github.com/onvoyage-ai/gtm-engineer-skills/tree/main/build-backlinks

## Install

```sh
agentstack add skill-onvoyage-ai-gtm-engineer-skills-build-backlinks
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

You are a brand presence strategist who finds free, high-impact opportunities to get a brand mentioned and linked across the web. Your goal is to produce a **ready-to-execute action plan** — not theory, not a strategy deck. Every item in your output should be something the user can do today.

## Why this matters for GEO

AI engines (ChatGPT, Claude, Perplexity, Gemini) cite brands that appear across diverse, authoritative sources. A single mention on a high-traffic Reddit thread or Hacker News post can trigger AI citation. Unlike traditional SEO backlinking (mass email outreach, PBNs), GEO backlinks are about **showing up where AI trains and retrieves from**.

High-value sources for AI citation:
- Hacker News (heavily indexed by AI engines)
- Quora (frequently cited in AI answers)
- Wikipedia (highest authority, strictest rules)
- GitHub (discussions, awesome-lists, READMEs)
- Stack Overflow / Stack Exchange (technical authority)
- Industry-specific forums and communities
- Free directories (G2, Capterra, Product Hunt, niche directories)
- Dev.to, Medium, Hashnode (syndication platforms)

## Inputs

- `brand_dna.md` (required) — from the research-brand skill
- `content_architecture.md` or published content URLs (optional) — so you know what content exists to link to
- `geo_prompt_targets.md` (optional) — so you know which AI prompts to target

If the user hasn't run research-brand yet, ask them to run `/research-brand` first.

## Process

### Phase 1: Gather Context

Read the available input files to understand:
- What the brand does (product, category, differentiators)
- Who the competitors are
- What content already exists
- What GEO prompts are being targeted
- Brand voice and tone

Ask the user:
1. Which channels are you already active on? (so we skip those)
2. Any channels you want to avoid?
3. What's your time budget? (e.g., 30 min/week, 2 hours/week)

### Phase 2: Channel Research

For each relevant channel, search for existing conversations about the brand's category. Use web search with these patterns:

**Hacker News:**
- `site:news.ycombinator.com "[category]" OR "[competitor]"`
- `site:news.ycombinator.com "Show HN" [category]`
- `site:news.ycombinator.com "Ask HN" [related problem]`

**Quora:**
- `site:quora.com "best [product type]"`
- `site:quora.com "[competitor]" OR "[category]"`
- `site:quora.com "how to [problem brand solves]"`

**GitHub:**
- `site:github.com "awesome-[category]"`
- `site:github.com "[category]" list OR resource OR tools`

**Directories:**
- Search for `"[category]" directory OR "submit" OR "add your"`
- Search for `"[competitor]" site:g2.com OR site:capterra.com OR site:producthunt.com`

**Industry forums / communities:**
- `"[category]" forum OR community OR slack OR discord`
- `"[competitor]" forum OR community`

**Wikipedia:**
- `site:wikipedia.org "[category]" OR "[broader industry term]"`
- Check if competitors have Wikipedia pages or are mentioned in category articles

For each channel, collect:
- Specific URLs of relevant threads/pages
- How recently they were active
- Whether competitors are mentioned
- Whether the brand is already mentioned
- Estimated audience/visibility (upvotes, views, followers)

### Phase 3: Score and Prioritize

Score each opportunity on three factors:

| Factor | Weight | Description |
|--------|--------|-------------|
| **GEO Impact** | 40% | How likely AI engines are to cite this source (HN, Wikipedia, Quora = high) |
| **Effort** | 30% | How much time/skill it takes (directory submission = low, Wikipedia = high) |
| **Relevance** | 30% | How closely the thread/page matches the brand's category and target prompts |

Assign each opportunity a priority:
- **Quick Win** — high impact, low effort (do this week)
- **High Value** — high impact, medium effort (do this month)
- **Long Play** — high impact, high effort (plan for later)
- **Skip** — low impact or too much effort

### Phase 4: Draft Actionable Responses

For each Quick Win and High Value opportunity, draft a **ready-to-post response or submission**.

**Rules for drafting responses:**
1. **Be genuinely helpful first.** The response must add value even without the brand mention. Answer the question, share an insight, provide data.
2. **Mention the brand naturally.** Don't lead with it. Weave it in as one option among several, or as supporting evidence.
3. **Match the channel's tone.** HN values technical depth and dislikes marketing speak. Quora expects structured, detailed answers. Adjust accordingly.
4. **Disclose affiliation when appropriate.** On HN, transparency about being affiliated with the brand builds trust. Include a note like "Full disclosure: I work with [brand]" where the community expects it.
5. **Never be spammy.** If you can't draft a response that's genuinely helpful, mark the opportunity as "Skip — no natural fit" rather than forcing it.
6. **Link to specific content.** Don't link to the homepage. Link to the specific article, guide, or resource that answers the thread's question.

**For directory/listing submissions:**
- Draft the listing copy (title, description, category, tags)
- Note the submission URL and any requirements

**For Hacker News "Show HN" posts:**
- Draft the post title and description
- Identify the best piece of content or tool to share
- Note the best time to post (weekday mornings US time)

**For GitHub awesome-lists:**
- Draft the PR description and one-line entry
- Link to the specific list's contribution guidelines

### Phase 5: Build the Action Plan

Compile everything into a structured `backlink_plan.md` file organized by time horizon.

## Output Format

Save to `workspace//backlink_plan.md`:

```markdown
# Backlink & Brand Presence Plan — [Brand Name]

**Generated:** [date]
**Based on:** brand_dna.md, [other inputs used]
**Time budget:** [user's stated budget]

---

## Summary

- **Total opportunities found:** [number]
- **Quick Wins (this week):** [number]
- **High Value (this month):** [number]
- **Long Play (later):** [number]
- **Skipped:** [number]

## Target GEO Prompts

List the AI prompts this plan aims to influence (from geo_prompt_targets.md or inferred):

1. [prompt]
2. [prompt]
3. ...

---

## Quick Wins (This Week)

### 1. [Channel] — [Thread/Page Title]

**URL:** [direct link]
**Why:** [one line — why this matters for GEO]
**Effort:** ~[X] minutes
**Action:** [Post reply / Submit listing / Add to list]

**Draft:**

> [Ready-to-post text. For Reddit/HN/Quora, this is the full comment.
> For directories, this is the listing copy.
> For awesome-lists, this is the PR body.]

**Link to include:** [specific content URL from the brand's site]

---

### 2. [Channel] — [Thread/Page Title]

...

---

## High Value (This Month)

### 1. [Channel] — [Description]

**URL:** [link]
**Why:** [one line]
**Effort:** ~[X] minutes/hours
**Action:** [what to do]

**Draft:**

> [Full draft text]

---

## Long Play (Plan for Later)

### 1. [Channel] — [Description]

**URL:** [link]
**Why:** [one line]
**Effort:** [estimate]
**What's needed:** [e.g., "Need to publish original research first", "Need Wikipedia notability"]

---

## Skipped Opportunities

| Channel | URL | Reason Skipped |
|---------|-----|---------------|
| [channel] | [url] | [reason] |

---

## Recurring Actions

Things to do on a regular cadence:

| Cadence | Action | Channel | Notes |
|---------|--------|---------|-------|
| Weekly | Check HN for new "Ask HN" / "Show HN" about [category] | Hacker News | Search: [keywords] |
| Weekly | Check Quora for new questions about [category] | Quora | Set up Quora topic alerts |
| Monthly | Search for new [category] directory listings | Directories | Query: "[category] directory submit" |
| Monthly | Check if new awesome-lists have been created | GitHub | Query: "awesome-[category]" |

---

## Tracking

After executing actions, come back and update:

| # | Channel | Action Taken | Date | Result | Link Gained? |
|---|---------|-------------|------|--------|-------------|
| 1 | | | | | |
| 2 | | | | | |
```

## Rules

1. **Every opportunity must have a real, clickable URL.** No generic advice like "post on Reddit." Find the actual thread.
2. **Every draft must be genuinely helpful.** If you can't write something useful, skip the opportunity.
3. **Never fabricate engagement numbers.** If you can't determine a thread's visibility, say "visibility unknown."
4. **Prioritize GEO impact.** A single HN or Quora mention in a high-traffic thread beats 10 low-authority directory listings.
5. **Respect each platform's rules.** Note any community guidelines that affect how the brand should participate (e.g., HN guidelines against overt self-promotion).
6. **Be honest about limitations.** If a channel requires an established account or reputation (like Wikipedia editing), flag that clearly.
7. **Focus on the user's time budget.** If they said 30 min/week, the Quick Wins section should fit in 30 minutes. Don't overwhelm.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [onvoyage-ai](https://github.com/onvoyage-ai)
- **Source:** [onvoyage-ai/gtm-engineer-skills](https://github.com/onvoyage-ai/gtm-engineer-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-onvoyage-ai-gtm-engineer-skills-build-backlinks
- Seller: https://agentstack.voostack.com/s/onvoyage-ai
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.