Yes. Define a URL pattern like /piano-restorers/{brand}/{city}/ and SleekRank builds a page per combination from the sheet. Each combination renders its own H1, list of restorers, and meta tags, which is what ranks for queries like steinway restoration chicago or bosendorfer rebuild new york.

Remove the row from the sheet and flush the SleekRank cache. The restorer page stops resolving, the brand and city 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.

No. SleekRank only maps data you already have into a template page. Bios live in the sheet, written once there. If you want AI-assisted drafting, run a separate workflow and paste the output into the sheet bio 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 restorers 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. RPT status, brand specialties, restoration scope (action, soundboard, refinish), current capacity, and turnaround time are all standard fields. Keep capacity status in its own column so a one-cell edit can mark a restorer as full.

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 brands as a JSON array column. A list mapping renders each brand as a tag on the restorer page. For brand hubs, the restorer appears under each brand they service, without duplicating the canonical bio page across the brand taxonomy.

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