No. SleekRank does not generate design copy or step text. You provide the data, written by the tech or imported from an existing catalog, and SleekRank renders one indexable WordPress page per row using your base template. The actual step-by-step lives in your sheet or linked PDF.

Yes. Add a video URL column to the sheet and map it into an embed block or anchor element via a selector or tag mapping. The video slot appears on every design page automatically once the column is populated. Designs without a video can hide the slot via a small template conditional.

Add structured columns for base color, accent colors (as an array), and products (as an array). Map base color into a tag, accents and products into list mappings. Every design then presents palette and supplies in the same order, which is what clients and students expect.

Yes. Map a meta og:image column per row using a meta mapping, or pair SleekRank with SleekPixel to generate OG images keyed by design slug. SleekPixel can render a card with the design name, shape, and a swatch row without designing each card by hand.

Edit the row in the source sheet, clear the SleekRank cache, and the next request rebuilds that design page using the new data. The cache duration in the page-group config controls how often the sheet is re-read automatically. For urgent swaps, flush manually from the SleekRank settings.

Yes. Every generated URL is a real WordPress page registered with the sitemap. The base template is automatically noindexed so search engines crawl only the per-design URLs. Internal linking from a /nail-designs/ index page helps each design get discovered during crawl.

Yes, but it is a separate task. Build WordPress listing pages (manually or via another page group keyed by shape) that filter on the column. SleekRank itself renders detail pages, not faceted indexes, so the filtering logic lives in your theme or a small custom listing template.

Add a status column (active, seasonal, retired) and either filter the page group on it or surface the status as a badge in the template. Retired rows return 404 on the next cache refresh; seasonal rows can be served from a separate urlPattern like /seasonal/{slug}/ if you want them outside the main catalog.