No. SleekRank does not generate patterns 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 stitch-by-stitch 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 or anchor element via a selector or tag mapping. The button appears on every pattern page automatically once the column is populated. Pattern pages with no PDF can hide the button via a small template conditional.

Add structured columns for gauge (stitches and rows over four inches) and finished measurements (chest, length, sleeve). Map each into a fixed slot on the base page using tag or selector mappings. Every pattern then presents gauge and sizing in the same order, which is what knitters expect when comparing patterns.

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, yarn 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 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 /patterns/ 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 yarn weight — 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 (test-knit, published, retired) and either filter the page group on it or surface the status as a badge in the template. Test-knit patterns can be served from the same sheet with a different urlPattern like /test-knit/{slug}/ if you want them excluded from the public catalog.