# CMS Check Verify that a Framer CMS collection, its content, and the pages that display it are structured and connected correctly. ## Instructions ### Before checking - Inspect the collections, fields, items, CMS detail pages, and collection lists without editing content. - Read the Settings block first and use it as the source of truth. - Distinguish published items from drafts throughout the check. ### Collection structure - Check that every required field exists in each collection. - Check that field types fit their content: Option for fixed choices, Reference or Multi-reference for related items, Date for dates, Number for numbers, Link for URLs, Image for images, Formatted text only where rich formatting is needed. - Flag text fields that duplicate data another collection already holds and should be a reference. - Flag unused fields that no page or list reads. - Check that field names are clear and consistent across collections (e.g. Cover image in one, Thumbnail in another for the same role). - Check that fields needed for sorting and filtering (date, category, featured toggle) exist. ### Content quality - Check every item for empty required fields. - Check for placeholder content using the placeholder markers. - Check for duplicate titles, duplicate slugs, and near-duplicate items. - Check slugs against the slug rules, and flag slugs that changed after publishing when that can be detected, since old URLs may break. - Check titles and summaries against the length settings. - Check dates for the correct format, future dates, and missing dates. - Check images against the image rules: size, ratio, format, and file size. - Check that content images have alt text. Flag alt text that repeats the title or file name. - Check formatted text for heading levels: the body should not contain an H1 when the page template already has one. - Check formatted text for broken links, empty links, pasted styling, and empty paragraphs. - Flag items older than the stale content threshold for manual review. ### CMS detail pages - Check that the detail page template binds every field it should display. - Check that SEO title, description, and social image are mapped to CMS fields, with sensible fallbacks. Detailed metadata checks belong to the SEO check. - Check empty-state handling: layers bound to optional fields should hide when the field is empty instead of showing a gap or broken image. - Stress-test the template with the longest title, the shortest body, an item without an image, and an item with the maximum number of references. - Check that reference and multi-reference fields render and link to the correct detail pages. - Check that previous/next or related-item lists exclude the current item. ### Collection lists - Check each collection list's filter, sort order, and item limit against the settings. - Check that drafts do not appear in lists. - Check that pagination matches the pagination setting and works at the end of the list. - Check that each list has an empty state when filters can return no items. - Check that list items link to the correct detail pages. - Check that the number of items rendered on a single page is reasonable for load time. ### Scope limits - Do not rewrite content, rename fields, or restructure collections unless explicitly requested. - Do not audit layout, typography, or full on-page SEO beyond the mapping checks above. - Do not apply fixes unless explicitly requested. When fixing, never delete items or fields without confirmation, since CMS deletions can break live pages and URLs. ## Report to the User Mark each item as passed, issue found, needs manual review, or not applicable. Group results by collection, then by structure, content, detail page, and lists. For content issues, list the affected items by title and slug. For each issue, explain the impact and the recommended next step. End with: - Counts: items checked, items with issues, drafts, placeholder items. - Any settings that were inferred rather than provided. - The top three fixes by impact.