In a recipe, “make the dish” is not a usable instruction. Ingredients, actions, and expected results make it useful. A timer page should explain the duration, which button to press, and what happens next. Even the clearest written draft does not mean the tool itself is built and working.
Do this one thing now
Using your sketch, write a title and three lines of instructions. Each line should contain an action or a visible result. Separately label features that are not built or tested.
Here is a completed example
Title: Free meditation timer, no download 1. Choose “5 minutes.” 2. Press “Start timer” and check that the numbers count down. 3. At the end, the page displays “Timer finished.” Build note: These are planned behaviors, not built or tested features and not ready-to-publish promises.
Continue with your situation
I do not have a website
Write a draft without building a timer. You may ask someone willing to help to point to where they would start. That checks the instructions, not whether the timer works.
I have a website
Write or revise the instructions in your document, then try the main task on your page. For a timer, choose a duration, start, and wait for it to finish. Record what happened and any failure. Hand unbuilt features to the person responsible; follow your normal publishing approvals.
Keep it on your own paper or in your own document. No upload is needed. Mark work you have not done “not checked”; do not guess.
How do I know I am done?
The draft explains where to start and what comes next. Facts and features are supported or marked for checking. Write “tested successfully” only after actually testing and recording the outcome.
What can wait?
Do not add meditation history just to make the page longer or promise health outcomes. Paper practice can stop at the draft. A real timer still has to be built.
Open when you need more
What should I check in AI-written content?
Check steps, facts, and sources. Remove invented testimonials or performance numbers. Use images you have permission to use. Verify promises such as “free” or “no download.”
Complete work checklist, technical guides, templates, and sources
After the small exercise, consult this for your real project as needed. It retains the full scope of the original six-stage workflow.
Editorial sources reviewed · Not tested end-to-end on a live site
Entry requirement
Enter with a brief; existing content can enter with a specific improvement goal.
Goal
Produce a verifiable, useful content package ready for a publisher.
Concepts first
- Original value can be tested steps, clear examples, a comparison method, or a tool; it need not be a new discovery. Citation is not permission to rewrite someone’s whole article.
- The title must match the page’s promise. A meta description summarizes the page; Google may generate a different snippet from the content.
Rendering
Running page code to assemble the readable page.
Do not confuse: Working in your browser does not prove equivalent crawler access.
See examples and evidence →Internal link
A link from one page of your site to another.
Do not confuse: A sitemap entry is not an internal link; important links should be usable and crawlable.
See examples and evidence →Page title / title link
Your title describes the page; Google may generate the result’s title from multiple sources.
Do not confuse: HTML title, visible H1, and search-result title are distinct.
See examples and evidence →Meta description / snippet
You can provide a description; Google may instead build the snippet from page content.
Do not confuse: Providing a description does not guarantee it appears verbatim.
See examples and evidence →Inputs
- A page brief, reliable sources, licensed assets, and any necessary qualified reviewer.
Actions
03.1Draft around the task
State who the page is for, what they will achieve, and what they need. For each step include input, action, and expected result. Add troubleshooting to fragile steps. Use verifiable examples, never invented customer outcomes.
Output: A complete draft with demonstrations explicitly labeled as examples.
03.2Check facts and sources
Check numbers, product steps, dates, and causal claims against primary sources. Test actions you claim to have tested and record the environment and result; otherwise say untested. AI may help organize, but generated references are not evidence.
Output: Fact log: claim, source, review date, and test status.
03.3Prepare the page package
Prepare an accurate page title, short description, readable headings, and descriptive links; explain necessary terms. Place images near relevant text and supply useful text alternatives. Identify authors/reviewers and substantive update dates without faking freshness.
Output: Publishable body, metadata, assets, and annotations.
03.4Run a beginner walkthrough
Ask a target reader or someone unfamiliar with the project to follow the page and record where they get stuck. Review terminology, links, and examples separately in each language rather than translating labels only. Fix major gaps before handoff; do not pad to a word-count target.
Output: Walkthrough findings, fixes, and unresolved questions.
Tools
- Text editor/CMS draft and browser. AI is an optional assistant, not a fact source.
Tasks to delegate within this stage
This stage currently has no dedicated execution Skill. Follow the manual guide; tools from other stages do not establish automated production or outreach.
Deliverables
- Content package: body, title, description, assets/rights, links, fact log, locale versions, and reader-test notes.
Copy this stage’s blank template →
Acceptance criteria
- The promised task is achievable, important facts are traceable, no metrics or reviews are fabricated, assets are usable, and both languages contain substantive content.
Stop conditions
- Pause publication if core steps fail, sources are insufficient, or rights are unclear. SEO presentation cannot remedy unreviewed high-risk medical, legal, or financial advice.
Next step
Once accepted, proceed to stage 4. A finished draft is not a live page.
Official sources
- Creating helpful, reliable, people-first content ↗
People-first content, original value, and reliability. · 2026-10-10 - Control your snippets in search results ↗
Search snippets may come from body content; meta descriptions are not mandatory display copy. · 2026-10-10 - SEO Starter Guide ↗
SEO purpose, no ranking guarantee, and promotion. · 2026-10-10 - Spam policies for Google web search ↗
Link spam, keyword stuffing, and scaled low-value content boundaries. · 2026-10-10
Stage structure, checklists, output templates, and diagnostic sequence are original First Crawl teaching design, not a Google-certified curriculum or ranking formula.
I understand this step. See how AI can help.
Optional. Check the required input and expected result first. Installing a Skill does not complete the work or authorize publishing, messaging, or account access.
There is no dedicated production Skill for this lesson. Complete the manual exercise above; tools from other lessons do not build this page.
The complete packages are source-reviewed; live-site execution is NOT_RUN. Private reports require existing access. Complete instruction packages are available in Chinese and English.
Continue to the next lesson
Next: check a live public page if you have one; otherwise learn from the inspection example.