No. Composite scoring lives in your sheet, computed via sheet formulas across the input factor columns. SleekRank renders the composite value exactly as your sheet provides it. The platform's job is to keep methodology, factor breakdown, and rank consistent across every /index/{slug}/ URL, not to perform the math behind the index.

Store the methodology copy in a single cell on a parent record or a dedicated methodology sheet. Selector mapping injects that copy into a methodology block on the base template, so every /index/{slug}/ page renders identical disclosure. Edit one cell to refine the methodology language across the entire catalog at once.

Yes. Each input factor lives in its own column on the matrix sheet. A list mapping over those columns renders a per-factor contribution table on the index page, so readers see which factors drove the composite for that subject. Carry a percentage_contribution column per factor if you want explicit weighting visible per row.

Carry a year column on each row. For sites that overwrite each year, update the factor columns and recompute composites; for sites that preserve history, append rows with year-suffixed slugs like vienna-livability-2025 and vienna-livability-2026. Both patterns work; the suffix approach keeps prior URLs resolving permanently.

Yes. SleekRank exposes every generated URL through its sitemap and noindexes the base template page automatically. Submit the sitemap in Search Console once; new index slugs added to the matrix start getting crawled after the next rewrite flush. Old slugs you delete stop resolving and drop from the sitemap on regeneration.

Yes. Build a separate page group at /index/all/ or use the base template as a directory page that lists every subject sorted by rank via list mapping over the full matrix. Internal links to /index/{slug}/ pages render as anchors from the rank column, keeping the index hub aligned with the canonical ordering.

Yes. Carry a prior_composite column with last edition's composite value and a delta column with the difference. Tag mapping renders the delta as a stamp on each index page. Readers see whether the subject improved or regressed across editions without referencing an archived URL.

Yes. Use meta mapping at og:image pointing to a per-row image URL column, or pair with SleekPixel and a templated suffix so /index/vienna-livability/ renders a preview showing subject, composite, and rank without manual asset work for every page.