Certifications live in the roster sheet as columns (APA status, AAPP membership, state license, year certified, expiration). When a renewal lands, edit the cell, flush the SleekRank cache, and every page that references the examiner picks up the new value. There is no per-page editing because the data layer is the source of truth.

Yes. Use one page group with the pattern /polygraph/{slug}/ for per-examiner pages, and a second page group with /polygraph/{specialty}/{city}/ for the combination hubs. Both groups read the same roster, and list mappings in the hub template render the relevant examiners. One source feeds both surfaces.

Set the status column to retired and flush the cache. The personal page can either return 404 (remove the row entirely) or render a retired banner (keep the row, change the status). Hub lists filter on active status, so the examiner disappears from specialty and city pages without orphaning the canonical URL.

Each generated URL is a real WordPress page with full HTML, sitemap inclusion, and per-page meta tag mappings. The base template page is auto-noindexed so it never competes with the generated children. New examiners typically index within a few crawls of the sitemap update.

Yes. Store each credential as a column or as a JSON array of credential objects. A list mapping renders one badge per credential on the examiner page, and hub filters can index by credential level for buyers who require a specific tier (full member, associate, master).

Yes. SleekRank uses an existing WordPress page as the template, so Bricks, Elementor, Gutenberg, Oxygen, and classic themes all work. Rendering happens on the page output, so the directory inherits whatever the site already looks like without theme changes.

Store jurisdictions as a JSON array column. A list mapping renders each jurisdiction as a tag on the examiner page. For city hubs, generate the URL pattern from the primary city column so the examiner does not duplicate across every jurisdiction they are licensed in.

Build the form once into the base template using your normal form plugin and inject the examiner's email or routing ID via a selector mapping into a hidden field. Submissions then route directly to the examiner without per-page form configuration or duplicated forms.