# Rendering SEO & GEO Metadata on Your Site
> Source: https://agilitycms.com/docs/developers/rendering-seo-geo-metadata
Agility stores your pages' SEO and **GEO** fields and returns them from the Fetch API. It doesn't write markup into your site. **Your site builds the structured data (JSON-LD) and the `` metadata each time it renders a page.** It builds them from those fields *and* from the content itself.
This article covers where that markup comes from, how the pieces combine, and how to build it with `@agility/geo` and `@agility/nextjs`.
## The short version
- **Nothing is generated inside Agility.** Saving or publishing a page doesn't create JSON-LD. Your site creates it when it renders the page.
- **Most of it is built automatically** by `buildJsonLd()` from `@agility/geo`, or `` in Next.js: an Organization and WebSite, the page's WebPage, and a breadcrumb.
- **Content you already have becomes structured data in your code.** A blog post's title, image, date and author can become a BlogPosting. An FAQ component's questions can become an FAQ. Nobody retypes them as JSON-LD.
- **Editors fill the gaps** with the **JSON-LD schema** field on the **GEO** tab: anything the site can't work out from content. They can also correct a generated value.
- **Everything ends up in one `@graph`**, in one ``
```
Always serialize with `serializeJsonLd` (or `jsonLdScriptTag`, which returns the whole tag), never `JSON.stringify`. Editors write the Summary and JSON-LD, and plain JSON lets text such as `` break out of the tag.
On other stacks, read `page.geo` and `page.seo` (and `item.geo` / `item.seo` for a dynamic item) from the Fetch API and build the graph the same way. If your site renders none of these, the fields are stored and served, but nothing appears on your pages.
## The AI settings
**AI Crawlers** and **Include in llms.txt** are stored and returned by the Fetch API (`geo.ai.crawl`, `geo.ai.llmsInclude`), but **they don't block or list anything by themselves.** They take effect only when your site's `robots.txt` and `llms.txt` routes read them. See [Controlling Which Crawlers and AI Bots Can Read Your Site](/docs/developers/controlling-crawlers-and-ai-bots) for a `robots.txt` route, and [Making Your Agility-Powered Site Readable by AI](/docs/developers/making-your-site-readable-by-ai#2-publish-an-llmstxt-index) for an `llms.txt` route. Builders for both files are planned for `@agility/geo`.
## Check the result
Agility doesn't preview the final JSON-LD: the **JSON-LD schema** field validates only what the editor typed. Check the page your site renders:
- Open it in Google's [Rich Results Test](https://search.google.com/test/rich-results) or the [Schema Markup Validator](https://validator.schema.org/). The GEO tab links to both.
- In code or tests, run `validateJsonLd()` on the built graph. It flags broken JSON, misspelled types, and the same organization described twice under different `@id`s:
```ts
import { buildJsonLd, validateJsonLd, type BuildJsonLdOptions } from "@agility/geo"
declare const options: BuildJsonLdOptions
const { valid, errors, warnings } = validateJsonLd(buildJsonLd(options))
```
## Moving from Additional Header Markup
Before these fields, JSON-LD went into **Additional Header Markup**. That still renders, but as a separate block: it isn't validated, escaped or merged, so the same organization can end up described twice. Move it into **JSON-LD schema** or, better, into site settings and code. Then clear the old field. Sites not yet on these packages can keep using [Additional Header Markup](/docs/developers/structured-data-and-ai-crawlers) as before.
---
## Related pages
- [Website Deployment Checklist](https://agilitycms.com/docs/developers/website-deployment-checklist.md)
- [Legacy Content Migration](https://agilitycms.com/docs/developers/legacy-content-migration.md)
- [Faster indexing with XML sitemaps and IndexNow](https://agilitycms.com/docs/developers/faster-indexing-with-xml-sitemaps-and-indexnow.md)
- [Making Your Agility-Powered Site Readable by AI](https://agilitycms.com/docs/developers/making-your-site-readable-by-ai.md)
- [Controlling Which Crawlers and AI Bots Can Read Your Site](https://agilitycms.com/docs/developers/controlling-crawlers-and-ai-bots.md)
- [Improving and Monitoring Lighthouse Scores](https://agilitycms.com/docs/developers/improving-and-monitoring-lighthouse-scores.md)
- [Adding Structured Data and AI-Crawler Rules](https://agilitycms.com/docs/developers/structured-data-and-ai-crawlers.md)
Index of every docs page: https://agilitycms.com/docs/llms.txt