Pass latitude and longitude fields from the data into a map embed block in the base page via selector mappings. Each generated page reads its own coordinates without any per-page work. Most embed providers accept lat/lng URL parameters; SleekRank only needs to inject them into the iframe src.

Yes. That's a separate page that uses the same data via a list mapping rendering each branch as a card. SleekRank can drive both the per-branch URLs and the all-branches index from one source - no duplicate data, no sync issues.

Add a temporary_closure or holiday_hours field to the data. Use a selector mapping that swaps a banner on the page based on the field value. Operations toggles one cell, the right branch shows the closure notice within the cache window.

It complements GBP. Google still pulls Maps results from the GBP listing, while SleekRank-generated landing pages handle organic search and "[brand] [city]" queries that GBP doesn't capture. The LocalBusiness schema on the SleekRank page also reinforces the entity Google associates with the brand.

Run two page groups with different base templates and URL patterns - /locations/{slug}/ for corporate, /franchise/{slug}/ for franchised - sourced from the same sheet via a category column, or from two separate sheets. Same plugin, two configs.

After the row is added and the cache refreshes (configurable per source), the page is live and crawlable. Most teams set a 1-hour cache during launches and a 24-hour cache thereafter. Manual cache flush via WP-CLI or the admin pushes immediately.

Yes. Add a region or country column and use selector mappings to swap content blocks based on the value - currency, date format, language hints, regional offers. The base template stays one file; the data carries the regional difference.

Add a tracking_id or location_id field per row and inject it as a data attribute via a selector mapping into your analytics scripts. Every form submit, click, or call event then attributes correctly to the specific branch without per-page tagging.