There is no hard plugin limit. Page groups with several hundred rows are common across the SleekRank install base. Performance is driven by cacheDuration and source response time, not row count. Most recipe catalogs sit comfortably in the 50-500 row range and rebuild in seconds on cache flush.

Add a JSON-LD script block to the base page and use a meta mapping that fills its content from the row's columns. SleekRank substitutes name, prepTime, recipeIngredient (from the ingredients array), recipeInstructions (from the steps array), and image at render time. The result validates in Google's Rich Results test.

Yes. SleekRank uses a normal WordPress page as the template, so any theme or builder works. The mappings target elements you place on that base page, whether they were rendered by Bricks, Elementor, Gutenberg, or a classic theme. Style the base page once and every Tunisian dish inherits the look.

Yes. Every generated URL is added to the SleekRank sitemap, gets a 200 response, and carries the page's own meta. The base template page is excluded from the sitemap and noindexed so it never competes with the real dish pages in search results.

Yes. Use conditional mappings keyed on a layout column (e.g. stew, pastry, dessert) so each dish renders the right sub-template. Pastries can show malsouka technique notes, stews can show pot recommendations, all from the same base page with conditional blocks.

The corresponding URL returns a 404 on the next request after cache flush, and the sitemap entry is removed. Google drops it from the index over the following crawl cycle. Set up a redirect mapping if the recipe was renamed rather than retired so the old URL points at the new slug.

Make each row genuinely different in ingredient amounts, method, or regional notes. Tunisian variants on shared base techniques (couscous, ojja, shakshuka) each carry their own region, spice mix, and prep notes. Add a few unique sentences per row in a description column so the body copy varies meaningfully across pages.

Yes. SleekRank supports multiple data source types per page group: Google Sheets, CSV, JSON URL, JSON file, Notion, REST API, and CSV URL. Run primary recipes from the editorial sheet and overlay translation arrays from a separate JSON. Mappings reference either source by column name.