No. SleekRank does not generate patterns or instruction 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 sewing instructions live in a linked PDF, your sheet, or a downloadable booklet.

Yes. Add a PDF URL column and map it into a download button or anchor via selector or tag mapping. The button appears on every pattern page once the column is populated. Free patterns can show the link openly; paid patterns can wire the button into your WooCommerce or EDD checkout for that SKU.

Store yardage as a JSON object keyed by size (XS through 3XL, say) per fabric type, and selector-map it into a structured table on the base page. Size range itself lives as its own column. Every pattern then presents the same yardage layout, which is what sewists check before cutting fabric.

Yes. Map a meta og:image column per row, or pair SleekRank with SleekPixel to generate dynamic OG images keyed by pattern slug. SleekPixel can render a card with the pattern name, fabric type, and a finished photo without designing each share preview by hand.

Edit the row in the source sheet, clear the SleekRank cache, and the next request rebuilds that pattern's page from the new data. 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 page.

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

Yes, with a second page group. Build a listing page group keyed on a column like garment_type or difficulty with a filtered URL pattern like /sewing/type/{slug}/. SleekRank itself renders detail pages; faceted indexes live in a separate page group reading from the same source.

Add a version column (1.0, 1.1, 2.0) and surface it on the page via selector mapping. When you ship a revised version, update the row plus a changelog column. The page reflects the new version immediately on cache flush, and existing customers can see exactly what changed since they downloaded.