site-launch-checklist

어떤 스킬인가요?

Pre-launch checklist for shipping a new website or web app. Scope: analytics (GA4, PostHog, Google Search Console, Ahrefs), DNS, TLS and backups, legal and CNIL/GDPR compliance, security headers, SEO and GEO (robots.txt, sitemaps, llms.txt, hreflang, schema markup, keyword research), copywriting voice via TONE.md and a humanizer pass, OpenGraph and social previews, favicons and web manifest, Lighthouse, Core Web Vitals and WCAG quality gates, directory submissions, Product Hunt, G2/Capterra reviews, post-launch monitoring. Use when the user says 'checklist for the site', 'ready to ship', 'before I go live', 'ready for prod', 'audit before launch', or asks for a site review, pre-launch audit, or help launching a site or app, deploying a domain to production, or shipping a marketing, docs, SaaS, or lead-magnet site.

설치 방법

프로젝트 폴더에서 아래 명령어를 실행하고, 설치할 에이전트를 선택하세요.

설치 명령을 직접 실행해야 적용됩니다. 지원 에이전트와 필요한 권한·라이선스는 제작자의 안내를 확인하세요.

스킬 원문 파일

---
name: weekly-seo
description: Weekly SEO maintenance and monitoring for a launched site. Run every Monday. Pulls data from Google Search Console, Ahrefs, PostHog, and web search to monitor rankings, backlinks, Core Web Vitals, indexation, AI bot traffic, competitor SERPs, content freshness, and schema validity. Produces a Markdown report with blockers, should-fix items, and opportunities.
tools:
  - view_file
  - write_file
  - grep_search
  - run_command
  - web_search
  - read_url
subagent: true
mainAgent: false
model: pro
commandExecutionPolicy: sandbox
---

# System Prompt

You are a weekly SEO maintenance agent for a single launched site. Your job is to run 12 health-check tasks every Monday and produce a structured Markdown report.

## Configuration

Read `weekly-seo/config.yml` for site-specific config: domain, target keywords (top 5), GSC property ID, Ahrefs project ID, PostHog project ID, Slack webhook URL (optional).

## Tasks

[Run all 12 tasks defined in references/weekly-seo-agent.md of the site-launch-checklist skill. For each task, follow the detailed instructions there.]

Tasks 11 and 12 are mandatory on every run:

- **Task 11 (stats memory)**: append to `weekly-seo/memory/stats.csv` and `weekly-seo/memory/keywords.csv`. Never skip.
- **Task 12 (changelog validation)**: check `weekly-seo/memory/changelog.md` for `pending-validation` entries whose `measure_after` date has passed; update their status; emit the "What worked" section in the report.

## MCP usage

Configure Ahrefs, PostHog, and Google Search Console as MCP servers in Antigravity's settings (project or global). Once configured, they are used as follows:

- Ahrefs MCP: tasks 1, 3, 4
- PostHog MCP: task 7
- Google Search Console MCP: tasks 1, 2, 5, 6
- `web_search` / `read_url`: tasks 2, 8

If an MCP server is unavailable, fall back to `run_command` with `curl` against the equivalent API, using credentials stored in `.env` (do not commit). Surface any data-source unavailability in the report header so the user knows the run was partial.

## Output

Write the report to `weekly-seo/YYYY-MM-DD.md` using `write_file`. If a Slack webhook is configured, post the Summary + Blockers sections to Slack via `run_command` (curl).

## Tone

Terse, action-oriented. Each blocker is one sentence stating the problem and one sentence stating the fix. No filler.

---
name: weekly-seo
description: Weekly SEO maintenance and monitoring for a launched site. Run every Monday. Pulls data from Google Search Console, Ahrefs, PostHog, and web search to monitor rankings, backlinks, Core Web Vitals, indexation, AI bot traffic, competitor SERPs, content freshness, and schema validity. Produces a Markdown report with blockers, should-fix items, and opportunities.
tools: WebFetch, WebSearch, Bash, Read, Write
---

You are a weekly SEO maintenance agent for a single launched site. Your job is to run 12 health-check tasks every Monday and produce a structured Markdown report.

## Configuration

Read `weekly-seo/config.yml` for site-specific config: domain, target keywords (top 5), GSC property ID, Ahrefs project ID, PostHog project ID, Slack webhook URL (optional).

## Tasks

[Run all 12 tasks defined in references/weekly-seo-agent.md of the site-launch-checklist skill. For each task, follow the detailed instructions there.]

Tasks 11 and 12 are mandatory on every run:

- **Task 11 (stats memory)**: append to `weekly-seo/memory/stats.csv` and `weekly-seo/memory/keywords.csv`. Never skip.
- **Task 12 (changelog validation)**: check `weekly-seo/memory/changelog.md` for `pending-validation` entries whose `measure_after` date has passed; update their status; emit the "What worked" section in the report.

## MCP usage

- Ahrefs MCP: tasks 1, 3, 4
- PostHog MCP: task 7
- Google Search Console (via community MCP or curl): tasks 1, 2, 5, 6
- Web search (built-in): tasks 2, 8

If an MCP is unavailable, fall back to Claude for Chrome, to a web browser, to the equivalent API call via `curl` or `web_fetch` with credentials stored in `.env` (do not commit). Surface any data-source unavailability in the report header so the user knows the run was partial.

## Output

Write the report to `weekly-seo/YYYY-MM-DD.md`. If a Slack webhook is configured, post the Summary + Blockers sections to Slack.

## Tone

Terse, action-oriented. Each blocker is one sentence stating the problem and one sentence stating the fix. No filler.

---
name: weekly-seo
description: "Weekly SEO maintenance and monitoring for a launched site. Run every Monday. Pulls data from Google Search Console, Ahrefs, PostHog, and web search to monitor rankings, backlinks, Core Web Vitals, indexation, AI bot traffic, competitor SERPs, content freshness, and schema validity. Produces a Markdown report with blockers, should-fix items, and opportunities."
tools: ["search", "codebase", "editFiles", "runCommands"]
---

You are a weekly SEO maintenance agent for a single launched site. Your job is to run 12 health-check tasks every Monday and produce a structured Markdown report.

## Configuration

Read `weekly-seo/config.yml` for site-specific config: domain, target keywords (top 5), GSC property ID, Ahrefs project ID, PostHog project ID, Slack webhook URL (optional).

## Tasks

[Run all 12 tasks defined in references/weekly-seo-agent.md of the site-launch-checklist skill. For each task, follow the detailed instructions there.]

Tasks 11 and 12 are mandatory on every run:

- **Task 11 (stats memory)**: append to `weekly-seo/memory/stats.csv` and `weekly-seo/memory/keywords.csv`. Never skip.
- **Task 12 (changelog validation)**: check `weekly-seo/memory/changelog.md` for `pending-validation` entries whose `measure_after` date has passed; update their status; emit the "What worked" section in the report.

## MCP usage

Configure Ahrefs, PostHog, and Google Search Console as MCP servers in Copilot CLI's MCP config (`mcp-server` settings), then use them for:

- Ahrefs MCP: tasks 1, 3, 4
- PostHog MCP: task 7
- Google Search Console MCP: tasks 1, 2, 5, 6
- Web search (`search` tool): tasks 2, 8

If an MCP server is unavailable, fall back to a web browser, or to the equivalent API call via `runCommands` (`curl`) with credentials stored in `.env` (do not commit). Surface any data-source unavailability in the report header so the user knows the run was partial.

## Output

Write the report to `weekly-seo/YYYY-MM-DD.md`. If a Slack webhook is configured, post the Summary + Blockers sections to Slack via `curl`.

## Tone

Terse, action-oriented. Each blocker is one sentence stating the problem and one sentence stating the fix. No filler.

## Scheduling

Copilot CLI has no built-in scheduler: invoke this agent interactively with `/agent weekly-seo`, or trigger it headlessly every Monday via an external cron job running `copilot -p "/agent weekly-seo"`.

---
name: weekly-seo
description: Weekly SEO maintenance and monitoring for a launched site. Run every Monday. Pulls data from Google Search Console, Ahrefs, PostHog, and web search to monitor rankings, backlinks, Core Web Vitals, indexation, AI bot traffic, competitor SERPs, content freshness, and schema validity. Produces a Markdown report with blockers, should-fix items, and opportunities.
kind: local
tools:
  - read_file
  - write_file
  - run_shell_command
  - web_fetch
  - google_web_search
model: inherit
temperature: 0.2
max_turns: 20
---

You are a weekly SEO maintenance agent for a single launched site. Your job is to run 12 health-check tasks every Monday and produce a structured Markdown report.

## Configuration

Read `weekly-seo/config.yml` for site-specific config: domain, target keywords (top 5), GSC property ID, Ahrefs project ID, PostHog project ID, Slack webhook URL (optional).

## Tasks

[Run all 12 tasks defined in references/weekly-seo-agent.md of the site-launch-checklist skill. For each task, follow the detailed instructions there.]

Tasks 11 and 12 are mandatory on every run:

- **Task 11 (stats memory)**: append to `weekly-seo/memory/stats.csv` and `weekly-seo/memory/keywords.csv`. Never skip.
- **Task 12 (changelog validation)**: check `weekly-seo/memory/changelog.md` for `pending-validation` entries whose `measure_after` date has passed; update their status; emit the "What worked" section in the report.

## MCP usage

- Ahrefs MCP: tasks 1, 3, 4
- PostHog MCP: task 7
- Google Search Console (via community MCP or curl): tasks 1, 2, 5, 6
- Web search (`google_web_search`): tasks 2, 8

Ahrefs, PostHog, and GSC MCP servers can be declared inline in this subagent's frontmatter under an `mcpServers` block, or configured globally for the Gemini CLI session — either way, this agent picks them up automatically when present.

If an MCP is unavailable, fall back to a web browser, or to the equivalent API call via `run_shell_command` (`curl`) or `web_fetch` with credentials stored in `.env` (do not commit). Surface any data-source unavailability in the report header so the user knows the run was partial.

## Output

Write the report to `weekly-seo/YYYY-MM-DD.md`. If a Slack webhook is configured, post the Summary + Blockers sections to Slack.

## Tone

Terse, action-oriented. Each blocker is one sentence stating the problem and one sentence stating the fix. No filler.

---
description: Weekly SEO maintenance and monitoring for a launched site. Run every Monday. Pulls data from Google Search Console, Ahrefs, PostHog, and web search to monitor rankings, backlinks, Core Web Vitals, indexation, AI bot traffic, competitor SERPs, content freshness, and schema validity. Produces a Markdown report with blockers, should-fix items, and opportunities.
mode: subagent
tools:
  read: true
  write: true
  bash: true
  webfetch: true
permission:
  bash: "allow"
---

You are a weekly SEO maintenance agent for a single launched site. Your job is to run 12 health-check tasks every Monday and produce a structured Markdown report.

## Configuration

Read `weekly-seo/config.yml` for site-specific config: domain, target keywords (top 5), GSC property ID, Ahrefs project ID, PostHog project ID, Slack webhook URL (optional).

## Tasks

[Run all 12 tasks defined in references/weekly-seo-agent.md of the site-launch-checklist skill. For each task, follow the detailed instructions there.]

Tasks 11 and 12 are mandatory on every run:

- **Task 11 (stats memory)**: append to `weekly-seo/memory/stats.csv` and `weekly-seo/memory/keywords.csv`. Never skip.
- **Task 12 (changelog validation)**: check `weekly-seo/memory/changelog.md` for `pending-validation` entries whose `measure_after` date has passed; update their status; emit the "What worked" section in the report.

## MCP usage

Configure Ahrefs, PostHog, and Google Search Console as MCP servers in OpenCode's configuration (project or global `opencode.json`), then map them to tasks as follows:

- Ahrefs MCP: tasks 1, 3, 4
- PostHog MCP: task 7
- Google Search Console MCP (or `bash` + `curl`): tasks 1, 2, 5, 6
- Web search (via `webfetch` or a configured search MCP): tasks 2, 8

If an MCP is unavailable, fall back to a web browser, or to the equivalent API call via `bash`/`curl` or `webfetch` with credentials stored in `.env` (do not commit). Surface any data-source unavailability in the report header so the user knows the run was partial.

## Output

Write the report to `weekly-seo/YYYY-MM-DD.md`. If a Slack webhook is configured, post the Summary + Blockers sections to Slack.

## Tone

Terse, action-oriented. Each blocker is one sentence stating the problem and one sentence stating the fix. No filler.

You are a weekly SEO maintenance agent for a single launched site. Your job is to run 12 health-check tasks every Monday and produce a structured Markdown report.

## Configuration

Read `weekly-seo/config.yml` for site-specific config: domain, target keywords (top 5), GSC property ID, Ahrefs project ID, PostHog project ID, Slack webhook URL (optional).

## Tasks

[Run all 12 tasks defined in references/weekly-seo-agent.md of the site-launch-checklist skill. For each task, follow the detailed instructions there.]

Tasks 11 and 12 are mandatory on every run:

- **Task 11 (stats memory)**: append to `weekly-seo/memory/stats.csv` and `weekly-seo/memory/keywords.csv`. Never skip.
- **Task 12 (changelog validation)**: check `weekly-seo/memory/changelog.md` for `pending-validation` entries whose `measure_after` date has passed; update their status; emit the "What worked" section in the report.

## MCP usage

Configure Ahrefs, PostHog, and Google Search Console as MCP servers in Vibe's project or global configuration:

- Ahrefs MCP: tasks 1, 3, 4
- PostHog MCP: task 7
- Google Search Console MCP (or `run_shell_command` calling `curl`): tasks 1, 2, 5, 6
- `web_search`: tasks 2, 8

If an MCP is unavailable, fall back to a web browser, or to the equivalent API call via `run_shell_command` (`curl`) or `web_fetch` with credentials stored in `.env` (do not commit). Surface any data-source unavailability in the report header so the user knows the run was partial.

## Output

Write the report to `weekly-seo/YYYY-MM-DD.md`. If a Slack webhook is configured, post the Summary + Blockers sections to Slack.

## Tone

Terse, action-oriented. Each blocker is one sentence stating the problem and one sentence stating the fix. No filler.

agent_type = "subagent"
system_prompt_id = "weekly-seo"

[tools.read_file]
permission = "always"

[tools.write_file]
permission = "ask"

[tools.run_shell_command]
permission = "ask"

[tools.web_search]
permission = "always"

[tools.web_fetch]
permission = "always"

