SleekRank renders whatever the data row carries. The sheet holds pre-calculated calories, grams, and percentages. If you want an interactive macro calculator widget on the page, ship a small Alpine component that reads the gram-per-kilogram coefficients as data attributes and updates the displayed splits based on a body-weight slider. SleekRank handles the static SEO surface; the widget handles ad-hoc input.

Either compute one from the other in the sheet using a formula column, or accept the redundancy and add a validation pass before publishing. Most editors prefer the formula approach because it catches manual entry errors before they reach the page, and the column edit propagates everywhere on the next cache flush.

Yes. Define one page group per diet at /macro-calculator/keto/{slug}/, /macro-calculator/paleo/{slug}/, /macro-calculator/carnivore/{slug}/. Each points at its own dataset. The base WordPress page can be shared if the layout is the same, or split per diet for tailored visual treatments. Splitting helps when the food source vocabularies differ enough to warrant separate templates.

Lock the diet vocabulary in the sheet to a canonical set (keto, very-low-carb, low-carb, moderate, high-carb) and document the carb threshold for each. Editors entering 'low-carb' for what should be 'keto' get caught at data-entry time because the column accepts only canonical values. Slugs reflect the canonical labels so URLs stay clean.

Add a protocol column with values like steady, carb-cycle, refeed and either bake the cyclic pattern into the macro arrays (day_1_macros, day_2_macros) or use a separate timeline mapping. For carb-cycling specifically, a day_split list mapping rendering each day's macros works well alongside the average daily totals.

SleekRank caches the source per cacheDuration set in seconds. Edit the sheet, clear the SleekRank cache via WP-CLI or admin, and the next request rebuilds the page with new data. For macro splits (a slow-changing domain) set cacheDuration high so the sheet is not constantly refetched.

Yes. Each generated URL is a real WordPress page included in the sitemap. The base template is excluded automatically so the scaffolding does not compete with real scenario pages. Run a rewrite flush after adding new slugs so the routes resolve immediately on production.

Yes. SleekRank ships with a related entries helper that filters by category and renders up to six related pages with a deterministic shuffle. Group scenarios by diet (all keto variants together) or by goal (all fat-loss variants) and the related cluster forms automatically per page.