Yes. Notion is one of the supported source types alongside Google Sheets, CSV, JSON, REST, and others. Connect a database via Notion's API and map its properties into the base page through tag, selector, list, and meta mappings. Rich text properties translate into HTML, multi-select into arrays for list mapping, and relations can join across tables for artist-to-exhibition connections.

Store them as an array on the artist row, with each entry containing show name, year, and gallery. The list mapping renders each entry as a list item on the artist page, sorted by year descending. When a show concludes, append it to the array on every participating artist's row, and their pages update on the next cache cycle without per-page editing.

Yes, by mapping an array of image URLs into a gallery markup block via selector mapping or list mapping. SleekRank does not host images but injects per-artist URLs from your CDN or media library. The base template defines the gallery block once with a Gutenberg gallery, Bricks slider, or Elementor carousel; the data layer fills it with artist-specific images.

Run separate page groups per language with translated columns, or use a translation layer downstream. SleekRank itself just consumes whatever data you feed it, so a French roster sheet and an English roster sheet can drive /fr/art/{slug}/ and /en/art/{slug}/ respectively, with hreflang tags injected via meta mapping to indicate language relationships.

No. SleekRank noindexes the base template automatically so only per-artist, per-gallery, and per-exhibition pages compete in search. The base page is a working template that exists for the data layer to populate, not a page meant to surface to readers. Search Console reports will show only the generated URLs as indexable, which keeps the catalog clean.

Yes. Map a portrait URL into the og:image meta mapping, or pair with SleekPixel for dynamic per-artist OG images that overlay the artist name, medium, and current show over a styled background. Per-artist OG images materially improve social click-through compared to a single gallery-default image when collectors share artist links.

Edit the bio column in Notion or the sheet, then flush SleekRank's cache for that source. The corrected bio appears on the artist page, the gallery roster page, and any other URL that references it on the next request. With a short cache duration set, edits propagate automatically without a manual flush, at the cost of slightly more frequent source reads.

Yes, if you keep a single roster source where each artist row records every gallery that represents them as a JSON array. The artist page lists all galleries; each gallery page filters to artists whose array includes that gallery's slug. Cross-representation common in contemporary art shows up correctly without duplicating artist rows per gallery, which avoids the maintenance burden of split records.