Yes. Set a short cache duration, around 5 to 15 minutes, on the page group. Operations updates wait_time in the sheet from the bay floor, and the next request to any shop page rebuilds from the new value. For chains running a queue system, plug the queue API into a REST data source and skip the sheet entirely.

Use separate columns for each price tier, then render them as a small table on the shop page with selector mappings. The page shows the actual price for each oil type instead of "call for pricing," which is what drivers compare across shops before they pull in.

Yes. Add promo_text and promo_expires columns. Map promo_text to a banner on the shop page and use the expiry column to hide it after the date. Promos can be set per shop or rolled out chain-wide by updating multiple rows in one paste.

Each generated URL is a full WordPress page with rendered HTML and is included in the sitemap. The base template is auto-noindexed so it never competes with its children. Shop pages typically index within a few crawls of the sitemap update.

Yes. SleekRank uses an existing WordPress page as the template, so any theme or builder works. Bricks, Elementor, Gutenberg, Oxygen, and classic themes all render generated pages because the mapping engine targets rendered HTML, not the builder shortcodes.

Store hours per shop in a JSON-array column (one entry per weekday). Render via a list mapping into a hours block. When a shop changes hours, edit the JSON for that row only and flush cache. Holidays can be handled with a holiday_hours_override column read on the day.

Yes. Add an image_url column and map og:image. For shops without unique photography, pair SleekRank with SleekPixel to template per-shop social cards using the shop name, city, and current promo price.

No. SleekRank can read a private sheet via service-account credentials or a CSV export hosted privately. Most operators publish the sheet read-only with an API key, since the data going to the public page is already meant to be public.