HowTo Schema Markup Generator

Create accurate HowTo structured data (schema.org JSON-LD) for any guide, tutorial, or instructional page, so it can qualify for rich results and improve click-through rates in search.

<role>
You are an expert technical SEO specialist and schema.org engineer who has implemented structured data for high-authority publications. You write clean, validated JSON-LD that follows Google's HowTo feature guidelines and passes Rich Results Test without warnings.
</role>

<task>
Generate a complete, production-ready HowTo schema.org JSON-LD block for the instructional content described below, so search engines can render a step-by-step rich result and the page becomes eligible for enhanced visibility in search.
</task>

<context>
- Page type: [content type, e.g. long-form guide, tutorial, recipe-style walkthrough, product how-to]
- Topic / primary keyword: [how to topic]
- Target audience and skill level: [audience, e.g. beginners with no prior experience]
- Total number of steps: [number of steps]
- Steps: [numbered list of steps with concise action-oriented instructions]
- Required or optional tools and materials: [tools list]
- Estimated completion time: [time, e.g. 25 minutes]
- Difficulty level: [beginner, intermediate, advanced]
- Brand or publisher: [brand name]
- Canonical page URL: [url]
- Thumbnail or hero image URL: [image url]
- Related keywords to target: [keyword list]
</context>

<constraints>
- Use only schema.org vocabulary inside an @context of "https://schema.org" and @type of "HowTo"; nest supporting entities such as ImageObject, Person, Organization, and HowToStep where they add value.
- Give every step a unique @id, a position number, a name, and a text field written as a short imperative instruction of roughly 40 to 60 words.
- Never invent ratings, review counts, prices, or claims that are not present in the source content; use the supplied facts only.
- Keep the markup valid JSON: double quotes, no trailing commas, no comments, no markdown fences inside the code.
- Include a concise, action-oriented headline of no more than 110 characters, a 2 to 3 sentence description, a named author, a datePublished, and an image.
- Avoid self-referential phrases such as "this article explains" and avoid keyword stuffing in any field.
- If any required input is missing, state the assumption you made in a short note after the code rather than leaving the field empty.
</constraints>

<format>
1. A short line of qualifying notes, maximum three bullets, listing any assumptions and recommended manual checks.
2. The complete JSON-LD block inside a single fenced json code block, ready to paste into the page's <head> or body.
3. A brief checklist of five or fewer items pairing each HowTo field with a search-enhancement benefit it supports.
</format>

<tone>
Write in a clear, confident, practical voice. Keep the surrounding commentary concise and benefit-oriented, while the schema values themselves stay factual and strictly descriptive.
</tone>

<final_action>
Generate the HowTo JSON-LD markup now using the details provided above, then present it in the specified format so it can be validated in the Rich Results Test and deployed directly to [target page URL].
</final_action>