HowTo, Recipe and Event schema — Indian-context recipes

Quick frame: Three structured-data types Indian publishers underuse — HowTo for financial procedures (filing ITR, applying for PAN), Recipe for Indian cuisine, Event for India-timezone gatherings. Each has India-specific gotchas around ISO timing and language.

HowTo for Indian financial procedures

Google restricted HowTo rich results to desktop and select verticals in September 2023, but the schema still earns AI Overview citations and remains a strong topical signal. Use it on:

• ITR filing step-by-steps.
• PAN / TAN application walkthroughs.
• NPS subscription / withdrawal procedures.
• GST registration flows.

5–10 steps is the sweet spot, each with a clear name and meaningful text. Use the HowTo schema generator.

Recipe schema for Indian cuisine

Recipe schema still earns full rich results (the recipe card with image, time, rating, cuisine). For Indian publishers, fill in:

• recipeCuisine: "Indian", "South Indian", "Bengali" etc.
• cookTime / prepTime in ISO 8601 (PT30M = 30 mins).
• recipeYield: "4 servings" or just "4".
• recipeIngredient: one per line, with quantities.

Event schema for IST events

The most common Event schema bug: timezone string. Validators reject "IST" strings — always use the offset form:

"startDate": "2026-09-12T09:00:00+05:30"

Both startDate and endDate need the offset. For hybrid events (common post-2020), set eventAttendanceMode to MixedEventAttendanceMode and provide both Place (physical venue) and VirtualLocation (URL).

Use the Event schema generator — it defaults to +05:30.

What unites all three

Google's requirement that schema match visible content. If your HowTo says 5 steps, your page must show 5 steps. If your Recipe lists 8 ingredients, all 8 must be in the page. If your Event lists a venue, the venue must appear on the page. Skip this and you lose rich-result eligibility.

Validation workflow

After deploying any of the three, run the URL through Google's Rich Results Test. Look for warnings (recoverable) and errors (blocking). Full walkthrough in validating schema with Google rich results.

FAQ

Q. Can I use HowTo and Recipe on the same page? A. No — they conflict. Pick one. Recipe is the right choice for any food-related procedure; HowTo for non-food procedures.

Q. Does Event schema need offers for free events? A. Yes — set price: 0 and availability: Free. Without an offers block, eligibility for the Event rich result is reduced.

Q. Should language be specified for Indic-language Recipe / HowTo? A. Use inLanguage with the language code ("hi", "ta"). Helps Google serve the right language to the right searcher.