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 favour established recipe domains, but the structured-data prerequisite is handled.

Store ingredients as a JSON array column. The list mapping renders each entry as an li in the base page's ingredients block. There is no plugin-side length limit, only the sheet's column character limit (50,000 in Google Sheets, more than enough for any recipe).

Yes. Add a parallel array of image URLs alongside the instructions array. A list mapping renders steps with their image attached. Storage stays in your media library or a CDN; the data only carries the URLs.

Build the print view once into the base page using a CSS print stylesheet. Every generated recipe inherits it automatically because the print stylesheet ships with the template page. No per-recipe configuration needed.

Export the existing recipes to CSV or JSON and feed them in as a SleekRank data source. SleekRank doesn't migrate recipe-plugin custom posts directly - it builds a fresh, scalable corpus from data. Set up redirects from the old URLs before flipping the new ones live.

Pair SleekRank with SleekPixel to generate dynamic Open Graph images per recipe, or include an og_image URL per row pointing at a hero photo. The meta mapping for og:image picks the right field. Both approaches let each recipe carry its own share card.

Add a status column (draft, live, seasonal) and a conditional mapping that gates publication. Or maintain a parent recipe and link to seasonal variants via a related_slugs column rendered as a list. Both patterns keep variants discoverable without diluting the main recipe's authority.

Yes. Add columns for calories, protein, carbs, and fat, and map them into a nutrition card block via selectors. The Recipe schema also accepts nutrition fields, so the same data flows into both the visible card and the JSON-LD.