A Webflow CMS collection with unclear or unforgiving fields causes editor mistakes: required fields with no help text, reference fields that break when items are removed, and required images that block imports. Nobody reviews the schema until content goes wrong.

Name the collection, and it finds it in Webflow, listing matches if the name is ambiguous, and reads every field definition. It flags required fields without help text, uneditable fields, reference and multi-reference fields, required image, file and rich text fields, and unclear or duplicated names. You get the collection's field count, a table of only the fields with issues, most serious first, and recommended changes. It is read-only and marks a field as unclear rather than guessing its purpose.

Your CMS schema becomes easier for editors to fill correctly, with fewer broken links and failed imports.

SEO titles and descriptions in Webflow are set page by page, so missing values, duplicates and lengths that search engines cut off build up unnoticed. Checking every page in the Designer is slow, and template pages for collections hide their own problems.

Optionally give a title filter and choose whether to include drafts, and it reads the pages on your Webflow site, ignoring archived ones. It flags empty SEO titles and descriptions, titles over 60 characters, descriptions under 70 or over 160, and values repeated across pages, and lists collection template pages separately because their SEO usually comes from item fields. The table shows missing values first, then duplicates, then length problems. It is read-only and reports problems without writing replacement copy unless you ask.

You fix the SEO gaps that hurt search visibility, starting with missing values, without checking each page by hand.

Webflow CMS items get published with required fields still empty, an image missing or a summary left blank, and they only show up as broken pages. Checking every item against the collection's required fields by hand is tedious.

Name the collection and how many items to examine, and it finds the collection's required fields in Webflow, always counting name and slug, then reads its items that are not archived. Each item is checked for missing keys, empty values, empty lists and images or files with no URL. You get counts of complete and incomplete items, a table of what each incomplete item is missing, and a per-field count showing the worst field. It is read-only and says when the item limit means the result is a sample.

Incomplete CMS items are found and fixed before visitors land on half-finished pages of your site.

Old Webflow CMS items stay live long after they stop being true, with past events, expired offers and last year's dates. Finding them means sorting every collection by update date and reading each item to judge it.

Name the collection and a staleness threshold, and it reads the live, published items in Webflow not updated since the cutoff. For each it notes the age and looks for content that dates it, such as a past date field, a year in the name or an expired offer, recommending archive when it finds evidence and review otherwise. It is read-only, leaves archiving to you, and treats evergreen content like team or product pages as review, because age alone is not a reason to archive.

Outdated content comes off your site in a reasoned way, without archiving pages that are old but still right.

On a large Webflow site, nobody quite knows how many CMS collections exist, how many items each holds, or which ones have a template page to show them. Answering that means opening every collection and page.

Optionally give a name filter, and it lists the CMS collections on your Webflow site and, for each, counts the fields and reference fields, the items and drafts, and finds the template page that renders it. You get one table, plus flags for collections with no template page, collections with no items and collections that are mostly drafts. It is read-only, shows counts at the record limit as a minimum, and marks a failed read as unknown while carrying on with the rest.

You get a clear map of the site's CMS, with orphaned and empty collections ready to tidy up.

Edits in the Webflow CMS can sit unpublished for weeks, and items created as drafts are sometimes forgotten altogether. Finding what is waiting means comparing last updated and last published dates item by item.

Name a lookback period, and optionally a collection, and it reads recently updated items in Webflow and sorts each into never published or changed since publishing, leaving out items that are already live. Results are grouped by collection with the longest-waiting work at the top and totals per status. Item names come from the name field, or the slug when that is missing, and collections with nothing waiting are left out. It is read-only and never claims to have published anything.

Finished work stops sitting in draft, because you can see exactly what is waiting to go live.

Knowing what changed on a Webflow site last week means checking collections, CMS items and pages separately, and working out which edits are still unpublished. That is hard to answer quickly when someone asks what went out.

Give a date range, and it reads the Webflow collections, CMS items and pages that changed in it. Items are classed as new, edited or archived, with whether each has been published since its last update. You get headline counts, tables by collection and for pages, and a closing list of edits not yet published. It is read-only and does not invent who made a change or what the old value was, because Webflow records only when something changed.

You can answer what changed on the site, and what is still unpublished, for any period in one report.