No. SleekRank does not produce nail-layout templates or pattern art. You provide the data, which includes a PDF or image URL for the printable template, and SleekRank renders one indexable WordPress page per row. The actual nail-layout file stays in your linked PDF or image.

Yes. Add a PDF URL column to the sheet and map it into a download button via a selector or tag mapping. The button appears on every pattern page once the column is populated. Patterns with no PDF can hide the button via a small template conditional.

Add a threads array per row with brand, color name, and color code per shade. Map the array to a list selector so every pattern renders the thread list in the same order with the same styling. Builders can copy it straight into a shopping list.

Yes. Map a meta og:image column per row using a meta mapping, or pair SleekRank with SleekPixel to generate dynamic OG images keyed by pattern slug. SleekPixel can render a card with the pattern name, nail count, and a finished-photo thumbnail.

Edit the row in the source sheet, clear the SleekRank cache, and the next request rebuilds the affected page using the new data. The cache duration in the page-group config controls how often the sheet is re-read automatically. For urgent fixes, 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-pattern URLs. Internal linking from a /string-art/ index page helps each pattern get discovered during crawl.

Yes, but it's a separate task. Build WordPress listing pages, manually or via another page group keyed by difficulty or size, that filter on the column. SleekRank itself renders detail pages, not faceted indexes, so the filtering lives in your theme.

Store sizes in one canonical unit and convert in the base template via a small helper, or add separate metric and imperial columns and switch via a query parameter. A single canonical column is usually cleaner than maintaining both versions in parallel.