Autopilot: the posts AI would cite, written and published on your site
Most of what AI cites is writing: comparisons, guides, answers to the question a buyer typed. Finding which posts to write, writing them properly and getting them onto your site is the work nobody has time for. Autopilot does all three. It picks topics from evidence, never from a keyword list: the questions your scan shows you losing, the pages the engines cite instead, what people type, what your rivals publish. Each topic is then put to a live engine, and it is only written if the engine answers and leaves you out. The post is written from your own site's facts, in your voice, set in your site's own design, and committed to your repository as a finished page.
How it works
It reads your site's design
CiteGraph opens your site the way a visitor does and takes its header, its footer, its fonts, its colours and the width it sets text in. Every post is set inside that, so it looks like you built it. No access to your code is needed for this, and nothing on your site changes.
It plans from evidence, then checks
Topics come from the questions your last scan lost, the pages the engines cited for them, Google's own suggestions in your category, and your rivals' sitemaps. Each candidate is asked of a live engine. The queue shows what it answered, whether it named you, and how many pages it cited, so you can see why every topic is there.
It writes, then publishes
Each post is written from a ledger: facts your own pages state, with the page each came from, and sentences quoted word for word from the public pages the engine cited. A second model edits it. Code checks refuse any number or link with no source. The finished page, its picture, a blog index and a sitemap go to your GitHub repository in one commit, as a pull request or straight to your branch.
In depth
You choose how much it does alone
Ask me first, and every post waits for you. Publish for me, and posts that pass every check go out on their own. A post that fails a check is never published without you, whichever you choose.
Every change can be taken back
The Autopilot screen keeps a ledger of everything CiteGraph has committed to your repository, with a link to each commit. Revert removes that post's files and rebuilds the index and sitemap without it.
A picture in your colours, with no words in it
Each post gets one illustration, drawn in your site's palette in a style you pick once. A second model looks at every picture for letters, numbers and logos. One that has any is drawn again, and dropped if it fails twice. Charts and tables in a post are drawn in code from real numbers, never generated.
Then it watches what happens
With the crawler tracker installed you see AI crawlers opening your posts. The weekly scan reports whether the engines began naming you and citing your pages. Those three things are the top of the Autopilot screen.
What we won't claim: that a post will be cited. We write the page a careful engine would want to quote and we measure what happens next, with the margin of error printed. We also won't invent. A fact your site does not state is left out or asked of you, never guessed, and no post ever speaks for you anywhere but your own site. Today it publishes to sites whose code lives on GitHub; on anything else you can download each finished page.
Common questions
How is this different from an AI blog writer?+
An AI blog writer starts from a keyword and writes from its training data. Autopilot starts from a question a live engine already answers without you, and may use only your own site's facts and sources quoted word for word. Any number or link with no source is refused by code, not by a prompt.
Will the posts look like my site?+
Yes. Your header, footer, fonts, colours and text width are read from your live site and every post is set inside them. You can preview the design before anything is published, on desktop and phone widths.
How often does it post?+
Starter posts twice a week, Growth once a day and Scale up to three times a day, on one site per account. You can choose a slower pace, and a new site starts gently.
What access does it need?+
Reading your design needs none. Publishing needs a GitHub token limited to one repository, with contents and pull requests set to read and write. It is stored encrypted, never shown again, and you can disconnect it at any time.
What if I don't like a post?+
In ask-first mode nothing goes out without you. Anything already published can be reverted from the Autopilot screen with one click, which removes the page and rebuilds the index and sitemap.
Does it work with WordPress or Webflow?+
Not yet. Today it publishes to sites whose code is on GitHub, which covers Next.js, Astro, React, Vue and most coded sites. On other platforms you can download each finished page and add it yourself.
See it on your own domain — first dossier in about a minute.