Why Schema Matters Now — Not Later

Schema markup — also called structured data — is code you add to your website to tell search engines explicitly what your content is about. Instead of Google having to infer that a page describes an event, or that your organisation is a registered charity, schema tells it directly.

Most nonprofits treat schema as an advanced technical task to tackle once other things are in place. This is a mistake. Schema implementation is straightforward, especially in Webflow, and the payoffs — enhanced search result displays, better content categorisation, improved local visibility — compound over time.

This guide covers which schema types matter for nonprofits, how to implement them in Webflow, and how to verify they're working correctly.

What Schema Actually Does

Search engines use schema to generate "rich results" — enhanced displays in search that go beyond the standard title and meta description. These can include star ratings, event dates, FAQ expandables, breadcrumbs, and more.

Beyond rich results, schema helps search engines categorise your content more accurately. An Organisation schema that identifies your charity registration number, your mission, and your geographic area of operation gives Google clearer signals about who you are and what you do. This improves your chances of appearing for the right queries from the right audiences.

Schema Types That Matter for Nonprofits

Organisation Schema

This is the most important schema for any nonprofit. It establishes your organisation's identity in structured data.

Key properties to include:

• @type: "NGO" or "NonProfit" (both are valid; NGO is broadly recognised)
• name: Your organisation's legal name
• url: Your website URL
• logo: URL to your logo image
• description: A clear description of your organisation and mission
• address: Your registered address (using PostalAddress schema)
• telephone: Main contact number
• email: Main contact email
• sameAs: Links to your official profiles (Companies House, Charity Commission, LinkedIn, etc.)

The sameAs property is particularly valuable. Linking your website schema to your Charity Commission record, your Companies House registration, and your LinkedIn profile helps search engines confirm your organisation's legitimacy and connect information across the web.

WebSite Schema

WebSite schema enables the sitelinks search box — the search field that sometimes appears within your search result — and helps establish your site as an entity with a searchable structure.

Add this to your homepage:‍

{  "@context": "https://schema.org",  "@type": "WebSite",  "url": "https://yourcharitywebsite.org.uk",  "name": "Your Charity Name",  "potentialAction": {    "@type": "SearchAction",    "target": "https://yourcharitywebsite.org.uk/search?q={search_term_string}",    "query-input": "required name=search_term_string"  }}

‍


Only include the potentialAction if your site actually has search functionality.

Event Schema

If your organisation runs events — fundraising evenings, awareness days, volunteer training, sector conferences — Event schema can generate enhanced displays in search results including date, location, and ticket information.

Key properties:

• name: Event title
• startDate: ISO 8601 format (e.g., 2025-06-15T19:00:00)
• endDate: ISO 8601 format
• location: Either a Place schema (for in-person events) or VirtualLocation
• description: Event description
• organizer: Reference to your Organisation schema
• offers: Ticket information if applicable (even for free events)
• eventStatus: EventScheduled, EventPostponed, EventCancelled, or EventMovedOnline

Article / BlogPosting Schema

For blog posts, news updates, and research publications, Article schema helps search engines categorise your content correctly and can improve how your articles appear in Google News and Discover.

Key properties:

• @type: "Article", "BlogPosting", or "NewsArticle" depending on content type
• headline: Article title
• datePublished: Publication date (ISO 8601)
• dateModified: Last update date
• author: Author name and URL
• publisher: Reference to your Organisation schema
• image: Featured image URL
• description: Article summary

FAQPage Schema

If you have a FAQ page or FAQ sections within pages, FAQPage schema can generate expandable questions and answers directly in search results. This increases your result's size and visibility, and can capture traffic directly on the search results page.

This is implemented as a list of Question/Answer pairs:

{  "@context": "https://schema.org",  "@type": "FAQPage",  "mainEntity": [    {      "@type": "Question",      "name": "How can I donate?",      "acceptedAnswer": {        "@type": "Answer",        "text": "You can donate online via our website, by bank transfer..."      }    }  ]}

BreadcrumbList Schema

Breadcrumb schema helps search engines understand your site structure and can display breadcrumb navigation in search results. This is particularly useful for sites with multiple content levels.

Implementing Schema in Webflow

There are two main approaches in Webflow: site-wide schema via custom code, and page-specific schema via embed elements.

Method 1: Site-Wide Schema via Head Code

For Organisation and WebSite schema that applies to your entire site, add the JSON-LD directly to your site's <head> via Webflow's custom code settings (Site Settings → Custom Code → Head Code).

This code runs on every page, which is appropriate for schema that describes your organisation globally.

Method 2: Page-Specific Schema via Embed Elements

For schema that varies by page — Article schema for each blog post, Event schema for each event — use a Webflow Embed element within the page body.

Place the Embed element in the page, add your JSON-LD within <script type="application/ld+json"> tags, and Webflow will render it in the page source. This approach works well for static content.

Method 3: Dynamic Schema via CMS and Custom Code

For CMS-powered content — where each blog post or event is a CMS item — you can use Webflow's CMS binding to populate schema properties dynamically. This involves placing an Embed element in your CMS template page with a JSON-LD script that uses Webflow's CMS field references for values like the article title, publication date, and description.

This is more complex to set up but ensures schema stays accurate as content updates. It's the right approach for any site with a substantial amount of CMS-managed content.

Verifying Schema Implementation

After implementing schema, verify it's working correctly:

• Google Rich Results Test (search.google.com/test/rich-results): Tests a URL or code snippet for valid schema and shows which rich results your markup might qualify for
• Schema.org Validator (validator.schema.org): Validates your markup against schema.org specifications
• Google Search Console: After your schema is indexed, Search Console's Enhancements reports show whether your structured data is valid or has errors

Common errors to watch for:

• Missing required properties for a schema type
• Date formats that don't match ISO 8601
• URLs that don't resolve (e.g., logo URLs to images that don't exist)
• Conflicts between page content and schema values

Schema and the Broader SEO Picture

Schema doesn't replace the other SEO fundamentals — quality content, appropriate title tags, mobile performance, backlinks. It builds on them. Adding Organisation schema to a site with poor technical foundations won't move your rankings. But on a well-structured site, it's a clear signal improvement worth implementing.

For the broader SEO foundations, see my guide on SEO for nonprofit websites. For the technical audit that identifies whether your foundations are solid before adding structured data, see the guide on technical SEO audits.

If you're starting a new Webflow build or undertaking a significant site refresh, schema implementation is something I include as part of the technical specification phase. 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.