Yes. Run a second page group with /ma/specialization/{slug}/ as the URL pattern, sourced from the same sheet. A list mapping filters rows whose specializations array includes the slug. One sheet, two URL patterns, no duplicate maintenance.

Store a JSON array of departments per row and render the same program under each department hub through a list filter. Decide whether each version is indexable or whether one is canonical, then set link rel canonical accordingly via meta mapping.

Either model them as separate rows for distinct URLs or keep one row with a JSON object describing track options and render both via list mappings on the same page. Separate rows give each track its own search slot.

Yes. Build the application CTA once into the base WordPress page and inject the application_url from the row via a selector mapping into the button href. Each program URL routes to the correct online application.

EducationalOccupationalProgram with provider as the school, occupationalCredentialAwarded as the MA degree, programType as the format, and timeToComplete as the length. Map fields to a JSON-LD block via a meta mapping, then validate one page in the Rich Results Test.

Store a JSON array of faculty slugs and render them as a small grid through a list mapping. Faculty bios live on their own indexable URLs elsewhere on the site, so the MA page links rather than duplicates.

Each hub lists different programs, different specializations, and different faculty. Give each one a unique meta description and intro paragraph keyed off the department, and the corpus reads as a real graduate catalog. Variation comes from the data.

Yes. Run multiple URL patterns scoped to /uk/ma/{slug}/ or /paris-campus/ma/{slug}/ with a campus column gating which rows render in each pattern. One roster, multiple campus catalogs.