No. SleekRank does not generate roasting copy or tasting notes. You provide the data, written by the roaster or imported from an existing log, and SleekRank renders one indexable WordPress page per row using your base template. The actual notes live in your sheet, JSON, or linked Artisan profile.

Yes. Add a profile URL column to the sheet and map it into a download button or anchor element via a selector or tag mapping. The button appears on every profile page automatically once the column is populated. Profiles without a linked file can hide the block via a template conditional.

Add structured columns for charge temperature, turning-point time, first-crack time, development ratio, and drop temperature. Map each into a fixed slot via tag or selector mappings. Every profile then presents the curve milestones in the same order, which is what roasters expect when comparing batches.

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 profile slug. SleekPixel can render a card with the origin, roast level, and total time without designing each card by hand.

Edit the row in the source sheet, clear the SleekRank cache, and the next request rebuilds that profile 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-profile URLs. Internal linking from a /roast-profiles/ index page helps each profile get discovered during crawl.

Yes, but it is a separate task. Build WordPress listing pages (manually or via another page group keyed by machine) 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.

Add a batch column and a parent-bean column. Either give every batch its own slug and URL or keep one row per latest-best profile and store older revisions in a history sheet referenced from the page. The first approach gives each iteration its own indexable URL.