No. SleekRank does not generate tab or notation. You provide the data, written by the instructor or imported from an existing library, and SleekRank renders one indexable WordPress page per row using your base template. The actual tab lives in your sheet, JSON, or linked image.

Yes. Add an audio URL column to the sheet and map it into an audio tag or oEmbed block via a selector or tag mapping. The player appears on every lick page automatically once the column is populated. Licks without audio can hide the block via a template conditional.

Add structured columns for key, parent scale, and tempo. Map key into a tag mapping for the H1 and title, scale and tempo into selector mappings. Every lick then presents the same hero stats in the same order, which is what players expect when comparing licks.

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 lick slug. SleekPixel can render a card with the lick name, key, and tempo without designing each card by hand.

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

Yes, but it is a separate task. Build WordPress listing pages (manually or via another page group keyed by style) 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 styles array column rather than a single style. Map it as a list and use it to drive both badges on the detail page and filtering on your listing pages. SleekRank reads array columns directly when the source is JSON or a typed Notion field.