Not directly. SleekRank renders from your data source. If your sheet pulls from a vendor release feed or you maintain it editorially, those values flow through on the cache cycle. The import layer is upstream of SleekRank, which is responsible for rendering whatever is current in the source consistently across solo and pair pages.

Both page groups read from the same devices sheet. The pairs group joins two rows at render time using a slug pair from a pairs sheet. A change to a device row updates every page that references the device, including per-device, pair, and any category roll-ups, after the cache window expires.

Define another page group with a different URL pattern, source from the same sheet, and filter on the supported_chains array or a bitcoin_only flag. A /hardware-wallets/bitcoin-only/ landing page becomes its own SEO target, with intro copy on the base page and the matching subset rendered from the source.

Yes. Connection_method is a column. A /hardware-wallets/air-gapped/ landing page filters on rows where the connection includes QR or microSD. List mapping renders the matching devices, and the same secure element and chain columns flow through to each category page.

Yes. The pairs sheet has its own verdict column. The per-device verdicts handle solo pages, and the pair verdict drives matchup-specific recommendations. If a pair row's verdict is empty, the template can fall back to a templated summary built from the two solo verdicts. You control the wording per matchup when nuance is needed.

Add a discontinued_date column. Selector mapping renders a discontinuation note on the affected per-device page, and pair pages can either keep the comparison for historical traffic or fall back to a successor device chosen from a successor_slug column.

Yes. Map an image URL column to og:image with the meta type, so each per-device page renders its own social card. Pairing with SleekPixel lets the OG image render on the fly from the row data, overlaying device name, secure element, and price on a styled background.

Add companion_apps as a JSON column with software wallet slugs. List mapping renders the compatible software grid per device, and a /hardware-wallets/metamask-compatible/ landing page filters on rows where MetaMask is present in the array, giving you a per-software comparison from the same data.