AEO NIUEXA

Content Briefs and Articles

7 min read

Content Gaps

A content gap is a tracked question that AI engines answered without naming you, often while citing a competitor. On the brand page, Find content gaps looks for them in the answers already stored; finding them is free and sends nothing to an AI. Each gap says who was named instead and what page you could publish. Generate a brief from it, acknowledge it or dismiss it.

The Content gaps panel: Where can I buy fresh single-origin coffee beans online? Ridgeway Roasters is named in the AI answer, you are not; a suggestion to publish a Buy beans online page, with Generate brief, Acknowledge and Dismiss.
A content gap with a suggested page and the cost of a brief.

From Gap to Published Page

Brief
1 credit
An editorial plan that takes the cited competitor page into account
Article
2 credits
The full text, written from the brief and its sources
Social posts
1 credit
Posts that point to the article

The cost is shown on each button before you click. Generation runs in the background; you can leave the page.

Briefs

A brief lists the target keywords and questions, a recommended outline and length, notes on the brand voice, the call to action and its claim register. Export it as Markdown or JSON for a writer, mark it complete, or generate the article from it.

A brief: Export Markdown, Export JSON and Mark complete, the article language with the option to include an FAQ, Generate full article, and the status, recommended words, generated articles and claims that need a source.
A brief, ready to hand to a writer or to turn into an article.

The Claim Register

Briefs and articles list every material claim they make and the page that supports it. A source must be one of the pages the generator was given; when the AI names any other page, that source is removed and the claim needs a source. For each claim you can add a source, confirm it yourself (for facts only you can know, such as your prices) or leave it out. The AI only saw a title and an excerpt of each source page, so open it and check that it says the same before you publish.

Articles and the Review Step

The article is written natively in the language you choose (English or Italian), answers the target question in its first paragraph and uses only the brief's sources and confirmed claims. Its structured data is built on our side, with an "Add author name" placeholder until you set a default author under Content settings, and the publication date left for you to fill in.

Before you publish lists what to check:

  • every claim that needed a source has one, or is left out;
  • no "[source needed]" marker ("[fonte necessaria]" in Italian articles) is left in the text;
  • the facts only you can confirm are checked;
  • an author is named, and the publication date is filled in when you publish.

Then choose Reviewed and approved. Approval is refused while a claim still needs a source or a "[source needed]" marker is left; the other items are reminders. The approval covers that exact saved version: saving a change to the title or text withdraws it. Only an approved version can go live. Exports keep the label that says the text was written with AI.

Where to publish: the best place for an article is a page on your own site, so every crawler reads it. Deploy to live page adds an approved article to a page through Auto-Fix instead: visitors' browsers show it, but most AI fetchers do not run scripts and will not see it. Links to other websites are listed for you to review before it goes live.

Language and Author

Content settings on the Briefs page set the defaults for every brief, article and set of social posts of the brand: the language (the site's language, English or Italian) and the author who goes into each article's markup. You can still pick another language before each generation. Name only someone who really writes or reviews the content.