- Webflow & CMS
Schema Markup for Nonprofit Websites: How to Implement It in Webflow
Key takeaways
- Schema markup is structured code that tells search engines what your content is, and implementing it in Webflow is more straightforward than most nonprofits assume.
- Organisation schema is the priority for any charity, and its sameAs property (linking to your Charity Commission record, Companies House registration, and LinkedIn) helps Google disambiguate your organisation in search results.
- Other schema types worth carrying are WebSite, Event, Article/BlogPosting and BreadcrumbList; FAQPage no longer earns a rich result, because Google retired that feature in 2026.
- Webflow supports three implementation routes: site-wide JSON-LD in head code, page-specific embed elements, and dynamic schema populated from CMS fields so it stays accurate as content changes.
- Validate every implementation with the Google Rich Results Test, the Schema.org Validator, and Search Console, watching for missing properties, non-ISO date formats, and mismatches between schema and page content.
- Schema builds on SEO fundamentals rather than replacing them: quality content, title tags, and performance still matter.
Summary
How to implement schema markup on a Webflow nonprofit website: which types still earn a rich result, the three ways to add JSON-LD in Webflow, and how to test what you have added.
Why Schema Matters Now, Not Later
Schema markup is code you add to your website to tell search engines explicitly what your content is about. Most nonprofits treat it as an advanced task to tackle later. This is a mistake. Schema implementation is straightforward in Webflow and the payoffs compound over time.
What Schema Actually Does
Search engines use schema to generate rich results: enhanced displays that go beyond the standard title and meta description. Beyond rich results, schema helps categorise your content more accurately. An Organisation schema identifying your charity registration number, mission, and geographic area gives Google clearer signals about who you are and what you do.
Schema Types That Matter for Nonprofits
Organisation Schema
The most important schema for any nonprofit. Key properties: @type ("Organization", or the NGO subtype; schema.org has no "NonProfit" type), name, url, logo, description, address, telephone, email, and sameAs.
The sameAs property is particularly valuable. Linking your schema to your Charity Commission record, Companies House registration, and LinkedIn profile gives Google external records to match you against. Google's own framing is that organisation markup on your home page "can help Google better understand your organization's administrative details and disambiguate your organization in search results". Disambiguation is the benefit on offer.
WebSite Schema
Google removed the sitelinks search box in November 2024, so the potentialAction search markup this schema used to carry now earns nothing. There is no need to strip it out: Google said unsupported structured data of this kind causes no errors. WebSite schema on your homepage is still supported, for site names.
Event Schema
For fundraising evenings, volunteer training, and sector conferences. Google shows the event rich result only for events bookable by the general public at a physical location, so an online-only event does not qualify. Key properties: name, startDate, endDate, location, description, organizer, offers, and eventStatus. Use ISO 8601 date format throughout.
Article / BlogPosting Schema
For blog posts and research publications. Key properties: @type ("Article", "BlogPosting", or "NewsArticle"), headline, datePublished, dateModified, author, publisher, image, and description.
FAQPage Schema
The FAQ rich result is gone. Google added a deprecation notice in May 2026 and removed the documentation on 15 June 2026, so FAQPage markup no longer produces expandable questions and answers in search results. The FAQ section itself still earns its place on the page: see what belongs on a nonprofit FAQ page.
BreadcrumbList Schema
Helps search engines understand your site structure and can display breadcrumb navigation in search results, though Google now shows it on desktop only. Particularly useful for sites with multiple content levels.
Implementing Schema in Webflow
Method 1: Site-wide schema via head code. For Organisation and WebSite schema, add JSON-LD to Site Settings → Custom Code → Head Code. This runs on every page.
Method 2: Page-specific schema via embed elements. For Article and Event schema, use a Webflow Embed element within the page body with JSON-LD inside <script type="application/ld+json"> tags.
Method 3: Dynamic schema via CMS. For CMS-powered content, use Webflow's CMS field references within an Embed element on the template page to populate schema properties dynamically. This ensures schema stays accurate as content updates. It's the right approach for any site with substantial CMS-managed content.
Verifying Schema Implementation
- Google Rich Results Test: Tests a URL for valid schema and shows which rich results your markup might qualify for
- Schema.org Validator: Validates your markup against schema.org specifications
- Google Search Console: After indexing, the Enhancements reports show whether your structured data is valid or has errors
Common errors: missing required properties, date formats not matching ISO 8601, URLs that don't resolve, and conflicts between page content and schema values.
Schema and the Broader SEO Picture
Schema doesn't replace SEO fundamentals: quality content, title tags, mobile performance, backlinks. It builds on them. For the broader SEO foundations, see the guide on SEO for nonprofit websites. For the technical audit that identifies whether your foundations are solid, see the guide on technical SEO audits.
If you're assessing an existing site, the Blueprint Audit reviews your current structured data alongside the other technical and content factors that affect search performance.
Two clicks. Three things.
Send the address of your website. Within two working days you get a short email naming the three things a funder would hold against it, including what AI assistants like ChatGPT and Google’s AI Overviews currently say about you. No report, no call, no follow-up unless you ask.
Received. Your three things arrive within two working days.
That did not send. Email hello@socialectric.com with your website address and I will reply from there.
Frequently asked questions
- What is schema markup and is it worth a small charity's time?
Schema markup is code you add to your site that tells search engines explicitly what your content is about. Most nonprofits file it under advanced tasks to tackle later, which is a mistake: it is straightforward to implement in Webflow and the payoff compounds over time. Search engines use it to generate rich results that go beyond the standard title and description, and to categorise your content more accurately.
- Which schema type matters most for a charity?
Organisation schema. The key properties are @type, set to Organization or its NGO subtype (schema.org has no NonProfit type), plus name, url, logo, description, address, telephone, email and sameAs. The sameAs property is the valuable one: linking to your Charity Commission record, your Companies House registration and your LinkedIn profile gives Google external records to match you against. Google's stated benefit is disambiguation, not ranking. Its Organization structured data guide says the markup can help it understand your administrative details and tell your organisation apart from others in search results.
- What other schema types should we consider?
WebSite schema on the homepage, which Google still supports for site names, though the sitelinks search box it used to enable was removed in November 2024. Event schema for fundraising evenings, volunteer training and conferences, using ISO 8601 dates; Google shows the event rich result only for events the general public can book, held at a physical location. Article or BlogPosting schema for blog posts and research publications. BreadcrumbList schema to describe your site structure, which is particularly useful when you have several content levels. FAQPage schema earns nothing in Google Search any more: the FAQ rich result was retired in 2026. A visible, maintained FAQ section is still worth having, for the reasons set out in what belongs on a nonprofit FAQ page.
- How do we add schema to a Webflow site?
Three ways, depending on the scope. For Organisation and WebSite schema, paste the JSON-LD into Site Settings, then Custom Code, then Head Code, so it runs on every page. For page-specific markup such as Article or Event, put the JSON-LD inside a script tag of type application/ld+json in a Webflow Embed element in the page body. For CMS-driven content, use Webflow's CMS field references inside an Embed element on the template page so the schema populates dynamically and stays accurate as content changes, which is the right approach for any site with substantial CMS-managed content.
- How do we check the markup is valid?
Use Google's Rich Results Test to check a URL and see which rich results the markup might qualify for, the Schema.org Validator to check it against the schema.org specifications, and the Enhancements reports in Google Search Console once the page is indexed to see whether the structured data is valid or throwing errors. The common failures are missing required properties, dates that do not match ISO 8601, URLs that do not resolve, and schema values that conflict with what is actually on the page.
- Will schema markup improve our search rankings by itself?
No. Schema builds on SEO fundamentals rather than replacing them, so quality content, title tags, mobile performance and backlinks still do the heavy lifting. Nor is it an AI-visibility lever: Google's AI optimisation guide states that structured data is not required for generative AI search and that there is no special schema.org markup you need to add. For what does matter to AI answers, see answer engine optimisation for nonprofits. If you are assessing an existing site, the Blueprint Audit reviews your current structured data alongside the other technical and content factors that affect search performance.