$ postbuild git paid
Pricing ($29) Scan Your Live URL
Technical Comparison CLI & Web Workspace

postbuild vs. Manual Submissions

Run one command on your deployed site to audit 8 SEO & AI-crawler checks, generate missing robots.txt, sitemap.xml, and llms.txt files, and prepare 74 curated directories + 11 launch communities (9 URL auto-prefilled links + 76 standalone web forms) with a dedicated @postbuild.dev verification inbox.

Comparing SaaS Launch & Directory Submission Options

Founders typically choose between manual spreadsheet tracking, submission agencies ($149 to $299+), or CLI and workspace prep with npx git-paid.

Approach Typical Cost Verification Inbox Technical SEO & llms.txt
Manual Spreadsheets $0 (manual form entry) Clutters personal email Hand-written config files
Directory Submission Agencies $149 to $299 per site Shared third-party Gmail Not included (links only)
postbuild (npx git-paid) $29 one-time (Launch Pass) Dedicated acme-com@postbuild.dev (30-day retention) Generates robots.txt, sitemap.xml, llms.txt, JSON-LD & 7 draft HTML product pages

CLI & MCP Quickstart

Run from your terminal after deploying to Vercel, Railway, Render, or Fly.io, or scan any URL directly in the web workspace.

# 1. Authenticate your Launch Pass & write SEO files + 7 draft pages
$ npx git-paid login pb_live_... && npx git-paid fix https://your-project.com
# 2. Preview directory submission forms & prepare prefilled launch links
$ npx git-paid submit https://your-project.com --limit 10
# 3. Read verification OTPs from your @postbuild.dev inbox
✔ Extracted OTP codes & confirmation links
Run Free Readiness Scan on Your URL

What the $29 Launch Pass Unlocks

One-time payment per project domain. All sales are final once your files unlock, except where required by law (Terms). If your files fail to generate, your license key cannot be activated, or domain verification cannot open your inbox, email support@postbuild.dev for a fix or a full refund.

Curated Directories & Communities: 85 targets (CSV + Auto-Fill)
Dedicated Verification Inbox: acme-com@postbuild.dev (30 days)
Targeted HTML Product Templates: 7 draft pages (.zip + CLI)
Technical SEO & AI Crawler Files: robots.txt, sitemap.xml, llms.txt
Claude Code & Cursor Integration: npx -y git-paid mcp

Manual Post-Build Setup vs. postbuild (npx git-paid)

Post-Build Task Manual Setup / Spreadsheets postbuild (npx git-paid)
85-Directory & Community Launch Kit Hours of repetitive copy-pasting & UTM tagging across 85 sites 9 URL auto-prefilled links + 76 form links with 1-click Auto-Fill Bookmarklet & CSV export
Directory Verification Emails & OTPs Clutters personal inbox with directory signup and confirmation emails Dedicated acme-com@postbuild.dev inbox (30-day retention) that extracts 6-digit OTPs & confirmation links
Technical SEO & AI Crawler Files Hand-written robots.txt, sitemap.xml, JSON-LD, and llms.txt Writes robots.txt, sitemap.xml, and llms.txt to public/ (preserving existing rules) and 7 noindex draft pages to .postbuild/pseo/
AI Coding Agent Workflow Switching between browser tabs, docs, and terminal scripts Built-in MCP server (npx -y git-paid mcp) for Claude Code, Cursor, and Windsurf

Related Post-Build Guides & Checklists

Browse additional guides indexed in sitemap.xml and llms.txt: