← Docs

How autopilot works

Autopilot runs every Monday morning. It compares this week's AI citation data against last week's, finds pages that lost visibility, diagnoses the weakest factor on each page, and generates (or publishes) a fix automatically.

Requirements

Autopilot is not available on every plan. You need three things:

Growth plan or higher

Autopilot is enabled on the Growth plan ($99/mo), the Agency plan ($299/mo), and during active free trials. Starter and Free plans do not include autopilot. You can check your plan in Settings → Billing.

At least 2 weeks of citation data

Autopilot compares this week vs. last week. If there is no baseline from the prior week, it skips that site. This means autopilot won't run until your second week on the platform.

CMS connected (for auto-publishing)

Without a CMS connection, autopilot still detects drops and generates fix snippets, but it cannot publish them. You'll get an email with the fix and a note to apply it manually. Connect your CMS in Settings → Plugins to enable one-click publish.

What happens every Monday

  1. Weekly scan runs at 6am. Aeonic crawls your tracked keywords across AI engines (ChatGPT, Perplexity, Claude, Google AI) and records whether each engine cited your site.
  2. Autopilot runs at 8am.For each site on a paid plan with autopilot enabled, it compares this week's citation data against last week's.
  3. Detects drops. It groups citations by page URL and calculates the citation rate (cited / total checks). Any page with a rate drop of more than 30%, or a page that was cited last week but not at all this week, gets flagged.
  4. Diagnoses the weakest factor. For each flagged page (up to 3 per site), autopilot runs the citability analyzer to score all 13 factors. It takes the lowest-scoring factor as the fix target.
  5. Generates a fix. Using AI, it generates a ready-to-use snippet: a new meta description, schema markup, FAQ section, content refresh, or other fix depending on which factor scored lowest.
  6. Publishes if CMS is connected. If the site has a CMS adapter configured, autopilot creates an action record, auto-approves it, and publishes through the adapter. The action is logged as published or failed.
  7. Sends an email. The site owner gets an email notification for each fix, including the page URL, which factor was targeted, and whether the fix was published or needs manual attention.

What autopilot can fix automatically

The following fixes can be generated and published without human intervention:

Issue typeWhat autopilot doesCMS required?
Missing meta descriptionGenerates a 155-character description using AI based on page title and contentTo publish
Missing or weak title tagGenerates an optimized 60-character titleTo publish
Missing schema markupGenerates Organization, Article, or Product JSON-LD based on page typeTo publish
Missing FAQ sectionGenerates 5 Q&A pairs with FAQPage schemaTo publish
Missing canonical tagSets the canonical URL to the page's own URLTo publish
Missing H1Generates an H1 from the page title and URL contextTo publish
Missing Open Graph tagsGenerates og:title, og:description, og:url, and og:typeTo publish
Duplicate meta descriptionGenerates a unique description that differentiates the pageTo publish
Missing alt textGenerates descriptive alt text for up to 5 images per pageTo publish
Weak statistics / dataSuggests 3 quantitative data points with placeholder numbers you can replaceManual only

What autopilot cannot fix

Some issues require human judgment or access autopilot does not have:

  • Content rewrites -- Autopilot can refresh small sections, but it will not rewrite an entire page. If Content Depth or Readability scores low, you need to expand and edit the content yourself.
  • Site architecture changes-- URL structure, internal linking, navigation, and sitemap issues are outside autopilot's scope.
  • Trust signals -- Adding a real author bio, credentials, and Person schema requires your specific author information.
  • Attributed expert perspectives -- Autopilot cannot fabricate quotes from real people. You need to add genuine trust-building quotes manually.
  • robots.txt and llms.txt changes -- These are site-wide configuration files that autopilot does not modify. Use the Aeonic dashboard to generate recommended content, then update the files on your server.
  • Third-party platform issues -- If AI bots are blocked by your CDN (Cloudflare, Sucuri), or your host blocks the REST API, autopilot cannot fix that. You need to update your hosting configuration.

Reviewing what autopilot did

Every autopilot action is logged. You can review what changed:

  • Email notifications -- After each autopilot run, you get an email per fix with the page URL, the targeted factor, and whether the fix was published or needs manual attention.
  • Action log in the dashboard -- Go to your site dashboard. Published actions show the adapter used, the published URL, and a timestamp. Failed actions show the error message.
  • Rollback -- If a fix made things worse, you can roll back from the action detail view. For WordPress, this restores the previous title or meta description. For GitHub, it deletes the committed files.

How to disable autopilot

Autopilot is tied to your plan, not a toggle. To stop autopilot from running:

  • Disconnect your CMS-- Without a CMS connection, autopilot generates fixes but cannot publish them. You'll still get emails, but nothing changes on your live site.
  • Downgrade to Starter -- The Starter plan ($39/mo) does not include autopilot. You keep citation monitoring and manual fix generation, but automated weekly fixes stop.
  • Contact support -- If you want to stay on Growth but pause autopilot temporarily, reach out and we can disable it for your organization.

Frequency and limits

  • Autopilot runs once per week (Monday 8am UTC), after the weekly citation scan completes.
  • It processes up to 3 dropped pages per site per run, prioritized by severity of the citation drop.
  • On the Growth plan, autopilot covers up to 3 sites. On Agency, up to 10 sites.
  • Fixes are generated with AI (temperature 0.4 for consistency) and capped at low-risk changes. Autopilot will never delete content or make high-risk structural changes.