The International Code Council (ICC) publishes a member-jurisdiction list. State building-code commissions publish their own per-state rosters. Some construction-tech startups (PermitFlow, Shovels) maintain proprietary datasets sourced from open records. Most SleekRank setups start with ICC data, normalize jurisdiction names, and augment with state-level rosters for completeness.

Incorporated cities issue their own permits within city limits. Unincorporated areas fall under county permit jurisdiction. Some metros (Los Angeles County) handle both for different geographies. Add a jurisdiction_type field marking city, county, or special district, and let the page template render the appropriate label and authority per row in the dataset.

Most building departments require the application to be filed through their official portal for plan-review tracking. Default to a prominent outbound link to the portal with checklists and required-document lists rendered on your hub page. Embedding the actual form rarely works because the portal needs an authenticated session for plan upload.

Municipal fee schedules typically update on July 1 or January 1 depending on the jurisdiction's fiscal calendar. Most setups refresh the fee field annually via a maintained CSV import, with a last-verified timestamp rendered on each page. For projects with valuation-percentage fees, render the percentage and the base rather than a flat number.

If your dataset includes staff names (some open-data programs publish them), create a second page group for inspectors at /inspector/{slug}/. Then in the building-permits template, render the assigned inspector or reviewer as a link. Most setups skip this because staff turnover makes the corpus drift quickly without active maintenance.

PermitFlow and Shovels are paid construction-tech platforms with full automation around the actual filing workflow. Both source from the same jurisdiction data SleekRank uses. They build product on top of the data; SleekRank builds an indexable corpus. The two layers complement each other rather than compete for traffic on the same queries.

Some cities (Chicago, New York, San Francisco) publish all issued permits as open data with addresses. Run that as a separate page group at /permit/{slug}/ keyed by permit number, with the jurisdiction page linking to the historical-permits index. Two corpora, cross-linked, covering both directional intents (find the portal vs find a specific permit).

SleekRank stores each resolved row in wp_sleek_rank_items at roughly 10-30 KB per jurisdiction depending on fee-schedule depth. Two thousand rows is a 20-60 MB MySQL footprint, trivial on any production database. Most teams pair the corpus with edge HTML caching so first paint is fast for contractors searching during bid review.