Yes, two clean approaches work. Treat each finish as its own SKU row with a unique slug like north-star-fridge-french-door-stainless and -black-stainless, which gives each finish its own indexable URL — useful if shoppers search by finish. Or store finishes as an array on a single row and render them through the list mapping inside one model page. Brands typically pick the first approach for SEO; retailers often pick the second for inventory simplicity.

Store dimensions however the catalog stores them — inches, centimeters, height-only, or full HxWxD. SleekRank inserts the column value into the template via a tag or selector mapping without imposing a format. If you need consistent rendering across mixed catalogs, normalize dimensions in your data pipeline before SleekRank reads the row, or use a list mapping to render a dimensions table with separate rows for height, width, and depth.

Yes. The rest_api source handles authenticated JSON endpoints, so a PIM or product master feed from Akeneo, inRiver, Salsify, or a custom system drives the pages directly. Auth headers go in the page-group config, and cacheDuration controls refetch cadence. Many brands trigger a manual flush after the nightly PIM run, so the public catalog aligns with merchandising decisions on the same day they're made internally.

No. SleekRank renders existing data into the template. Long-form copy still lives in the base page or in a column you author. Many appliance brands pair SleekRank with a separate description column written by merchandising or an AI-assisted draft reviewed by an editor. SleekAI's chat or chatbot features can support that workflow on the editorial side, but the SleekRank render itself is structured data only.

Two clean approaches. Remove the row entirely and the page falls out of the sitemap on next regeneration, returning 404 for the URL. Or keep the row, set a 'discontinued' status flag, and adjust the template to render a wind-down state with links to similar current models — preserving the URL's backlinks and historical SEO equity. Most retailers pick the second approach for high-traffic models that still drive search.

Each model URL is a real WordPress page added to the sitemap. The base template stays noindex'd so only model pages compete in search. This means north-star-fridge-french-door and atlas-front-load-washer each get their own indexable URL targeting the branded model query, which is where appliance-shopping search traffic concentrates.

Energy Star, CEE Tier, and DOE rating fields live as columns in the catalog. When recertifications happen — typically annually or after a model refresh — the column updates and every affected page reflects the new rating on cache flush. The same pattern handles regional rating systems like EU energy labels, with separate columns per region driving conditional rendering in the template.

Yes. Add columns for installation type, electrical requirements, water-line specs, and accessory SKUs. Render them through tag mappings in a 'before you buy' block, or through a list mapping if accessories live as an array. Linking accessories back to their own SleekRank-generated pages — vent kits, water filters, installation parts — gives the catalog cross-linking without a separate content workflow.