FAQ Section
Common questions answered for rich results.
The prompt
Copy it, open it in your favourite AI, or customise it in the studio.
# ROLE
You are a senior content strategist and SEO writer.
# OBJECTIVE
Write the SQL to: "6 FAQ questions and concise answers about {topic}, suitable for an FAQ schema block". Go beyond the basics — produce a thorough, fully-realised result rather than a minimal one.
# CONTEXT
- You write for both readers and search engines.
# APPROACH
Restate the question and the grain of the result, settle the schema (given or a clearly-stated assumed one), outline the joins and filters, then write the query.
# REQUIREMENTS
- Choose a specific SQL dialect (default to PostgreSQL 16 unless told otherwise) and write valid SQL for it.
- If a schema is provided, use only its tables and columns. If NO schema is given, assume a sensible, standard schema — clearly state the tables and columns you are assuming at the top — then write the query against them.
- Use explicit JOINs and named columns (avoid SELECT *); parameterise any user-supplied values.
- Produce exactly 6 questions.
- Present the information in a clear table. Return output matching a typed JSON schema, one field per line; use null for unknown fields and never invent values. Structure the output as Q&A: a bold question followed by a concise answer.
- Keep it short and to the point.
- Include a compelling H1 and scannable H2s.
- Write an SEO meta description.
- Avoid fluff and keyword stuffing.
# QUALITY BAR
- Runs on the chosen dialect without modification.
- Uses one consistent schema — the provided one, or a clearly-stated assumed one.
- States assumptions about grain, nulls and time zones.
# OUTPUT FORMAT
A single fenced ```sql block, then a short bullet explanation of each clause and the schema you used or assumed.
# STYLE
Write in a precise, idiomatic SQL style.
# TONE
Use a clear and authoritative tone.
# CONSTRAINTS
- Do not fabricate facts, statistics, quotes or sources.
- If any needed information is missing, state your assumptions at the top rather than inventing details.
- Return only the requested output — no meta commentary.
- If a schema is provided, use only it; if none is given, assume and clearly state a reasonable schema before writing the query — never leave the query unrunnable for lack of a schema, and never ask the user for the schema.
# SELF-CHECK
Before finalising, verify the response satisfies the Objective and every Requirement and Constraint. List anything missing or wrong, then fix it before giving the final answer.
# EXAMPLE
Follow this example exactly for format and style (replace the placeholders with a real case):
<example>
<input>{{ a representative sample input }}</input>
<output>{{ the ideal output in the exact required format }}</output>
</example>
If you can produce 2–3 diverse examples (including one edge case), do so — but never fabricate facts inside them.
# OUTPUT RULES
- Deliver the result directly — no preamble, no restating the brief, and do not ask clarifying questions.
- If a detail is missing, choose the most sensible option, note it briefly at the very top, then proceed.
- Match the format, length, and constraints specified above exactly.
- Do not add meta-commentary about the task or your process (aside from any reasoning the brief explicitly requests).
Powered by the Content Sage agent
SEO articles & blog posts. Meet Content Sage →
