Yes. Download the registry export as CSV from the AOA member portal, then point SleekRank at the file via a file data source. Configure the column that holds the slug, set a cache duration, and the plugin renders one page per row. Re-upload the CSV when your for-sale list changes, or schedule pulls from a Google Sheet kept in sync with the export.

Add dam_slug and sire_slug columns in the export. Use a selector mapping to render those values as links to the parent animals' own pages. Since the parents are typically also rows in the same sheet, this creates an automatic pedigree graph that helps buyers and search engines walk the family tree without any manual linking.

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 the availability field to sold; the selector mapping renders the badge and disables the inquiry form so leads do not waste time.

Each page is unique by ARI number, color genetics, fiber grade, dam, sire, and price. As long as the lead paragraph and structured data differ per row, this is not duplicate content. Color and micron count alone provide meaningful per-page variation across animals of the same general type, and Google treats this the same as any other catalog.

Yes. Store the AFD, SD, and CV values in three columns and pass them through a list mapping that feeds a small bar chart component on the base page. For sellers who do not have lab fiber data on every animal, leave those columns empty and the template hides the chart automatically via a conditional selector.

Yes. Map color, price, availability, and image to a JSON-LD Product block via a meta mapping. Google indexes live alpacas the same way it indexes any high-value item, and including price and availability in the schema unlocks rich result eligibility. Validate the markup once with the Rich Results Test before publishing.

Run a second page group at /suri-alpacas/{slug}/ filtered to suri rows from the same sheet, and a third for huacaya. The data source supports a filter expression so one combined inventory sheet feeds multiple URL patterns without duplicating any rows or maintaining two parallel catalogs.

Yes. The base page holds your inquiry form, which inherits the animal slug as a hidden field via a meta mapping. When a buyer submits from /alpaca-listings/true-black-huacaya-female-ari-12345/, the email arrives with the ARI number and slug attached so you know exactly which animal triggered the message without any guesswork on your end.