Yes through your import layer. SleekRank renders from your data source. A cron script that pulls TVL from DefiLlama or a similar API and writes back to your sheet feeds new numbers in on the cache cycle. The import 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 protocols sheet. The pairs group joins two rows at render time using a slug pair from a pairs sheet. A change to a protocol row updates every page that references the protocol, including per-protocol, 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 category. A /defi/dexes/ landing page becomes its own SEO target, with intro copy on the base page and the matching subset rendered from the source.

Yes. Filter on the deployed_chains array. A /defi/arbitrum/ landing page renders the protocols deployed on Arbitrum, with the same TVL and audit columns flowing through. Each chain becomes its own SEO surface from the same source.

Yes. The pairs sheet has its own verdict column. The per-protocol 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 an incident column with date, type, and severity. Selector mapping can render an exploit banner on the affected per-protocol page during a defined window. If you choose to downrank the protocol 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-protocol page renders its own social card. Pairing with SleekPixel lets the OG image render on the fly from the row data, overlaying protocol name, TVL, and chain count on a styled background.

Add a last_governance_change column with date and parameter summary. Selector mapping renders a small note on the affected per-protocol page so readers see when the fee or risk parameter last moved. The fee_model and risk columns themselves update in the same edit so the displayed numbers stay aligned with the note.