Yes, indirectly. Keep free_tier_rps and paid_tier_pricing columns in the sheet, and let your editorial team update them as the explorer's published pricing changes. SleekRank reads whatever is in the source on the cache cycle, so the propagation is automatic once the row is updated. The detection itself is upstream of SleekRank, which handles the render layer.

Both page groups read from the same explorers sheet. The chain group joins every explorer supporting a given chain at render time using a chains sheet. A change to an explorer row updates every page that references it, including per-explorer, per-chain, 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 contract_verification or a feature_score column. A /explorer/contract-verification/ landing page becomes its own SEO target, with intro copy on the base page and the matching subset rendered from the source.

Yes. Add columns for self_hostable, hosted_instance_url, and any deployment quirks. The template renders a self-host block via selector mapping when relevant, and a /explorer/self-hosted/ landing page can list the relevant explorers as a separate page group filtered on the flag.

Yes. The chains sheet has its own verdict column. The per-explorer verdicts handle solo pages, and the chain verdict drives chain-specific recommendations. If a chain row's verdict is empty, the template can fall back to a templated summary built from the top three explorers' verdicts.

Update a discontinued flag and a successor_slug column. The template renders a deprecation banner via selector mapping when the flag is set, and the successor field can link to the recommended replacement. Add a 301 redirect to preserve link equity for any backlinks the deprecated explorer earned.

Yes. Map an image URL column to og:image with the meta type, so each per-explorer page renders its own social card. For per-chain pages, you can render the chain logo or a coverage visualization. Pairing with SleekPixel lets the OG image render on the fly from the row data, overlaying explorer name, chains supported, and free tier on a styled background.

Add an api_methods_supported column listing the methods exposed (eth_call, eth_getLogs, debug_traceTransaction). The template renders a method matrix via list mapping, and per-method pages can be a separate page group filtered on the array, so developers searching for a specific RPC method land on the right explorer.