Anywhere structured. Google Sheets and Notion work well for chef-led teams, JSON in the repo works for static archives, and a SQL database fits teams with engineering support. SleekRank reads any of them via the matching data source type.

Store the method as a JSON array where each step is an object with title, text, and optional duration. The list mapping renders whatever length the data carries, so a quick bun method and a three-day laminated dough share the same template without code changes.

Eligibility depends on valid Recipe schema, image quality, and overall site authority. SleekRank produces compliant JSON-LD from your data fields, so the technical bar is met. The carousel decision is Google's and tends to favor established recipe domains, but the structured-data prerequisite is handled.

Yes. Add a parallel array of image URLs alongside the method array, and a list mapping renders each step with its image attached. Storage stays in your media library or a CDN; the row only carries the URLs.

Store one canonical unit (grams works best for pastry) and use a small client-side toggle in the base template that converts visible values on the fly. The source stays single, and readers see whichever system they prefer.

Build the print view once into the base page using a CSS print stylesheet. Every generated pastry inherits it automatically, so the print layout stays consistent and needs no per-recipe configuration.

Add a related_techniques column listing slugs (lamination, tempering, pate-a-choux) and a list mapping renders them as links into a technique pages section. Cross-linking by technique compounds internal authority without manual curation.

Add a season column with values like winter, spring, summer, autumn, year-round. A filtered list mapping drives a seasonal cluster, and an optional status column gates whether out-of-season recipes show on the index or only at their permalink.