Turn Any How-To Blog Post into HowTo Schema

Act as a structured-data engineer. I'll paste a how-to / tutorial blog post. Extract steps, tools, supplies, time, and images into a complete Schema.org HowTo JSON-LD block, and audit any step AI engines won't cite confidently.

Post context: URL [https://YOUR-DOMAIN.COM/blog/...] · author [NAME] · author URL [URL or BLANK] · published [YYYY-MM-DD] · updated [YYYY-MM-DD or SAME] · featured image URL [https://...] · total time [ISO "PT2H30M", plain, or BLANK to estimate] · cost USD [AMOUNT or BLANK]

Post content (markdown or HTML):
[PASTE]

Extract: every distinct step in execution order — imperative name, 1-3 sentence text, image URL if present (null if not — don't invent), anchor URL if present · all tools · all supplies · total time (estimate if missing, show reasoning) · the implicit question, as `name` + `description`.

Output:
1. Extraction summary — step count, tool count, supply count, time + reasoning, featured image confirmed y/n, implicit question
2. Step audit table: # · Name · Has text · Has image · Has anchor · AEO-ready (y/n + one-line issue) — with a one-line fix for any that aren't
3. Full <script type="application/ld+json"> HowTo block — name, description, image, totalTime, estimatedCost, supply, tool, step (name/text/image/url), datePublished, dateModified, author. JSON-valid; omit fields rather than null where valid
4. Deploy — paste location, microdata-vs-JSON-LD warning, any guessed or estimated value flagged; the Schema.org validator at https://validator.schema.org to check the block; one plain sentence telling me that HowTo is not among the rich results Google supports, so this markup will not change how my post looks in Google results; and a one-line offer to write Article markup for this post, a type Google does support

Success means the step count in the JSON-LD equals the step count in the post, and no URL in the block is one that isn't in the post or my context.

Apply every rule, limit, and format above to every item in the deliverable, not just the first one. Deliver the complete result in one response — every section filled in, nothing deferred to a follow-up.

If a required input is missing, ask for it once before starting; otherwise proceed and label any assumption you made.

Notes: R40 refresh; tuned to vendor prompting guidance