Yes. Most show miniature horses are double-registered with both AMHA and AMHR. Add both registration number columns in your sheet and SleekRank renders them as separate badges via two selector mappings. Buyers checking dual-registration status see both numbers immediately on every page without flipping between two different registry portals manually.

Add a column for world_champion_ancestors as a comma-separated list of names. Use a list mapping to fan the names into a labeled pedigree section. For buyers searching for show-quality bloodlines, putting champion ancestors directly in the page body and in the meta description provides per-page variation that lifts long-tail search rankings.

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 buyers do not waste time on placed horses.

Each page is unique by registration number, height, color, dam, sire, and price. As long as the lead paragraph and structured data differ per row, this is not duplicate content. Color genetics and height alone provide meaningful per-page variation across horses of similar age and discipline within the same farm 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 rows in the same sheet, this creates an automatic four-generation pedigree graph that helps buyers walk the family tree without leaving your site at all.

Yes. Map color, height, price, availability, and image to a JSON-LD Product block via a meta mapping. Google indexes live miniature 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 /amha-under-32/{slug}/ filtered to under-32-inch rows from the same sheet, and a third for the 32-to-34 division. The data source supports a filter expression so one combined inventory sheet feeds multiple URL patterns without duplicating rows or maintaining parallel files across multiple data source paths.

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 /miniature-horse-listings/pinto-mare-32in-world-champion-bred/, the email arrives with the AMHA number and slug attached so you know exactly which horse triggered the message immediately.