Yes. Define a URL pattern like /luthiers/{family}/{city}/ and SleekRank builds a page per combination from the sheet. Each combination renders its own H1, list of luthiers, and meta tags, which is what ranks for queries like archtop guitar builder portland or harp maker minneapolis.

Remove the row from the sheet and flush the SleekRank cache. The maker page stops resolving, the family 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 builder.

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 luthiers 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. GAL number, instrument family, build style, accepted commission types, current waitlist length are all standard fields. Keep waitlist status in its own column so a one-cell edit can mark a builder as closed to new orders.

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

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