Yes. Define a URL pattern like /ironworkers/{specialty}/{local}/ and SleekRank renders a page per combination from the sheet. Each combination gets its own H1, list of certified workers, and meta tags, which is what ranks for queries like structural ironworker Local 40.

Store aws_certs as a JSON array column listing 1G, 2G, 3G, 4G, 6G ratings. A list mapping renders the certification stack, and the per-specialty hubs can filter on 6G presence for jobs requiring pipe welding qualification across the union local.

Edit the aws_certs column to remove the lapsed rating and flush the cache. The badge disappears from the page, the per-specialty hubs drop the worker from filters that required it, and the sitemap regenerates on the next cache refresh.

Yes. Add osha_rigger and osha_signal_person boolean columns. Selector mappings inject the card badges on the page, and the per-specialty hub for rigging and hoisting filters on these so only OSHA-carded workers appear in those listings.

Each generated URL is a real WordPress page with full HTML and ships in the auto-generated XML sitemap. The base template is auto-noindexed. Google treats each ironworker URL as a distinct page with its own canonical, Open Graph, and Person or LocalBusiness schema.

Yes. SleekRank uses an existing WordPress page as the template, so Bricks, Elementor, Gutenberg, Oxygen, and classic themes all render through the mapping layer without rewriting the directory design from scratch.

Yes. Store project_gallery as a JSON array of image URLs and project descriptions per shop. A list mapping renders the gallery on each shop page, and a per-project-type hub can publish /ironworkers/bridge-work/ filtered to shops with bridge projects in the portfolio.

Add an iw_classification column with values like apprentice, journeyman, or foreman. A selector mapping injects the badge, and the per-local hubs can filter so signatory contractors only see workers at the classification their project requires.