postbuild Technical SEO and AI Crawlers
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.
8-Point Technical SEO & AI Crawler Diagnostic Signals
Every postbuild scan inspects the initial server-rendered HTTP response (before client-side JavaScript hydration) across 8 launch-critical checks.
| Check | What We Inspect | Non-Destructive Fix |
|---|---|---|
| 1–4. Head Metadata & JSON-LD | <title>, server-rendered <h1>, meta description, OpenGraph image (og:image), and SoftwareApplication JSON-LD. |
Generates head-seo-snippet.html and a 1200x630 og-card.png social card. |
| 5. AI Search Crawlers | Checks /robots.txt for OAI-SearchBot, PerplexityBot, and ClaudeBot rules. |
Adds rules for AI crawlers via robots-additions.txt and copies any existing Disallow: lines under each new crawler per RFC 9309. |
| 6. XML Sitemap | Streams up to 64 KB of /sitemap.xml (including large multi-megabyte sitemaps) and checks Sitemap: directives in robots.txt. |
Preserves existing sitemaps and provides sitemap-starter-routes.xml for newly published product pages. |
| 7–8. Checkout & Telemetry | Detects Stripe/Polar/LemonSqueezy checkout links or /pricing routes and analytics scripts. |
Generates PostbuildCheckoutGate.jsx for drop-in Stripe Checkout integration. |
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.
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.
acme-com@postbuild.dev (30 days)
.zip + CLI)
robots.txt, sitemap.xml, llms.txt
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: