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

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 automatically once the column is populated. Patterns without a PDF can hide the button via a small template conditional.

Add structured columns for leather weight, stitching style, and finished size, plus a JSON array for tools. Map the array into a list selector and the scalar fields into tag mappings. Every pattern then presents these specs in the same order, which is what makers expect when sourcing supplies.

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, leather weight, and a sample photo without designing each card by hand.

Edit the row in the source sheet, clear the SleekRank cache, and the next request rebuilds that pattern's page using the new data. The cache duration in the page-group config controls how often the sheet is re-read. 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. An internal /leathercraft/ index page helps each pattern get discovered during crawl.

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

Add a status column (test, published, retired) and either filter the page group on it or surface the status as a badge in the template. Test patterns can be served from the same sheet under a different urlPattern like /test-patterns/{slug}/ if you want them excluded from the public catalog.