No. SleekRank does not generate any build content. The instructions, parts lists, and photography come from the creator. SleekRank renders one indexable WordPress page per row from the source data using a base template. The actual step-by-step PDF or video lives in your sheet column or linked storage.

Add a PDF URL column and map it into a download button via selector or tag mapping. The button appears on every build page once the column is populated. Builds without a PDF can hide the button through a small template conditional, or the row can list an external instructions link instead.

Add structured columns for pieces (integer as string) and age_range (e.g. '8+', '12+'). Tag-map each into a hero stat element. Every build then presents the same format in the same place, which is what builders expect when scanning a catalog or comparing two builds across browser tabs.

Yes. Map a meta og:image column per row using a meta mapping, or pair SleekRank with SleekPixel to generate dynamic OG cards keyed by build slug. SleekPixel can render a card with the build name, piece count, and a sample 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 build'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 a manual flush from the SleekRank settings makes the change live immediately.

Yes. Every generated URL is a real WordPress page included in the SleekRank sitemap. The base template is automatically noindexed so search engines crawl only the per-build URLs. Internal linking from a /builds/ index page helps each build get discovered during crawl.

Yes, with a second page group. Build a listing page keyed on a column like theme or difficulty, point it at the same source, and a filtered URL pattern like /builds/theme/{slug}/ generates the index pages automatically. SleekRank itself renders detail pages, faceted indexes are a separate page group.

Add a type column (official, moc, retired) and either filter the page group on it or surface the type as a badge in the template via selector mapping. Retired sets can also be served from the same sheet with a different urlPattern like /retired/{slug}/ if you want them grouped separately from active builds.