No. SleekRank does not translate or generate vocabulary. You provide the dataset — written by language editors, reviewed by native speakers, and versioned in the sheet — and SleekRank renders pages from those rows. The translation work, including disambiguation between similar terms, stays with your editors. SleekRank is a rendering layer.

Yes. Use a theme column and either include it in the slug like /vocab/spanish-a1-travel/ or run separate page groups per theme. The same sheet can drive multiple page groups: one keyed by language-and-level, one keyed by language-level-and-theme, depending on which slices of the catalog you want as their own URLs.

Embed example sentences inside each word object and render them inside the list mapping. SleekRank renders whatever HTML you map. A typical word object has fields for term, translation, transliteration, and an example, with the list-item template laying them out consistently. Example audio can be referenced by URL the same way.

Yes. Add an audio URL per word and render an audio element inside the list item. SleekRank places the HTML you map. A common pattern is to host audio files in the WordPress media library or a CDN, reference them by URL in the sheet, and render a small play button on each list item via the template.

Edit the source row, clear the SleekRank cache, and every page that references that word is rebuilt on the next request. For corrections caught after a native-speaker review, this matters: a single word might appear on multiple level lists, multiple theme lists, and multiple language-pair lists, all of which update from one sheet edit.

Yes. Each language-and-level URL is a real WordPress page in the sitemap. The base template is auto-excluded. Internal linking from a /vocab/ language index, from related-level links, and from theme indexes helps every combination get discovered, including long-tail queries like 'Italian B2 work vocabulary'.

Yes. Expose the sheet via a JSON endpoint or REST API and consume it from a separate flashcard front-end. SleekRank renders the public pages; the flashcard app reads the same rows. One source of truth means corrections land everywhere — public pages, flashcards, and any printable PDFs generated from the same data.

Add a variant column (Castilian, Latin American, European Portuguese, Brazilian Portuguese) and either filter the page group by variant or include the variant in the slug. Keeping variants in the same sheet means a corrected gloss can apply across variants where appropriate, with explicit overrides where the variant differs.