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.
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.