Yes. SleekRank renders into your existing WordPress page, so any access control plugin such as Restrict Content Pro or MemberPress can gate the base template. Public stubs can show discipline labels and counts while detailed bios and contact info sit behind login, all driven from the same source sheet.

Use a junction sheet that maps designer_id to one or more discipline slugs. A list mapping inside the discipline page iterates that junction to render the designer card on each relevant page. The designer row stays normalised in the master roster while the directory pages stay rich and accurate.

Store credits as a JSON array on each row, or join a separate credits sheet by designer_id. A list mapping iterates the array and renders one credit card per entry. Update the JSON column after a release, and the new credit appears on every relevant page on the next cache refresh.

Not when the data carries the difference. Designer counts, named shipped credits, seniority breakdowns, and signature studios all vary by discipline slice. Avoid copy-paste paragraphs that swap only the discipline name, because Google detects that pattern. Rich per-row data drops duplicate-content risk substantially.

Yes. Add a region column to the source sheet and define a second page group with a URL pattern such as /game-designer-directory/{region}/{slug}/. Both page groups can read the same IGDA roster CSV. SleekRank dedupes the sitemap so each URL appears once even though the underlying data is shared.

Flag the row with a public column set to false. A SleekRank source-level filter excludes those rows entirely, so they never reach a generated page. If you only want to mask the name, replace it with an alias in the source sheet, and the discipline page shows the alias on the next cache refresh.

Yes. A WordPress custom post type with ACF or Meta Box fields is a supported data source. SleekRank reads the post list as rows and the field values as columns, which suits design orgs that already maintain rosters inside the WordPress admin rather than in Google Sheets or Notion.

Pass the slug into a hidden form field on your existing contact form. Form submissions arrive tagged with the discipline slug they came from, so your hiring team sees which slices drive applications. Selector mappings inject the slug into the form's data-source attribute without any custom JavaScript.