Yes, as long as the export is a CSV with a column suitable for slugification. Most production teams add a derived slug column in Google Sheets and point SleekRank at the published CSV URL. From there the mappings handle every field, no reshaping or custom code required.

Run two page groups. Use /vfx-artist-directory/{slug}/ for discipline slices and /vfx-artist/{slug}/ for individual artist profiles. Both can point at the same roster CSV with different URL patterns and mapping sets, and they share a single sitemap that lists every URL once.

Drop the studio name from the row in the source sheet or replace it with a redacted placeholder. On the next cache refresh the page no longer mentions the studio. Selector mappings render empty without breaking layout, so the rest of the page stays intact while the sensitive field disappears.

Only if you push them live in a single batch with overlapping intent. The recommended pattern is to launch the highest-intent disciplines first, monitor Search Console for crawl and index, then expand. The base template page is automatically excluded from the sitemap and marked noindex so it never competes.

Meta tag mappings inject JSON-LD into the head of each generated page using row values. Map names, primary discipline, IMDb URL, and reel URL into a Person schema block, and Google sees rich structured data on every URL. Test with the Rich Results Test before launching.

Yes. Use a locale column in the source sheet, then run a page group per locale at /vfx-artist-directory-de/{slug}/ or behind a Polylang/WPML language tree. Mappings reference the localised columns, and the base template page is duplicated per language with the same selector structure.

Update the mapping configuration once in the SleekRank settings. The mapping engine is keyed to column names, so renaming primary_software to lead_software in the source means updating the corresponding mapping target. No re-render is required beyond clearing the cache so the page reads the new fields.

Store a JSON array of recent credits in a credits column on the row, or join a separate credits sheet by artist_id. A list mapping iterates the array and renders each credit as a card in a recent work block. Update the JSON column to publish new credits on the next cache refresh.