No. SleekRank does not generate sketches or any visual design. You provide the data, written and sketched by the designer or imported from an existing catalog, and SleekRank renders one indexable WordPress page per row using your base template. The actual sketch lives as an image URL in your sheet.

Yes. Add separate sketch_url and example_url columns and map each into an image element via selector mapping. Both images appear on every layout page once the columns are populated. Layouts with only a sketch (no example yet) can hide the example slot via a small template conditional.

Add structured columns for page_size (e.g. '12x12') and photos (integer as string) and tag-map each into a hero stat element on the base page. Every layout then presents page size and photo count in the same place, which is what scrapbookers check first when planning a session.

Yes. Map a meta og:image column per row, or pair SleekRank with SleekPixel to generate dynamic OG images keyed by layout slug. SleekPixel can render a card with the layout name, page size, and a sketch thumbnail without designing each share preview by hand.

Edit the row in the source sheet, clear the SleekRank cache, and the next request rebuilds that layout's page from 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 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-layout URLs. Internal linking from a /scrapbook/ index page helps each sketch get discovered during the next crawl.

Yes, with a second page group keyed on the column. A filtered URL pattern like /scrapbook/theme/{slug}/ generates index pages per theme (vacation, holiday, baby, birthday) automatically from the same source. SleekRank itself renders detail pages; faceted indexes live in their own page group.

Add a sizes array column listing all supported sizes, and either render the array as a list on the page or create separate rows per size variant if each combo deserves its own URL. The choice depends on whether size-specific search intent is strong enough to justify dedicated pages.