Yes. The data layer is cached per row, so the page count is bounded by your sitemap budget and crawl strategy, not by SleekRank. A 10,000-row roster from AWS plus 5,000 enrichment rows from Yelp renders without code changes. Most directories slow their growth long before they hit a technical ceiling because Google's crawl rate caps how fast new URLs get indexed.

The aws_cert_expiry column is read at cache refresh time. A mapping turns the date into a status string, and the template uses that string to render an active, expiring, or expired badge. When the roster source updates after a recertification, the next cache refresh pulls the new expiry and every affected page picks up the change.

Drop the row from the source and SleekRank returns a clean 404 for the URL on the next refresh. The XML sitemap also removes the entry, so Search Console deindexes it on its normal cycle. You never have to manually unpublish a WordPress page for a defunct shop.

Yes. process_types and primary_metal map to list templates the same way the rest of the data does. The sidebar filter reads the live dataset, so adding a row that lists "Orbital TIG" makes that filter option appear automatically. No taxonomy migration is needed when the underlying data evolves.

Yes. Address, lat/lng, hours, and shop name columns map to LocalBusiness JSON-LD via meta and selector mappings. Search Console picks up the structured data on its normal crawl, and the rich result eligibility check passes because the schema is rendered server-side, not injected by JavaScript after page load.

Use SleekRank's multi-source feature. The AWS list is the primary source, Yelp is the enrichment source, and a join field, usually a normalized address or shop ID, links the two. The page group exposes both as columns on the same row, so each generated page renders certifications and ratings together without a second request.

Filters are computed from the current dataset on each cache refresh, not stored as static taxonomy. A new metal added to a row appears as a filter option without any setup, and a metal that no longer exists in any row stops showing up. The directory stays aligned with the source of truth automatically.

Yes. The XML sitemap is generated for every produced URL the moment the page group goes live. Submit the sitemap to Search Console and Google starts discovering pages on its normal cycle. There is no separate static export to upload or per-page meta to configure before crawling can begin.