Yes. Use a column or JSON field for image URLs and map it with the meta type for og:image, the selector type for the hero image, and the list type for in-page galleries with multiple works. Keep images on a CDN or your media library so renaming hosts does not invalidate the catalog. For dynamic OG variations, pair with SleekPixel.

Remove the row from the sheet. After the cache window, the URL stops being generated, drops from the sitemap, and returns a 404 to crawlers. If the page had earned backlinks, set a 301 redirect from the old URL to a relevant medium or city page to preserve that link equity rather than serving a 404 to existing readers and search engines.

No. SleekRank uses an existing WordPress page as the template, so it works with whatever theme or builder built that page. Bricks, Elementor, Oxygen, Gutenberg, and any classic theme all work the same way. The placeholder structure you build once is what every generated artist page renders, with row data swapped in via mappings.

The cache duration you set per source determines refresh frequency. Six hours is a reasonable default for active rosters, daily for quieter ones. You can also flush the cache manually after a big update from the WordPress admin without waiting for the cache to expire, which is useful when a major announcement needs to go live immediately.

Yes. SleekRank reads from Notion, Google Sheets, CSV, JSON, and REST API sources. Connect a Notion database via the API and map its properties into the base page through tag, selector, list, and meta mappings. Rich text fields translate into HTML, multi-select into arrays, and database relations into joined data across tables.

No. SleekRank does not generate images. It maps image URLs from your data into the page. Pair with SleekPixel if you want dynamic OG images that overlay the artist name, medium, and current show over a styled background. SleekPixel renders OG images from data on the fly, which is the right pairing for per-artist social cards.

Yes. Keep a separate works sheet or JSON file with each work as a row, joined to the artist by artist slug. The artist page can render works filtered to their slug via list mapping, and each work can have its own URL at /artists/{slug}/work/{work-slug}/ if you create a nested page group. This keeps the works dataset clean rather than embedding it as nested arrays on the artist row.

Store galleries as a JSON array on the artist row rather than a single string. The list mapping renders each gallery as a linked list item on the artist page. For gallery-specific roll-ups, the gallery-keyed page group can match any artist whose array includes that gallery's slug, so cross-representation common in fine art shows up correctly without duplicate artist rows.