Yes. Each joined row becomes one cached WordPress page, so the practical ceiling is your sitemap budget, not SleekRank. A 5,000-row directory with BBB and IUPAT data joined renders without code changes. Most directories pace their growth to match Google's crawl rate, which is usually the bottleneck on indexation, not the page generation itself.

The bbb_rating column refreshes whenever the source refreshes. A mapping renders the rating as a pill and the template switches color based on the value. A glazier that drops from A+ to B+ in a quarterly BBB export shows the new rating on the next cache refresh, no manual edits to any WordPress page.

Yes, if the source includes it. The IUPAT roster is loaded as a secondary source and joined on company name and address. When a glazier joins or leaves a local, the membership pill updates on the next refresh. Non-union shops simply do not render the pill, the rest of the template stays intact.

Yes. The specialties column maps to a list facet on the page group. Storefront, auto, mirror, shower, curtainwall, and residential each become a filter chip in the sidebar, and the available chips are computed from the live dataset. Adding a niche specialty to a row makes that chip appear automatically.

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, so Search Console deindexes it during its normal crawl. You never have to manually unpublish a WordPress page for a glazier who is no longer in business.

Yes. Address, hours, lat/lng, and company name columns map to LocalBusiness JSON-LD via meta and selector mappings. Service area and specialties nest inside as Service entries. The rich result eligibility check passes because the schema renders server-side, not via JavaScript after page load.

Each source has its own cache duration. BBB exports usually update monthly, IUPAT rosters refresh quarterly. Configure each independently, and SleekRank pulls them on their own cadence. The join happens at render time, so a glazier added to BBB this week joins their union pill next quarter when IUPAT refreshes, automatically.

Yes. The XML 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 glaziers added to either source after launch appear as live pages and join the sitemap on the next refresh.