Yes. Use one page group for per-host pages reading the hosts sheet, and a second page group with a pairs sheet for the head-to-heads. The pairs sheet only needs the slug pair and any pair-specific verdict; the join against the hosts table at render time pulls in both hosts' details. This keeps the data normalized: one host edit propagates to per-host and pair pages alike.

Not directly. It reads from your data source on the cache cycle. If you wire a sheet that pulls live prices via a Google Sheets formula or a connected script, those flow through. SleekRank itself does not scrape host websites or call hosting APIs. The right pattern is to run a separate scraping job on a schedule that updates the sheet, then let SleekRank read the updated values on the next cache cycle.

Add an affiliate_url column to the hosts sheet and map it via selector or tag mapping into the buy button or call-to-action in your template. Every page that references the host renders the correct affiliate URL automatically. When a hosting affiliate program migrates URL formats, edit one cell and the change propagates to the per-host page and every pair page on the next cache flush.

The base page is auto-excluded and noindexed. Generated pages are indexable by default. To noindex a specific host, drop the row from the source or add a noindex column and map it into a meta robots tag via meta mapping. Removing the row stops the URL from generating entirely; the noindex column keeps the URL but signals search engines to skip it.

Remove the row. After the cache window, the URL stops being generated and falls out of the sitemap. The pair pages that referenced that host also stop generating because the join fails on a missing host row. If the per-host page had backlinks, set up a 301 redirect to a similar host page to preserve link equity rather than serving 404s to existing readers.

Yes. The base page is a regular WordPress page, so anything you would put on a normal review page works inside the template. Comparison table plugins, pricing widgets, and CTA blocks render normally. SleekRank only injects data into the template through mappings; it does not interfere with other plugins on the page or replace any of their functionality.

Add a promo_price column alongside the regular starting_price column, and a promo_expires date column. Map both into the template with conditional rendering — selector mapping can hide the promo block when the expiry passes. A weekly script can clear stale promos automatically, keeping pages from showing expired deals to readers who would lose trust on the click-through.

Yes. Add columns for benchmark scores, uptime percentage, and TTFB results, then map them via tag mapping into stat blocks on the base template. For pair pages, the side-by-side render lets readers compare benchmark numbers directly. Refresh the benchmark columns quarterly when you re-test, and every page reflects the current numbers without per-page editing.