HowTo Micromarkup Section Generator for How-To Guides

A ready-to-use prompt that turns a raw how-to topic into a complete HowTo section with schema.org microdata, timed steps, supplies and tools — structured for search-rich marketing pages.

<role>
You are a senior technical SEO strategist and structured data specialist who has spent a decade writing schema.org microdata for high-performing marketing and content websites.
</role>

<task>
Write one complete "HowTo" micromarkup section for a step-by-step guide on [topic], ready to paste into the HTML of [page type] so search engines can read it as an eligible rich result.
</task>

<context>
- The guide lives on [website name], a [industry] site written for [target audience].
- The documented process is: [step 1], [step 2], [step 3] — delivered as [number of steps] total steps.
- Every step carries a short action title, one or two sentences of instruction, an estimated duration, and an image reference where visuals help.
- The section also needs the supporting HowTo fields: name, description, totalTime, estimatedCost, supply list, tool list, and a yield or result statement.
- It is placed at [placement in page, e.g. immediately after the intro paragraph] and must match the surrounding style: [inline microdata using item scopes on existing elements].
- The reader arrived from [traffic source, e.g. organic search] and has never used [tool or product] before.
</context>

<constraints>
- Use only valid schema.org HowTo vocabulary and correct microdata syntax: wrap the section in itemscope itemtype="https://schema.org/HowTo" and attach each itemprop to the element that actually contains its value.
- Keep steps in strict sequence with values beginning at 1, and express every duration in ISO 8601 format such as PT30M.
- Write instructions in the imperative voice, one action per line, phrased so a reader can follow them without outside help.
- Keep the full section under [length limit] words or characters so page weight stays light.
- Describe images with specific, non-repetitive alt text, and escape ampersands and quotation marks inside attribute values.
- Rely only on the details supplied above; leave any unknown value as a clearly marked [placeholder to confirm] rather than inventing prices, statistics, or product names.
- Add no competitor references, no keyword stuffing, and no claims the context does not support.
</constraints>

<format>
Deliver the finished markup in this order:
1. A one-sentence opening that states what the reader will accomplish by the end.
2. The steps as an ordered list, each item carrying its own microdata attributes.
3. A short closing line pointing to [related resource, product, or call to action].
Return only the finished markup block, with no commentary before or after it.
</format>

<tone>
Clear, confident, and encouraging. Prefer short active sentences, plain language over jargon, and a helpful tone that respects the reader's time.
</tone>

Now write the HowTo micromarkup section for [topic] using the details above.