Yes. Place a Book JSON-LD template on the base page with placeholders for name, author, isbn, datePublished, genre, and image, and use selector mappings to inject per-row values. SleekRank handles the data swap; the schema markup itself lives on your page. Every generated URL emits identical schema quality without per-page authoring, which Google's Rich Results Test will validate.

Add series and series_order columns to the source. The page-group config can sort by those fields when rendering the author page, so a four-book series shows up in order even if you added the third book first. New titles slot into the right position automatically when you fill in their series_order, without renumbering existing posts as you would with manual WordPress pages.

Map a cover URL column into an img tag via selector mapping. SleekRank does not host or generate images, but it injects the right URL per book. Keep covers on a CDN or your media library, since renaming the host of those URLs would invalidate every page at once. For dynamic OG covers with title overlay, pair with SleekPixel.

Yes. Filter the sheet on a category column into separate page groups, each with their own URL pattern and metadata. /books/fiction/{slug}/ and /books/non-fiction/{slug}/ can run from the same source filtered to those rows. The author and genre roll-ups can stay shared or split per category, depending on how you want the site map to look.

Add an availability column and filter the page group on it. Out-of-print rows stop rendering after the next cache refresh and drop from the sitemap. If the page had backlinks, set a 301 redirect to the author page or the next-in-series title to preserve that link equity rather than serving a 404 to crawlers and readers.

Yes. Map the cover URL column into the og:image meta mapping, or pair with SleekPixel for dynamic per-book OG images that overlay the title and author over a styled background. Per-book OG images materially improve click-through from social shares and Slack previews compared to a single site-wide default image.

Store authors as a JSON array on the row instead of a single string. The list mapping renders each author into a list item or comma-separated string on the page. For the author roll-up groups, you can either generate a page per primary author or split each multi-author book into multiple author entries via a normalized side table.

Yes. Add columns for amazon_url, bookshop_url, and any other retailer affiliate links you carry. Selector mapping injects each URL into the corresponding button on the base template. Editing one row updates buy buttons everywhere that book appears, which beats hand-editing dozens of WordPress posts when an affiliate program changes its link format.