Yes. Define a URL pattern like /location-scouts/{region}/{productionType}/ and SleekRank builds a page per combination from the sheet. Each combination renders its own H1, scout list, and meta tags, which is what ranks for queries like nyc location scout commercial.

Update the row with the new regions or production types, or mark them inactive, then flush the SleekRank cache. The scout's page either updates or stops resolving, and the region and production type hubs reflect the change automatically.

No. SleekRank only maps fields from the sheet into the template. Bios live in the sheet, written once there. For AI-assisted drafting, run that workflow separately and paste output into the bio column before the next sync.

Each generated URL is a real WordPress page with full HTML and appears in the sitemap. The base template page is auto-noindexed so it never competes with the generated children. New scouts typically index within a few crawls after a sitemap update.

Yes. Any column in the sheet maps into the page using tag or selector mappings. LMGI tier, DGA acceptance, accepted production types like feature or TV or commercial, accepted regions, and recent credits are all standard fields the template engine supports.

Yes. SleekRank uses an existing WordPress page as the template, so Bricks, Elementor, Gutenberg, Oxygen, and classic themes all work because the rendering happens at page output. The directory inherits whatever look the commission already uses.

Store regions as a JSON array column. A list mapping renders each region as a tag on the scout page, and the scout appears under each region hub they cover. There is one canonical scout page so search engines see no duplicates.

Yes. Build the form once into the base page using your normal form plugin and inject the scout email or routing ID via a selector mapping into a hidden field. Submissions then route to the correct scout without per-page form configuration.