Yes. Each row in the ICPI roster becomes one cached page, so the practical ceiling is your sitemap budget and Google's crawl rate, not SleekRank. A 5,000-row directory renders without code changes. Most directories pace their growth so the sitemap submission and indexation cycle stays within Search Console's normal cadence.

The icpi_level column refreshes whenever the ICPI source refreshes. A mapping renders the certification level as a pill, and the template adjusts the page accordingly. When an installer upgrades from CIP to AP after the next test cycle, the new credential appears on the next cache refresh without WordPress edits.

Yes. The materials column maps to a list facet on the page group. Brick, concrete, natural stone, cobblestone, porcelain, and permeable each become a chip in the sidebar, and the available chips are computed from the live data. Adding an installer who does porcelain pavers makes that chip appear automatically.

Yes. The permeable_certified column drives a sustainability pill on the page and a filter chip in the sidebar. Municipal stormwater RFPs and LEED-credit GCs can filter directly to permeable-certified installers, which is impossible on a generic home services aggregator that does not store that field.

Drop the row from the source and the URL returns a 404 on the next refresh. The sitemap removes the entry on the same cycle. If an installer loses ICPI certification but stays in business, the row updates in place, the cert pill disappears, and the page stays live to preserve the URL and any inbound links.

Yes. Address, hours, service area, and business name map to LocalBusiness JSON-LD via meta and selector mappings. Materials and install methods nest inside as Service entries. The rich result eligibility check passes because the schema is rendered server-side, not after JavaScript runs in the browser.

Yes. Configure ICPI as the primary source and any secondary source, state contractor licensing, BBB ratings, or your internal vetting roster, as enrichment on the same page group. A join field links them, and each generated page renders both ICPI credentials and the secondary signal.

Yes. The sitemap is generated for every produced URL the moment the page group goes live. Submit it to Search Console once and Google discovers the URLs on its normal cycle. New installers added to the ICPI roster after launch appear as live pages and join the sitemap on the next refresh.