Writing good pages
Publish pages that are useful and unique. Never publish volume for its own sake.
Google punishes "scaled content abuse": many pages made only to rank. Flocon AI is built to avoid this. Your published pages are capped by your plan. But the quality is up to you and your AI.
This guide is the longer version of the advice your AI tool already receives when it connects to the MCP server.
The rules
- One page = one real question or need.
- Unique data on every page. Not the same text with a new name.
- Real facts only. Prices, features, dates, numbers. If your AI does not know, it must say so.
- Answer first. The first block answers the question in 2 to 3 sentences.
- No keyword stuffing. Write for people. AI search reads meaning, not keyword counts.
- Publish only pages you would be happy to read.
Start with a short description block
The first block of a page should be a description block. It is the answer-first intro.
- Answer the title's question directly.
- 2 to 3 sentences.
- Include the key fact (a price, a name, a number).
AI search tools often quote this part.
Add structure that AI can cite
- Comparison tables. Use a
tableblock for features, prices and limits. - Stats with sources. Name the source in the text.
- FAQ. Use a
faqblock with real questions people ask. - Fresh dates. Update a page when facts change.
updatedAtis a real date and is used fordateModified. - Related pages. Use a
relatedblock to link pages of the same topic.
Keep SEO fields tight
- Title: 60 characters or less.
- Description: between 140 and 160 characters.
If you go over, the MCP server returns a warning. Your AI then fixes it.
Path conventions
Pages have no type or template field. A page type is just a path. These paths work well:
| Path | Use it for | Example |
|---|---|---|
/alternatives/[tool] | People who look for an alternative to a tool | /alternatives/notion |
/vs/[a]-vs-[b] | A head-to-head comparison | /vs/notion-vs-obsidian |
/integrations/[tool] | How your product works with a tool | /integrations/slack |
/use-cases/[job] | How a type of person uses your product | /use-cases/agencies |
Paths use lowercase letters, digits and dashes. No locale prefix and no trailing slash.
What to put in each type
/alternatives/[tool]: why people leave the tool, a comparison table, who should stay, who should switch./vs/[a]-vs-[b]: a fair table, a clear verdict for each case. Be honest about weak points./integrations/[tool]: what the integration does, setup steps, limits, a FAQ./use-cases/[job]: the problem of this person, how your product solves it, a real example.
Release pages slowly with scheduled publishing
Your AI can write 30 pages in one chat. Do not publish 30 pages in one day.
A sudden spike looks unnatural to Google. Steady growth looks natural.
Use publishAt to schedule each page:
- Ask your AI: "Create these 30 pages and release one a day."
- Each page gets a
publishAtdate in the future. - The page is hidden from your website, your sitemap and
llms.txtuntil that date.
A scheduled page uses one of your published page slots, even before it goes live.
Plan limits help you
Your plan limits published pages in total, not per month. The total number of pages (published and draft) is capped too. See pricing.
Use drafts to review a batch before you publish it.
Checklist before you publish
- The first block answers the question.
- The page has data that no other page has.
- Every fact is real and checked.
- There is a table or a FAQ where it helps.
- Title and description have the right length.
- The page is scheduled if you publish many pages.
Updated