Yes, if the source exposes JSON, CSV, or a REST endpoint your WordPress server can reach. SleekRank does not integrate with proprietary voice casting platforms like Voice123 or Voices.com 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 audition CTA via a conditional in the base page while keeping the URL alive. The second pattern preserves accumulated backlinks and lets agents reference past role details when negotiating sequel sessions or pickup work for the same project.

Yes. Map an image URL column to og:image, or pair SleekRank with SleekPixel to render dynamic role cards combining project type, voice profile, 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 voice acting Discord servers or agent email blasts during active casting periods.

No. SleekRank renders pages and does not process audition file uploads or payments. Use a selector mapping to link to the studio's submission portal or casting director's intake form. Most aggregators link out to keep the official channel as the source of truth and avoid handling audio files on the directory side, which scale poorly in WordPress media libraries.

Yes. Add a project type column and reference it in the urlPattern as /voice-casting/{project}/{slug}/, or run parallel page groups per type if base page layouts need to differ between animation, games, commercials, and audiobooks. 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 usage scope (broadcast, web, in game, perpetuity), buyout terms, and royalty structure, then surface them through tag and list mappings in the base page template. Usage and royalty drive audition decisions for voice actors and agents calculating long term value beyond the session day rate, so surface these prominently.

Store voice profile descriptions as structured columns (age range, gender, tone, accent) and map them through selector or tag blocks in the base page. Detailed profiles attract qualified auditions and reduce mismatched submissions, which saves time on both the casting and talent side and tightens the audition shortlist before sessions begin.