No. SleekRank does not generate music theory or chord 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 notes live in your sheet, JSON, or linked PDF.

Yes. Add an audio or video 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 progression page automatically once the column is populated. Progressions with no track can hide the block via a template conditional.

Add structured columns for key (e.g. 'C major'), mode, and a chords array. Map key into a tag mapping for the H1 and title, mode into a selector, and the chord array into a list mapping. Every progression then presents key and chords 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 progression slug. SleekPixel can render a card with the progression name, key, and chord list without designing each card by hand.

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

Yes, but it is a separate task. Build WordPress listing pages (manually or via another page group keyed by genre) 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 with a unique slug (i-v-vi-iv-in-c, i-v-vi-iv-in-g) or keep one row per shape and render transposed chord lists at request time with a small Twig helper. The first approach gives each transposition its own indexable URL.