Sanity SEO done right: Open Graph, JSON-LD, fallbacks

A quick walkthrough of how we handle SEO inside every Sanity project we build - the exact schema patterns, fallback logic, and Open Graph setup we use as a default baseline on Turbostart Sanity.

Frequently asked questions

Why does Sanity need a custom SEO schema when it's already unopinionated?
Sanity's unopinionated nature means it can handle anything from blogs to e-commerce systems, but this flexibility doesn't include built-in SEO defaults. The speaker provides a reusable SEO schema pattern that works across all project types, giving you a consistent baseline without forcing opinions on the content model itself.
What's the purpose of having both a title field and an SEO title field?
The title field serves as your primary content field (like a blog post title), while the SEO title acts as a fallback override. This allows you to use the same editing experience across different document types—some may not need the SEO tab at all, but when they do, the SEO title takes precedence for search engines.
How should you handle Open Graph setup for different social platforms?
You can set up dedicated Open Graph fields for title, description, and image. You can go further and create platform-specific overrides for Twitter, Facebook, and LinkedIn if needed, but the speaker recommends starting with the basic Open Graph fields as your de facto baseline.
What does the speaker mean by 'set and forget' JSON-LD?
Instead of manually writing JSON-LD schemas, pull data you're already storing in Sanity (titles, descriptions, authors) directly into JSON-LD through your GROQ queries. This way you enter the data once and the schema generates automatically, requiring no ongoing maintenance.
Why include both SEO no index and SEO hide from lists fields?
No index prevents search engines from indexing a page, useful for PPC landing pages. Hide from lists removes the page from specific lists within your site without affecting search indexing, giving you granular control over both search visibility and internal navigation.
Where can you find the reusable SEO schema pattern the speaker uses?
The Turbo Art Sanity repository on GitHub contains the exact schema patterns. Look specifically at the SEO fields definition and the GROQ queries to see how the speaker implements title, description, image, no index, and hide from lists across all projects.


Continue watching

Get in touch

Fill out the form below and we'll get back to you