1. Define The Task
We identify the role, task, likely source material, final work product, review lens, and common failure modes before writing prompt copy.
How We Build Prompt Pages
Every task page starts from the user decision: what the person is trying to create, what source material they have, what the output should look like, and what a human must check before use.
Page method
Turn a broad request into a reviewable prompt
Use this to decide whether the prompt has enough input, output shape, and checking steps.
Ready checks3 of 3 ready
Request is concreteReady
Name the actual work, source material, rough version, or notes you plan to use.
Use context is clearReady
State where the answer will be used, who will read it, and what must stay out.
Checker is namedReady
Keep one person or review lens responsible before the answer is reused.
Input material
Name the notes, examples, audience, and constraints ChatGPT is allowed to use.
Review focus: Input material. Why this matters: Name the notes, examples, audience, and constraints ChatGPT is allowed to use.. Planned request: I need a prompt that turns a rough topic into a structured article plan.. Use context: This will be used before assigning writing work, so the result must be easy for an editor to scan.. Who checks it: An editor checks search intent, examples, internal links, and unsupported claims.. Before using the answer, check privacy, unsupported claims, missing context, tone, and whether a human needs the final call. If any part is unclear, ask for the missing detail before writing.
Nothing saved yet
2. Create The Workbench
Each task receives a recommended prompt, additional prompt types, variables, example inputs, expected output notes, follow-up prompts, and human review checks.
3. Show The Rough Input
A page should name what the user brings first: notes, audience, constraints, source material, and the reason a first answer might fail.
4. Review For Usefulness
We check whether the page gives a useful first action, avoids unsupported claims, separates assumptions from source material, and includes safety boundaries.
5. Keep It Navigable
Long pages include anchors, prompt filters, related task links, and role guides so users can move from broad context to a copyable prompt.
6. Keep Claims Modest
We do not turn a prompt example into a ranking, traffic, backlink, endorsement, or performance claim. Those require live data and outside records.
External Proof Boundary
Search rankings, traffic, backlinks, mentions, endorsements, and third-party approval are not claimed from planning notes. Those signals require a live domain, Search Console data, current search-result review, and publicly visible outside references with dated review notes.
Source References
- Google Search Central: SEO Starter GuideUsed to keep titles, descriptions, internal links, and page structure understandable to users and search engines.
- Google Search Central: people-first contentUsed as the editorial bar for practical examples, clear ownership, and pages that answer a real task.