Yes. Google Sheets is one of the supported source types, alongside CSV, JSON files, JSON URLs, REST APIs, and Notion databases. Configure the sheet ID and tab name, set a cache duration, and SleekRank reads the sheet on the configured cadence. Permissions are handled via the sheet share settings; a 'view' role to the service account is enough.

Store them as an array (or pipe-separated string) in the data, then use a list mapping to repeat a list-item template inside the base page. The list-item template can include the example, an optional context note, and an audio link if you have audio per example. SleekRank repeats the template once per array entry on render.

No. SleekRank only renders pages from data you already have. The meanings, origins, registers, and example sentences need to live in your sheet, JSON file, or other source. The lexicographic work — including resolving contested etymologies and choosing the right register label — stays with your editorial team.

Selector or tag mappings replace the inner HTML of a target element, so basic markup in the data field — italics for foreign-language phrases, a link to a primary source, a small inline citation — renders as expected on the page. Sanitize HTML at the source if untrusted contributors can edit the sheet directly.

Yes. SleekRank registers generated URLs with the sitemap and noindexes the base template page so only the per-idiom URLs get crawled. New rows added between sitemap regenerations get picked up on the next sitemap rebuild. Internal linking from a /idioms/ index helps less-popular phrases get discovered.

Yes. Add the column in the sheet, add a mapping pointing to a target element on the base page, flush the cache, and the field renders on every page that has a value. Pages with empty register can either show a default label or hide the slot via template conditional. Adding a new field is one column plus one mapping, not hundreds of post edits.

Either store meanings as an array on the row (one phrase, multiple senses) and render with a list mapping, or split into separate rows with slugs like /idioms/run-out-1/ and /idioms/run-out-2/. The array approach keeps the URL count clean; the split approach gives each sense its own ranking target. Choose based on how learners search.

Yes. Add a variant column (American, British, Australian) and either render it as a badge on the page or filter the page group by variant. Keeping variants in the same sheet means a phrase like 'knock up' that means very different things across dialects can have explicit per-variant entries with appropriate register and examples for each region.