Yes, if the source exposes JSON, CSV, or a REST endpoint your WordPress server can reach. SleekRank does not integrate with proprietary booking platforms directly. Most agencies build a middleware export from their internal booking system into a normalised JSON feed, then point a SleekRank page group at that feed for rendering on the configured cacheDuration.

Use a status column and either drop closed rows at the urlPattern level so they fall out of the sitemap, or hide the submit CTA via a conditional in the base page while keeping the URL alive. The second pattern preserves accumulated backlinks and lets mother agencies reference past booking details when negotiating future shoots for the same client.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel to render dynamic booking cards combining shoot type, location, and rate. Configure the meta mapping in the page group and each call gets a unique social card for the times the URL is shared in agency email blasts or modeling Slack channels during active booking windows.

No. SleekRank renders pages and does not process submissions, polaroids, or comp card uploads. Use a selector mapping to link to the agency's submission portal or model booker email. Most agencies link out to keep the official channel as the source of truth and avoid handling sensitive model data on the directory side.

Yes. Add a shoot type column and reference it in the urlPattern as /model-calls/{type}/{slug}/, or run parallel page groups per type if base page layouts need to differ between editorial, runway, e-commerce, and fit work. Each group reads the same feed but applies different filters and templates, keeping URLs distinct and rankable per shoot type cluster.

Edit the feed or sheet and clear the SleekRank cache. Pages reflect the new values on the next request. For productions that shift shoot windows often, set cacheDuration low during peak fashion week periods so changes propagate without manual flushes. The trade off is more frequent fetches from the data source under traffic load.

Yes. Add columns for usage scope (digital, print, broadcast), buyout terms, and duration, then surface them through tag and list mappings in the base page template. Usage and buyout drive submission decisions for agents calculating long term value, so surfacing these prominently improves the quality of submissions reaching the booking team.

Surface sizing requirements neutrally per industry casting language. Store height, measurements, and size range as structured columns and map them through selector blocks. Avoid exposing client identity if a booking is under NDA, by using a separate visibility flag column the base page respects to keep brand confidentiality intact pre release.