Schema Markup for Webflow Sites (Free JSON-LD Method)

Webflow doesn't generate schema markup automatically — you have to add it yourself. The good news: Webflow makes it easy. Page settings have a "Inside head tag" custom code field that accepts any JSON-LD you paste. Five minutes and your Webflow page has valid schema. Our free generator builds the code; this guide walks through adding it.

Why Webflow Doesn't Add Schema for You

Unlike Shopify (which adds basic Product schema) and WordPress with Yoast (which adds Article schema), Webflow doesn't include any schema markup by default. Every Webflow page ships with zero structured data unless you add it.

This isn't a Webflow flaw — it's a design choice. Webflow gives you full control over the page head, which means you can add exactly the schema you need without fighting auto-generated patterns. The trade-off is that you have to do it yourself.

For most Webflow sites, this is actually better. Auto-generated schema often misses the fields that matter most for your specific content. Hand-built schema (using a generator) gives you cleaner, more complete markup.

Adding Schema to a Single Webflow Page

The fastest method, for any single page:

1. In the Webflow designer, open the page you want to add schema to
2. Click the gear icon (page settings) in the left sidebar
3. Scroll down to the "Custom Code" section
4. Find the "Inside head tag" field
5. Use our free schema markup generator to build your JSON-LD
6. Copy the entire script tag (including the opening and closing tags)
7. Paste into the "Inside head tag" field
8. Click Save, then publish your site

The schema is now in your page head on every visit to that page. View source on the live URL to confirm.

Adding Schema That Should Be on Every Page

For schema that should appear on every page (typically Organization schema for your brand), add it to the site-wide head instead of per-page.

1. From the Webflow designer, click Project Settings (the gear icon at the top)
2. Go to the Custom Code tab
3. In the "Head Code" field, paste your schema script
4. Save and publish

Now the schema appears on every page of the site. Use this for Organization, but NOT for Article, Product, or page-specific schema — those should be per-page so each page has its own unique schema.

Sell Custom Apparel — We Handle Printing & Free Shipping

Schema for CMS Collection Pages (Blog Posts, Products)

For CMS collection pages — like blog posts or product collections where each item has its own page from a template — you want the schema to populate dynamically with each item's data. Webflow supports this through the CMS field referencing system.

Open the collection page template (e.g., your blog post template). Go to page settings → custom code → "Inside head tag." Paste your schema, then use the + Add Field button to insert CMS field references where dynamic values should go:

• Replace static title with the title field reference
• Replace static description with the post summary field
• Replace static date with the published date field
• Replace static image URL with the featured image URL field
• Replace static author with the author name field

Save and publish. Now every blog post or product page has its own unique schema with that item's actual data — no manual work per post.

Common Webflow Schema Patterns

Three patterns cover most Webflow sites:

Pattern 1: Marketing site. Organization schema in site-wide head code. WebSite schema (with potentialAction for site search) on the homepage. Article schema on blog post template using CMS field references. FAQ schema on the FAQ page.

Pattern 2: SaaS site. Same as marketing site, plus Product schema on the pricing page (treating your software as a Product), Service schema on individual service pages, and Review schema if you display testimonials with ratings.

Pattern 3: Local business with Webflow. Organization schema site-wide, LocalBusiness schema on the homepage and contact page (with address, hours, phone), Article schema on blog template, FAQ schema on the FAQ page.

Build the JSON-LD for each pattern with the generator, then drop into the appropriate page settings.

Validating Webflow Schema After Publishing

Webflow's "Inside head tag" code only outputs after you publish. Always publish before validating — staging URLs won't have your schema.

After publishing, run the published page URL through Google's Rich Results Test. If the schema is parsing correctly, you'll see the schema type in the test results. If there's an error, the test points to which line is broken.

One Webflow-specific gotcha: if you use CMS field references inside JSON, Webflow may HTML-escape some characters that break JSON. Test with at least one published item to make sure the dynamic values render as valid JSON. If they don't, you may need to use plain HTML instead of CMS references for problematic fields.

Frequently Asked Questions

Where exactly do I paste schema in Webflow?

Page settings → Custom Code → "Inside head tag" field. For site-wide schema, use Project Settings → Custom Code → "Head Code" instead. Both accept full script tags with JSON-LD.

Does Webflow add any schema automatically?

No. Webflow ships with zero schema by default — no Article, no Product, no Organization. You add everything manually. This gives you full control but requires doing the work.

Can I use CMS field references inside schema?

Yes. In the per-page custom code field for a CMS collection template, you can use the + Add Field button to insert references to that collection's fields. The schema then renders dynamically per item with that item's data.

Will my schema get stripped if I edit the page in the designer?

No. Custom code in page settings is preserved across designer edits. Only direct edits to that field will change it. Your schema is safe.

Can I have multiple schema blocks on one Webflow page?

Yes. Paste multiple script tags in the same "Inside head tag" field, each with its own schema. Google parses all of them. Common combination: Article + FAQ + Breadcrumb on a single blog post.

Does the schema work on the Webflow free .webflow.io subdomain?

Yes, but Google may not index .webflow.io subdomain pages aggressively. Schema works correctly there for testing, but for production SEO you should use a custom domain.