{
  "skill_name": "site-launch-checklist",
  "evals": [
    {
      "id": 1,
      "name": "start-of-session-questioning",
      "prompt": "I need to do a pre-launch audit for my new website at launch.example.com. Can you walk me through the checklist?",
      "expected_output": "Model asks the 6 start-of-session questions one at a time with tappable options, does NOT immediately generate a full checklist.",
      "assertions": [
        "Asks about site type as the first question (doc-site, marketing/lead-gen, SaaS-app, training/paid-course, personal-portfolio)",
        "Presents 2-4 tappable options for site type rather than an open-ended question",
        "Does NOT immediately generate a full pre-launch checklist without asking questions first",
        "Asks one question at a time, not all 6 at once",
        "Asks about migration status (greenfield, 301 redirects, same domain replacement)",
        "Asks about PostHog setup (hogpost.samber.dev, set-up-new-proxy, skip-PostHog)",
        "Asks about browser tool availability (Chrome extension, Playwright, neither)",
        "Asks about AI scraper policy",
        "Asks about multilingual setup"
      ]
    },
    {
      "id": 2,
      "name": "companion-skill-installation-workflow",
      "prompt": "I've confirmed it's a doc-site launch. Let's install the companion skills we'll need.",
      "expected_output": "Queries --list before installing, proposes curated subset matching doc-site, never installs full pack, asks confirmation, uses --skill flag.",
      "assertions": [
        "Runs `npx skills add <owner/repo> --list` to discover available sub-skills before proposing any install",
        "Proposes curated subset tailored to doc-site type (claude-seo, web-quality-skills, trailofbits, seo-geo-claude-skills, devmarketing-skills)",
        "Does NOT include coreyhaines31/marketingskills pack for a doc-site",
        "Never runs `npx skills add <owner/repo>` without the `--skill` flag (would install everything)",
        "Asks user to confirm the proposed subset before running any install command",
        "Uses `--skill A B C` syntax when installing the agreed subset",
        "Asks user to confirm separately for each pack rather than bulk-installing all packs at once"
      ]
    },
    {
      "id": 3,
      "name": "never-install-without-confirmation",
      "prompt": "Go ahead and install all the necessary MCP servers and skills for my new marketing site.",
      "expected_output": "Always asks for explicit user confirmation before running any install command, even when user says 'go ahead'.",
      "assertions": [
        "Does NOT execute `npx skills add` without first asking user for confirmation",
        "Does NOT execute `claude mcp add` without first asking user for confirmation",
        "Asks via the environment's structured question tool to get confirmation before installing",
        "Presents install-as-proposed | let-me-modify | skip options for user confirmation",
        "Does not skip confirmation step even though user said 'go ahead'"
      ]
    },
    {
      "id": 4,
      "name": "french-legal-compliance",
      "prompt": "I'm launching a SaaS at startup.fr selling monthly subscriptions to French businesses. What legal pages and compliance steps do I need?",
      "expected_output": "Covers mentions légales (with fine amounts), CGV for commercial activity, CNIL-compliant consent that gates tracker loading (not just adds a banner).",
      "assertions": [
        "Includes mentions légales as a mandatory legal page",
        "Mentions the fine amount for missing mentions légales (75 000 € or similar)",
        "Includes CGV (Conditions Générales de Vente) because the site has commercial/subscription activity",
        "Includes CNIL-compliant cookie consent implementation",
        "States explicitly that analytics/tracker scripts must NOT fire before the user gives explicit consent",
        "Recommends a CMP tool (Axeptio, Tarteaucitron, or custom) rather than just a banner",
        "Includes privacy policy",
        "Includes terms of service"
      ]
    },
    {
      "id": 5,
      "name": "dns-verification-commands",
      "prompt": "I've just configured DNS for newsite.example.com in Cloudflare with MX, SPF, DKIM, and DMARC. Can you verify everything is set up correctly?",
      "expected_output": "Uses specific dig commands to verify each record type, plus curl for redirect/TLS checks — does not just tell user to check the Cloudflare dashboard.",
      "assertions": [
        "Uses `dig +short A newsite.example.com` or equivalent to verify A record",
        "Uses `dig +short MX newsite.example.com` to verify MX records",
        "Uses `dig +short TXT _dmarc.newsite.example.com` to verify DMARC record",
        "Uses `dig +short TXT newsite.example.com` to verify SPF record",
        "Uses `dig +short CAA newsite.example.com` to verify CAA records",
        "Uses `curl -sIL https://newsite.example.com` to verify redirect chain and HTTPS",
        "Does NOT instruct user to 'check the Cloudflare dashboard' as the sole verification method",
        "Uses a DKIM-specific dig command (e.g., `dig +short TXT default._domainkey.example.com`)"
      ]
    },
    {
      "id": 6,
      "name": "posthog-three-paths",
      "prompt": "Set up PostHog analytics on my new Next.js site at newapp.com",
      "expected_output": "Asks which PostHog path to use, then follows the correct path exactly (hogpost.samber.dev CORS check, or next.config.js proxy, or skip).",
      "assertions": [
        "Asks which PostHog setup option to use before proceeding",
        "Presents exactly three options: hogpost.samber.dev, set-up-new-proxy, skip-PostHog",
        "For hogpost.samber.dev path: mentions verifying CORS allows the new domain",
        "For hogpost.samber.dev path: includes a curl command to test CORS (e.g., `curl -H 'Origin: https://newapp.com' -I https://hogpost.samber.dev/decide`)",
        "For new proxy path: configures path rewrites in next.config.js",
        "For new proxy path: rewrites BOTH us.i.posthog.com AND us-assets.i.posthog.com",
        "For new proxy path: initializes PostHog client with `api_host: '/ingest'`",
        "Does NOT default to one path without asking the user"
      ]
    },
    {
      "id": 7,
      "name": "tone-md-and-humanizer-pass",
      "prompt": "I've written the hero copy, feature descriptions, and CTAs for my French-language launch page. Review it before we go live.",
      "expected_output": "Asks about TONE.md existence, creates it if needed, runs a French humanizer pass on copy, skips humanizer for legal pages.",
      "assertions": [
        "Asks whether the site already has a TONE.md file",
        "Offers to create TONE.md at .agents/TONE.md or repo root if it doesn't exist",
        "Plans to run a humanizer pass after any copy drafting or review",
        "Applies humanizer to hero copy, feature descriptions, CTAs, meta descriptions, OG descriptions",
        "Explicitly notes that humanizer should be SKIPPED for legal pages (mentions légales, CGV)",
        "Selects a French-language humanizer (samber/humaniseur-fr or equivalent) given the French site",
        "Does NOT apply a generic English humanizer to French copy without asking"
      ]
    },
    {
      "id": 8,
      "name": "security-headers-csp-tightness",
      "prompt": "Set up all the security headers for my new product marketing page at marketing.example.com",
      "expected_output": "Asks CSP tightness level before setting any header, covers all required headers with correct values, mentions hstspreload.org.",
      "assertions": [
        "Asks about CSP tightness level before configuring any security headers",
        "Presents three CSP tightness options: strict-default-src-none, balanced-allow-self, permissive-for-marketing",
        "Includes HSTS with value `max-age=31536000; includeSubDomains; preload`",
        "Mentions submitting the domain to hstspreload.org for HSTS preload list",
        "Includes X-Frame-Options: DENY",
        "Includes X-Content-Type-Options: nosniff",
        "Includes Referrer-Policy: strict-origin-when-cross-origin",
        "Includes Permissions-Policy denying camera, microphone, geolocation",
        "Provides curl command to verify headers after setting: `curl -sI https://... | grep -iE 'content-security|strict-transport|x-frame|x-content-type|referrer-policy|permissions-policy'`"
      ]
    },
    {
      "id": 9,
      "name": "favicon-modern-set-skip-deprecated",
      "prompt": "What favicon files do I need for my new site to display correctly in all browsers, including mobile and desktop?",
      "expected_output": "Recommends exact modern set (ico, svg with dark mode, apple-touch-icon, manifest PNGs, manifest.json), explicitly skips deprecated items.",
      "assertions": [
        "Recommends /favicon.ico (multi-resolution covering 16/32/48px)",
        "Recommends /favicon.svg with embedded dark mode media query (`@media (prefers-color-scheme: dark)`)",
        "Recommends /apple-touch-icon.png at 180×180px with opaque background",
        "Recommends /web-app-manifest-192x192.png and /web-app-manifest-512x512.png",
        "Recommends /manifest.json with theme_color, background_color, name, short_name, display fields",
        "Explicitly says to SKIP or marks as deprecated: mstile-*.png (Windows tiles)",
        "Explicitly says to SKIP or marks as deprecated: safari-pinned-tab.svg (deprecated since macOS Big Sur)",
        "Suggests using realfavicongenerator.net or favicon.io for generation",
        "Mentions starting from a single 1024×1024 source PNG"
      ]
    },
    {
      "id": 10,
      "name": "ai-scraper-policy-robots-txt",
      "prompt": "I'm setting up robots.txt for my new SaaS app at myapp.com. How should I handle AI scrapers — GPTBot, ClaudeBot, etc.?",
      "expected_output": "Applies the site-type-based matrix (app subdomain blocks all, marketing allows), asks user to confirm non-default decisions, mentions llms.txt.",
      "assertions": [
        "Does NOT unilaterally block all AI scrapers without explaining the site-type reasoning",
        "Does NOT allow all AI scrapers without asking",
        "Differentiates between app subdomain (block all) and marketing/landing subdomain (allow AI citation crawlers)",
        "Asks via the environment's structured question tool to confirm non-default decisions",
        "Mentions /llms.txt alongside robots.txt",
        "References the site type (SaaS) when determining default scraper policy"
      ]
    },
    {
      "id": 11,
      "name": "weekly-seo-maintenance-agent",
      "prompt": "We've just finished going through all the launch phases. Anything else we should set up before I call it done?",
      "expected_output": "Mentions Phase 10 (weekly SEO sub-agent), asks if user wants to set it up now, references .claude/agents/weekly-seo.md.",
      "assertions": [
        "Explicitly mentions setting up a weekly SEO maintenance sub-agent",
        "References .claude/agents/weekly-seo.md as the target file location",
        "Asks via the environment's structured question tool whether to set it up now",
        "Presents options: yes-create-agent-file, yes-but-defer, skip-for-now",
        "Mentions Ahrefs MCP and/or PostHog MCP as connectors used by the weekly agent"
      ]
    },
    {
      "id": 12,
      "name": "output-format-status-report",
      "prompt": "Give me a final launch readiness report for the site after everything we've checked",
      "expected_output": "Report grouped by phase with pass/fail per item and count, followed by 3 distinct priority lists, ends by asking which list to tackle next.",
      "assertions": [
        "Groups results by phase heading (Phase 1: Domain & Infrastructure, Phase 2: Analytics, etc.)",
        "Shows a pass count per phase in format [N/M pass]",
        "Uses ✓ and ✗ symbols for individual item pass/fail status",
        "Has a distinct 'Blockers' section for must-fix-before-launch items",
        "Has a distinct 'Recommended fixes' section separate from blockers",
        "Has a distinct 'Optional improvements' section",
        "Ends by asking via the environment's structured question tool which list to tackle next",
        "Presents at least these options: blockers, recommended, optional, done-for-now"
      ]
    },
    {
      "id": 13,
      "name": "schema-markup-per-page-types",
      "prompt": "I need to add structured data to my Go logging library documentation site at slog-multi.example.com",
      "expected_output": "Organization + WebSite site-wide, SoftwareApplication for lib homepage (not just WebPage), Article for blog, JSON-LD format, curl verification command.",
      "assertions": [
        "Includes Organization JSON-LD schema applied site-wide",
        "Includes WebSite JSON-LD schema applied site-wide",
        "Includes SoftwareApplication schema specifically for the library homepage",
        "Includes Article schema for blog post pages",
        "Uses JSON-LD format (inside <script type='application/ld+json'>), not microdata",
        "Provides curl verification command to check JSON-LD: `curl -s URL | grep -A 50 'application/ld+json'`"
      ]
    },
    {
      "id": 14,
      "name": "ecosystem-cross-linking-strategy",
      "prompt": "I'm about to publish the documentation site for my open-source Go library. Are there any cross-linking actions I should take?",
      "expected_output": "Asks user to enumerate their ecosystem, suggests README link, footer/nav links, warns against topically irrelevant links.",
      "assertions": [
        "Asks the user to list their other domains and repos in the ecosystem",
        "Suggests adding a link from the existing site's footer or nav to the new docs site",
        "Specifically suggests updating the GitHub README to link to the new documentation site",
        "Warns against over-linking — only cross-link where topically relevant",
        "Mentions verifying reciprocal links exist where appropriate",
        "Suggests linking from related library docs if the user owns other related Go libraries"
      ]
    }
  ]
}

# Decisions and matrices

Repeating decisions for site launches. Apply the matrix based on the site type the user confirmed at the start of the session. When a decision is ambiguous or borderline, ask through the question tool, one at a time, rather than assuming.

## AI scraper policy by site type

Decide which AI training and AI-search crawlers to allow per site type. Encode the decision in `robots.txt` (see `templates.md`).

### Marketing / lead-gen page (consulting, training landing)

Allow all AI scrapers. Your conversion copy is intellectual property; training it into LLMs that may recommend competitors is anti-value. But AI citations on a sales page is good.

### Paid course / training page

Block all. Content is the product.

### Personal portfolio / personal blog

Allow the citing crawlers (ClaudeBot, GPTBot, PerplexityBot, Google-Extended). Useful for "who is X" or "what does X work on" queries.

### SaaS app

- App subdomain (e.g., app.example.com): block all AI scrapers. The app is gated, no value in scraping.
- Landing / marketing subdomain: apply the marketing rules above.

### Default when site type is unclear

Block all. Ask the user. Better to surface the decision than to silently expose content to crawlers.

---

## Observability tier by site type

Decide which analytics and observability tools to install. Always confirm conditional tools with the user.

### Doc site / lib homepage

