What this is: The stage where the actual draft lives, a rich-text editor where you refine the copy, iterate with AI, manage images, and add FAQs.
By now the AI has produced a full draft from your Brief, Outline, and (if enabled) Research. The Written stage is where you polish it.
At the top of the stage you'll find the SEO meta fields:
The body is a rich-text (WYSIWYG) editor with three parts:
Each section shows a live word count and has a full formatting toolbar (bold, italic, links, lists, quotes, and more).
To turn a phrase into a link:
The linked text turns gold and underlined. To change a link, click inside it and open the link button again: the current URL is pre-filled. To remove one, click inside it and use the x button next to the link button.
The link button is greyed out until you select some text, because a link needs something to attach to.
You have several ways to refine the draft with AI:
Tip: Use Edit all with AI for consistency changes ("make the tone more casual across the whole piece"), and the per-section menu for surgical fixes on one paragraph.
Tip: If an AI edit doesn't land the way you wanted, open History and restore an earlier snapshot.
FAQ questions come from two places, and the editor tells you which. Questions taken from real Google People also ask results are marked (PAA); the rest were generated. PAA questions are used word for word on purpose: their exact phrasing is what Google shows and how people ask an assistant, so rewriting them into keyword phrasing loses the point. Answers are written to be lifted whole, so aim for a direct answer in the first sentence and 40-75 words that make sense on their own.
Above the draft sits a card labelled AI Answer Layer, described in the app as what AI engines quote when they cite this article. It is the extractable summary of the piece, and it is what ends up in the article's structured data.
It holds three things:
The TL;DR always exists and always feeds the article's structured data. Whether it also appears as a visible block at the top of the published article is a separate choice, and you control it in two places:
Gotcha: Clearing the TL;DR text removes the rendered block entirely, whichever way the toggle is set. An empty TL;DR means nothing to show.
Before a draft is saved, the platform checks that each factual claim in it actually rests on a source, and removes the ones that don't. This runs automatically on every article, whether it came from chat or from the pipeline.
A claim counts as sourced when the link sits in the same sentence, or in a short citation right after it. A link further up the page doesn't count.
What gets checked:
What happens to an unsourced claim:
The platform will never invent a citation to keep a claim. That would just move the fabrication one step down. Cited links are also fetched: one that no longer resolves counts as no link at all, so the claim it was supporting is treated as unsourced.
The link has to be one you can see. A figure can also carry a source behind the scenes, in the article's structured data. That is what search engines and AI assistants read, but a reader never sees it, so it is not a citation on its own. Where a figure has a working source recorded that way, the platform now writes it into the sentence as a real link and adds it to References. Where it doesn't, the claim is treated as unsourced like any other.
Every article carries two source lists, and they mean different things:
Both lists appear at the end of the article everywhere it goes: the editor, the Google Docs and Word exports, and the published page on WordPress or Webflow.
Gotcha: If a draft comes back shorter than you expected, check the editor notes on the article. Anything removed here is listed there with the reason. The fix is to give the writer real sources: add them to your trusted sources, paste them into chat, or link them yourself in the editor.
There is no backfill: articles saved before this existed keep their unsourced claims until you regenerate them.
The Export menu in the title row saves a copy of the current stage. On the Written stage you can export to Google Docs, Word (.docx), PDF, or Create .md file.
This downloads the article as a markdown file built for AI tools rather than for reading in Word.
The file has two parts:
Use it when you want to hand the piece to an AI assistant and have it understand not just the words but the structure behind them: which sources you cited, which facts carry numbers, and which entities the piece is about. Google Docs and Word carry the prose and both source lists, but only the markdown file carries the answer layer on top of them: the TL;DR, the entities, the statistics with their sources, the publish and update dates, and the (PAA) marks. PDF is prose only.
Tip: FAQ questions that came from real Google "People also ask" results are marked (PAA) in the file, so you can tell them apart from ones that were generated.
Gotcha: The file reflects what is saved. If you have just typed an edit, let autosave finish before exporting.
When the draft is ready, click Approve Written to move to the Extras stage.
Gotcha: Approving locks the Written stage. To edit it again later, Unlock, which deletes and regenerates the stages after it.
Start a 14-day free trial, or book a walkthrough.