No. The anagrams sheet is precomputed against your chosen dictionary in a separate pipeline (a Python script, a one-off SQL job, whatever fits your stack). SleekRank renders pages from the precomputed sheet. Recomputing on the fly per request would be slow; precomputing makes the page render fast and cacheable.

Carry a dictionary column on each anagram row with the source name. The template either renders separate buckets per dictionary or exposes a filter UI that hides results outside the player's preferred list. The same anagram row can carry multiple dictionary tags if a word appears in more than one corpus.

Yes. The anagrams sheet can include rows for shorter words made from a subset of the input letters, carrying a length column smaller than the input letter count. List mapping groups results by length so full-length anagrams appear first, then five-letter sub-words, then four-letter sub-words, and so on.

Append a row to the inputs sheet with slug, letters, sorted_letters, and letter_count. Run your anagram-generation pipeline to populate the anagrams sheet for the new input. After cacheDuration elapses or you clear the items table, /anagram-of/{slug}/ resolves and lands in the sitemap on the next rewrite flush.

Yes. SleekRank exposes every generated URL through its sitemap and noindexes the base template page automatically. Submit the sitemap in Search Console once; new input rows start getting crawled after the next rewrite flush.

Yes. Use meta mapping at og:image pointing to a per-input image URL column, or pair with SleekPixel and a templated suffix so /anagram-of/listen/ and /anagram-of/trace/ each render their own preview with input letters and anagram count without manual asset work.

Canonicalize on sorted_letters. "Listen" and "silent" share the same sorted-letter signature, so decide editorially whether one canonical slug serves both queries or whether each gets its own URL with cross-links. The sorted_letters column makes the equivalence visible during audit.

Edit or remove rows in the anagrams sheet, or flag them inactive with a status column the list mapping respects. Flush the cache and the corrected anagram set propagates to every relevant page. Keep a dictionary_version column to track which corpus run produced each row.