Yes. Define a URL pattern like /organ-builders/{action}/{region}/ and SleekRank builds a page per combination from the sheet. Each combination renders its own H1, list of shops, and meta tags, which is what ranks for queries like tracker organ builder midwest or electric pipe organ northeast.

Remove the row from the sheet and flush the SleekRank cache. The shop page stops resolving, the action and region hubs update to omit them, and the sitemap regenerates. Set a redirect in your normal WordPress redirects plugin if you want traffic routed to a successor shop.

No. SleekRank only maps data you already have into a template page. Shop histories live in the sheet, written once there. If you want AI-assisted drafting, run a separate workflow and paste the output into the sheet description column before the next sync.

Each generated URL is a real WordPress page with full HTML and appears in the sitemap. The base template page is auto-noindexed so it never competes with the generated children. New shops typically index within a few crawls after the sitemap update.

Yes. Any column in the sheet maps into the page using selector or tag mappings. APOBA year, action type, scale, current commission status, and historical project list are all standard fields. Keep status in its own column so a one-cell edit can mark a shop as full through a given year.

Yes. SleekRank uses an existing WordPress page as the template, so Bricks, Elementor, Gutenberg, Oxygen, and classic themes all work because rendering happens on the page output. The directory inherits whatever look the publication already uses.

Store action types as a JSON array column. A list mapping renders each action type as a tag on the shop page. For action hubs, the shop appears under each action type they offer, without duplicating the canonical page across the action taxonomy.

Yes. Build the inquiry form once into the base page using your normal form plugin and inject the shop email or routing ID via a selector mapping into a hidden field. Submissions route to the correct shop without per-page form configuration.