There is no fixed cap. The page count is whatever your data source contains. Ten rows yields ten per-database pages plus up to forty-five pair combinations if you wire a pairs sheet. Each page is rendered on demand using your WordPress template, so the practical limit is hosting capacity rather than SleekRank itself.

It refreshes on the cache duration you set per page group. Default is 24 hours. For categories that move daily, set a shorter window. After a major launch, run a manual cache flush with wp db query "DELETE FROM wp_sleek_rank_items" and pages rebuild on the next request from the latest source rows.

Yes. The base page is a regular WordPress page, so Bricks, Elementor, Gutenberg, GenerateBlocks, Breakdance, and other builders render normally. SleekRank only injects row data into the template through tag, selector, list, and meta mappings. It does not replace your layout or interfere with builder functionality.

The base page is auto-excluded and noindexed. Generated pages are indexable by default. To noindex a specific row, drop it 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 entirely; the noindex column keeps the URL but signals search engines to skip it.

Yes, through conditional rendering on column values. Add a tier_type or has_serverless column and use it to show or hide template sections. A database without a free tier can hide the free-tier block automatically; a database with a regional edition can render an extra map block, all driven by row values rather than per-page editing.

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

Make sure each row has a unique verdict, hero subheadline, and use-case framing column. Mappings should pull from per-row text, not template defaults. Pair pages render side by side rather than duplicating per-database content, and the urlPatternSample plus row uniqueness keeps the corpus at a one-page-per-database ratio.

Yes. Define another page group with use case as the slug. /databases/for-serverless/, /databases/for-edge/, /databases/for-analytics/ join the relevant rows through a separate sheet. The provider matrix is shared, the use-case sheet decides which databases appear on which page, all from the same source data.