One pixel plus a server-side NPM adapter ship FAQ schema, llms.txt, robots updates, and freshness signals to your site. Six sub-features keep it honest: deploy-approval workflow, automated verifier, auto-rollback on regression, AI bot-crawl tracker, and a cross-platform deployment dashboard. No developer queue. No surprise overwrites. No silent failures.
Every AI visibility tool on the market tells you what to fix. None of them fix it. You get a report that says “add FAQ schema to your top 20 pages,” “create an llms.txt file,” “update your Organization schema.” Then the report sits in a Google Drive folder for months while the developer queue stays 8 weeks out.
Autopilot closes that gap with six locked sub-features. AI bot-crawl detection runs server-side via the NPM adapter, catching bots the JS pixel can't because it never renders. Hybrid fix delivery ships fixes through the pixel + NPM model. The deploy-approval workflow routes every fix through tier-gated quotas and keeps a full history of every change, so anything can be rolled back. The verifier + auto-rollback checks every deployed fix every 10 minutes against your rendered HTML and auto-rolls back regressions. The AI bot-crawl tracker tracks which AI bots crawl which pages. The cross-platform deployment dashboard unifies all of it for agencies managing mixed installs across a client roster.
The result: your fixes go live the same day you approve them, and the system tells you the moment any one of them breaks.
Server-side tracking via @topslot/server-pixel. Spots AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) the moment they request a page, and records the crawl. Catches bots that the JS pixel can't, because those bots never render the page.
Client-side JS pixel injects FAQ schema, llms.txt link, robots.txt update, and dateModified freshness signals at render time. Server-side adapter unifies signals across both layers. Adapters ship for Next.js, Express, Remix, and Nuxt.
Every fix goes through pending, approved, deployed, ending as either rejected or rolled back. Tier-gated quotas: Starter 1/day, Growth 1/day, Agency 5/day. A full history of every change is kept, so anything can be rolled back. You always know what was deployed and by whom.
Every 10 minutes, the verifier checks every deployed fix against your rendered HTML. With server-side adapter installed, missing fixes trigger auto-rollback + email alert. JS-only installs mark the fix verified with a warning instead. Alerts are throttled to one per brand per 24 hours.
Lives as the Bot Crawls tab in AI Traffic Analytics. Breakdowns by bot, by day, and by top pages show which AI models are crawling which pages. A separate view splits crawls by how each one was caught, so you know which part of your install is doing the work.
Agency-tier unified view per brand. Three columns: JS pixel (configured + health + 30-day stats), NPM adapter, static fallback. 30-day stacked-bar timeline of detection sources. Designed for managing mixed-install configurations across a client roster.
Run a one-page render check on any URL and see exactly what JavaScript-blind AI crawlers receive versus what a browser renders. No pixel needed to start, so you can find the gap before you install anything.
Generates and injects FAQ structured data based on your content. FAQPage schema increases AI citation rates because it gives models pre-formatted question-answer pairs to extract.
Deploys full Organization structured data including name, logo, social profiles, founding date, and description. Helps AI models build accurate entity profiles of your brand.
Creates and maintains an llms.txt file at your domain root telling AI crawlers what your company does, what pages matter, and how to cite you. Updated automatically as your site changes.
AI models give strong preference to content updated within the last 90 days. The pixel injects dateModified schema and last-updated metadata so AI models treat your pages as current, not stale.
Configures robots.txt to allow AI crawlers selectively (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) while keeping other bot policies intact. Per-page controls for sensitive sections.
Every change Autopilot makes is versioned and recorded. The deploy-approval workflow's change history shows what was deployed, when it went live, and what it replaced. The verifier + auto-rollback handles regressions; manual rollback is one click.
You know you need schema markup and llms.txt but you don't have a developer on staff. Autopilot handles the technical work; the deploy-approval workflow keeps you in control of every change.
Your developer queue is 8 weeks long. Marketing can't wait when AI visibility shifts weekly. Deploy fixes through the approval workflow without filing a Jira ticket; the verifier catches regressions automatically.
Install one pixel per client site and manage all deployments through the cross-platform deployment dashboard. White-label reports show clients exactly what was fixed, what was rolled back, and which AI models are actively crawling them.
Your engineers are building product, not updating schema. Autopilot keeps your marketing site optimized for AI search. Server-side adapters ship for Next.js, Express, Remix, and Nuxt. Install in one PR, then never touch it again.
Pixel install works on every tier including Free.
Auto-fix deploy is available on Starter and above. Starter caps at 1 deploy per day; Growth at 1/day; Agency at 5/day.
Verifier + auto-rollback on regression: Growth and Agency.
Cross-platform deployment dashboard: Agency only.
▸ GUIDED ONBOARDING INCLUDED ON EVERY PAID PLAN
No. The pixel loads asynchronously after your page content renders. It adds less than 2 KB to your page weight and does not block the critical rendering path. Lighthouse scores remain unchanged.
The deploy-approval workflow moves every fix through clear stages: pending, approved, deployed, with rejected and rolled back as the two ways a fix ends. Quotas are tier-gated: Starter 1/day, Growth 1/day, Agency 5/day. Every fix keeps a full history of every change made to it, so anything can be rolled back. You always know what was deployed, when, and by whom.
The verifier + auto-rollback check runs every 10 minutes against every deployed fix. If your install includes the server-side adapter and the fix is missing from the rendered HTML, the system flags it as a regression, rolls it back to the previous state automatically, and emails you. If you only have the JS pixel installed, the fix is marked verified with a warning instead, meaning we can confirm less, not that it failed. Alerts are throttled to one per brand per 24 hours so you don't get an alert storm during a transient outage.
The AI bot-crawl tracker catches GPTBot, ChatGPT-User, ClaudeBot, Claude-Web, Google-Extended, PerplexityBot, Anthropic-AI, Applebot-Extended, FacebookBot, and more. Each crawler is identified by how it announces itself, the network it comes from, and how it behaves. The Bot Crawls tab in AI Traffic Analytics breaks crawls down by bot, by day, and by top pages, so you know which AI models are actively crawling which of your pages.
The cross-platform deployment dashboard is a unified three-column view per brand: JS pixel (configured + health + 30-day stats), NPM server adapter, and static fallback. Includes a 30-day stacked-bar timeline showing detection-source breakdown across pixel / npm / static. Designed for agencies managing fixes across multiple client sites with mixed install configurations. Available on Agency.
Yes. Remove the script tag from your site header and all deployed fixes are removed on the next page load. Autopilot does not modify your source code or CMS database. Server-side adapter installs are removed by uninstalling the NPM package.
No. Autopilot detects existing schema markup on each page before deploying. If Yoast or RankMath already provides FAQ schema, the engine skips that page and focuses on pages without coverage. The deploy-approval workflow shows you the conflict explicitly so you can choose to keep, replace, or merge.
Run a free Scorecard and get a list of fixes Autopilot can deploy through the approval workflow. The verifier checks every one of them every 10 minutes after deploy.
Check your visibility, free →