When Google deprecated HowTo rich results in classic SERPs, half the SEO industry deleted the markup. That was a mistake. LLMs love HowTo — it's the cleanest possible instruction structure, and Perplexity/ChatGPT quote it near-verbatim.
- Google shrank HowTo rich results — but didn't stop parsing them.
- Perplexity and ChatGPT cite HowTo-structured steps preferentially.
- Ship on tutorials, recipes, fix-it guides — never on opinion pieces.
The minimum viable HowTo block
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to reset a WordPress password",
"step": [
{ "@type": "HowToStep", "name": "Open wp-login.php", "text": "Navigate to /wp-login.php on your site." },
{ "@type": "HowToStep", "name": "Click Lost your password", "text": "Enter your email address." }
]
}HowTo schema is dead.
It's dead in classic SERPs. It's very much alive in AI answer engines.
You need HowTo on every post.
Only on real how-to content. Everywhere else it's spam.
Will Google punish HowTo on non-howto content?
Yes — it counts as misleading structured data. Ship it only when the page truly is a step-by-step guide.
Ship this workflow inside WordPress
WBP Omni SEO Pro turns every playbook on this blog into an approvable, reversible diff.
Get WBP Omni SEO ProAffiliate — this link goes to the official WBP Omni SEO Pro product page.