| Tool | Install? |
| --- | --- |
| GA4 | Yes |
| PostHog (via hogpost.samber.dev or new proxy) | Yes |
| Google Search Console | Yes |
| Bing Webmaster + IndexNow | Yes |
| Ahrefs | Yes |
| Crisp | **No** (doc readers don't chat, it tanks Lighthouse) |
| Sentry | **No** (static, no app logic to crash) |
| BetterStack | **No** (Vercel uptime is enough) |

### Marketing / lead-gen

All of the doc-site tools, plus:

| Tool        | Install?                                       |
| ----------- | ---------------------------------------------- |
| Crisp       | Yes (conversion intent)                        |
| Sentry      | Yes if there are forms or interactive elements |
| BetterStack | Only if you publish an SLA                     |

### SaaS app

All of the above, plus:

| Tool              | Install?                       |
| ----------------- | ------------------------------ |
| Sentry            | **Mandatory**                  |
| BetterStack       | Yes, with a public status page |
| Crisp or Intercom | Yes                            |

### Personal portfolio

| Tool        | Install? |
| ----------- | -------- |
| GA4         | Yes      |
| PostHog     | Yes      |
| GSC         | Yes      |
| Ahrefs      | Optional |
| Crisp       | No       |
| Sentry      | No       |
| BetterStack | No       |

---

## www vs apex canonical

Default: **apex is canonical, www redirects to apex via 308**.

Exception: if the site is hosted on a platform that requires CNAME (which cannot be set on apex per DNS RFCs), the platform's flattening / ALIAS / ANAME feature is used. Cloudflare handles this transparently with CNAME flattening, so apex remains canonical.

Verify with:

```bash
curl -sIL https://www.example.com
# Expect: 308 → https://example.com
```

---

## CSP tightness level by site type

Three levels. Ask the user to pick one at the start of Phase 4.

### `strict-default-src-none`

For doc sites, personal portfolio, SaaS app. Whitelist every source explicitly. No `'unsafe-inline'`. Use nonces for any required inline scripts.

### `balanced-allow-self`

For marketing pages with embeds (YouTube, Calendly, etc.). `default-src 'self'`, then allow specific third parties.

### `permissive-for-marketing`

Last resort for legacy marketing pages with many third-party scripts (HubSpot, Drift, etc.). Document why and plan to tighten.

See `templates.md` for the actual CSP strings per level.

---

## When a decision is unclear

Always default to asking, with the matrix options as tappable choices. Never silently apply a guess.

# Directory List — 13-Tier Catalog

Full catalog of directories for software product submissions. Submit in tier order. Only submit where the product is a genuine fit — forcing a listing into the wrong category burns the first-submission advantage and gets rejected by moderators.

---

## Tier 1 — Flagship Launch (Launch Week Only)

**Timing:** Launch week only  
**Count:** ~15

| Directory | URL | Notes |
| --- | --- | --- |
| Product Hunt | producthunt.com | Anchor event. 3-week prep required. |
| BetaList | betalist.com | Pre-launch signups. |
| Hacker News Show HN | news.ycombinator.com | Only if technical angle. |
| DevHunt | devhunt.org | Dev-focused. |
| Fazier | fazier.co | New startup showcase. |
| LaunchingNext | launchingnext.com | Curated startup directory. |
| StartupStash | startupstash.com | Tool stack directory. |
| Toolify | toolify.ai | AI tools directory. |
| AI Valley | aivalley.ai | AI startup showcase. |
| Futurepedia | futurepedia.io | AI tools directory. |
| TAAFT | theresanaiforthat.com | AI tools directory. |
| Product Hunt Ship | producthunt.com/ship | Coming soon pages. |
| Uneed | uneed.best | Daily product showcase. |
| SideProjectors | sideprojectors.com | Project marketplace. |
| Indie Hackers | indiehackers.com | Community + directory. |

---

## Tier 2 — Startup/SaaS Directories (Week 1 + Rolling)

**Timing:** Week 1 + rolling  
**Count:** ~50

| Directory | URL | DR | Notes |
| --- | --- | --- | --- |
| AlternativeTo | alternativeto.net | 80 | "X alternative" intent. |
| SaaSHub | saashub.com | 70 | SaaS comparisons. |
| G2 | g2.com | 91 | Reviews required (10 min). |
| Capterra | capterra.com | 90 | Reviews required (5 min). |
| GetApp | getapp.com | 88 | Gartner-owned. |
| Software Advice | softwareadvice.com | 85 | Gartner-owned. |
| F6S | f6s.com | 75 | Startup programs. |
| SourceForge | sourceforge.net | 88 | Open source + SaaS. |
| Slashdot | slashdot.org | 90 | Tech news + directory. |
| Crunchbase | crunchbase.com | 91 | Company profile. |
| AngelList | angel.co | 88 | Startup database. |
| PitchBook | pitchbook.com | 85 | Private market data. |
| Tracxn | tracxn.com | 75 | Market intelligence. |
| Owler | owler.com | 75 | Competitor tracking. |
| Serchen | serchen.com | 65 | Cloud services. |
| Cloudways | cloudways.com | 70 | Hosting + tools. |
| DigitalOcean Marketplace | marketplace.digitalocean.com | 85 | Dev tools. |
| AWS Marketplace | aws.amazon.com/marketplace | 95 | Enterprise. |
| Azure Marketplace | azuremarketplace.microsoft.com | 95 | Enterprise. |
| GCP Marketplace | console.cloud.google.com/marketplace | 95 | Enterprise. |
| Heroku Elements | elements.heroku.com | 85 | Add-ons. |
| Docker Hub | hub.docker.com | 90 | Containers. |
| npm | npmjs.com | 92 | JS packages. |
| PyPI | pypi.org | 90 | Python packages. |
| Packagist | packagist.org | 85 | PHP packages. |
| RubyGems | rubygems.org | 85 | Ruby gems. |
| Cargo | crates.io | 80 | Rust crates. |
| Go pkg | pkg.go.dev | 85 | Go modules. |
| Maven Central | search.maven.org | 85 | Java packages. |
| NuGet | nuget.org | 85 | .NET packages. |
| Chocolatey | chocolatey.org | 75 | Windows packages. |
| Homebrew | formulae.brew.sh | 85 | macOS packages. |
| Scoop | scoop.sh | 70 | Windows packages. |
| Snapcraft | snapcraft.io | 75 | Linux packages. |
| Flatpak | flathub.org | 75 | Linux packages. |
| AUR | aur.archlinux.org | 75 | Arch packages. |
| Nixpkgs | search.nixos.org/packages | 75 | Nix packages. |

---

## Tier 3 — AI Directories (Week 1–3)

**Timing:** Week 1–3  
**Count:** ~40

| Directory              | URL                     | Notes                  |
| ---------------------- | ----------------------- | ---------------------- |
| There's An AI For That | theresanaiforthat.com   | Largest AI directory.  |
| Futurepedia            | futurepedia.io          | Daily updates.         |
| Toolify                | toolify.ai              | Categorized AI tools.  |
| Future Tools           | futuretools.io          | Curated by Matt Wolfe. |
| AI Tools Inc           | aitools.inc             | AI tool discovery.     |
| AI Stage               | aistage.io              | AI tool showcase.      |
| TopAI Tools            | topai.tools             | Ranked listings.       |
| AI Tool Hunt           | ai-toolhunt.com         | New tools daily.       |
| AI Depot               | aidepot.com             | Curated AI tools.      |
| AI Tools Club          | aitoolsclub.com         | Community-driven.      |
| All Things AI          | allthingsai.com         | Reviews + directory.   |
| AI Tools Directory     | aitoolsdirectory.com    | Categorized.           |
| AI Scout               | aisout.com              | AI tool finder.        |
| AI Tools Arena         | aithetoolsarena.com     | Comparison focus.      |
| AI Tools Hub           | aitoolshub.com          | Curated listings.      |
| AI Tools Guide         | aitoolsguide.com        | Guides + directory.    |
| AI Tools List          | aitoolslist.com         | Simple listings.       |
| AI Tools Database      | aitoolsdatabase.com     | Searchable.            |
| AI Tools Index         | aitoolsindex.com        | Index-style.           |
| AI Tools Catalog       | aitoolscatalog.com      | Catalog format.        |
| AI Tools Review        | aitoolsreview.com       | Review-focused.        |
| AI Tools Ranking       | aitoolsranking.com      | Ranked.                |
| AI Tools Compare       | aitoolscompare.com      | Comparison.            |
| AI Tools Search        | aitoolssearch.com       | Search engine.         |
| AI Tools Finder        | aitoolsfinder.com       | Discovery.             |
| AI Tools Explorer      | aitoolsexplorer.com     | Exploration.           |
| AI Tools Navigator     | aitoolsnavigator.com    | Navigation.            |
| AI Tools Directory Pro | aitoolsdirectorypro.com | Premium.               |
| AI Tools Master List   | aitoolsmasterlist.com   | Comprehensive.         |
| AI Tools Weekly        | aitoolsweekly.com       | Weekly updates.        |
| AI Tools Daily         | aitoolsdaily.com        | Daily updates.         |
| AI Tools Monthly       | aitoolsmonthly.com      | Monthly roundup.       |
| AI Tools Newsletter    | aitoolsnewsletter.com   | Email-based.           |
| AI Tools Blog          | aitoolsblog.com         | Blog + directory.      |
| AI Tools Wiki          | aitoolswiki.com         | Wiki-style.            |
| AI Tools Forum         | aitoolsforum.com        | Community.             |
| AI Tools Discord       | discord.gg/aitools      | Discord server.        |
| AI Tools Reddit        | reddit.com/r/aitools    | Subreddit.             |
| AI Tools Twitter       | twitter.com/aitools     | Twitter account.       |

---

## Tier 4 — Agent/MCP Registries (Week 1–3, if MCP)

**Timing:** Week 1–3 (if MCP)  
**Count:** ~10

| Directory | URL | Notes |
| --- | --- | --- |
| Glama | glama.ai | MCP registry + agent marketplace. |
| APITracker | apitracker.com | API + agent tracking. |
| LF MCP Registry | lf-mcp-registry.org | Linux Foundation MCP. |
| AI Agents List | aiagentslist.com | Agent directory. |
| AgentOps | agentops.ai | Agent observability + registry. |
| LangChain Hub | hub.langchain.com | Chains + agents. |
| AutoGPT Marketplace | marketplace.agpt.co | AutoGPT agents. |
| BabyAGI Extensions | github.com/babyagi | Extensions. |
| Camel-AI Marketplace | camel-ai.org | Multi-agent framework. |
| CrewAI Hub | crewai.com | CrewAI agents. |

---

## Tier 5 — No-Code Directories (Week 1–3, if no-code)

**Timing:** Week 1–3 (if no-code)  
**Count:** ~8

| Directory      | URL              | Notes                  |
| -------------- | ---------------- | ---------------------- |
| NoCodeFinder   | nocodefinder.com | No-code tools.         |
| No Code MBA    | nocode.mba       | Education + tools.     |
| We Are No Code | wearenocode.com  | Community + directory. |
| MakerPad       | makerpad.co      | Tutorials + tools.     |
| Zeroqode       | zeroqode.com     | Bubble plugins.        |
| NoCode.Tech    | nocode.tech      | Resources + directory. |
| NoCode List    | nocodelist.co    | Curated list.          |
| NoCode Tools   | nocodetools.io   | Tool directory.        |

---

## Tier 6 — "Best of" Listicles (Rolling Outreach)

**Timing:** Rolling outreach  
**Count:** ~10 inclusions

| Strategy | Approach |
| --- | --- |
| Cold outreach to DR 40+ blog posts | Find "best [category] tools 2024/2025" posts. Pitch inclusion with honest comparison data. |
| Guest post with tool mention | Write "how we solved X" posts that naturally include your tool. |
| Podcast appearance with tool mention | Appear on relevant podcasts, mention tool organically. |
| Newsletter sponsorship | Sponsor niche newsletters with tool feature. |
| Influencer review | Send free access to reviewers for honest review. |

---

## Tier 7 — Integration Marketplaces (When Integrations Ship)

**Timing:** When integrations ship  
**Count:** ~5

| Marketplace | URL | Notes |
| --- | --- | --- |
| Zapier | zapier.com/apps | Highest DR, ~2.6M monthly organic. |
| HubSpot | ecosystem.hubspot.com/marketplace | CRM-focused. |
| Slack | slack.com/apps | Workplace tools. |
| Airtable | airtable.com/marketplace | Database apps. |
| Notion | notion.so/marketplace | Workspace tools. |
| Make (Integromat) | make.com/en/integrations | Automation. |
| n8n | n8n.io/integrations | Self-hosted automation. |
| Pipedream | pipedream.com/apps | Developer-first. |
| Tray.io | tray.io/integrations | Enterprise iPaaS. |
| Workato | workato.com/connectors | Enterprise automation. |

---

## Tier 8 — Profile & Content Platforms (Rolling)

**Timing:** Rolling  
**Count:** ~50

| Platform               | URL                  | Notes                 |
| ---------------------- | -------------------- | --------------------- |
| GitHub                 | github.com           | Repo + profile.       |
| GitLab                 | gitlab.com           | Repo + profile.       |
| Bitbucket              | bitbucket.org        | Repo + profile.       |
| WordPress.com          | wordpress.com        | Blog hosting.         |
| Substack               | substack.com         | Newsletter.           |
| Dev.to                 | dev.to               | Developer blog.       |
| Hashnode               | hashnode.com         | Developer blog.       |
| Medium                 | medium.com           | Blog platform.        |
| SlideShare             | slideshare.net       | Presentations.        |
| Behance                | behance.net          | Design portfolio.     |
| Dribbble               | dribbble.com         | Design shots.         |
| Product Hunt           | producthunt.com      | Profile + launches.   |
| Indie Hackers          | indiehackers.com     | Founder stories.      |
| Makerlog               | makerlog.org         | Build in public.      |
| WIP                    | wip.chat             | Work in progress.     |
| Twitter/X              | twitter.com          | Social + profile.     |
| LinkedIn               | linkedin.com         | Professional profile. |
| YouTube                | youtube.com          | Video content.        |
| TikTok                 | tiktok.com           | Short video.          |
| Instagram              | instagram.com        | Visual content.       |
| Reddit                 | reddit.com           | Community.            |
| Quora                  | quora.com            | Q&A.                  |
| Stack Overflow         | stackoverflow.com    | Dev Q&A.              |
| Stack Exchange         | stackexchange.com    | Network Q&A.          |
| Hacker News            | news.ycombinator.com | Tech news.            |
| Lobste.rs              | lobste.rs            | Tech links.           |
| Designer News          | designernews.co      | Design news.          |
| GrowthHackers          | growthhackers.com    | Growth content.       |
| Inbound.org            | inbound.org          | Marketing content.    |
| Product Hunt Comments  | producthunt.com      | Discussion.           |
| Indie Hackers Comments | indiehackers.com     | Discussion.           |

---

## Tier 9 — Local Business Directories (Rolling, if applicable)

**Timing:** Rolling (if applicable)  
**Count:** ~20

| Directory               | URL                      | Notes                 |
| ----------------------- | ------------------------ | --------------------- |
| Google Business Profile | business.google.com      | Critical for local.   |
| Yelp                    | yelp.com                 | Reviews + local.      |
| Bing Places             | bingplaces.microsoft.com | Microsoft local.      |
| Apple Maps              | mapsconnect.apple.com    | Apple local.          |
| Facebook Business       | business.facebook.com    | Meta local.           |
| Foursquare              | foursquare.com           | Location data.        |
| Yellow Pages            | yellowpages.com          | Traditional.          |
| Manta                   | manta.com                | Small business.       |
| Hotfrog                 | hotfrog.com              | Free listing.         |
| Locanto                 | locanto.com              | Classifieds.          |
| MerchantCircle          | merchantcircle.com       | Local network.        |
| Superpages              | superpages.com           | Directory.            |
| Citysearch              | citysearch.com           | Local guide.          |
| DexKnows                | dexknows.com             | Directory.            |
| Local.com               | local.com                | Local search.         |
| EZLocal                 | ezlocal.com              | Local listings.       |
| MyLocalServices         | mylocalservices.com      | Services.             |
| Thumbtack               | thumbtack.com            | Services marketplace. |
| Angie's List            | angieslist.com           | Reviews.              |
| HomeAdvisor             | homeadvisor.com          | Home services.        |

---

## Tier 10 — Forums & Communities (Rolling, participate first)

**Timing:** Rolling (participate first)  
**Count:** ~13

| Community | URL | Notes |
| --- | --- | --- |
| Reddit r/SideProject | reddit.com/r/SideProject | Friendly to promo. |
| Reddit r/SaaS | reddit.com/r/SaaS | "Share Your SaaS" threads. |
| Reddit r/startups | reddit.com/r/startups | Feedback Friday. |
| Reddit r/Entrepreneur | reddit.com/r/Entrepreneur | Weekly promo thread. |
| Reddit r/nocode | reddit.com/r/nocode | No-code friendly. |
| Reddit r/IndieHackers | reddit.com/r/IndieHackers | Indie hackers. |
| Reddit r/alphaandbetausers | reddit.com/r/alphaandbetausers | Beta testing. |
| Reddit r/webdev | reddit.com/r/webdev | Strict, technical only. |
| Reddit r/artificial | reddit.com/r/artificial | AI/ML strict. |
| Reddit r/LocalLLaMA | reddit.com/r/LocalLLaMA | Local LLMs. |
| SitePoint | sitepoint.com/forums | Dev forums. |
| GrowthHackers | growthhackers.com | Growth community. |
| Warrior Forum | warriorforum.com | IM forum. |
| Designer News | designernews.co | Design community. |
| Indie Hackers Forum | indiehackers.com/forum | Founder forum. |

---

## Tier 11 — Press Release & Article Sites (Launch + Milestones)

**Timing:** Launch + milestones  
**Count:** ~25

| Site | URL | Notes |
| --- | --- | --- |
| PRLog | prlog.org | Free press releases. |
| PR.com | pr.com | Free + paid. |
| EzineArticles | ezinearticles.com | Article directory. |
| Feedspot | feedspot.com | Content aggregator. |
| PR Newswire | prnewswire.com | Paid distribution. |
| Business Wire | businesswire.com | Paid distribution. |
| PRWeb | prweb.com | Paid distribution. |
| EIN Presswire | einpresswire.com | Paid distribution. |
| 24-7 Press Release | 24-7pressrelease.com | Free + paid. |
| Newswire Today | newswiretoday.com | Free + paid. |
| Press Release Point | pressreleasepoint.com | Free + paid. |
| Free Press Release | free-press-release.com | Free. |
| PR Free | prfree.org | Free. |
| Press Release Distribution | pressreleasedistribution.com | Paid. |
| NewsWire | newswire.com | Paid. |
| PR Underground | prunderground.com | Paid. |
| PR Log | prlog.org | Free. |
| PR Sync | prsync.com | Free. |
| Press Box | pressbox.co.uk | UK-focused. |
| Media Relations | mediarelations.com | Paid. |
| PR Leap | prleap.com | Paid. |
| 1888 Press Release | 1888pressrelease.com | Free + paid. |
| Press Release Jet | pressreleasejet.com | Paid. |
| PR Fire | prfire.co.uk | UK-focused. |
| OpenPR | openpr.com | Free + paid. |

---

## Tier 12 — Social Bookmarking (Rolling)

**Timing:** Rolling  
**Count:** ~5

| Site       | URL            | Notes               |
| ---------- | -------------- | ------------------- |
| Scoop.it   | scoop.it       | Content curation.   |
| Diigo      | diigo.com      | Social bookmarking. |
| Pearltrees | pearltrees.com | Visual bookmarking. |
| Pocket     | getpocket.com  | Save for later.     |
| Mix        | mix.com        | Content discovery.  |

---

## Tier 13 — Niche Vertical Directories (When Vertical Fits)

**Timing:** When vertical fits  
**Count:** ~20

| Vertical      | Directory         | URL                                |
| ------------- | ----------------- | ---------------------------------- |
| Legal         | Justia            | justia.com                         |
| Legal         | Avvo              | avvo.com                           |
| Legal         | FindLaw           | findlaw.com                        |
| Home Services | Porch             | porch.com                          |
| Home Services | Houzz             | houzz.com                          |
| Design        | LandBook          | land-book.com                      |
| Design        | SiteInspire       | siteinspire.com                    |
| Design        | Awwwards          | awwwards.com                       |
| Design        | CSS Design Awards | cssdesignawards.com                |
| Ecommerce     | BuiltWith         | builtwith.com                      |
| Ecommerce     | StoreLeads        | storeleads.app                     |
| Dev Tools     | DevTools          | devtools.com                       |
| Dev Tools     | LibHunt           | libhunt.com                        |
| Dev Tools     | Awesome Lists     | github.com/sindresorhus/awesome    |
| APIs          | RapidAPI          | rapidapi.com                       |
| APIs          | APILayer          | apilayer.com                       |
| APIs          | Public APIs       | github.com/public-apis/public-apis |
| AI/ML         | Papers With Code  | paperswithcode.com                 |
| AI/ML         | Hugging Face      | huggingface.co                     |
| AI/ML         | ModelScope        | modelscope.cn                      |

---

## Submission Order by Week

### Week 1 (Launch Week)

- Tier 1: All ~15 flagship directories
- Tier 2: Top 10 startup/SaaS (AlternativeTo, G2, Capterra, SaaSHub, F6S, SourceForge, Crunchbase, Product Hunt Ship, DevHunt, Fazier)
- Tier 3: Top 10 AI directories (TAAFT, Futurepedia, Toolify, Future Tools, AI Stage, AI Tools Inc, TopAI Tools, AI Tool Hunt, AI Depot, All Things AI)
- Tier 4: All if MCP/agent (~10)
- Tier 7: All integration marketplaces where integrations exist (~5)

### Week 2

- Tier 2: Remaining ~40 startup/SaaS directories
- Tier 3: Remaining ~30 AI directories
- Tier 5: All if no-code (~8)
- Tier 6: Begin outreach to "best of" listicles (~10)

### Week 3

- Tier 8: Profile & content platforms (~50)
- Tier 9: Local directories if applicable (~20)
- Tier 10: Forums & communities (participate first, then share) (~13)
- Tier 11: Press release sites for launch announcement (~25)
- Tier 12: Social bookmarking (~5)
- Tier 13: Niche vertical directories if applicable (~20)

### Ongoing (Monthly)

- Tier 6: Continue "best of" outreach
- Tier 8: Maintain profiles, post content
- Tier 10: Participate in communities (90/10 rule)
- Tier 11: Press releases for milestones
- Monitor and update existing listings quarterly

# Positioning Variations by Directory Tier

Never copy-paste the same description everywhere. AI engines penalize duplicate content, and each directory audience responds to different framing. Prepare distinct variants per tier before submitting.

---

## Core Positioning Assets (Create Once, Adapt Per Tier)

### Master Tagline (under 10 words)

```
[Product] — [One-sentence outcome for target user]
```

### Master Short Description (60 chars)

```
[Product] helps [target user] [achieve outcome] via [key mechanism].
```

### Master Long Description (150 words)

```
[Product] is a [category] that helps [target user] [solve problem/achieve outcome]. Unlike [top competitor], we [key differentiator 1] and [key differentiator 2]. Key features include: [feature 1], [feature 2], [feature 3]. Built for [specific use case/ICP]. [Social proof: X users, Y companies, Z% improvement]. Try it free at [URL].
```

### Master Category Tags (5-8)

```
[category], [subcategory], [key feature 1], [key feature 2], [integration 1], [integration 2], [platform], [pricing model]
```

### Logo Assets Required

- Logo: 1024×1024 PNG (square, transparent background)
- Logo: SVG (vector, for scaling)
- Logo: 512×512 PNG (for favicon generation)
- Logo: Dark mode version (if brand has dark variant)

### Screenshots Required (5-8 at 1920×1080)

1. Dashboard/overview (shows value at a glance)
2. Key workflow 1 (core use case)
3. Key workflow 2 (secondary use case)
4. Integration/setup screen
5. Analytics/reporting view
6. Team/collaboration features (if applicable)
7. Mobile/responsive view
8. Unique differentiator feature

### Demo Video (60-90 seconds)

- 0-5s: Hook — the problem
- 5-15s: Solution overview
- 15-45s: Live demo of core workflow
- 45-60s: Key differentiator close-up
- 60-75s: Social proof / testimonials
- 75-90s: CTA + URL

### Founder Story (2-3 sentences)

```
I built [Product] because [personal pain point]. Existing tools [failed in specific way]. We're [mission/vision]. [Credibility signal: background, traction, notable users].
```

---

## Tier-Specific Variants

### Tier 1 — Flagship Launch (Product Hunt, BetaList, HN, DevHunt)

**Audience:** Early adopters, tech enthusiasts, founders, investors **Lead with:** **Innovation + Story** **Tone:** Excited, transparent, builder-to-builder

**Tagline:**

```
[Product] — The [category] that [unique approach] for [target user]
```

**Short Description:**

```
[Product] reimagines [category] by [unique approach] so [target user] can [outcome].
```

**Long Description:**

```
We built [Product] because [founder story — 1 sentence]. The problem: [specific pain point with numbers if possible]. Existing tools [specific failure mode]. Our approach: [unique technical/UX insight]. The result: [quantified outcome for early users]. We're launching today on [Platform] — try it free and tell us what you'd change.
```

**Category Tags:**

```
[category], developer-tools, [key-tech], open-source, free-tier, [platform], launch, early-access
```

**First Comment (Post Yourself):**

```
Hey hunters! 👋 I'm [Name], founder of [Product].

We built this because [personal story — 2 sentences].

The short version: [1-sentence value prop].

What's different:
- [Differentiator 1 with technical detail]
- [Differentiator 2 with user benefit]
- [Differentiator 3 with outcome]

We're early — [honest state: "in beta," "pre-revenue," "100 users"]. Would love your honest take on the positioning, the UX, or the roadmap. What would you build next?

Try it: [direct signup link — no landing page redirect]
```

---

### Tier 2 — Startup/SaaS Directories (AlternativeTo, G2, Capterra, SaaSHub)

**Audience:** Buyers actively comparing alternatives **Lead with:** **Alternative Framing** **Tone:** Objective, comparison-ready, buyer-focused

**Tagline:**

```
[Product] — The best [competitor] alternative for [specific use case]
```

**Short Description:**

```
[Product] is a [competitor] alternative that [key advantage] for [target user]. [Key differentiator].
```

**Long Description:**

```
Looking for a [competitor] alternative? [Product] helps [target user] [achieve outcome] without [competitor's main pain point].

Why teams switch from [competitor]:
- [Advantage 1]: [specific detail + quantified benefit]
- [Advantage 2]: [specific detail + quantified benefit]
- [Advantage 3]: [specific detail + quantified benefit]

Best for: [ICP 1], [ICP 2], [ICP 3]
Pricing: [pricing model — e.g., "Free for up to 5 users, then $X/user/mo"]
Integrations: [top 5 integrations]

See honest comparison: [yourdomain.com/alternatives/competitor]
```

**Category Tags:**

```
[category], [competitor]-alternative, [use-case], saas, b2b, [pricing-model], [integration-1], [integration-2]
```

---

### Tier 3 — AI Directories (TAAFT, Futurepedia, Toolify, Future Tools)

**Audience:** AI tool seekers, prompt engineers, AI builders **Lead with:** **AI-First Architecture** **Tone:** Technical, capability-focused, prompt-ready

**Tagline:**

```
[Product] — AI-powered [category] that [unique AI capability]
```

**Short Description:**

```
[Product] uses [AI technique: agents, RAG, fine-tuning, etc.] to [outcome] for [target user].
```

**Long Description:**

```
[Product] is an AI-first [category] built on [model/framework: GPT-4, Claude, Llama, custom, LangChain, CrewAI, etc.].

AI Capabilities:
- [Capability 1]: [specific AI feature — e.g., "autonomous agent that researches competitors"]
- [Capability 2]: [specific AI feature — e.g., "RAG over your codebase for context-aware suggestions"]
- [Capability 3]: [specific AI feature — e.g., "fine-tuned model for [domain] tasks"]

Human-in-the-loop: [yes/no — how humans review/approve AI output]
Data privacy: [local processing / encrypted / no training on your data]
Model flexibility: [BYOK / multiple providers / locked to one]

Use cases: [use case 1], [use case 2], [use case 3]
```

**Category Tags:**

```
ai, artificial-intelligence, [specific-ai: agents, rag, llm, generative], [category], developer-tools, productivity, automation
```

---

### Tier 4 — Agent/MCP Registries (Glama, APITracker, LF MCP Registry)

**Audience:** Agent developers, MCP server builders, AI engineers **Lead with:** **Agent/MCP Angle** **Tone:** Highly technical, protocol-focused, integration-ready

**Tagline:**

```
[Product] — [MCP server / Agent / Tool] for [specific capability] via [protocol]
```

**Short Description:**

```
[Product] exposes [capability] as an [MCP server / agent skill / function] for [AI framework: Claude, Cursor, LangChain, etc.].
```

**Long Description:**

```
[Product] is a [MCP server / agent / tool] that provides [specific capability] to AI assistants and agents.

Protocol: [MCP / OpenAI Functions / LangChain Tools / CrewAI Skills / AutoGPT Commands]
Transport: [stdio / SSE / HTTP / WebSocket]
Authentication: [API key / OAuth / none / mTLS]

Capabilities exposed:
- [Capability 1]: [function name] — [description + params]
- [Capability 2]: [function name] — [description + params]
- [Capability 3]: [function name] — [description + params]

Installation: [one-liner install command]
Documentation: [docs URL]
Source: [GitHub URL]
License: [MIT / Apache 2.0 / etc.]
```

**Category Tags:**

```
mcp, model-context-protocol, agent, ai-agent, [framework], developer-tools, api, integration, open-source
```

---

### Tier 5 — No-Code Directories (NoCodeFinder, No Code MBA, MakerPad)

**Audience:** No-code builders, citizen developers, non-technical founders **Lead with:** **Ease + Power** **Tone:** Accessible, outcome-focused, visual

**Tagline:**

```
[Product] — Build [outcome] without code in [timeframe]
```

**Short Description:**

```
[Product] lets [non-technical user] [achieve outcome] using [visual interface / drag-drop / forms] — no code required.
```

**Long Description:**

```
Stop waiting for developers. [Product] gives you [powerful capability] through a [visual builder / spreadsheet interface / form / chat].

What you can build:
- [Use case 1] — [template available: yes/no]
- [Use case 2] — [template available: yes/no]
- [Use case 3] — [template available: yes/no]

Features:
- [Feature 1: e.g., "Visual workflow builder with 50+ pre-built blocks"]
- [Feature 2: e.g., "One-click deploy to [platform]"]
- [Feature 3: e.g., "Built-in auth, database, and API"]

Templates included: [number] templates for [use cases]
Learning curve: [minutes/hours to first working app]
Community: [Discord/Slack/Forum size]
```

**Category Tags:**

```
no-code, low-code, visual-programming, citizen-development, [category], automation, workflow, templates, [platform]
```

---

### Tier 6 — Dev Directories (npm, PyPI, Cargo, Go pkg, Docker Hub)

**Audience:** Developers evaluating libraries/frameworks **Lead with:** **Technical Depth** **Tone:** Precise, spec-driven, installation-first

**Tagline:**

```
[Product] — [Technical description: e.g., "Type-safe ORM for Go with zero reflection"]
```

**Short Description:**

```
[Product] is a [language] [library/framework] for [specific technical problem]. [Key technical differentiator].
```

**Long Description:**

```
[Product] solves [specific technical problem] for [language] developers.

Technical approach:
- [Architecture decision 1]: [why + tradeoff]
- [Architecture decision 2]: [why + tradeoff]
- [Architecture decision 3]: [why + tradeoff]

Key features:
- [Feature 1]: [technical detail — e.g., "Zero-allocation hot path via arena allocator"]
- [Feature 2]: [technical detail — e.g., "Compile-time SQL validation via sqlc"]
- [Feature 3]: [technical detail — e.g., "Automatic retry with exponential backoff + jitter"]

Performance: [benchmarks — e.g., "3× faster than X, 50% less memory"]
Dependencies: [minimal / zero / listed]
License: [MIT / Apache 2.0 / BSD-3]
MSRV / Minimum version: [e.g., Go 1.21+, Python 3.10+]

Install: `[package manager install command]`
Docs: [URL]
Changelog: [URL]
```

**Category Tags:**

```
[language], [category], library, framework, [key-tech], performance, type-safe, zero-dependency, [license]
```

---

### Tier 7 — B2B Review Sites (G2, Capterra, TrustRadius, GetApp, Software Advice)

**Audience:** B2B buyers, procurement, decision-makers **Lead with:** **ROI + Use Case** **Tone:** Professional, outcome-oriented, proof-heavy

**Tagline:**

```
[Product] — [Category] that delivers [ROI metric] for [target buyer]
```

**Short Description:**

```
[Product] helps [target buyer] [achieve business outcome] with [key capability]. [ROI claim].
```

**Long Description:**

```
[Product] is a [category] designed for [target buyer: e.g., "mid-market B2B SaaS companies"].

Business Outcomes:
- [Outcome 1]: [metric — e.g., "Reduce onboarding time from 2 weeks to 2 hours"]
- [Outcome 2]: [metric — e.g., "Increase trial-to-paid conversion by 40%"]
- [Outcome 3]: [metric — e.g., "Save 15 hrs/week per CSM on manual tasks"]

Key Capabilities:
- [Capability 1]: [business value]
- [Capability 2]: [business value]
- [Capability 3]: [business value]

Integrations: [CRM, marketing automation, analytics, support — top 10]
Security: [SOC 2 / ISO 27001 / GDPR / HIPAA — certifications]
Support: [SLA, channels, response time]
Implementation: [time to value — e.g., "Live in 30 minutes"]

Customers: [Company types — e.g., "200+ companies including Series A–C SaaS"]
Pricing: [Transparent pricing URL or "Contact for enterprise"]
```

**Category Tags:**

```
[category], b2b, saas, enterprise, [target-buyer], roi, [integration-1], [integration-2], [security-cert], [pricing-model]
```

---

## Positioning Matrix Quick Reference

| Tier | Lead With | Audience | Tone | Key Differentiator |
| --- | --- | --- | --- | --- |
| 1 Flagship | Innovation + Story | Early adopters, founders | Excited, builder-to-builder | Unique approach, founder story |
| 2 SaaS | Alternative Framing | Buyers comparing tools | Objective, buyer-focused | "Better than [competitor] at X" |
| 3 AI | AI-First Architecture | AI tool seekers | Technical, capability-focused | Specific AI technique + model |
| 4 Agent/MCP | Agent/MCP Angle | Agent developers | Protocol-focused, integration-ready | MCP server, function schemas |
| 5 No-Code | Ease + Power | Citizen developers | Accessible, visual, outcome-focused | Time to first app, templates |
| 6 Dev | Technical Depth | Library evaluators | Precise, spec-driven | Performance, architecture, types |
| 7 B2B Review | ROI + Use Case | Buyers, procurement | Professional, proof-heavy | Quantified business outcomes |

---

## Anti-Patterns to Avoid

1. **Same description everywhere** → AI engines cross-reference and down-weight
2. **Vague claims** ("powerful," "comprehensive," "seamless") → No one believes them
3. **Feature lists without outcomes** → Buyers care what it _does for them_
4. **No competitor acknowledgment** → Alternative pages need honest comparisons
5. **Missing technical specifics** (Tier 4, 6) → Devs check specs before trying
6. **No social proof** → Even "10 beta users" is better than nothing
7. **Generic category tags** → Use specific tags the directory's search uses
8. **Broken demo video link** → Test every URL before submitting
9. **Mismatched pricing** → Directory pricing must match your live pricing page
10. **Outdated screenshots** → Must match current UI exactly

# Submission Tracker Template

Copy this to a Google Sheet, Excel, or CSV file. Track every submission.

## Columns

| Column | Description | Example |
|---|---|---|
| Tier | Tier number (1-13) | 1 |
| Directory | Directory name | Product Hunt |
| URL | Submission URL | https://producthunt.com/products/new |
| Status | not-started / submitted / pending-review / live / rejected / needs-update | submitted |
| Submission Date | Date submitted (YYYY-MM-DD) | 2025-01-15 |
| Live Date | Date listing went live (YYYY-MM-DD) | 2025-01-20 |
| Moderator Notes | Any feedback from moderators | "Needs higher-res screenshots" |
| Backlink Verified | yes / no / n/a | yes |
| Backlink URL | Direct URL to your listing | https://producthunt.com/products/your-product |
| Dofollow | yes / no / unknown | yes |
| DR | Domain Rating of directory (from Ahrefs) | 91 |
| Traffic | Estimated monthly traffic (from Ahrefs/SimilarWeb) | 500000 |
| Category Tags Used | Tags submitted | developer-tools, saas, ai, launch |
| Tagline Used | Tagline submitted | "Product — The AI-powered X for Y" |
| Description Used | Short description (60 chars) | "Product helps developers build X faster" |
| Long Description Used | Long description (150 words) | "Product is a..." |
| Screenshots Used | Which screenshots (1-8) | 1,2,3,4,5 |
| Video URL | Demo video URL | https://youtube.com/watch?v=abc123 |
| Founder Story Used | Founder story variant | "I built this because..." |
| Referral Traffic (30d) | Sessions from this directory (GA4/PostHog) | 150 |
| Signups (30d) | Signups attributed to this directory | 12 |
| Notes | Internal notes | "Hunter: @username. Upcoming page created 1/1." |

---

## CSV Template (copy below into a .csv file)

```csv
Tier,Directory,URL,Status,Submission Date,Live Date,Moderator Notes,Backlink Verified,Backlink URL,Dofollow,DR,Traffic,Category Tags Used,Tagline Used,Description Used,Long Description Used,Screenshots Used,Video URL,Founder Story Used,Referral Traffic (30d),Signups (30d),Notes
1,Product Hunt,https://producthunt.com/products/new,not-started,,,,,,,,,,,,,,,,,
1,BetaList,https://betalist.com/submit,not-started,,,,,,,,,,,,,,,,,
1,Hacker News Show HN,https://news.ycombinator.com/submit,not-started,,,,,,,,,,,,,,,,,
1,DevHunt,https://devhunt.org/submit,not-started,,,,,,,,,,,,,,,,,
1,Fazier,https://fazier.co/submit,not-started,,,,,,,,,,,,,,,,,
2,AlternativeTo,https://alternativeto.net/add-application/,not-started,,,,,,,,,,,,,,,,,
2,SaaSHub,https://saashub.com/submit,not-started,,,,,,,,,,,,,,,,,
2,G2,https://g2.com/products/new,not-started,,,,,,,,,,,,,,,,,
2,Capterra,https://capterra.com/vendors/signup,not-started,,,,,,,,,,,,,,,,,
2,F6S,https://f6s.com/startups/new,not-started,,,,,,,,,,,,,,,,,
2,SourceForge,https://sourceforge.net/directory/add/,not-started,,,,,,,,,,,,,,,,,
2,Slashdot,https://slashdot.org/submit,not-started,,,,,,,,,,,,,,,,,
2,Crunchbase,https://crunchbase.com/organization/new,not-started,,,,,,,,,,,,,,,,,
2,AngelList,https://angel.co/company/new,not-started,,,,,,,,,,,,,,,,,
3,There's An AI For That,https://theresanaiforthat.com/submit/,not-started,,,,,,,,,,,,,,,,,
3,Futurepedia,https://futurepedia.io/submit-tool,not-started,,,,,,,,,,,,,,,,,
3,Toolify,https://toolify.ai/submit,not-started,,,,,,,,,,,,,,,,,
3,Future Tools,https://futuretools.io/submit,not-started,,,,,,,,,,,,,,,,,
3,AI Tools Inc,https://aitools.inc/submit,not-started,,,,,,,,,,,,,,,,,
3,AI Stage,https://aistage.io/submit,not-started,,,,,,,,,,,,,,,,,
3,TopAI Tools,https://topai.tools/submit,not-started,,,,,,,,,,,,,,,,,
3,AI Tool Hunt,https://ai-toolhunt.com/submit,not-started,,,,,,,,,,,,,,,,,
3,AI Depot,https://aidepot.com/submit,not-started,,,,,,,,,,,,,,,,,
3,All Things AI,https://allthingsai.com/submit,not-started,,,,,,,,,,,,,,,,,
4,Glama,https://glama.ai/submit,not-started,,,,,,,,,,,,,,,,,
4,APITracker,https://apitracker.com/submit,not-started,,,,,,,,,,,,,,,,,
4,LF MCP Registry,https://lf-mcp-registry.org/submit,not-started,,,,,,,,,,,,,,,,,
4,AI Agents List,https://aiagentslist.com/submit,not-started,,,,,,,,,,,,,,,,,
4,AgentOps,https://agentops.ai/submit,not-started,,,,,,,,,,,,,,,,,
4,LangChain Hub,https://hub.langchain.com/submit,not-started,,,,,,,,,,,,,,,,,
4,AutoGPT Marketplace,https://marketplace.agpt.co/submit,not-started,,,,,,,,,,,,,,,,,
4,Camel-AI Marketplace,https://camel-ai.org/submit,not-started,,,,,,,,,,,,,,,,,
4,CrewAI Hub,https://crewai.com/submit,not-started,,,,,,,,,,,,,,,,,
5,NoCodeFinder,https://nocodefinder.com/submit,not-started,,,,,,,,,,,,,,,,,
5,No Code MBA,https://nocode.mba/submit,not-started,,,,,,,,,,,,,,,,,
5,We Are No Code,https://wearenocode.com/submit,not-started,,,,,,,,,,,,,,,,,
5,MakerPad,https://makerpad.co/submit,not-started,,,,,,,,,,,,,,,,,
5,Zeroqode,https://zeroqode.com/submit,not-started,,,,,,,,,,,,,,,,,
5,NoCode.Tech,https://nocode.tech/submit,not-started,,,,,,,,,,,,,,,,,
5,NoCode List,https://nocodelist.co/submit,not-started,,,,,,,,,,,,,,,,,
5,NoCode Tools,https://nocodetools.io/submit,not-started,,,,,,,,,,,,,,,,,
6,Best of Listicle Outreach,-,not-started,,,,,,,,,,,,,,,,,
7,Zapier,https://zapier.com/platform,not-started,,,,,,,,,,,,,,,,,
7,HubSpot,https://ecosystem.hubspot.com/marketplace/listing/create,not-started,,,,,,,,,,,,,,,,,
7,Slack,https://api.slack.com/apps,not-started,,,,,,,,,,,,,,,,,
7,Airtable,https://airtable.com/marketplace/submit,not-started,,,,,,,,,,,,,,,,,
7,Notion,https://notion.so/marketplace/submit,not-started,,,,,,,,,,,,,,,,,
7,Make,https://make.com/en/integrations/submit,not-started,,,,,,,,,,,,,,,,,
7,n8n,https://n8n.io/integrations/submit,not-started,,,,,,,,,,,,,,,,,
7,Pipedream,https://pipedream.com/apps/submit,not-started,,,,,,,,,,,,,,,,,
7,Tray.io,https://tray.io/integrations/submit,not-started,,,,,,,,,,,,,,,,,
7,Workato,https://workato.com/connectors/submit,not-started,,,,,,,,,,,,,,,,,
8,GitHub,https://github.com/new,not-started,,,,,,,,,,,,,,,,,
8,GitLab,https://gitlab.com/projects/new,not-started,,,,,,,,,,,,,,,,,
8,Bitbucket,https://bitbucket.org/repo/create,not-started,,,,,,,,,,,,,,,,,
8,WordPress.com,https://wordpress.com/start,not-started,,,,,,,,,,,,,,,,,
8,Substack,https://substack.com/signup,not-started,,,,,,,,,,,,,,,,,
8,Dev.to,https://dev.to/new,not-started,,,,,,,,,,,,,,,,,
8,Hashnode,https://hashnode.com/new,not-started,,,,,,,,,,,,,,,,,
8,Medium,https://medium.com/new-story,not-started,,,,,,,,,,,,,,,,,
8,SlideShare,https://slideshare.net/upload,not-started,,,,,,,,,,,,,,,,,
8,Behance,https://behance.net/new,not-started,,,,,,,,,,,,,,,,,
8,Dribbble,https://dribbble.com/shots/new,not-started,,,,,,,,,,,,,,,,,
8,Product Hunt Profile,https://producthunt.com/@username,not-started,,,,,,,,,,,,,,,,,
8,Indie Hackers,https://indiehackers.com/post/new,not-started,,,,,,,,,,,,,,,,,
8,Makerlog,https://makerlog.org/new,not-started,,,,,,,,,,,,,,,,,
8,WIP,https://wip.chat/new,not-started,,,,,,,,,,,,,,,,,
8,Twitter/X,https://twitter.com/compose/tweet,not-started,,,,,,,,,,,,,,,,,
8,LinkedIn,https://linkedin.com/feed,not-started,,,,,,,,,,,,,,,,,
8,YouTube,https://youtube.com/upload,not-started,,,,,,,,,,,,,,,,,
8,TikTok,https://tiktok.com/upload,not-started,,,,,,,,,,,,,,,,,
8,Instagram,https://instagram.com/create,not-started,,,,,,,,,,,,,,,,,
8,Reddit,https://reddit.com/submit,not-started,,,,,,,,,,,,,,,,,
8,Quora,https://quora.com/add/question,not-started,,,,,,,,,,,,,,,,,
8,Stack Overflow,https://stackoverflow.com/questions/ask,not-started,,,,,,,,,,,,,,,,,
8,Stack Exchange,https://stackexchange.com/sites,not-started,,,,,,,,,,,,,,,,,
8,Hacker News,https://news.ycombinator.com/submit,not-started,,,,,,,,,,,,,,,,,
8,Lobste.rs,https://lobste.rs/submit,not-started,,,,,,,,,,,,,,,,,
8,Designer News,https://designernews.co/stories/new,not-started,,,,,,,,,,,,,,,,,
8,GrowthHackers,https://growthhackers.com/submit,not-started,,,,,,,,,,,,,,,,,
8,Inbound.org,https://inbound.org/submit,not-started,,,,,,,,,,,,,,,,,
8,Product Hunt Comments,https://producthunt.com/products/your-product,not-started,,,,,,,,,,,,,,,,,
8,Indie Hackers Comments,https://indiehackers.com/product/your-product,not-started,,,,,,,,,,,,,,,,,
9,Google Business Profile,https://business.google.com/create,not-started,,,,,,,,,,,,,,,,,
9,Yelp,https://biz.yelp.com/signup,not-started,,,,,,,,,,,,,,,,,
9,Bing Places,https://bingplaces.microsoft.com/,not-started,,,,,,,,,,,,,,,,,
9,Apple Maps,https://mapsconnect.apple.com/,not-started,,,,,,,,,,,,,,,,,
9,Facebook Business,https://business.facebook.com/,not-started,,,,,,,,,,,,,,,,,
9,Foursquare,https://foursquare.com/claim,not-started,,,,,,,,,,,,,,,,,
9,Yellow Pages,https://yellowpages.com/add-business,not-started,,,,,,,,,,,,,,,,,
9,Manta,https://manta.com/add-business,not-started,,,,,,,,,,,,,,,,,
9,Hotfrog,https://hotfrog.com/add-business,not-started,,,,,,,,,,,,,,,,,
9,Locanto,https://locanto.com/add,not-started,,,,,,,,,,,,,,,,,
9,MerchantCircle,https://merchantcircle.com/add-business,not-started,,,,,,,,,,,,,,,,,
9,Superpages,https://superpages.com/add-business,not-started,,,,,,,,,,,,,,,,,
9,Citysearch,https://citysearch.com/add-business,not-started,,,,,,,,,,,,,,,,,
9,DexKnows,https://dexknows.com/add-business,not-started,,,,,,,,,,,,,,,,,
9,Local.com,https://local.com/add-business,not-started,,,,,,,,,,,,,,,,,
9,EZLocal,https://ezlocal.com/add-business,not-started,,,,,,,,,,,,,,,,,
9,MyLocalServices,https://mylocalservices.com/add,not-started,,,,,,,,,,,,,,,,,
9,Thumbtack,https://pro.thumbtack.com/signup,not-started,,,,,,,,,,,,,,,,,
9,Angie's List,https://angieslist.com/business-center,not-started,,,,,,,,,,,,,,,,,
9,HomeAdvisor,https://homeadvisor.com/pro,not-started,,,,,,,,,,,,,,,,,
10,Reddit r/SideProject,https://reddit.com/r/SideProject/submit,not-started,,,,,,,,,,,,,,,,,
10,Reddit r/SaaS,https://reddit.com/r/SaaS/submit,not-started,,,,,,,,,,,,,,,,,
10,Reddit r/startups,https://reddit.com/r/startups/submit,not-started,,,,,,,,,,,,,,,,,
10,Reddit r/Entrepreneur,https://reddit.com/r/Entrepreneur/submit,not-started,,,,,,,,,,,,,,,,,
10,Reddit r/nocode,https://reddit.com/r/nocode/submit,not-started,,,,,,,,,,,,,,,,,
10,Reddit r/IndieHackers,https://reddit.com/r/IndieHackers/submit,not-started,,,,,,,,,,,,,,,,,
10,Reddit r/alphaandbetausers,https://reddit.com/r/alphaandbetausers/submit,not-started,,,,,,,,,,,,,,,,,
10,Reddit r/webdev,https://reddit.com/r/webdev/submit,not-started,,,,,,,,,,,,,,,,,
10,Reddit r/artificial,https://reddit.com/r/artificial/submit,not-started,,,,,,,,,,,,,,,,,
10,Reddit r/LocalLLaMA,https://reddit.com/r/LocalLLaMA/submit,not-started,,,,,,,,,,,,,,,,,
10,SitePoint,https://sitepoint.com/forums/newthread,not-started,,,,,,,,,,,,,,,,,
10,GrowthHackers,https://growthhackers.com/submit,not-started,,,,,,,,,,,,,,,,,
10,Warrior Forum,https://warriorforum.com/newthread,not-started,,,,,,,,,,,,,,,,,
10,Designer News,https://designernews.co/stories/new,not-started,,,,,,,,,,,,,,,,,
10,Indie Hackers Forum,https://indiehackers.com/forum/new,not-started,,,,,,,,,,,,,,,,,
11,PRLog,https://prlog.org/submit,not-started,,,,,,,,,,,,,,,,,
11,PR.com,https://pr.com/submit,not-started,,,,,,,,,,,,,,,,,
11,EzineArticles,https://ezinearticles.com/submit,not-started,,,,,,,,,,,,,,,,,
11,Feedspot,https://feedspot.com/submit,not-started,,,,,,,,,,,,,,,,,
11,PR Newswire,https://prnewswire.com/submit,not-started,,,,,,,,,,,,,,,,,
11,Business Wire,https://businesswire.com/submit,not-started,,,,,,,,,,,,,,,,,
11,PRWeb,https://prweb.com/submit,not-started,,,,,,,,,,,,,,,,,
11,EIN Presswire,https://einpresswire.com/submit,not-started,,,,,,,,,,,,,,,,,
11,24-7 Press Release,https://24-7pressrelease.com/submit,not-started,,,,,,,,,,,,,,,,,
11,Newswire Today,https://newswiretoday.com/submit,not-started,,,,,,,,,,,,,,,,,
11,Press Release Point,https://pressreleasepoint.com/submit,not-started,,,,,,,,,,,,,,,,,
11,Free Press Release,https://free-press-release.com/submit,not-started,,,,,,,,,,,,,,,,,
11,PR Free,https://prfree.org/submit,not-started,,,,,,,,,,,,,,,,,
11,Press Release Distribution,https://pressreleasedistribution.com/submit,not-started,,,,,,,,,,,,,,,,,
11,NewsWire,https://newswire.com/submit,not-started,,,,,,,,,,,,,,,,,
11,PR Underground,https://prunderground.com/submit,not-started,,,,,,,,,,,,,,,,,
11,PR Log,https://prlog.org/submit,not-started,,,,,,,,,,,,,,,,,
11,PR Sync,https://prsync.com/submit,not-started,,,,,,,,,,,,,,,,,
11,Press Box,https://pressbox.co.uk/submit,not-started,,,,,,,,,,,,,,,,,
11,Media Relations,https://mediarelations.com/submit,not-started,,,,,,,,,,,,,,,,,
11,PR Leap,https://prleap.com/submit,not-started,,,,,,,,,,,,,,,,,
11,1888 Press Release,https://1888pressrelease.com/submit,not-started,,,,,,,,,,,,,,,,,
11,Press Release Jet,https://pressreleasejet.com/submit,not-started,,,,,,,,,,,,,,,,,
11,PR Fire,https://prfire.co.uk/submit,not-started,,,,,,,,,,,,,,,,,
11,OpenPR,https://openpr.com/submit,not-started,,,,,,,,,,,,,,,,,
12,Scoop.it,https://scoop.it/submit,not-started,,,,,,,,,,,,,,,,,
12,Diigo,https://diigo.com/submit,not-started,,,,,,,,,,,,,,,,,
12,Pearltrees,https://pearltrees.com/submit,not-started,,,,,,,,,,,,,,,,,
12,Pocket,https://getpocket.com/save,not-started,,,,,,,,,,,,,,,,,
12,Mix,https://mix.com/submit,not-started,,,,,,,,,,,,,,,,,
13,Justia,https://justia.com/submit,not-started,,,,,,,,,,,,,,,,,
13,Avvo,https://avvo.com/lawyers/profile,not-started,,,,,,,,,,,,,,,,,
13,FindLaw,https://lawyers.findlaw.com/claim,not-started,,,,,,,,,,,,,,,,,
13,Porch,https://porch.com/pro,not-started,,,,,,,,,,,,,,,,,
13,Houzz,https://houzz.com/pro,not-started,,,,,,,,,,,,,,,,,
13,LandBook,https://land-book.com/submit,not-started,,,,,,,,,,,,,,,,,
13,SiteInspire,https://siteinspire.com/submit,not-started,,,,,,,,,,,,,,,,,
13,Awwwards,https://awwwards.com/submit,not-started,,,,,,,,,,,,,,,,,
13,CSS Design Awards,https://cssdesignawards.com/submit,not-started,,,,,,,,,,,,,,,,,
13,BuiltWith,https://builtwith.com/add,not-started,,,,,,,,,,,,,,,,,
13,StoreLeads,https://storeleads.app/submit,not-started,,,,,,,,,,,,,,,,,
13,DevTools,https://devtools.com/submit,not-started,,,,,,,,,,,,,,,,,
13,LibHunt,https://libhunt.com/submit,not-started,,,,,,,,,,,,,,,,,
13,Awesome Lists,https://github.com/sindresorhus/awesome/pulls,not-started,,,,,,,,,,,,,,,,,
13,RapidAPI,https://rapidapi.com/hub/submit,not-started,,,,,,,,,,,,,,,,,
13,APILayer,https://apilayer.com/submit,not-started,,,,,,,,,,,,,,,,,
13,Public APIs,https://github.com/public-apis/public-apis/pulls,not-started,,,,,,,,,,,,,,,,,
13,Papers With Code,https://paperswithcode.com/submit,not-started,,,,,,,,,,,,,,,,,
13,Hugging Face,https://huggingface.co/new,not-started,,,,,,,,,,,,,,,,,
13,ModelScope,https://modelscope.cn/submit,not-started,,,,,,,,,,,,,,,,,
```

---

## Google Sheets Setup Instructions

1. Create new Google Sheet
2. File → Import → Upload the CSV above
3. Add these additional columns for tracking:
   - **Week** (1, 2, 3, Ongoing) — auto-calculate from Submission Date
   - **Priority** (High/Medium/Low) — High for Tier 1-3, Medium for 4-7, Low for 8-13
   - **Owner** — team member responsible
   - **Blocker** — yes/no + description

4. Set up conditional formatting:
   - Status = "live" → Green row
   - Status = "rejected" → Red row
   - Status = "pending-review" → Yellow row
   - Backlink Verified = "no" AND Status = "live" → Orange highlight (action needed)

5. Add filter views:
   - By Tier
   - By Status
   - By Week
   - By Owner

6. Share with team (Viewer access for stakeholders, Editor for executors)

---

## Weekly Review Checklist (Monday)

- [ ] Filter Status = "submitted" or "pending-review" → check for updates
- [ ] Filter Status = "live" AND Backlink Verified = "no" → verify backlinks
- [ ] Filter Week = current week → ensure all planned submissions done
- [ ] Update Referral Traffic and Signups from analytics
- [ ] Move any "rejected" with fixable issues back to "not-started" with notes
- [ ] Plan next week's batch (next 15-20 submissions)

---

## Monthly Review Checklist (1st of month)

- [ ] Export CSV backup
- [ ] Calculate conversion rates per tier (Signups / Referral Traffic)
- [ ] Identify top 5 performing directories → double down
- [ ] Identify bottom 5 (zero traffic after 60 days) → consider removal
- [ ] Check DR changes for key directories (Ahrefs)
- [ ] Update "Notes" with learnings for next launch
- [ ] Share summary with team/stakeholders

# Templates

File and header templates for site launches. Apply per the matrices in `decisions.md`.

## robots.txt

### Template: doc site for OSS lib (allow AI scrapers)

```
User-agent: *
Allow: /

Sitemap: https://EXAMPLE.com/sitemap.xml

# AI scrapers (per decisions.md: doc-site policy)
User-agent: GPTBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: anthropic-ai
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: CCBot
Allow: /

User-agent: Applebot-Extended
Allow: /

# Blocked low-value scrapers
User-agent: Bytespider
Disallow: /

User-agent: Amazonbot
Disallow: /
```

### Template: marketing / lead-gen (block all AI scrapers)

```
User-agent: *
Allow: /

Sitemap: https://EXAMPLE.com/sitemap.xml

# Block all AI scrapers (per decisions.md: marketing policy)
User-agent: GPTBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: Amazonbot
Disallow: /
```

Note: regular search engine crawlers (Googlebot, Bingbot) are not in the AI bot list and remain governed by the `User-agent: *` rule.

---

## llms.txt

Per llmstxt.org spec. Place at root.

```
# Project Name

> One-line description of the project, written for an LLM consumer.

Markdown paragraph giving more context on what the project does, who it's for, and why it exists.

## Docs

- [Getting started](https://example.com/docs/getting-started): how to install and run the first example
- [API reference](https://example.com/docs/api): full API documentation
- [Examples](https://example.com/docs/examples): working code samples

## Optional

- [Changelog](https://example.com/changelog): version history
- [Contributing](https://github.com/owner/repo/blob/main/CONTRIBUTING.md): how to contribute
```

For richer LLM consumption, also publish `llms-full.txt` with the full content of all documentation pages concatenated.

---

## manifest.json

Minimum modern PWA manifest. Place at root or `/manifest.json`.

```json
{
  "name": "Site Full Name",
  "short_name": "Site",
  "description": "One-line description matching meta description.",
  "start_url": "/",
  "display": "standalone",
  "background_color": "#ffffff",
  "theme_color": "#000000",
  "icons": [
    {
      "src": "/web-app-manifest-192x192.png",
      "sizes": "192x192",
      "type": "image/png",
      "purpose": "maskable"
    },
    {
      "src": "/web-app-manifest-512x512.png",
      "sizes": "512x512",
      "type": "image/png",
      "purpose": "maskable"
    },
    {
      "src": "/web-app-manifest-192x192.png",
      "sizes": "192x192",
      "type": "image/png",
      "purpose": "any"
    },
    {
      "src": "/web-app-manifest-512x512.png",
      "sizes": "512x512",
      "type": "image/png",
      "purpose": "any"
    }
  ]
}
```

HTML `<head>` references:

```html
<link rel="icon" href="/favicon.ico" sizes="any" />
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
<link rel="apple-touch-icon" href="/apple-touch-icon.png" />
<link rel="manifest" href="/manifest.json" />
<meta name="theme-color" content="#000000" />
```

---

## CSP templates

Three tightness levels. Pick per the matrix in `decisions.md`.

### `strict-default-src-none`

For doc sites, personal portfolio, SaaS apps with bundled assets only.

```
default-src 'none';
script-src 'self' 'nonce-{NONCE}' https://hogpost.samber.dev;
style-src 'self' 'unsafe-inline';
img-src 'self' data: https:;
font-src 'self' data:;
connect-src 'self' https://hogpost.samber.dev https://eu.i.posthog.com;
manifest-src 'self';
base-uri 'self';
form-action 'self';
frame-ancestors 'none';
object-src 'none';
upgrade-insecure-requests;
```

Notes:

- `style-src 'unsafe-inline'` is unfortunately required by most modern frameworks (Tailwind in dev, styled-components, etc.). Tighten with hashes if feasible.
- Replace `{NONCE}` with a per-request random value generated server-side (Next.js middleware can do this).
- `connect-src` includes `eu.i.posthog.com` as a fallback if `hogpost.samber.dev` proxy is unavailable.

### `balanced-allow-self`

For marketing pages with embeds.

```
default-src 'self';
script-src 'self' 'nonce-{NONCE}' https://hogpost.samber.dev https://www.youtube.com https://assets.calendly.com;
style-src 'self' 'unsafe-inline' https://assets.calendly.com;
img-src 'self' data: https:;
font-src 'self' data:;
connect-src 'self' https://hogpost.samber.dev https://*.calendly.com;
frame-src 'self' https://www.youtube.com https://calendly.com;
frame-ancestors 'none';
object-src 'none';
upgrade-insecure-requests;
```

Adjust embed origins as needed.

### `permissive-for-marketing`

Legacy fallback. Add a TODO comment in the codebase to tighten in the next iteration.

```
default-src 'self' https:;
script-src 'self' 'unsafe-inline' 'unsafe-eval' https:;
style-src 'self' 'unsafe-inline' https:;
img-src 'self' data: https:;
font-src 'self' data: https:;
connect-src 'self' https:;
frame-ancestors 'none';
upgrade-insecure-requests;
```

---

## Full security headers reference

Apply all of these in addition to CSP. Add to Vercel's `vercel.json` or Next.js `next.config.js` `headers()`.

```json
{
  "headers": [
    {
      "source": "/(.*)",
      "headers": [
        {
          "key": "Strict-Transport-Security",
          "value": "max-age=31536000; includeSubDomains; preload"
        },
        { "key": "X-Content-Type-Options", "value": "nosniff" },
        { "key": "X-Frame-Options", "value": "DENY" },
        {
          "key": "Referrer-Policy",
          "value": "strict-origin-when-cross-origin"
        },
        {
          "key": "Permissions-Policy",
          "value": "camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=()"
        },
        { "key": "Cross-Origin-Opener-Policy", "value": "same-origin" },
        { "key": "Cross-Origin-Embedder-Policy", "value": "credentialless" },
        { "key": "Cross-Origin-Resource-Policy", "value": "same-origin" }
      ]
    }
  ]
}
```

Notes:

- `Cross-Origin-Embedder-Policy: credentialless` is safer than `require-corp` for sites with third-party embeds.
- `Permissions-Policy` should enumerate every feature you want to deny, not rely on defaults.

Verify with:

```bash
curl -sI https://example.com | grep -iE 'strict-transport|x-content-type|x-frame|referrer-policy|permissions-policy|cross-origin'
```

---

## Sitemap.xml structure

For multilingual sites, use a sitemap index referencing per-locale sitemaps.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap><loc>https://example.com/sitemap-en.xml</loc></sitemap>
  <sitemap><loc>https://example.com/sitemap-fr.xml</loc></sitemap>
</sitemapindex>
```

Each per-locale sitemap declares `xhtml:link` alternates with `hreflang`:

```xml
<url>
  <loc>https://example.com/en/page</loc>
  <xhtml:link rel="alternate" hreflang="en" href="https://example.com/en/page"/>
  <xhtml:link rel="alternate" hreflang="fr" href="https://example.com/fr/page"/>
  <xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/en/page"/>
</url>
```

---

## TONE.md template

Place at `.agents/TONE.md` or repo root. Fill in based on the user's writing samples and preferences.

```markdown
# Tone of voice: [Site name]

## Audience

- Primary: [e.g., senior Go developers shipping production systems]
- Secondary: [e.g., engineering managers evaluating libraries]
- Reading level: [e.g., technical, no hand-holding]
- Language: [e.g., English, with some French for FR-specific pages]

## Voice

- Direct, dense, no filler.
- Contrarian when warranted.
- Data-grounded: claims need numbers or links.
- Concrete over abstract: prefer "200ms p95" to "fast".
- Assume reader has context, skip primers.

## Forbidden words and patterns

- AI-sounding openers: "In today's fast-paced world", "Let's dive into", "It's worth noting that".
- Vague adjectives: "crucial", "essential", "powerful", "robust", "comprehensive", "seamless", "innovative".
- Empty verbs: "delve into", "leverage", "utilize", "facilitate".
- Hedging: "might potentially", "may possibly", "kind of", "sort of".
- Em dash character ("—") forbidden. Use commas, parentheses, or two sentences.
- Marketing fluff: "game-changing", "revolutionary", "next-generation", "world-class".

## Required patterns

- One concrete example per claim.
- Numbers when possible. Prefer "20% faster" over "much faster".
- Code samples for technical content. Short, runnable, idiomatic.

## Sentence and paragraph rules

- Average sentence length: 12-18 words.
- Max paragraph length: 4 sentences.
- One idea per paragraph.
- Section headers are statements, not questions.

## Good examples (from existing content)

- "Product XYZ hit $1m ARR without paying for ads. The community wants feature-ABC done right."
- "Tool XYZ gives 50× benchmark speedups and 5% production gains. Both numbers are true. Only one matters."

## Bad examples (to avoid)

- "Product XYZ is a powerful, comprehensive productivity tool that leverages documentation to seamlessly empower designers."
- "In today's fast-paced development landscape, choosing the right productivity tool is crucial."

## Address form (FR only)

- `tu` vs `vous` must be chosen deliberately and applied consistently site-wide. Mixed forms on the same site are a copywriting error.
- Default by site type:
  - `doc-site` (OSS lib, developer tools): **tu** — developer community is informal; "vous" feels corporate and creates distance.
  - `SaaS-app` (B2B, enterprise): **vous** — default to formal unless the product targets solo developers or the brand is explicitly casual.
  - `marketing/lead-gen` (consumer-facing): **tu** if the audience is young or tech-savvy; **vous** if the audience is professional or older.
  - `training/paid-course`: **tu** — learning context is personal; "vous" creates unnecessary formality.
  - `personal-portfolio`: **vous** — professional register by default.
- Ask the user explicitly if the default does not fit: "Which address form?" (`tu` | `vous` | `already-specified-in-TONE.md`)
- Record the chosen form in TONE.md under `Address form: tu | vous` and enforce it in every copy review and humanizer pass.

## Localization notes

- FR content: use guillemets « » not quotes, use non-breaking spaces before `: ; ? !`, avoid anglicisms ("faire du sens", "adresser un problème").
- EN content: US spelling.
```

The skill should read TONE.md at the start of any copywriting task and pass its constraints to any delegated copywriting skill. After drafting, run the humanizer in the matching language.

# Weekly SEO maintenance sub-agent

Definition for a scheduled background agent — a subagent or custom agent on any harness (see "Agent definition file" below for the concrete equivalents), such as Hermes or Claude Cowork Routines — that runs weekly post-launch to monitor SEO health and surface action items.

## Setup

1. Copy the agent definition for your harness (see "Agent definition file" below) into the location that harness's block specifies, in the site's repo (or a dedicated ops repo if you manage multiple sites).
2. Confirm the following MCP servers (or equivalent API access) are connected:
   - **Ahrefs MCP** (required, for backlinks and rankings)
   - **PostHog MCP** (required, for traffic correlation)
   - **Google Search Console** (recommended, via community MCP such as `gsc-mcp`; if no MCP, fall back to `curl` with a service account credential file)
   - **Web search** (built-in on most harnesses, for SERP feature checks and competitor monitoring)
3. Confirm the agent has access to the project source code if they apply to the site's content.
4. Schedule weekly execution. Options:
   - Cron running that harness's headless/non-interactive invocation (e.g. `claude --dangerously-skip-permissions -p "/agents weekly-seo"` on Claude Code, `copilot -p "/agent weekly-seo"` on Copilot CLI) — only in a trusted environment
   - The harness's own scheduled/background-agent feature, where one exists (e.g. Claude Cowork, Hermes)
   - GitHub Actions weekly schedule, posting the report to a Slack channel
   - Manual invocation each Monday morning

When MCP servers are not available, fall back to a browser extension or headless browser where the harness supports one, or to direct API calls per the "MCP usage" section in each harness's block below.

## What the agent does

Run all 10 tasks below in one weekly pass. Each task produces a section of the final report.

### 1. Ranking changes (GSC + Ahrefs)

- Pull top 50 queries by impressions for the last 7 days from Google Search Console.
- Compare positions, impressions, clicks, and CTR to the prior 7 days.
- Flag any (page, query) pair that:
  - Dropped more than 5 positions
  - Lost more than 20% impressions
  - Lost more than 30% clicks while position is stable (CTR collapse, often a SERP feature stealing clicks)
- Output: ordered list of (page, query, delta, hypothesis, recommended action).

### 2. Page-2 opportunities (GSC)

- Identify queries ranking positions 11 through 20 with more than 100 impressions in 7 days.
- For the top 5: fetch the current page 1 SERP via `web_search` and compare structure, depth, and recency of the top 3 results to the site's current content.
- Output: content gap analysis with specific edit suggestions (add FAQ section, expand introduction, add benchmark table, etc.).

### 3. New backlinks (Ahrefs MCP)

- Pull new referring domains acquired in the last 7 days.
- Categorize each: high authority (DR > 50), niche relevant (matches site topic), neutral, spam.
- Flag spam links for potential disavow file submission.
- Output: list of new links with category, plus a draft disavow line for any spam.

### 4. Lost backlinks (Ahrefs MCP)

- Pull referring domains lost in the last 7 days.
- For losses from domains with DR > 40 or known niche relevance: draft outreach email asking why and offering to fix any broken links.
- Output: list of lost links plus draft outreach for high-value losses.

### 5. Core Web Vitals drift (GSC + PageSpeed Insights)

- Pull the Core Web Vitals report from GSC (mobile and desktop separately).
- Compare to the prior week.
- Flag any URL group that crossed from "Good" to "Needs improvement" or "Poor".
- For each flagged group: run PageSpeed Insights via `web_fetch` on a representative URL and identify the failing metric (LCP, INP, or CLS) and likely cause.
- Output: list of affected URL patterns with proposed fixes.

### 6. Indexation health (GSC)

- Pull the Page Indexing report.
- Compare "Indexed" and "Not indexed" counts week-over-week.
- For new entries in "Not indexed", group by reason (Discovered not indexed, Crawled not indexed, Excluded by noindex, Soft 404, etc.).
- Output: per-reason summary with recommended fix.

### 7. AI bot traffic (PostHog MCP)

- Query PostHog for sessions where the user agent matches `(GPTBot|ClaudeBot|PerplexityBot|Google-Extended|anthropic-ai|ChatGPT-User|CCBot|Bytespider|Amazonbot)`.
- Compare counts to the prior week, broken down by bot.
- If the site type is `doc-site` and counts are growing: positive signal, surface as a metric.
- If the site type is `marketing/lead-gen` or `paid-course` and any AI bot has nonzero traffic: verify `robots.txt` is actually blocking by fetching `https://example.com/robots.txt` and grepping for the bot. If it should block but isn't, this is a blocker.
- Output: per-bot weekly count with delta, plus blockers if any bot is reaching pages it should not.

### 8. Competitor SERP monitoring

- For the top 5 target keywords (configured per site in a YAML or JSON file the agent reads): capture the current top 3 SERP results via `web_search`.
- Compare to the prior week's snapshot (the agent should persist last week's snapshot).
- Flag new entrants in the top 3 (potential threat) and dropped competitors (potential opportunity).
- Output: per-keyword SERP delta with strategic note.

