No. SleekRank does not generate pour copy or step text. You provide the data, written by the barista or imported from an existing curriculum, and SleekRank renders one indexable WordPress page per row using your base template. The actual step-by-step lives in your sheet, JSON, or linked video.

Yes. Add a video URL column to the sheet and map it into an oEmbed block or anchor element via a selector or tag mapping. The video slot appears on every design page automatically once the column is populated. Designs without video can hide the slot via a template conditional.

Add structured columns for pour type (free pour or etched), milk texture, cup size, and shot volume. Map pour type into a tag mapping, milk texture and cup size into selectors. Every design then presents the same hero stats in the same order.

Yes. Map a meta og:image column per row using a meta mapping, or pair SleekRank with SleekPixel to generate dynamic OG images keyed by design slug. SleekPixel can render a card with the design name, pour type, and cup size without designing each card by hand.

Edit the row in the source sheet, clear the SleekRank cache, and the next request rebuilds that design page using the new data. The cache duration in the page-group config controls how often the sheet is re-read automatically. For urgent fixes, flush manually from the SleekRank settings.

Yes. Every generated URL is a real WordPress page registered with the sitemap. The base template is automatically noindexed so search engines crawl only the per-design URLs. Internal linking from a /latte-art/ index page helps each design get discovered during crawl.

Yes, but it is a separate task. Build WordPress listing pages (manually or via another page group keyed by pour type) that filter on the column. SleekRank renders detail pages, not faceted indexes, so the filtering logic lives in your theme or a small custom listing template.

Treat each combination as its own row with a unique slug (heart-into-tulip, rosetta-with-tulip-top). That gives every combination its own indexable URL and lets you link related-pours by referencing the parent slugs in a related array column.