Yes. Define a URL pattern like /pool-table-movers/{size}/{city}/ and SleekRank renders a page per combination from the sheet. Each combination gets its own H1, list of qualified crews, and meta tags, which is what ranks for queries like nine foot table mover Austin across the billiards directory.

Store slate_reseal_capable as a boolean column. A selector mapping injects the slate-reseal badge on each page, and a per-capability hub can publish /pool-table-movers/slate-reseal/{city}/ filtered to crews with documented slate specialists on staff and antique-table experience in portfolios.

Edit the brand_authorizations column to remove the brand and flush the cache. The badge disappears, the per-brand hubs drop the listing, and the sitemap regenerates on the next cache refresh. The dealer network stays the source of truth, so customers never book from stale dealer claims.

Yes. Add an antique_experience boolean and an antique_table_brands JSON array column. A list mapping renders the antique experience on each page, and a per-brand hub can publish /pool-table-movers/antique-brunswick/ filtered to crews with documented vintage Brunswick experience listed.

Each generated URL is a real WordPress page with full HTML and ships in the auto-generated XML sitemap. The base template is auto-noindexed. Google treats each crew URL as a distinct page with its own canonical, Open Graph metadata, and LocalBusiness schema markup.

Yes. SleekRank uses an existing WordPress page as the template, so Bricks, Elementor, Gutenberg, Oxygen, and classic themes all render through the mapping layer without rewriting the directory design from scratch or migrating any brand-layer styling work.

Yes. Store crew_size as a number and equipment_list as a JSON array. A list mapping renders the equipment stack on each crew page including slate dollies, level kits, and reseal supplies, and the per-equipment hub can publish equipment-specific filtered listings.

Delete the row from the sheet and flush the cache. The mover URL stops resolving and returns 404, the size and city hubs update to omit them, and the sitemap regenerates. For planned closures, redirect the slug to the relevant city hub to preserve link equity.