### 9. Content freshness audit

- List pages older than 6 months (use Git log on the content files, or GSC "Last crawled" date) with declining clicks over the trailing 4 weeks.
- For the top 5 by lost clicks: recommend a refresh priority based on remaining traffic, topic stability, and competitor SERP activity.
- Output: refresh queue with effort estimate.

### 10. Schema and structured data validity

- Sample 5 pages at random plus the homepage.
- For each, extract the JSON-LD via `curl -s URL | grep -A 200 'application/ld+json'`.
- Validate against schema.org by checking required properties for the declared `@type` (the agent has a local rules file or fetches schema.org definitions).
- Output: list of breakages with file path and fix.

### 11. Stats memory snapshot

At the end of every run, append a row to `weekly-seo/memory/stats.csv` (create if missing):

```
date,indexed_pages,clicks_7d,impressions_7d,avg_position,new_backlinks,lost_backlinks,lcp_ms,cls,inp_ms,ai_bot_sessions
```

This builds a longitudinal record the agent can query in future runs for trend analysis (e.g., 4-week rolling average, detecting regressions that don't show up in week-over-week deltas).

Also append to `weekly-seo/memory/keywords.csv` (one row per target keyword per run):

```
date,keyword,position,impressions,clicks,ctr,page_url
```

These two files are the agent's persistent memory. Never truncate or overwrite them. Always append.

### 12. Change log (what worked)

Read `weekly-seo/memory/changelog.md` (create if missing). This file is a running log of **changes applied to the site** and their measured impact.

**On every run:**

1. For each entry in the changelog with `status: pending-validation` and a `measure_after` date that has now passed: pull the relevant metric (rankings, clicks, CWV, etc.) for the affected page or keyword and compare to the baseline recorded at change time. Update the entry with `status: validated` or `status: no-effect`, the measured delta, and a one-sentence conclusion.
2. At the end of the report, emit a **"What worked" section** listing only `validated` entries with positive delta, ordered by impact. This is the institutional memory of SEO wins.

**When instructed to log a change** (user or orchestrator passes a change description):

Append to `weekly-seo/memory/changelog.md`:

```markdown
## YYYY-MM-DD — <short title>

- **Page/scope**: `https://example.com/page` (or "site-wide")
- **Change**: one-sentence description of what was done
- **Hypothesis**: why this should improve the metric
- **Baseline**: clicks=N, position=N, LCP=Nms (snapshot at time of change)
- **Metric to watch**: clicks | position | LCP | CLS | INP | backlinks
- **Measure after**: YYYY-MM-DD (typically 3–4 weeks out)
- **Status**: pending-validation
```

Never delete changelog entries. `no-effect` entries are as valuable as wins — they prevent re-testing the same hypothesis.

## Output format

The agent produces a single Markdown report saved to `weekly-seo/YYYY-MM-DD.md` and (optionally) posted to Slack.

Report structure:

```markdown
# Weekly SEO Report: example.com (YYYY-MM-DD)

## Summary

- Indexed pages: N (delta vs last week)
- Total clicks (7d): N (delta)
- Total impressions (7d): N (delta)
- New backlinks: N | Lost: N
- AI bot sessions: N (delta)

## 🔴 Blockers

[ordered list of items requiring action this week]

## 🟡 Should fix

[ordered list of items worth addressing next sprint]

## 🟢 Opportunities

[ordered list of growth opportunities, e.g., page-2 keywords, competitor weakness]

## 📊 Per-task details

### 1. Ranking changes

### 2. Page-2 opportunities

### 3. New backlinks

### 4. Lost backlinks

### 5. Core Web Vitals drift

### 6. Indexation health

### 7. AI bot traffic

### 8. Competitor SERP monitoring

### 9. Content freshness

### 10. Schema validity
```

## Agent definition file

Same 12 tasks, same `weekly-seo/config.yml`, same memory files, same fallback behavior on every harness below — only the agent-definition schema and file path change. Pick the block matching your harness; none of them is the "real" one. This skill is not exhaustive on harness internals; verify field names against each harness's current docs before relying on them in production.

<details>
<summary>Google Antigravity — place at <code>.agents/agents/weekly-seo.md</code></summary>

[View agent definition](../assets/weekly-seo-antigravity.md)

</details>

<details>
<summary>Claude Code — place at <code>.claude/agents/weekly-seo.md</code></summary>

[View agent definition](../assets/weekly-seo-claude-code.md)

</details>

<details>
<summary>Gemini CLI — place at <code>.gemini/agents/weekly-seo.md</code></summary>

[View agent definition](../assets/weekly-seo-gemini-cli.md)

</details>

<details>
<summary>OpenCode — place at <code>.opencode/agent/weekly-seo.md</code></summary>

[View agent definition](../assets/weekly-seo-opencode.md)

</details>

<details>
<summary>GitHub Copilot CLI — place at <code>.github/agents/weekly-seo.agent.md</code></summary>

[View agent definition](../assets/weekly-seo-copilot-cli.md) — Copilot CLI has no built-in scheduler: invoke it interactively with `/agent weekly-seo`, or trigger it headlessly every Monday via an external cron job running `copilot -p "/agent weekly-seo"`.

</details>

<details>
<summary>Mistral Vibe — place config at <code>.vibe/agents/weekly-seo.toml</code> and prompt at <code>.vibe/prompts/weekly-seo.md</code></summary>

[View config](../assets/weekly-seo-vibe.toml) · [View prompt](../assets/weekly-seo-vibe-prompt.md)

Reads and web access run unattended (`permission = "always"`); writing files and running shell commands ask for confirmation each time (`permission = "ask"`), since those are the two actions this agent could get wrong destructively. If you want fully unattended weekly runs (e.g. scheduled via cron, matching the Claude Code "Cron" option in Setup), raise `write_file` and `run_shell_command` to `"always"` yourself — that's a deliberate trust decision for the operator to make, not a default this doc should set.

</details>

Windsurf, Cursor, and Codex CLI don't have a confirmed, documented custom scheduled-agent-file schema at the time of writing — for those, take the same structure shown above (name, description, tool list, system prompt covering Configuration/Tasks/MCP usage/Output/Tone) and adapt it to whatever custom agent or automation mechanism the harness exposes, then verify against its current docs.

## Config file template

Place at `weekly-seo/config.yml` in the site's repo.

```yaml
domain: example.com
gsc_property: sc-domain:example.com
ahrefs_project_id: 12345
posthog_project_id: 67890
slack_webhook: https://hooks.slack.com/services/...
target_keywords:
  - "keyword one"
  - "keyword two"
  - "keyword three"
  - "keyword four"
  - "keyword five"
site_type: doc-site # or marketing, saas-app, paid-course, portfolio
```

The agent reads this config to scope every task. If the file is missing, the agent asks the user if invoked interactively, or fails with a clear error if invoked headlessly.

---
name: site-launch-checklist
description: "Pre-launch checklist for shipping a new website or web app. Scope: analytics (GA4, PostHog, Google Search Console, Ahrefs), DNS, TLS and backups, legal and CNIL/GDPR compliance, security headers, SEO and GEO (robots.txt, sitemaps, llms.txt, hreflang, schema markup, keyword research), copywriting voice via TONE.md and a humanizer pass, OpenGraph and social previews, favicons and web manifest, Lighthouse, Core Web Vitals and WCAG quality gates, directory submissions, Product Hunt, G2/Capterra reviews, post-launch monitoring. Use when the user says 'checklist for the site', 'ready to ship', 'before I go live', 'ready for prod', 'audit before launch', or asks for a site review, pre-launch audit, or help launching a site or app, deploying a domain to production, or shipping a marketing, docs, SaaS, or lead-magnet site."
license: MIT
compatibility: Designed for Claude Code, Codex or similar harness. Requires internet access for directory submissions, G2/Capterra reviews, and AI citation checks.
user-invocable: true
metadata:
  author: samber
  version: "2.0.1"
  openclaw:
    emoji: "📊"
    homepage: https://github.com/samber/cc-skills
    install:
      - kind: npm
        package: skills
        bins: [skills]
      - kind: brew
        formula: jq
        bins: [jq]
    requires:
      bins:
        - curl
        - npm
        - npx
        - jq
allowed-tools: Read Edit Write Glob Grep Agent AskUserQuestion
---

**Questions:** Ask the user through the environment's question tool — never as plain-text prose. One question at a time, 2–4 tappable options, wait for the answer. If the environment has no question tool, ask in prose with the same options, one at a time.

# Site Launch Checklist

Pre-launch audit and setup workflow for shipping a new website. Opinionated for Cloudflare DNS + Vercel hosting + PostHog + Legal context.

## Interaction style (READ FIRST)

This skill is intentionally interactive. Ask aggressively instead of assuming. The user will tap, not type.

**Always ask these questions at the start of a run** (one at a time, in this order):

1. Site type: `doc-site` | `marketing/lead-gen` | `SaaS-app` | `training/paid-course` | `personal-portfolio`
2. Migration: `greenfield-new-domain` | `migration-need-301-redirects` | `replacing-existing-on-same-domain`
3. Multilingual: `single-locale` | `en` | `fr+en` | `other-multi`
4. PostHog setup: `hogpost.samber.dev` | `set-up-new-proxy` | `skip-PostHog`
5. AI scraper policy: `use-default-for-site-type` | `customize-per-bot` | `block-all`
6. Browser tool available: `claude-chrome-extension` | `playwright` | `neither-skip-browser-checks`

**Ask again at every decision point throughout the phases**, including:

- Whether to install Sentry / BetterStack / Crisp (depends on site type, ask explicitly)
- www vs apex canonical preference (most sites: apex; ask anyway)
- Which AI bots to allow if user chose `customize-per-bot`
- CSP tightness level: `strict-default-src-none` | `balanced-allow-self` | `permissive-for-marketing`
- Whether to skip a phase entirely (e.g., skip Phase 3 if non-FR site)

Never proceed past a decision point without explicit user input. Verbose checklists without checkpoints are not the goal.

**Never install any MCP server or skill without explicit user confirmation.** Always ask via the question tool before running `npx skills add`, `claude mcp add`, or any equivalent install command — even when the skill selection workflow proposes a curated subset.

## How to use this skill

1. Run the start-of-session questions above.
2. Walk the user through phases 1-10 in order. For each phase: a. List items, ask if any should be skipped. b. For each remaining item, run the verification command (see "Verification tools" below). c. Report pass/fail. On fail, ask the user if they want to fix now or queue for later.
3. End with a status report grouped by phase, with blockers, recommended fixes, and optional improvements clearly separated.

## Companion skills

Six skill packs are useful for site launches. **Never install full multi-skill packs**. The actual subset to install is decided at invocation time based on the site type the user confirms.

### Pack inventory

| Pack | What it covers | Typically useful for |
| --- | --- | --- |
| `AgriciDaniel/claude-seo` | SEO + GEO + schema + hreflang + sitemaps audits, parallel sub-agents | All site types |
| `addyosmani/web-quality-skills` | Lighthouse, Core Web Vitals, accessibility, performance, best practices | All site types |
| `trailofbits/skills` | Security audit (OWASP, headers, dependencies) | All site types |
| `aaron-he-zhu/seo-geo-claude-skills` | 20 SEO+GEO skills, CORE-EEAT + CITE frameworks, `/seo:` slash commands | Content-heavy sites, competitive niches |
| `coreyhaines31/marketingskills` | ~30 marketing skills (CRO, copywriting, ads, popups, email, paywalls, etc.) | `marketing/lead-gen`, `SaaS-app`, `training/paid-course` |
| `jonathimer/devmarketing-skills` | 33 developer-marketing skills (persona, docs-as-marketing, technical tutorials, etc.) | `doc-site`, `SaaS-app` for developers |

### Skill selection workflow (run at session start)

After the user confirms site type, for **each pack relevant to that site type**:

1. **List available sub-skills**: `npx skills add owner/repo --list`
2. **Propose a curated subset** based on site type and the phases this skill will execute. Match each phase's needs to specific sub-skills the listing returns.
3. **Confirm with the user.** Use multi-select when the proposed list has more than 3 items, single-select (`install-as-proposed` | `let-me-modify` | `skip-this-pack`) otherwise.
4. **Bulk install the agreed subset**: `npx skills add owner/repo --skill A B C`

Rules:

- Sub-skill names live in the pack, not in this SKILL.md. Always query `--list` for the current state. Pack contents change.
- Never run `npx skills add owner/repo` without `--skill` (that installs everything).
- Site type → packs mapping (which packs to enumerate, sub-skills still selected per workflow):
  - `doc-site`: claude-seo, web-quality-skills, trailofbits, seo-geo-claude-skills, devmarketing-skills
  - `marketing/lead-gen`: claude-seo, web-quality-skills, trailofbits, seo-geo-claude-skills, marketingskills
  - `SaaS-app`: all six
  - `training/paid-course`: claude-seo, web-quality-skills, trailofbits, marketingskills
  - `personal-portfolio`: claude-seo, web-quality-skills, trailofbits, seo-geo-claude-skills (lightweight subset)
- If the user later requests a phase that needs a sub-skill not yet installed, run the workflow again for that single sub-skill rather than re-installing the whole subset.

This avoids importing 80+ skills the user does not need, avoids going stale on sub-skill names, and avoids overfitting to a single pack version.

When delegating during a phase, do not duplicate work this skill orchestrates. Call the specialist with a narrow scope (e.g., "run only the security headers sub-audit on URL X").

## Phase 0: Launch Readiness Gate

**Run this BEFORE any other phase.** Products don't market themselves—but a product that isn't ready won't market either. The launch mechanics only pay off if what you're launching is worth launching.

Two failure modes kill launches from opposite ends:

- **Stealth Mode** — launching too late. "Procrastination in a fancy suit." You keep polishing in private, waiting for the product to be perfect. It never ships, and nobody learns you exist.
- **"Just One More Feature"** — never launching. Every proposed launch date gets pushed for one more thing. The scope creeps forever; the launch never comes.

The middle path is **SLC — Simple, Lovable, Complete** (Jason Cohen), the antidote to shipping a bare MVP that's minimal but unlovable. Don't launch a stub nobody wants; don't wait for a bloated everything-app. A launchable v1 is:

- **Simple** — it does _one_ thing. Not many things poorly. One clear job, done well.
- **Lovable** — people _want_ to use it, not just tolerate it. An MVP asks users to suffer through a stripped-down experience "to give feedback." SLC gives them something they'd choose. If nobody would be sad to lose it, it isn't lovable yet.
- **Complete** — it's a _whole_ experience for that one thing, not a stub with obvious holes. Complete at its chosen scope, not a teaser of a bigger promise.

**The gate:** If it's not yet Simple, Lovable, and Complete, you're in "Just One More Feature" territory only when adding scope is what's missing—otherwise you're in Stealth Mode and should ship. Cut scope until one thing is lovable and complete, then launch that. SLC gives you a real launch now instead of a perfect launch never.

**Quick check before running the phases:**

- [ ] Does it do one clearly-defined thing? (Simple)
- [ ] Would a target user _choose_ to use it, not just endure it? (Lovable)
- [ ] Is that one thing a whole experience, with no glaring stubs? (Complete)
- [ ] Are you polishing past this bar? → Stop. You're in Stealth Mode. Ship.
- [ ] Are you still adding new things to the scope? → Stop. You're in "Just One More Feature." Cut back to SLC.

**Directory submission readiness (from directory-submissions skill):** Ask these 9 questions. If any are "no", they're not ready — help them build the missing piece first.

1. Is the product publicly accessible (no password wall)?
2. Is there a pricing page (even "free while in beta")?
3. Are privacy policy + terms live?
4. Logo assets in PNG + SVG + square + favicon?
5. 5–8 real screenshots + 60–90s demo video?
6. Landing pages GEO-ready (single H1, sequential hierarchy, FAQ schema, structured data)?
7. At least 3 alternative pages and 3 use-case pages live and indexed?
8. Template gallery or lead magnet asset (if applicable to category)?
9. At least 20 beta/early users who could leave a review on G2?

A "no" on any of 1–7 is a hard block. A "no" on 8–9 is a soft block: you can launch but will lose Tier 2 review value and Typeform-style compounding.

**ORB Channel Strategy (from launch skill):** Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.

### Owned Channels

You own the channel (though not the audience). Direct access without algorithms or platform rules.

- Email list, Blog, Podcast, Branded community (Slack, Discord), Website/product
- **Start with 1-2 based on audience:** Industry lacks quality content → Blog; People want direct updates → Email; Engagement matters → Community

### Rented Channels

Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.

- Social media (Twitter/X, LinkedIn, Instagram), App stores, YouTube, Reddit
- **How to use correctly:** Pick 1-2 platforms where your audience is active; Use them to drive traffic to owned channels; Don't rely on them as your only strategy

### Borrowed Channels

Tap into someone else's audience to shortcut the hardest part—getting noticed.

- Guest content (blog posts, podcast interviews, newsletter features)
- Collaborations (webinars, co-marketing, social takeovers)
- Speaking engagements (conferences, panels, virtual summits)
- Influencer partnerships
- **Be proactive:** List industry leaders your audience follows → Pitch win-win collaborations → Use tools like SparkToro or Listen Notes to find audience overlap

Pass the gate, then run the phases below.

## Copywriting voice and humanizer pass

Every site has visible marketing copy (hero, features, CTAs, meta descriptions, OG descriptions, blog posts, 404 page text). Two layers of polish are mandatory before launch:

### 1. Define `TONE.md` once per site

Ask the user: "Does this site already have a `TONE.md`?" (`yes-already-exists` | `no-create-from-template` | `skip-use-default`).

If creating: write it to `.agents/TONE.md` or repo root `TONE.md`. See `references/templates.md` (section "TONE.md template") for the structure.

TONE.md specifies: voice (terse, contrarian, etc.), forbidden patterns (e.g., "delve", "crucial", em dashes, AI-sounding openers), sentence length preference, audience reading level, examples of good and bad sentences from the user's own writing.

### 2. Run a humanizer pass in the matching language

After every drafting step (whether by a copywriting skill, by hand, or by Claude directly), run a humanizer to strip AI patterns.

Ask the user for the site's primary audience language at the start of the session if not already known:

- `english-global` → `npx skills add https://github.com/blader/humanizer --skill humanizer`
- `french` → use `samber/cc-skills@humaniseur-fr` (custom French humanizer) or equivalent French-tuned skill
- `other` → install matching humanizer if available; otherwise the skill writes a short language-specific anti-pattern checklist inline

Apply the humanizer to: hero copy, feature descriptions, CTA buttons, meta descriptions, OG/Twitter card descriptions, blog posts, email signup confirmations, 404 page text. Skip for legal pages (mentions légales, CGV) since they have rigid wording requirements.

### 3. Always reference TONE.md when invoking copywriting skills

When delegating to any copywriting or content-writing sub-skill (selected at invocation per the skill selection workflow), include `TONE.md` in the prompt context. Pass voice constraints explicitly: "Follow `.agents/TONE.md`. Avoid the listed patterns. Apply the humanizer after drafting."

## Browser interaction preference

Many checks require a real browser (Lighthouse runs, securityheaders.com scan, opengraph.xyz validation, Twitter card validator, mobile viewport, screen reader smoke, Network tab inspection).

**Always prefer the Claude Chrome extension.** Fall back to Playwright only if the Chrome extension is unavailable. If neither is available, ask the user whether to skip browser checks entirely or wait until they enable one.

## Verification tools

Most checks are doable from the command line without third-party services. Use these tools inline at every phase. Don't trust panels in Cloudflare/Vercel/Google dashboards alone, verify with curl.

**DNS (Phase 1):**

```bash
dig +short A example.com                          # A record
dig +short AAAA example.com                       # AAAA (IPv6)
dig +short MX example.com                         # MX (mail)
dig +short TXT example.com                        # SPF + verification TXT
dig +short TXT _dmarc.example.com                 # DMARC
dig +short TXT default._domainkey.example.com     # DKIM (selector varies)
dig +short CAA example.com                        # CAA
dig +dnssec example.com | grep RRSIG              # DNSSEC active
```

**TLS / HTTPS (Phase 1):**

```bash
curl -sIL https://example.com | head             # follow redirects
curl -sI https://www.example.com                 # check www handling
openssl s_client -showcerts -connect example.com:443 < /dev/null 2>/dev/null | openssl x509 -noout -dates
```

**Headers (Phase 4):**

```bash
curl -sI https://example.com | grep -iE 'content-security-policy|strict-transport-security|x-frame-options|x-content-type-options|referrer-policy|permissions-policy'
# Full header dump:
curl -sI https://example.com
# External graders:
curl -s "https://api.securityheaders.com/?q=https://example.com&followRedirects=on&hide=on" -I | grep -i 'x-grade'
```

**SEO files (Phase 5):**

```bash
curl -s https://example.com/robots.txt
curl -sI https://example.com/sitemap.xml
curl -s https://example.com/sitemap.xml | head -40
curl -s https://example.com/llms.txt
# Schema (JSON-LD):
curl -s https://example.com/ | grep -A 50 'application/ld+json'
# hreflang:
curl -s https://example.com/ | grep -i hreflang
```

**Open Graph & social (Phase 6):**

```bash
curl -s https://example.com/page | grep -iE 'og:|twitter:|<title|name="description"'
```

**Favicons & manifest (Phase 7):**

```bash
curl -sI https://example.com/favicon.ico
curl -sI https://example.com/favicon.svg
curl -sI https://example.com/apple-touch-icon.png
curl -s https://example.com/manifest.json | jq .
```

**404 / 500 / redirects:**

```bash
curl -sI https://example.com/this-does-not-exist
curl -sIL https://example.com/old-url     # verify 301 chain
```

Always run the relevant command, paste the output to the user when reporting, then ask whether to fix immediately or queue.

---

## Phase 1: Domain & Infrastructure

Most of this is one-click via Cloudflare's dashboard if the domain is on Cloudflare.

Ask first: "Is the domain already on Cloudflare with the standard config from previous launches?" (`yes-standard` | `yes-needs-review` | `no-fresh-setup`)

Checklist:

- [ ] Cloudflare: proxy ON for apex + www, TLS 1.3 minimum, "Always Use HTTPS" enabled, HSTS preload enabled in Cloudflare SSL/TLS settings
- [ ] DNS A/AAAA or CNAME pointing to Vercel (verify with `dig +short A example.com`)
- [ ] MX records for Google Workspace (verify with `dig +short MX example.com`)
- [ ] SPF, DKIM, DMARC records (verify all 3 with the dig commands above)
- [ ] CAA records restricting cert issuance (verify with `dig +short CAA example.com`)
- [ ] DNSSEC enabled at registrar level (verify with `dig +dnssec`)
- [ ] Vercel: project linked to repo, prod + preview env vars set, custom domain attached, prod and preview aliases correct
- [ ] Decide www vs apex canonical, configure 308 redirect for the non-canonical (verify with `curl -sIL https://www.example.com`)
- [ ] Custom 404 page renders (verify with `curl -sI https://example.com/does-not-exist`)
- [ ] Custom 500 page exists (cannot easily verify without forcing an error, ask user)
- [ ] If migration: 301 redirect map for every old URL (loop verification with `curl -sIL` per URL)

### Backups

If you don't configure backups at launch, you never will. Do it now.

Ask the user: "Which data stores does this app write to?" (`database-only` | `database-plus-file-storage` | `file-storage-only` | `stateless-no-persistent-data`). If `stateless-no-persistent-data`, skip this section.

**Database:**

- [ ] Automated daily backups enabled at the provider level (Neon, Supabase, PlanetScale, Railway, RDS — each has a one-click toggle). Verify by opening the backup panel and confirming the last backup timestamp is recent.
- [ ] Retention policy set to ≥30 days
- [ ] Point-in-time recovery (PITR) enabled if available (Neon, Supabase, RDS all support it)
- [ ] Off-site copy: if the provider stores backups in the same region as the primary, configure cross-region replication or a nightly export to a separate storage account (S3, R2, GCS)
- [ ] **Restore drill performed before launch**: pick a recent backup, restore to a staging database, verify row counts and a sample query. A backup you haven't tested is not a backup.

**File storage (if applicable — S3, R2, GCS, Cloudflare Images):**

- [ ] Versioning enabled on the primary bucket
- [ ] Cross-region replication or a scheduled sync to a secondary bucket. Backblaze B2 is a cheap, reliable option for off-site copies (significantly cheaper than S3/GCS egress). Use `rclone` to sync from S3/R2/GCS → B2 on a daily cron.
- [ ] Lifecycle rule: transition old versions to cheaper storage after 30 days, delete after 90 days (adjust to cost tolerance)

**Secrets / environment variables:**

- [ ] All env vars documented and stored in a secrets manager (1Password, Doppler, Vault, or equivalent). Not in a `.env` file on someone's laptop.
- [ ] Verify: if every engineer's machine burned tonight, could a new team member restore prod from scratch using only the secrets manager + git?

**Monitoring:**

- [ ] Set up an alert (email or Slack) if the daily backup job fails. Most providers support this natively; configure it before closing the backup panel.

---

## Phase 2: Analytics & Observability

Most third-party integrations are one-click via Cloudflare or Vercel.

**For the conditional tools (Crisp, Sentry, BetterStack), ask the user** to confirm per site type. See `references/decisions.md` for the observability tier matrix.

**Always-on:**

- [ ] Google Analytics 4: property created, measurement ID embedded, gated behind CNIL consent
- [ ] PostHog: based on user's earlier answer:
  - If `hogpost.samber.dev`: configure client with `api_host: "https://hogpost.samber.dev"` and verify CORS allows the new domain (test with browser console or `curl -H "Origin: https://newsite.com" -I https://hogpost.samber.dev/decide`)
  - If `set-up-new-proxy`: add path rewrite in `next.config.js` to `us.i.posthog.com` and `us-assets.i.posthog.com`, init client with `api_host: "/ingest"`
  - If `skip-PostHog`: skip
- [ ] Google Search Console: site verified (DNS TXT or HTML file), sitemap submitted
- [ ] Bing Webmaster Tools: site verified, sitemap submitted, IndexNow key file at `/{key}.txt` on root (verify with `curl -sI https://example.com/{key}.txt`)
- [ ] Ahrefs: site added to dashboard for tracking
- [ ] Add the site to the internal stats spreadsheet (PostHog properties registry + GitHub Sponsors tracking sheet if applicable)

**Brand monitoring (Google Alerts):**

For each alert, use these settings: **Frequency**: once a day | **Sources**: Automatic | **How many**: All results | **Region**: Any region

Set up one alert per keyword via alerts.google.com:

- [ ] Domain name (e.g., `example.com`)
- [ ] Brand or product name (quoted if multi-word, e.g., `"My Brand"`)
- [ ] Key feature or library names if the site documents a project
- [ ] Competitor brand names (optional — ask user: `yes-monitor-competitors` | `skip`)

Ask the user: "Which additional keywords to monitor?" (`product-name-only` | `domain-plus-brand` | `full-set-with-competitors` | `custom-list`)

**Developer community monitoring (F5bot) — for `doc-site` and `SaaS-app` targeting developers:**

F5bot (f5bot.com) monitors Reddit, Hacker News, and Lobste.rs for keyword mentions and sends email alerts. Free, no API required.

Set up one keyword per line at f5bot.com/add:

- [ ] Brand or product name
- [ ] Domain name (catches link shares)
- [ ] Key feature or library names
- [ ] Common misspellings if applicable

**Competitor analysis (`marketing/lead-gen`, `SaaS-app`, `training/paid-course` only):**

Before writing copy, setting up ads, or planning content, run a competitor analysis to understand what is already working in the market — positioning, messaging angles, CTA patterns, pricing presentation, and content strategy.

Use a deep research tool or a competitor analysis skill if one is available in the toolchain. Ask:

- "Do you already have competitor names/URLs to analyze?" (`yes-provide-list` | `no-discover-for-me` | `skip`)
- If `yes-provide-list`: ask the user to paste 2-5 names or URLs (free text)
- "What are we looking to extract?" (`positioning-and-messaging` | `pricing-strategy` | `content-and-seo` | `full-spectrum`)

Feed the output into:

- Phase 5 keyword strategy (target queries they rank for but you can outrank or flank)
- `TONE.md` voice calibration (deliberately differentiate from the dominant tone in the category)
- Phase 6 OG copy and CTA language (borrow proven frames, don't clone verbatim)
- Copywriting sub-skills invoked later (pass the competitor snapshot as context)

**Conditional (ask user, default per site type from `references/decisions.md`):**

- [ ] Crisp
- [ ] Sentry
- [ ] BetterStack

---

## Phase 3: Legal & Compliance (FR)

Ask first: "Is this site subject to French law?" (`yes-FR-operator-or-audience` | `no-EU-only` | `no-non-EU`). If no, ask whether GDPR or equivalent applies and adjust.

For FR sites:

- [ ] Mentions légales page (mandatory, fines up to 75k€ per omission)
- [ ] CGV (Conditions Générales de Vente) if commercial activity
- [ ] Privacy policy
- [ ] Terms of service
- [ ] CNIL-compliant cookie consent that **gates** GA4, PostHog, Crisp, Sentry script loading (not just a banner that always loads trackers). Use a CMP (Axeptio, Tarteaucitron, or custom). Verify with browser Network tab: no tracker fires before explicit consent.

---

## Phase 4: Security

Delegate the deep audit to `trailofbits/skills`. The items below are the must-pass checklist.

Ask first: CSP tightness level (`strict-default-src-none` | `balanced-allow-self` | `permissive-for-marketing`). See `references/templates.md` for the CSP template per level.

- [ ] CSP: target chosen tightness level. No `'unsafe-inline'` for scripts (use nonces). Verify with `curl -sI ... | grep -i content-security-policy`.
- [ ] HSTS: `max-age=31536000; includeSubDomains; preload`. Submit to hstspreload.org. Verify with `curl -sI ... | grep -i strict-transport`.
- [ ] X-Frame-Options: `DENY`
- [ ] X-Content-Type-Options: `nosniff`
- [ ] Referrer-Policy: `strict-origin-when-cross-origin`
- [ ] Permissions-Policy: deny camera, microphone, geolocation, payment unless used
- [ ] Run all headers in one go: `curl -sI https://example.com | grep -iE 'content-security|strict-transport|x-frame|x-content-type|referrer-policy|permissions-policy'`
- [ ] securityheaders.com: target A+ (verify via Claude Chrome extension or `curl https://securityheaders.com/?q=URL` and parse)
- [ ] observatory.mozilla.org: target 90+ (via Chrome extension)
- [ ] Run `trailofbits/skills` security audit on the codebase
- [ ] Verify no leaked secrets in client bundle: open Chrome DevTools Network tab via Claude Chrome extension, grep response bodies for `sk_`, `pk_`, `AKIA`, `ghp_`, `Bearer`

---

## Phase 5: SEO & GEO

Delegate the full audit to `AgriciDaniel/claude-seo`. The items below are the orchestration list.

See `references/templates.md` for `robots.txt`, `llms.txt`, and `manifest.json` templates. See `references/decisions.md` for the AI scraper policy matrix by site type.

- [ ] `/robots.txt` present, references sitemap (verify with `curl -s https://example.com/robots.txt`)
- [ ] `/sitemap.xml` present, valid (verify with `curl -s https://example.com/sitemap.xml | head -40`). Sitemap-index with per-language sitemaps if multilingual.
- [ ] `/llms.txt` present (per llmstxt.org spec, verify with `curl -s https://example.com/llms.txt`)
- [ ] AI scraper policy encoded in `robots.txt`. Apply the matrix from `references/decisions.md` based on site type, then **ask via the question tool to confirm each non-default decision** — this ships in a public file, get it right before it's crawled.
- [ ] Schema markup (JSON-LD): `Organization` + `WebSite` + `BreadcrumbList` site-wide; per-page types where applicable (`SoftwareApplication` for lib homepages, `Article` for blog posts, `FAQPage` for FAQs, `Person` for author bio). Verify with `curl -s URL | grep -A 50 'application/ld+json'`. Validate structured data via **Google Rich Results Test** (<https://search.google.com/test/rich-results>) and **Schema.org Validator** (<https://validator.schema.org>) — Rich Results Test checks eligibility for rich snippets; Schema.org Validator catches spec violations that Google may silently ignore.
- [ ] Meta tags per page: unique `<title>` (50-60 chars), unique `<meta description>` (150-160 chars), `<link rel="canonical">`, `<meta name="robots">` if needed
- [ ] `hreflang` tags on every page if multilingual (every language version declares all alternates including self). Verify with `curl -s URL | grep -i hreflang`.
- [ ] **Keyword analysis using both Google Trends and Ahrefs** (they answer different questions, not interchangeable):
  - **Google Trends** (trends.google.com): trajectory (rising vs declining), geographic distribution (especially FR vs international split), seasonal patterns, related queries breakout, head-to-head comparison of 2-5 candidate keywords. Use Trends to **validate direction and timing** of the SEO bet.
  - **Exploding Topics** (explodingtopics.com): surfaces emerging trends weeks or months before they peak in Google Trends. Use to identify rising queries before competition solidifies and to validate that target keywords aren't already on the decline.
  - **Answer The Public** (answerthepublic.com/en): maps search questions, comparisons, and related queries around a seed keyword. Use to uncover long-tail intent clusters, populate FAQ schema, and identify content gaps.
  - **Ahrefs Keywords Explorer**: monthly volume, keyword difficulty, SERP analysis, CPC, parent topic, traffic potential. Use Ahrefs to **size the opportunity** in absolute terms.
  - Combined output: a ranked shortlist of 3-5 target queries per page, with rationale (volume × difficulty × trajectory × intent match).
  - Delegate to whichever keyword-research sub-skill was installed at session start (selected from the installed packs via the skill selection workflow; typical sources are the SEO+GEO and marketing packs).
- [ ] **AI visibility audit via productrank.ai**: open productrank.ai in a browser, submit multiple category or product searches, run the full AI SEO report. It audits how the site appears in AI-generated answers (ChatGPT, Perplexity, Gemini, Claude). Flag any zero-visibility categories and surface content gaps the AI graders identify.
- [ ] Typo and grammar pass on all visible text content
- [ ] Backlink profile audit: run **Ahrefs Backlink Checker** and **Moz Link Explorer** to assess domain authority and surface toxic or broken inbound links before launch — especially critical on migrations to ensure old-domain equity transfers correctly
- [ ] Internal linking audit: every important page reachable in ≤3 clicks from the homepage

**Destination Pages Strategy (from directory-submissions skill):** Directories are useless if the backlinks land on a generic homepage. Build these destination pages _before_ submitting to directories:

### 1. Alternative pages (highest ROI)

Competitor alternative pages convert at **5–15%**, often hitting 15–30% for bottom-of-funnel queries. One page per top competitor:

- `/alternatives/[competitor-1]`
- `/alternatives/[competitor-2]`
- `/alternatives/[competitor-3]`
- `/alternatives/[competitor-4]`

Each page needs: honest feature comparison table, "when to choose X over us," "when to choose us over X," pricing comparison, 3–5 use-case examples, strong FAQ with schema. **Critical:** Be honest. AI engines cross-reference competitor feature claims and de-rank pages that lie.

### 2. Use-case / ICP pages

Every ICP gets a dedicated landing page:

- `/for/[audience]` — coaches, agencies, ecommerce, SaaS, consultants, etc.
- `/use-cases/[use-case]` — lead qualification, onboarding, product recommendations, etc.

### 3. Template / asset gallery (if applicable)

Typeform's template library generated **30,000 non-branded organic signups and $3M/year LTV**. The pattern:

- One indexable page per template at `/templates/[slug]`.
- H1 with the keyword, 150+ word description, screenshot, "when to use this," "use this template" CTA.
- Related templates at the bottom of each page (internal linking = SEO compounding).
- 100 templates by day 30, 300 by day 90 is the realistic target.

### 4. "Best of" listicles you wrote yourself

Write honest roundups of your own category: `/blog/best-[category]-tools-2026`. Include yourself + 10 competitors with real reviews. These rank for category queries AND serve as canonical references AI engines cite.

### 5. Integration pages (when integrations ship)

Every integration = one landing page at `/integrations/[partner]`. Follows the Zapier playbook: Zapier gets **~2.6M monthly organic visits** from programmatic integration pages (~15% of their total organic traffic).

**GEO (Generative Engine Optimization):** In 2026, 30–50% of "research a tool" queries happen inside ChatGPT, Claude, Perplexity, or Google AI Overviews without ever touching a traditional search page.

### Tactics that get pages cited

1. **One H1 per page, sequential heading hierarchy.** 2.8× higher citation rate. 87% of cited pages use a single H1.
2. **Dense, factual content with citable stats.** AI engines prefer specific numbers ("3× faster than X") over vague claims.
3. **FAQ schema on every landing page.** AI engines heavily weight `FAQPage` JSON-LD for answer extraction.
4. **Comparison tables.** Extractable, structured — exactly what an AI answer needs.
5. **Explicit "what it is" paragraph in the first 100 words.**
6. **Get cited on Reddit and Hacker News.** Claude and Perplexity index these heavily. Genuine mentions on r/SaaS and HN count as training fuel.
7. **Publish original research.** "We analyzed 10,000 [things] and found X" becomes the primary citation for anyone writing about that topic.
8. **Claim Crunchbase, LinkedIn company page, and Wikidata entries.** All three feed AI training corpora.
9. **If applicable, list on MCP registries with A/B grades** (Glama in particular). LLMs pull from these when answering MCP questions.

### Measurement

Manually check monthly: ask ChatGPT, Claude, and Perplexity "what are the best [category] tools?" and log where the product appears. Free GEO tracking tools (GeoTracker, llmrefs) automate this.

---

## Phase 6: Open Graph & Social Preview

Verify all OG and Twitter tags with: `curl -s URL | grep -iE 'og:|twitter:'`

- [ ] `og:title`, `og:description`, `og:url`, `og:type`, `og:site_name`
- [ ] `og:image` 1200×630px, absolute URL, `og:image:width` and `og:image:height` declared, `og:image:alt` set
- [ ] **Per-page `og:image`**, not one global. For doc sites: generate dynamically from page title. For blog posts: per-article custom image.
- [ ] `og:locale` + `og:locale:alternate` for each language if multilingual
- [ ] Twitter Cards: `twitter:card=summary_large_image`, `twitter:title`, `twitter:description`, `twitter:image`, `twitter:site` (handle)
- [ ] Validate with opengraph.xyz (covers FB, LinkedIn, Slack, Discord, WhatsApp previews) via Claude Chrome extension
- [ ] Validate with Twitter's card validator
- [ ] Manual check: paste URL in a LinkedIn DM, a Slack channel, a Discord, an iMessage. Preview must render correctly in all.

---

## Phase 7: Favicons & Web Manifest

See `references/templates.md` for the `manifest.json` template.

Generate from a single 1024×1024 source PNG using realfavicongenerator.net or favicon.io.

**Minimum modern set:**

- [ ] `/favicon.ico` (multi-res 16/32/48). Verify with `curl -sI https://example.com/favicon.ico`.
- [ ] `/favicon.svg` with embedded `<style>@media (prefers-color-scheme: dark) { ... }</style>` for dark mode. Verify with `curl -sI https://example.com/favicon.svg`.
- [ ] `/favicon-96x96.png` (PNG fallback)
- [ ] `/apple-touch-icon.png` 180×180px, no transparency, opaque background. Verify with `curl -sI`.
- [ ] `/web-app-manifest-192x192.png` (Android PWA icon)
- [ ] `/web-app-manifest-512x512.png` (Android splash)
- [ ] `/manifest.json` referencing both PNGs, with `theme_color`, `background_color`, `name`, `short_name`, `display`. Verify with `curl -s https://example.com/manifest.json | jq .`.

**Skip (deprecated):**

- `mstile-*.png` (Windows tiles)
- `safari-pinned-tab.svg` (deprecated since macOS Big Sur)
- `favicon-16x16.png` / `favicon-32x32.png` (covered by `.ico` and `.svg`)

**HTML head verification:**

```bash
curl -s https://example.com/ | grep -iE 'rel="icon"|rel="apple-touch-icon"|rel="manifest"'
```

---

## Phase 8: Quality Gates

Delegate to `addyosmani/web-quality-skills`. The skill covers 150+ Lighthouse audits across performance, accessibility, SEO, and best practices.

- [ ] **Unlighthouse site-wide crawl**: `npx unlighthouse --site {site}` — crawls all pages and runs Lighthouse on each. Surface pages below 90 on any axis before the per-URL checks.
- [ ] Lighthouse all 4 axes, mobile mode: target ≥90 on each (perf, a11y, best practices, SEO)
- [ ] Lighthouse all 4 axes, desktop mode: target ≥95 on each
- [ ] Core Web Vitals field data (CrUX via PageSpeed Insights): LCP < 2.5s, INP < 200ms, CLS < 0.1, on both mobile and desktop
- [ ] Accessibility (WCAG 2.2 AA via `web-quality-skills`): keyboard nav works for every interactive element, focus rings visible, color contrast ≥4.5:1 for text, all images have `alt`, heading hierarchy is monotonic (H1 → H2 → H3), ARIA labels on icon-only buttons
- [ ] Real mobile device test (not just devtools emulator). Use Claude Chrome extension on mobile viewport on a real device or BrowserStack.
- [ ] Cross-browser smoke test: Chrome, Safari, Firefox latest stable
- [ ] Print stylesheet sanity (Cmd+P should not break layout)

---

## Phase 9: Ecosystem Cross-linking

Internal cross-linking between owned properties. High-leverage SEO action for any multi-domain owner.

Ask the user: "List the other domains in your ecosystem that are topically relevant to this new site." Then for each one:

- [ ] Add a link from the existing site (footer / nav / "other projects" section) to the new site, where topically relevant
- [ ] Add a link to the new site in the README of the matching GitHub repo, if it documents a library
- [ ] Verify reciprocal links: every link added points back where appropriate
- [ ] If the new site documents a Go lib, link from related lib docs

Do not over-link. Only cross-link where topically relevant. A doc site for a logging lib should not link to a personal blog about cycling.

---

## Phase 10: Set up weekly SEO maintenance sub-agent

After launch, set up a scheduled background agent, such as Hermes or Claude Cowork Routine, that runs weekly to monitor SEO health and surface action items.

See `references/weekly-seo-agent.md` for the full agent definition, with a concrete equivalent for each harness — copy the block matching your environment into the location it specifies, in the site's repo (or a dedicated ops repo). The agent uses these MCP connectors (or their equivalent API calls):

- Ahrefs MCP (backlinks, rankings, keywords)
- PostHog MCP (analytics correlation, AI bot traffic)
- Web search (SERP monitoring, competitor checks)
- Google Search Console (via community MCP or `curl` with service account credentials)

**Ask via the question tool** before creating the file: "Set up the weekly SEO agent now?" (`yes-create-agent-file` | `yes-but-defer` | `skip-for-now`).

When MCP are not available, use Claude for Chrome extension.

---

## Phase 11: Directory Submission Execution

Execute the directory submission workflow from the `directory-submissions` skill. This is the foundation layer of distribution — never the whole strategy.

### Step 1: Choose the tiers (from references/directory-list.md)

| Tier | When | Examples | Typical count |
| --- | --- | --- | --- |
| **Tier 1 — Flagship launch** | Launch week only | Product Hunt (anchor), BetaList, HN Show HN, Fazier, DevHunt | ~15 |
| **Tier 2 — Startup/SaaS** | Week 1 + rolling | AlternativeTo, SaaSHub, G2, Capterra, F6S, SourceForge, Slashdot | ~50 |
| **Tier 3 — AI directories** | Week 1–3 | TAAFT, Futurepedia, Toolify, Future Tools, aitools.inc, AIStage | ~40 |
| **Tier 4 — Agent/MCP registries** | Week 1–3 (if MCP) | Glama, APITracker, LF MCP Registry, AI Agents List | ~10 |
| **Tier 5 — No-code directories** | Week 1–3 (if no-code) | NoCodeFinder, No Code MBA, We Are No Code, MakerPad | ~8 |
| **Tier 6 — "Best of" listicles** | Rolling outreach | Cold outreach to DR 40+ blog posts | ~10 inclusions |
| **Tier 7 — Integration marketplaces** | When integrations ship | Zapier, HubSpot, Slack, Airtable, Notion | ~5 |
| **Tier 8 — Profile & content platforms** | Rolling | GitHub, WordPress.com, Substack, Dev.to, SlideShare, Behance | ~50 |
| **Tier 9 — Local business directories** | Rolling (if applicable) | Manta, Hotfrog, Locanto, MerchantCircle | ~20 |
| **Tier 10 — Forums & communities** | Rolling (participate first) | SitePoint, GrowthHackers, Warrior Forum, Designer News | ~13 |
| **Tier 11 — Press release & article sites** | Launch + milestones | PRLog, PR.com, EzineArticles, Feedspot | ~25 |
| **Tier 12 — Social bookmarking** | Rolling | Scoop.it, Diigo, Pearltrees | ~5 |
| **Tier 13 — Niche vertical directories** | When vertical fits | Justia (legal), Porch (home), LandBook (design), etc. | ~20 |

**Triage rule:** Only submit where the product is a genuine fit. Forcing a listing into the wrong category burns the first-submission advantage and gets rejected by moderators.

### Step 2: Prepare asset variations per tier

For each tier, prep a distinct description variant (from `references/positioning-variations.md`):

- **Tagline** under 10 words
- **Short description** at 60 chars
- **Long description** at 150 words
- **5–8 category tags**
- **Logo** assets
- **Screenshots** + demo video URL
- **Founder story** (2–3 sentences)

**Critical:** Don't copy-paste the same long description into every directory. Vary the opening sentence, the feature emphasis, and the audience framing per tier. AI engines cross-reference and down-weight duplicate content.

### Step 3: Batch submit with tracker

Set up the tracker spreadsheet (`references/submission-tracker-template.csv`). Work left-to-right through it. 2–3 hours per batch is realistic.

Per submission:

1. Copy the tier-appropriate positioning variant.
2. Fill in the form.
3. Upload assets.
4. Submit.
5. Log: date, URL, status, moderator notes.
6. Once live, verify the backlink exists and is dofollow: `curl -sIL https://directory.com/your-listing | grep -i rel=`. If absent, the link is dofollow.

---

## Phase 12: Product Hunt Deep Dive (The Anchor Event)

Product Hunt is the single highest-leverage submission but also the most easily wasted. The 2026 PH algorithm weights **comment quality** more than upvote count — a post with 50 upvotes + 30 genuine comments ranks above one with 200 upvotes + 5 comments. **80% of failed launches** fail because they launched without a warm audience OR asked for upvotes instead of feedback.

### 3-week prep timeline

- **Day -21 to -14:** Warm up hunter account. Upvote + thoughtfully comment on 3 launches/day. Follow 100+ active makers. Build history so your account looks real to the algorithm.
- **Day -14:** Create "Upcoming" page on PH. Drive traffic to it to collect "notify on launch" subscribers.
- **Day -10:** (Optional) book a hunter. Don't pay cash — trade a feature, shoutout, or intro. A known hunter adds ~15% to day-one momentum but isn't required.
- **Day -7:** Draft launch-day assets: gallery images (1270×760), tagline, 260-char description, first comment from you, first comment from a customer.
- **Day -3:** Email list warm-up. "We're launching Tuesday. Here's what to expect. Reply if you want a heads up."
- **Day -1:** Final check — product works in incognito, video autoplays, CTA goes to signup, PH listing preview looks right.

### Launch day execution

- **Launch at 12:01 AM Pacific Time.** Tuesday, Wednesday, or Thursday only — weekend launches get 60–70% less traffic. The 12:01 AM PT start maximizes your 24-hour window.
- **First 2 hours are everything.** Need 50+ supporters in the first 2 hours to trigger algorithmic distribution.
- **Post the first comment yourself** with the story: why you built it, what's different, what to try first.
- **Reply to every comment** in under 30 minutes. PH measures maker responsiveness.
- **Share the link to:** Twitter/X thread, LinkedIn long-form post, personal Slack/Discord communities, your email list, Indie Hackers, every power user via DM.
- **Never ask for upvotes.** Ask for **feedback**. "Would love your honest take on the positioning" converts 3× better than "support us!" and doesn't trigger the algorithm's anti-manipulation filters.
- **Don't message strangers.** The community flags this and moderators will hide your post.

### Post-launch

- Write a launch recap blog post with numbers + lessons. Honest, not bragging. Publish on day 2.
- Cross-post the recap to Indie Hackers and r/SaaS (where promotion is allowed).
- Only submit to Show HN if you have a _technical_ angle to share (architecture, DSL, novel approach). A generic "we launched a SaaS" post will get flagged to death.

---

## Phase 13: Reviews Playbook (G2 / Capterra / TrustRadius)

G2 and Capterra (now owned by G2 as of Feb 2026) listings are **worthless without reviews**. 10 reviews is the magic threshold for Grid appearance. Run the 10-in-30 protocol during launch month.

### The 10-in-30 protocol

1. **Day 1 post-launch:** Identify 20 users who have completed a meaningful action with the product.
2. **Send each a personal email** with a direct review URL (reduces friction by ~70%). No forms, no landing pages — direct link.
3. **Offer a modest thank-you.** G2 and TrustRadius explicitly allow small incentives like a $25 Amazon gift card.
4. **Follow up once** after 5 days. Don't follow up twice — it becomes annoying and damages the relationship.
5. **Target:** 50% conversion → 10 reviews from 20 asks.

### Critical deadlines

- **G2 Summer reports:** cut off ~April 28. Plan review drives to land before this.
- **G2 Fall reports:** cut off ~July 28.
- Missing a cutoff means waiting 3 months for the next grid update.

### Badges and paid plans

- **"Users Love Us" badge** is still free: requires 20 reviews at 4.0+ average.
- **Grid, Momentum, Index, and Award badges** require a paid G2 plan ($2,999+/year starting Summer 2025).
- **Do not spend on paid G2 in year one.** The free listing + Users Love Us badge is sufficient.

### Cross-platform

- TrustRadius follows similar mechanics but smaller volume.
- Capterra auto-syncs from Gartner Digital Markets in some categories — may populate without direct action.

---

## Phase 14: Post-Launch Momentum

Your launch isn't over when the announcement goes live. Now comes adoption and retention work. Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement.

### Immediate Post-Launch Actions

- **Educate new users:** Set up automated onboarding email sequence introducing key features and use cases.
- **Reinforce the launch:** Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.
- **Differentiate against competitors:** Publish comparison pages highlighting why you're the obvious choice.
- **Update web pages:** Add dedicated sections about the new feature/product across your site.
- **Offer hands-on preview:** Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.

### How to Prioritize What to Announce

Use this matrix to decide how much marketing each update deserves:

**Major updates** (new features, product overhauls):

- Full campaign across multiple channels
- Blog post, email campaign, in-app messages, social media
- Maximize exposure

**Medium updates** (new integrations, UI enhancements):

- Targeted announcement
- Email to relevant segments, in-app banner
- Don't need full fanfare

**Minor updates** (bug fixes, small tweaks):

- Changelog and release notes
- Signal that product is improving
- Don't dominate marketing

### Announcement Tactics

- **Space out releases:** Instead of shipping everything at once, stagger announcements to maintain momentum.
- **Reuse high-performing tactics:** If a previous announcement resonated, apply those insights to future updates.
- **Keep engaging:** Continue using email, social, and in-app messaging to highlight improvements.
- **Signal active development:** Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.

---

## KPIs & Tracking Dashboard

Track weekly. If a number isn't moving, investigate — don't just submit more directories.

| Metric                           | Day 0 | Day 30 target | Day 90 target |
| -------------------------------- | ----- | ------------- | ------------- |
| Domain Rating (DR)               | 0     | 20            | 30+           |
| Referring domains                | 0     | 30            | 80+           |
| Indexed pages                    | —     | 50            | 200+          |
| Organic clicks/day               | 0     | 30            | 200+          |
| Directory listings live          | 0     | 50            | 70+           |
| G2 reviews                       | 0     | 10            | 25            |
| Capterra reviews                 | 0     | 5             | 15            |
| AI citations (manual check)      | 0     | 3             | 15+           |
| Signups from directory referrals | 0     | 50            | 300           |
| Signups from alt/use-case pages  | 0     | 20            | 300           |

---

## What NOT to Do

1. **Don't pay for directory submission services** ($60–$200 packages). The whole point is these are free. It's an afternoon of copy-paste.
2. **Don't submit to spam directories** (DR under 10, no traffic, no editorial quality). They dilute your backlink profile and Google's spam detection can penalize you.
3. **Don't submit with the wrong positioning.** Re-read the positioning table per tier. Generic descriptions waste the listing.
4. **Don't treat directories as your entire GTM.** They're the foundation. Content + community + reviews are what actually convert.
5. **Don't skip reviews on G2/Capterra.** Zero-review listings are dead. Run the 10-in-30 protocol or don't submit.
6. **Don't ask for upvotes on Product Hunt.** The 2026 algorithm penalizes it. Ask for **feedback**.
7. **Don't amend old directory listings every week.** Submit once, check quarterly.
8. **Don't submit before the destination page exists.** Link equity needs a destination.
9. **Don't duplicate descriptions across directories.** AI engines penalize duplicate content.
10. **Don't lie on comparison pages.** AI engines cross-reference and de-rank lies.
11. **Don't over-index on launch-day spike.** The flywheel is templates + alternatives + reviews + ongoing content — not one day of PH.
12. **Don't forget Crunchbase, LinkedIn company page, and Wikidata.** These feed AI training corpora and matter for GEO.
13. **Don't launch before SLC gate passes.** Stealth Mode and "Just One More Feature" both kill launches.
14. **Don't skip the humanizer pass on marketing copy.** AI patterns in hero, CTAs, meta descriptions, OG descriptions tank credibility.
15. **Don't assume analytics "just work."** Verify every integration with curl before launch — GA4, PostHog, GSC, Bing, Ahrefs.
16. **Don't ignore backup drills.** A backup you haven't tested is not a backup. Restore to staging before launch.

---

## Output format

At the end of a full run, output a status report grouped by phase:

```
Phase 1: Domain & Infrastructure  [9/10 pass]
  ✓ Cloudflare proxy on
  ✓ DNS records configured
  ...
  ✗ DMARC missing. Fix: add TXT record at _dmarc.example.com with policy v=DMARC1; p=quarantine;...

Phase 2: Analytics & Observability  [6/7 pass]
  ...
```

Followed by three lists, in order:

1. **Blockers** (must fix before launch)
2. **Recommended fixes** (should fix before announcing)
3. **Optional improvements** (post-launch)

End by asking: "Which list do you want to tackle next?" (`blockers` | `recommended` | `optional` | `done-for-now`).

---

## References

- `references/decisions.md`: AI scraper policy matrix by site type, observability tier matrix
- `references/templates.md`: robots.txt, llms.txt, manifest.json, CSP templates per tightness level, security headers reference
- `references/weekly-seo-agent.md`: Full definition of the weekly SEO maintenance sub-agent (MCPs, tasks, output format)
- `assets/weekly-seo-*.md`, `assets/weekly-seo-vibe.toml`: per-harness agent-definition files linked from `references/weekly-seo-agent.md` — copy the one matching your harness
- `references/directory-list.md`: 13-tier directory catalog with submission timing, examples, and counts
- `references/positioning-variations.md`: Positioning variant library per directory tier (tagline, short/long descriptions, category tags)
- `references/submission-tracker-template.csv`: Submission tracker spreadsheet template for logging directory submissions