Schema markup

Schema markup is structured code added to a page that tells machines what the content means rather than only how it looks. It turns a page a human reads into data a machine can parse without guessing.

A page might display “Clean Water Initiative, 12 March 2026, Pristina”. A person infers a project, a date and a place. A machine sees three strings. Schema markup labels them explicitly, using a shared vocabulary from schema.org that search engines and AI systems both understand.

The vocabulary runs to hundreds of types. The ones that matter to nonprofits are a short list: Organization and NGO for the entity itself, Article for publications, Event for anything scheduled, FAQPage for question and answer content, and DefinedTerm for glossary entries like this one.

The benefit is not mystical. Markup does not make a page rank. It removes ambiguity, and ambiguity is where machines make mistakes. An organisation with proper markup, including its official name, logo, founding date and location, is far less likely to be confused with a similarly named one elsewhere. For nonprofits working across borders or in several languages, that disambiguation is the whole argument.

Related reading: What AI can actually do for a four-person team

What this means for your organisation

Add Organization schema to your homepage first. It is one block of code, under an hour with a plugin, and the single most useful piece of markup a nonprofit can have.

Related terms