Not directly. SleekRank renders from your data source. If your sheet pulls from a vendor docs page or you maintain it editorially, those values flow through on the cache cycle. The import layer lives 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 wallets sheet. The pairs group joins two rows at render time using a slug pair from a pairs sheet. A change to a wallet row updates every page that references the wallet, including per-wallet, 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. A /wallets/solana/ landing page becomes its own SEO target, with intro copy on the base page and the matching subset rendered from the source.

Yes. Add a multi_sig_support flag on each row. A /wallets/multisig/ landing page filters on that column. The template can render Safe, Squads, and similar tools alongside multi-sig variants of mainstream wallets, all from the same source.

Yes. The pairs sheet has its own verdict column. The per-wallet 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 security_incident column with date and severity. Selector mapping can render a banner on the affected per-wallet page during a defined window. If you choose to downrank the wallet on pair and category pages, a template conditional on incident severity handles that without removing the page itself.

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

Store hardware_compatibility as a JSON column with device slugs and connection method (Bluetooth, USB, QR). List mapping renders the compatible device grid per wallet, and a /wallets/ledger/ landing page can filter on rows where Ledger is present in the array, giving you a per-device comparison from the same data.