AI Discoverability

Helps documentation sites get discovered and cited by AI systems through directory registration and external authority building.

Load references/directories.md for the current list of llms.txt directories and submission details.

When to Use This Skill

• Registering a new llms.txt in public AI directories (item #25)
• Creating an external authority / backlinks strategy (item #26)
• Improving overall AI discoverability beyond technical optimizations

Item #25 — llms.txt Directory Registration

Prerequisites Check

Before starting registration, verify:

1. llms.txt exists at https://[site-url]/llms.txt — open it in a browser to confirm
2. The file is well-formed (H1, blockquote, H2 sections)
3. The site is publicly accessible (not behind auth)

If llms.txt is missing, stop and note: Item #1 must be completed before #25.

Registration Process

Read references/directories.md for the current directory list. For each directory:

llmstxthub.com

1. Visit https://llmstxthub.com
2. Use WebFetch to get the current submission form or process
3. Gather required info: site URL, llms.txt URL, description, category
4. Provide the user with step-by-step instructions (registration usually requires a human to complete the web form)

llmstxtdirectory.org

1. Visit https://www.llmstxtdirectory.org
2. Use WebFetch to get the current submission process
3. Provide user with the specific form fields needed

thedaviddias/llms-txt-hub (GitHub)

1. The repo is at https://github.com/thedaviddias/llms-txt-hub
2. Submission is a GitHub PR adding the site to the README
3. Provide the user with: the fork URL, what to add, and the PR template

Output for #25

Produce a checklist the user can work through:

## llms.txt Directory Submission Checklist

Your llms.txt is at: https://[site-url]/llms.txt ✓

### Directories to Submit To

- [ ] **llmstxthub.com** — [direct link to submission form]
  - Required: Site URL, description, category

- [ ] **llmstxtdirectory.org** — [direct link to submission form]
  - Required: Site URL, llms.txt URL, one-sentence description

- [ ] **thedaviddias/llms-txt-hub** — Submit a PR
  - Fork: https://github.com/thedaviddias/llms-txt-hub
  - Add to README: `| [Site Name] | [Site URL] | [llms.txt URL] | [Category] |`

Estimated time: 15-30 minutes

Item #26 — External Authority / Backlinks Strategy

Step 1: Research the current landscape

Use WebSearch to understand the current external presence:

Search: "[product name] review" site:g2.com OR site:capterra.com
Search: "[product name] github"
Search: "[product category] comparison blog" 2024 OR 2025
Search: "[product name] integration" OR "[product name] tutorial"

Note what exists and what gaps there are.

Step 2: Identify the target's niche

Based on the project (e.g., WMS/OMS/3PL for ShipEdge), identify:

• The primary software category (e.g., "warehouse management software")
• Key competitor names to appear alongside
• Developer communities where this type of product is discussed
• Industry publications or blogs

Use WebSearch to find:

• "best [category] software" lists (G2, Capterra, GetApp, Software Advice)
• Developer blogs covering this space
• GitHub awesome-lists for the category
• Stack Overflow tags related to the product category

Step 3: Produce the authority-building plan

Create a prioritized action plan:

## External Authority Building Plan for [Project]

### Tier 1 — Quick Wins (1-2 weeks)

**Software Directories (High AI Training Data Coverage)**

1. **G2 Listing** — g2.com/products/[product]/reviews
   - Impact: High — G2 pages are heavily indexed by AI training data
   - Action: Create/complete listing with detailed description, features, use cases
   - Est. time: 2-3 hours

2. **Capterra Listing** — capterra.com
   - Impact: High
   - Action: Submit product listing
   - Est. time: 1-2 hours

3. **[Niche-specific directory]** — [URL]
   - Action: [specific steps]

### Tier 2 — Content & Community (1-2 months)

**Open Source Integration**
- Create a minimal example repo: `github.com/[org]/[product]-examples`
- Shows real API usage
- Gets indexed by GitHub search + AI training data
- Action: Build a simple "Hello World" integration in the most popular platform (e.g., Shopify)

**Developer Blog Post**
- Target publications: [research and list 2-3 relevant blogs]
- Topic idea: "[How we solved X] with [product]" — a technical case study
- Impact: Developer blogs are heavily weighted in AI training data

**Stack Overflow Presence**
- Tag to watch: [relevant tag]
- Action: Answer 5-10 questions where the product is relevant
- Adds authoritative mentions in a heavily-indexed source

### Tier 3 — Long Term (3-6 months)

**Community Building**
- [Discord/Slack community if not existing]
- [Newsletter targeting developers in the space]

**Partnership Content**
- Guest posts on [integration partner] blogs
- Co-marketing with [complementary tools]

### Metrics to Track
- G2 rating and review count
- GitHub stars on example repos
- Mentions in "best [category]" lists when asked to AI tools
- Direct: ask ChatGPT/Perplexity "What is [product]?" and note what it says

Step 4: Set up tracking

Recommend a simple way to track AI mentions:

• Set up a Google Alert for the product name
• Periodically ask ChatGPT, Perplexity, and Claude: "What is [product]? Who should use it?"
• Track whether mentions become more accurate and common over time

Output Format

Present results clearly split into two sections:

1. #25 Submission Checklist — actionable steps the user can complete right now
2. #26 Authority-Building Plan — prioritized strategy with time estimates

Note: most of #26 requires the user to take action (write content, create accounts, etc.) — your role is to research and plan, not execute the outreach directly.