No. SleekRank does not translate or generate any content. You provide the translated phrases in a sheet — typically as an array of source-translated pairs per language pair — and SleekRank renders them on the per-pair page. Translation accuracy is your editorial responsibility, ideally handled by qualified translators who edit the sheet directly.

Yes. Use a meta mapping for og:image with a per-row column if your designer produces individual images, or pair with SleekPixel for dynamic images that take the slug as a parameter and render a branded card with the pair name on top of a designed template. SleekPixel handles the per-pair text without any manual design work.

Add columns for source ISO code (en) and target ISO code (es, fr, de) and map them into the page via tag or selector mappings. They become part of the data, available for hreflang attributes, schema.org Course markup, and any other downstream use. Keep them consistent across the sheet so machine consumers stay reliable.

Yes. Each direction is just another row with its own slug — spanish-english as a separate row from english-spanish. Add as many directions as you have translations for. The sheet stays flat, and each direction gets its own indexable URL with its own H1, meta, and phrase list. Translators decide which directions to prioritize based on demand.

SleekRank renders pages on whichever language version of the base page lives on. If you use Polylang or WPML, run one base page per site language and configure separate page groups per language. Each language version then has its own /learn/{slug}/ tree. SleekRank itself does not handle the multilingual routing; the multilingual plugin does.

Yes. Each generated URL is a real WordPress page included in the sitemap, suitable for indexing. The base template is excluded automatically so the scaffolding does not compete with the real pair hubs. Standard SEO plugins still handle canonicalization, per-page meta, and hreflang. Flush rewrites after adding new pair slugs.

Extend each phrase array entry into an object with source, target, and audioUrl fields. Map the array via a list mapping and render each entry through a template partial that handles the audio player. The sheet stays the source of truth; the rendering layer decides how to display the structured data on the page.

Yes. Tag each phrase entry with a category (greetings, numbers, food) and either pre-group them in the sheet or apply category filtering inside the base template. The list mapping respects array order, so the simplest approach is to sort by category in the sheet so greetings appear first, numbers next, and so on, with category headings rendered between groups.