Yes, if the source exposes JSON, CSV, or a REST endpoint your WordPress server can reach. SleekRank does not integrate with proprietary casting platforms like Breakdown Services or Casting Networks directly. Most aggregators build a middleware export from their internal CRM 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 agents reference past call details when negotiating future bookings for the same production or director.

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

No. SleekRank renders pages and does not process submissions, headshots, or self tape uploads. Use a selector mapping to link to the casting office's submission portal, often Casting Networks or a private intake form. Most aggregators link out to keep the official channel as the source of truth and avoid handling sensitive talent data on the directory side.

Yes. Add a project type column and reference it in the urlPattern as /casting/{project}/{slug}/, or run parallel page groups per type if base page layouts need to differ between features, commercials, and theater. Each group reads the same feed but applies different filters and templates, keeping URLs distinct and rankable per project cluster.

Edit the feed or sheet and clear the SleekRank cache. Pages reflect the new values on the next request. For productions that shift audition windows often, set cacheDuration low during active casting 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 union status (SAG-AFTRA, ACTRA, non union), usage scope, and buyout terms, then surface them through tag and list mappings in the base page template. Union status and usage drive submission decisions for actors and agents calculating residual potential, so surfacing these prominently improves the quality of submissions reaching the casting office.

For roles requiring specific age, ethnicity, or gender expression, surface this neutrally and professionally per industry casting language standards. Store these as structured columns and map them through selector blocks. Avoid exposing private production details like working title or location specifics if the production is under embargo, by using a separate visibility flag column the base page respects.