Set urlPattern to /shows/{show}/{slug}/ and include both show and slug columns in the sheet. The {show} segment usually points to a parent show page (run as another page group), so the URL hierarchy reads naturally. SleekRank assembles the path per row, and the sitemap includes every combination.

Yes. Use a show column on every row and let the urlPattern handle namespacing. For very large catalogs, split into separate page groups per show family (drama, comedy, animated) so cache and source management stays clean. Splitting by page group is also useful when different shows need different template variations.

No. SleekRank does not write any episode content. Provide the synopsis, recap, and guest cast in the sheet, and SleekRank renders one page per episode. Editorial accuracy is the editor's responsibility, ideally informed by official press materials or first-watch reviews. SleekRank's role is the rendering and routing layer.

Yes. Each generated URL is added to the SleekRank sitemap. The base template is excluded and noindexed. Episode queries are evergreen, especially for prestige shows people rewatch every few years. Submit the sitemap in Search Console and new episode pages get crawled within hours of cache flush.

Yes. A meta mapping pointing at a JSON-LD script tag produces full TVEpisode schema per page, with episodeNumber, seasonNumber, datePublished, partOfSeries, and director fields drawn from the row. Google's knowledge panels read this as a structured signal for episode-level rich results.

Add new episode rows to the sheet on release day; cache refresh propagates them to the live site. For very fresh content, set cacheDuration to under an hour during release windows and dial it back once the season finishes. Spoiler-tagging upcoming episodes is handled with a status column that the template reads.

Yes. Render previous and next episode links via selector mapping that pulls slugs from adjacent rows ordered by season and episode number. Episode hubs benefit from binge-friendly navigation. SleekRank's source order isn't sorted automatically; precompute the navigation slugs in a script that pushes to the sheet, or order rows per source on read.

Add separate columns for production_order and air_order. The default URL uses one (typically air order); a secondary page group can render the alternative ordering at /shows/{show}/production-order/. For shows with skipped numbering or webisodes between seasons, handle each as its own row with a clear ordering field.