Yes through your import layer. SleekRank renders from your data source. A cron script that pulls APRs from a yield aggregator 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 pools sheet. The pairs group joins two rows at render time using a slug pair from a pairs sheet. A change to a pool row updates every page that references the pool, including per-pool, 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 asset_pair column. A /yield-farming/usdc/ 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 chain. A /yield-farming/arbitrum/ landing page renders pools on Arbitrum, with the same APR 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-pool 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-pool page during a defined window. If the pool is paused, a template conditional can replace the APR block with a paused notice until the column is cleared.

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

Store base_apr_pct and reward_apr_pct as separate columns, plus a reward_token column. Selector mapping renders the split on every per-pool page so readers see how much of the APR depends on a volatile reward token. A note column can flag historically volatile rewards so the catalog stays honest about composition.