Yes. Most draft farms own horses across Belgian, Percheron, and crossbred registries. Add a registry_name and registry_number column in your sheet and SleekRank renders the right registry icon via a selector mapping. Buyers checking registration status see the right registry badge immediately on every page without flipping between separate breed association portals at all.

Add training_level and driving_type columns in the export. Use a selector mapping to render training level as a badge and another for driving type, whether single, team, four-up, or six-up hitch. Buyers shopping for a specific hitch role can immediately filter every listing without opening pages one by one to read training notes.

Remove the row from the sheet or mark it sold. On the next cache refresh, the URL returns 404 and drops from the sitemap automatically. If you want a soft sold badge instead, keep the row but set availability to sold; the selector mapping renders the badge and disables the inquiry form so leads do not waste time on placed horses anymore.

Each page is unique by registry number, breed, height, weight, training level, dam, sire, and price. As long as the lead paragraph and structured data differ per row, this is not duplicate content. Breed and training type alone provide meaningful per-page variation across draft horses of similar color and age range across the catalog.

Yes. Add dam_slug, sire_slug, paternal_grandsire_slug, and maternal_grandsire_slug columns in your export. Use selector mappings to render each as a link. Since ancestors are typically also rows in the same sheet, this creates a four-generation pedigree graph that helps serious buyers walk the family without leaving your site once.

Yes. Map breed, height, weight, price, availability, and image to a JSON-LD Product block via a meta mapping. Google indexes live draft horses the same way it indexes any high-value item, and including price and availability unlocks rich result eligibility in shopping. Validate once with the Rich Results Test before publishing the catalog.

Run a second page group at /draft-crosses/{slug}/ filtered to crossbred rows from the same sheet, and keep the main pattern for purebred Belgian, Percheron, Clydesdale, and Shire entries. The data source supports a filter expression so one combined sheet feeds multiple URL patterns without duplicating rows across multiple files.

Yes. The base page holds your inquiry form, which inherits the horse slug as a hidden field via a meta mapping. When a buyer submits from /draft-horse-listings/belgian-gelding-single-driving-16hh/, the email arrives with the registry number and slug attached so you know exactly which horse triggered the message instantly.