Foundation
an editorial brief defining user intent, the primary question, and the next useful action

Practical guide by MOTA Media Group
A useful page answers a real question early, relies on verified facts, and offers a relevant next step. Search structure makes the answer easier to find, but it does not replace subject matter and cannot guarantee rankings or traffic.
For editors, marketing teams, subject-matter owners, and website teams preparing service, guide, product, or knowledge pages that must be useful and maintainable.
Identify whether the reader wants to understand, compare, prepare, or choose; write the direct answer into the H1 and lead; build headings around real questions; assign an owner to claims, prices, cases, limits, and documents; and use only relevant existing internal routes. Review metadata, repetition, unsupported statements, and the next update date.
The final configuration follows the approved brief, channels, source materials, schedule, and rights framework.
an editorial brief defining user intent, the primary question, and the next useful action
a verified fact sheet with owners, available examples, limits, and prohibited claims
a heading structure and internal-link map built around distinct reader questions
unique page metadata with a named fact owner and review date for changeable information
Use these examples as a starting point. A producer will confirm the actual production route after reviewing the brief.
Scope, inputs, timeline, approvals, and usage rights are confirmed for the actual project.
Scope, inputs, timeline, approvals, and usage rights are confirmed for the actual project.
Scope, inputs, timeline, approvals, and usage rights are confirmed for the actual project.


Move from the current task to production, evidence, estimation, or project launch without losing context.
SEO content: answer the question and enable the next useful action
Start with an audience and one outcome: explain, demonstrate, support a choice or prepare an enquiry. Collect facts, source assets and constraints, and name the person who checks them. Annotate references with the technique you want and the reason for it.
Separate the master content from platform adaptations. Check format, duration, mobile readability, sound, subtitles and safe areas. Agree versions, timing and review rounds before production.
Before handoff, verify facts, contacts, links, filenames and asset permissions. Give every version a clear purpose and approval status. Publication, paid placement and account access are agreed separately from content production.