Use the Airtable API source with a pollInterval matching the cacheDuration. SleekRank refetches on the schedule, so any row added or retired in Airtable appears or disappears from the public directory within a day, with no manual republish on the WordPress side.

Yes. Store styles as a comma-separated column and map them through a list selector that wraps each item in an anchor tag pointed at /muralist-directory/?style=. The parent index reads the same query string and filters the card grid, keeping the data source and the UI in lockstep.

Yes, when each page carries unique style tags, scope, city and project URLs. That per-row variation, combined with the parent index linking every artist card, gives Google enough signal to crawl and index the directory at scale. The first 500 typically index within four weeks of submission.

Give each identity its own row with its own slug, and use a parent_collective column to link them. The base template can render a 'Also known as' block that pulls the related slugs through a list mapping, so visitors discovering one identity find the other without orphan listings.

Yes. Create a second page group with URL pattern /muralist-by-scope/{scope}/ pointed at a derived view of the same Airtable base. The 3,000 source rows can power per-artist and per-scope directories from one canonical source without duplicating data anywhere.

Yes. Add a hero_image column with a CDN URL and map it through a selector mapping onto the hero img src. Per-row meta image and per-row OG image use the same column, so the artist's strongest commission becomes the share card automatically.

The base template carries a VisualArtist JSON-LD block with placeholders that SleekRank fills from row fields: name, address, knowsAbout (style tags) and url. Every artist page emits valid structured data, which is what Knowledge Graph parsers actually read on the public web.

Add a editorial_intro column carrying 80 to 150 words of curator copy per artist and map it through a selector mapping onto the lead paragraph. The rest of the page is rendered from structured fields, so the editorial layer stays optional and the directory still feels human-written.