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

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 scale page automatically once the column is populated. Scales without audio can hide the block via a template conditional.

Add structured columns for the interval formula (e.g. '1 b3 4 5 b7') and a positions array with one entry per fretboard shape. Map the formula into a tag mapping, positions into a list mapping. Every scale then presents the formula and positions 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 scale slug. SleekPixel can render a card with the scale name, root, and intervals without designing each card by hand.

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

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

Either store each transposition as its own row (a-minor-pentatonic, c-minor-pentatonic, etc.) or keep one row per mode and transpose at render time with a Twig helper. The first approach gives each transposition its own indexable URL and dramatically expands the long-tail surface.