Skip to content

Page uses schema types Google deprecated for desktop rich results in H1 2026 (HowTo / PracticeProblem / MathSolver)

Schema markup is hidden code added to a webpage that describes its content in a structured way, so search engines can display it as a rich result, such as a step-by-step box, instead of a plain blue link. This site still uses three schema types, HowTo, PracticeProblem and MathSolver, that Google stopped supporting for desktop rich results from January 2026. The markup itself isn't broken, but it no longer does the job it was added for. This doesn't break anything visibly, but deprecated schema is a quiet freshness signal to Google and AI crawlers that a page hasn't been actively maintained, which can work against it when freshness is weighed against newer competitor pages. The one exception is if AI-engine citation is specifically your goal, since some AI systems still read HowTo schema even though Google's rich results no longer act on it. Your developer and content team should migrate any HowTo content into a standard Article with an ordered list and Step schema, and remove or replace PracticeProblem and MathSolver markup with Question and Answer schema instead. This is a markup swap rather than a content rewrite, and the engine estimates about 2 hours of work once the affected pages are identified.

Why this matters

This doesn't break anything visibly, but deprecated schema is a quiet freshness signal to Google and AI crawlers that a page hasn't been actively maintained, which can work against it when freshness is weighed against newer competitor pages. The one exception is if AI-engine citation is specifically your goal, since some AI systems still read HowTo schema even though Google's rich results no longer act on it.

How to fix it

Your developer and content team should migrate any HowTo content into a standard Article with an ordered list and Step schema, and remove or replace PracticeProblem and MathSolver markup with Question and Answer schema instead. This is a markup swap rather than a content rewrite, and the engine estimates about 2 hours of work once the affected pages are identified.