Schedule a monthly pull of the LCSJ community member list into your Google Sheet, mapping member identifiers to slugs. SleekRank re-imports on the configured cache duration, so any retired maker returns a clean 404 and any new member appears on a fresh URL within a day of joining the community.

Yes. Store specialties as a comma-separated column and map them through a list selector pointed at a ul on the base template. The parent index reads the same column for the craft filter, so a buyer needing a holster maker in their state finds qualified makers without scanning every page in the directory.

Yes, provided each row carries unique craft, city, membership year and portfolio. LCSJ data provides that per-row variation natively, and the parent index gives Google a single hub linking every card. Most directories of this size index meaningful coverage within six to eight weeks of submission.

Delete the row from the source sheet and clear the SleekRank item cache. The URL stops resolving, the entry leaves the sitemap on the next rewrite flush and the parent index drops the card. The LCSJ community roster stays the source of truth, not your WordPress post archive.

Yes. Create additional page groups with URL patterns like /saddle-maker-directory/{slug}/ and /holster-maker-directory/{slug}/ pointed at filtered views of the same source. The 2,000 rows can power one master directory plus several craft-specific directories without duplicating data anywhere.

Yes. Add a turnaround_weeks column with a number per row and map it through a tag mapping onto a hero meta line that renders 'commissions in X weeks'. The parent index can range-filter the same column, so buyers with a deadline find makers who can meet it without phoning every studio in the directory.

The base template carries a VisualArtist or LocalBusiness JSON-LD block with placeholders that SleekRank fills from row fields: name, address, knowsAbout (craft), telephone and url. Every maker page emits valid structured data, which is what Knowledge Graph and Local Pack parsers read on the public web.

Add a starting_price column carrying a string like 'wallets from $240' and map it through a tag mapping onto a pricing badge in the hero. For range filtering on the parent index, add a numeric starting_price_usd column the index can sort and filter on. The data source carries both.