Publish a FAQ one question at a time

You already wrote the answers. They live on one page, folded into an accordion, each behind a click. That is comfortable for a visitor scanning for their own question, and it is close to the hardest arrangement possible for anything that reads without clicking.

One question, one address

The unit that gets quoted is an address. A page that answers a single question can be read, cited and linked on its own; the same answer, sitting eighth in a list of twenty, comes with nineteen others attached and no way to point at it.

So the question becomes the title of the page, and the answer becomes the text. markleex.com/@yourname/faq/do-you-deliver-to-europe is a whole document, and it says one thing.

Say that it is a question

Put question: true at the top of the page and the structured data says what the page is: the title is published as the question, the text as its accepted answer. A reader that never sees your words still knows which part is being asked and which part is the answer.

The head page that lists them all does not carry that markup, and this is deliberate: it shows titles, not answers, and our markup only ever claims what the page actually shows.

Keep them together

Publish one head page with children: true and it serves the list of every question under it, without you maintaining that list. Add children_order: manual and a rank on each page if the order matters, which it usually does: what people ask first goes first.

Which questions to write

The ones you are actually asked, in the words people use, not the ones you wish they asked.

• What it costs, or how it is quoted when it varies.
• How long it takes, from the day someone says yes.
• Where you work, and where you do not.
• What is not included: the answer nobody publishes and everybody needs.
• What happens if it goes wrong: returns, warranty, what you cover.
• How to start, in the smallest number of steps that is true.

Then you find out which ones matter

Reads are counted per address, so each question tells you how often it was read and by which houses of AI. An accordion can never tell you that: it is one page, and every answer inside it shares the same number.

The questions that come up and have no page yet are the ones worth writing next, and that is the whole loop.

How to do it

1. List the questions you are actually asked, in the words people use to ask them.
2. Publish one page per question, with the question as the title and the answer as the text.
3. Add question: true to each of them, so the markup says it is a question and its answer.
4. Publish a head page with children: true, which serves the list of them all.
5. Watch which questions get read, and write the answers that are missing.

If the FAQ already exists somewhere, connect your assistant to Markleex and hand it the page: it splits it into one page per question and publishes them, keys included, in a single pass.

What it costs

A space is $0.83 a month, with 10 pages included, so the questions you get asked most are covered before anything is added. See the pricing.