Yes. Define a URL pattern like /archaeologists/{scope}/{state}/ and SleekRank renders a page per combination from the sheet. Each combination gets its own H1, list of firms, and meta tags, which is what ranks for queries like Section 106 archaeologist Arizona or Phase I survey Texas on Google search results.

Edit the rpa_status column to lapsed and flush the cache. The badge disappears from the firm page, the per-scope and per-state hubs drop the listing, and the sitemap regenerates on the next refresh. The roster stays the source of truth so the federal agency never books a Section 106 review from a lapsed RPA firm.

Add a shpo_listed_states column that stores all states a firm appears on the state historic preservation office list. A list mapping renders the badge per state, and the same firm appears on every state hub where they hold SHPO listing without duplication in the directory.

Each generated URL is a real WordPress page with full HTML and ships in the auto-generated XML sitemap. The base template page is auto-noindexed so it never competes with the children. Google treats each firm URL as a distinct page with its own canonical and Open Graph metadata across the directory.

Yes. SleekRank uses an existing WordPress page as the template, so Bricks, Elementor, Gutenberg, Oxygen, and classic themes all render through the mapping layer. The directory design stays put, only the data source changes from manual edits to the RPA roster sheet for the public directory.

Yes. Add a curation_facility column to the roster. A tag mapping injects the curation badge into the firm page, and a per-curation hub can publish /archaeologists/with-curation-facility/ filtered to firms that maintain federally accredited curation for projects requiring long-term storage of cultural materials.

Delete the row from the sheet and flush the cache. The firm URL stops resolving and returns 404, the scope and state hubs update to omit them, and the sitemap regenerates on the next refresh. For rebrands, redirect the old slug to the new firm so any earned link equity is preserved.

Yes. Instead of a static sheet, point the page group at the RPA membership endpoint with cacheDuration set to refresh weekly. Live registration status, fresh continuing education, and disciplinary actions propagate to the public directory without any manual sync from ops.