Store recipe slugs as an array column on each ingredient row. SleekRank reads that array via a list mapping and renders each slug as a card or link on the rendered hub. The list element on the base page becomes the target; SleekRank fills it with one item per slug. The recipe content itself stays in whatever post type or recipe plugin you already use.

Yes. A zucchini-feta tart slug should sit in both ingredients' arrays. SleekRank does not enforce uniqueness — it just renders whatever slugs you list per row. That makes cross-tagging recipes easy and means a single recipe can drive long-tail traffic from several different ingredient hubs without duplicate content concerns.

Maintain a substitution array per ingredient. Each entry can be a plain string ("swap chickpeas with white beans") or an object with notes. Editorial controls accuracy; SleekRank just renders the array via a list mapping. Keep the substitution data in the sheet next to the ingredient row so editors update both fields at once and the hub stays consistent.

Each generated URL is added to the sitemap automatically. The base template is excluded and noindex'd so the scaffolding never competes with the real hubs. Standard SEO plugins handle canonicalization and per-page meta. Flush rewrites after adding new ingredient slugs so the routes resolve immediately on production.

Yes. Maintain a season field per recipe and either filter the displayed array by current month inside the base template, or order the array in the sheet so summer dishes show first during summer. The list mapping respects array order, so curation stays in the sheet, while richer logic (current-month filtering) belongs in the template layer.

Not for the ingredient hubs themselves. Pair with whatever recipe plugin or post type already powers your individual recipes — WP Recipe Maker, Tasty Recipes, custom CPTs, all fine. SleekRank renders the ingredient-level hub; the linked slugs point to your existing recipe pages, and the user navigates from hub to recipe naturally.

Pick one slug convention (chickpeas, zucchini, sweet-potato) and stick to it across the catalog. SleekRank just renders the slug you give it. If users type singular forms, configure redirects from /recipes/ingredient/chickpea/ to /recipes/ingredient/chickpeas/. WordPress core or a redirect plugin handles that without touching the page group config.

Yes. Add nutrition columns (calories per 100g, fiber, protein) to the ingredient row and map them via tag or selector mappings. Keep claims accurate by sourcing from a single authoritative dataset like USDA. Because every hub reads from the same row, fixing a bad number once fixes it across the entire catalog on the next cache cycle.