No. Scoring is your editorial judgment captured in the sheet. SleekRank renders the per-criterion values, weighted totals, and reviewer notes exactly as you enter them. The platform's role is to keep the framework consistent and the rendering identical across every /scorecards/{slug}/ URL, not to influence what each cell should contain.

Add the column to the matrix sheet, score it for every existing subject, update the parent record with the criterion definition and weight, then clear the items cache. Every scorecard page rerenders with the new criterion in its table, the new definition in the framework block, and the new contribution to the weighted total.

Yes, though it weakens cross-scorecard comparability. Carry a per-subject weights JSON or per-criterion weight column on the matrix row, recompute totals against those weights in the sheet, and render the resulting total via tag mapping. Add a disclosure on pages with non-default weighting so readers know the framework varied.

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

Yes. Either keep prior years as separate slugs like acme-crm-2025 with frozen data, or maintain a history sheet keyed by subject_slug and year, mapped into a per-page changelog block via list mapping. Readers see how the score moved across cycles without breaking the canonical /scorecards/{slug}/ URL.

Carry a usability_note, performance_note, and so on for each criterion as their own columns. The base scorecard template includes note slots tied to selector IDs like #note-usability and #note-performance. Selector mapping fills each slot with the per-row note, so every cell explanation is auditable on the same row as the score itself.

Yes. Run a separate SleekRank page group at /scorecards/category/{category}/ that filters the same matrix by category column and renders a directory of scorecards in that group. Or expose a static category index via the base page that lists all scorecards using a list mapping over the unfiltered matrix.

Yes. Use meta mapping at og:image pointing to a per-row image URL column, or pair with SleekPixel and a templated suffix so /scorecards/acme-crm/ renders a preview showing the subject name and total score without manual asset work for every scorecard.