What HowTo schema is
HowTo is the Schema.org type for step-by-step procedural instructions — a tutorial, a recipe (with the more specific Recipe subtype), a maintenance procedure. The shape: a top-level HowTo object with a name and description, plus a step array of HowToStep objects. Each HowToStep has a name and text, and optionally an image or video. Additional HowTo properties: tool (a HowToTool array — objects used but not consumed), supply (a HowToSupply array — consumed), totalTime (an ISO 8601 duration), estimatedCost, performTime, prepTime, yield.
The September 2023 deprecation
Google removed the HowTo rich result across both desktop and mobile in September 2023. The Search Central changelog announcement was terse: the rich result was no longer shown, and the dedicated HowTo documentation page was retired. The deprecation was complete — there were no carve-outs by vertical (unlike FAQ, which retained eligibility for government and health authorities), no regional differences, no plans to reintroduce in any form Google has communicated.
When to use HowTo in 2026
Install HowTo only on articles that are genuinely step-by-step procedural instructions. A blog post with a few tips is not a HowTo. A 7-step setup guide with named steps is. The test: can the article be reduced to a numbered list of named steps without losing its essential structure? If yes, HowTo applies. If no, skip it. Squarespace owners often install HowTo on articles that aren't really procedural — a 'how to choose the right paint colour' post that's really an opinion piece, for example — which is structurally invalid and adds maintenance burden without benefit.
Required and recommended fields
Schema.org's HowTo type has no hard required fields, but a useful install carries: name (the procedure title), description (a short summary), step (an array of HowToStep, each with name + text). Recommended additions where applicable: tool (a HowToTool array, objects used but not consumed), supply (a HowToSupply array, consumed), totalTime (ISO 8601 duration), image (an image of the finished result), estimatedCost (when relevant).
Copy-paste JSON-LD example
The block below is a HowTo schema for a 5-step Squarespace photo-prep procedure. The example mirrors the howTo prop format already used inside the Article layout on this site — every page passing a howTo prop ends up emitting structurally similar JSON. Replace the procedure name and steps with your own.
Where to paste it on Squarespace
HowTo goes per-page on the article that carries the procedural instructions. Open the article page in the Squarespace editor, Page Settings > Advanced > Page Header Code Injection, paste the script block, save. The schema only makes sense on a page that actually contains a step-by-step procedure visible to users — installing HowTo on a page that doesn't display steps technically violates the content-fidelity policy.
Validation steps
Validate at validator.schema.org rather than Google's Rich Results Test. Since Google retired the HowTo rich result, the Rich Results Test no longer specifically tests HowTo — it parses the markup but reports 'no rich result available' as expected. The Schema.org validator confirms structural validity against the current Schema.org vocabulary. A clean Schema.org validation is the success signal.
Common gotchas on Squarespace
Three gotchas catch most HowTo installs. First: installing HowTo on articles that aren't actually procedural — a how-to-style title with discursive content. The schema parses but misrepresents the page. Second: expecting a Google rich-result enhancement after the 2023 deprecation — none arrives. The win is AI engine extraction and structural integrity. Third: schema/visible mismatch — the schema lists 7 steps but the page only displays 5 visibly. Audit by reading the page top to bottom and matching each visible step to a schema step.
Related schema types
HowTo typically ships alongside Article on the same page — the Article describes the page as editorial content, the HowTo describes the procedural structure inside. Recipe is the HowTo subtype that still triggers Google rich results in 2026 (for food recipes specifically); use Recipe instead of HowTo when the procedure is a recipe. BreadcrumbList belongs alongside on every page.