How Do You Check Schema Markup on Every CMS Page at Once?

How do you check schema markup on every CMS page at once?

Crawl the site with a tool that extracts and validates structured data, then read the results by template. A crawler can pull JSON-LD from every CMS item in one pass and flag missing or invalid markup. Search Console helps too, but its reports only show a sample of items, so they cannot prove every page is correct.

Most schema problems on a CMS site are not one-off mistakes. They are template problems that repeat on every item. A blog template that pulls an empty author field. A case study template that outputs a date in the wrong format. A FAQ block that breaks when an item has no questions.

Testing one URL at a time will not find these. You need to see every item built from the same template side by side. That is what a crawl-based audit gives you, and it is one of the first technical checks I run on a large Webflow CMS.

Why is checking one page at a time not enough?

Because CMS schema fails item by item, even when the template looks correct. The markup is built from fields, and fields vary. One item has a missing image, another has a title with an unusual character, a third has an empty date. Testing a single page tells you the template can work, not that every item does.

Google's Rich Results Test and the Schema Markup Validator are excellent tools. I use them constantly while building. But they take one URL at a time. On a CMS with hundreds of items, you would need hundreds of manual tests to be sure, and nobody does that.

I covered the single-URL check in how to test schema markup after a Webflow publish. That habit is right for a change you just made. For an audit of what is already live, you need something that scales.

What does Search Console show, and what does it miss?

Search Console's rich result reports show valid and invalid items Google found, grouped by rich result type. Google's own help page says the reports show a sample of detected items, and the issue table is limited to 1,000 rows. They tell you a problem exists. They do not guarantee they have listed every affected page.

That sampling detail changes how I use these reports. Google's help documentation says an invalid item has at least one critical issue preventing it from appearing as a rich result. Those reports are the right place to spot a pattern. If you need to confirm a specific URL that is not listed, Google points you to the URL Inspection tool.

Search Console also only reports on rich result types it supports. If you add schema types for other reasons, such as clarity for AI systems, you will not see them in these reports at all. My earlier piece on finding schema errors on a Webflow blog with Search Console covers how to read the reports. This article covers what to do when the sample is not enough.

How does a crawl-based schema audit work?

A crawler visits every URL in your site, reads the structured data on each page, and validates it. Screaming Frog's SEO Spider is the tool I reach for. Its documentation says it can extract JSON-LD, Microdata, and RDFa, validate against Schema.org, and check required and recommended properties for Google rich result features.

Two settings matter. Screaming Frog's user guide says that by default it will not extract and report on structured data, so you must enable each format you want under the extraction configuration. Then you turn on the validation options. Its docs say validation issues for required properties are classed as errors and recommended-property issues are classed as warnings.

The guide also mentions a case-sensitive option. Schema.org types and properties are case sensitive, but the guide notes that Google and other search engines validate regardless of case, so it typically recommends leaving that option off. I follow that advice unless I am debugging something specific.

Cost is worth knowing. Screaming Frog's guide states that the free version has a 500 URL crawl limit. For a small Webflow site that may be enough. For a large CMS, you will need a paid license or a different crawler.

How do you set up the crawl for a Webflow CMS?

Start from your sitemap so every published CMS item is included, enable JSON-LD extraction and both validation options, and limit the crawl to your own domain. Then run it and export the structured data results. On most Webflow sites, JSON-LD is the only format you need to enable, since that is how custom schema is usually added.

Using the sitemap as the URL list matters on a CMS. Some items are only reachable through pagination or filters. A crawler following links from the home page can miss them. A sitemap gives you the list of pages you have told search engines about, which is the list you care about.

Before you run the full crawl, test it on a small batch. Ten URLs from each template is plenty. Check that schema is being extracted at all. If the Structured Data tab is empty for pages you know carry JSON-LD, the extraction setting is off or the schema is being injected in a way the crawler is not rendering.

How do you read the results by template?

Group every URL by the CMS template it comes from, then look at error and warning counts per group. If one template shows errors on most items, the template is the problem. If only a handful of items fail, the data in those items is the problem. Fix templates first, then fix individual items.

This grouping is the most useful step in the whole audit. A list of 400 errors looks overwhelming. The same list grouped into "blog template, missing author on 380 items" and "case studies, invalid date on 20 items" is two tasks.

In Webflow, template problems usually trace to a field binding in the custom code embed that builds the JSON-LD. Item problems usually trace to empty or oddly formatted fields. I keep a short note of which CMS field feeds which schema property. It makes this kind of diagnosis much faster.

Which schema errors matter most on a CMS site?

Errors on required properties for rich results you actually want matter most, because they stop those results from appearing. Next come warnings on recommended properties for your most important templates. Last are validation issues on types Google does not use for rich results, which matter mainly for clarity and consistency.

Not every warning needs action. If a recommended property does not apply to your content, leaving it out is fine. Filling it with placeholder text to silence a warning makes your markup less accurate, which is worse than a warning.

Also remember that valid schema does not guarantee a rich result. Google decides whether to show one. I wrote about that gap in why schema can validate and still not show. The audit's job is to make sure your markup is correct and complete. What Google does with it is a separate question.

How often should you run a schema audit?

Run a full crawl after any template change that touches schema, and on a regular schedule for a busy CMS. Quarterly works for most sites. If you publish many items a week, monthly is better. Between full audits, watch the Search Console reports for sudden changes in invalid items.

The trigger that matters most is a template edit. A small change to a Webflow template, such as renaming a field or moving an embed, can silently break schema on every item that uses it. A quick crawl after the change catches that before it shows up as a drop in rich results weeks later.

For high-volume CMS sites, I also like a simple check in the publishing workflow itself. If items are created through an automation, the automation can confirm that the fields schema depends on are filled before the item goes live. Preventing an empty field is easier than finding it in an audit.

What should you do next?

Pull your sitemap, crawl it with JSON-LD extraction and validation turned on, and group the results by template. Fix any template that fails on most of its items, then work through individual items with missing or broken fields. Compare what you find with your Search Console reports, and schedule the next crawl.

A crawl-based audit turns schema from something you hope is right into something you have checked. On a CMS, that is the only way to be confident, because every item is its own page with its own data.

If you want help auditing schema across a large Webflow CMS, or building the checks into your publishing workflow, reach out. As a Certified Webflow Partner, this is work I do often, and I am happy to look at your setup.