Check SEO fields and copy in Sanity Studio

The @siteoshq/sanity plugin adds an SEO/GEO Audit document tab with separate SEO and Text checks. It reads the document types and fields you configure, including supported related content and language-specific mappings.

Install and configure

The current release is 0.3.0, verified with Sanity 6.16.0 and React 19.2.8. It requires Node.js 22.12 or later. Review the supported versions and full setup guide before changing an existing Studio.

Install in the package that owns your Studio, using its existing package manager:

pnpm add @siteoshq/sanity@0.3.0

Adapt the published configuration example to your schema names, field paths and website behavior. The plugin does not infer your routes, metadata templates or language fallbacks.

Use withSiteosDocumentView inside the existing Structure tool. This fragment assumes you have created the mapped siteosOptions; keep the rest of your Studio configuration:

import { structureTool } from "sanity/structure";
import { withSiteosDocumentView } from "@siteoshq/sanity";
import { siteosOptions } from "./siteos.config";

// Inside your existing plugins array:
structureTool({
  // Preserve your existing structure and other options.
  defaultDocumentNode: withSiteosDocumentView(siteosOptions),
});

If you already have a defaultDocumentNode, pass it as the helper's second argument. Custom singleton document views may need explicit wiring; the setup guide covers both cases. Restart Studio after configuration and deploy it through your usual workflow when ready.

Connect your Project

An administrator connects Studio to the intended SiteOS Organization, Project and SEO-enabled environment. The connection is shared through a protected Sanity document. Local and hosted Studio origins need separate connections; connect again from the deployed Studio URL.

Verify the Project and environment shown in the audit tab. For a team rollout, review the connection-document permissions in the setup guide, particularly with custom Sanity roles.

Check SEO fields

Save the draft, open SEO/GEO Audit → SEO and select Check SEO. Depending on your mappings, checks cover metadata, headings, images, links, slug, duplicate content fields, canonical URL, indexing preference, social image and focus keyword.

These deterministic checks do not use AI or research credits. Open field takes you to the relevant editor field. Unconfigured or unavailable evidence stays visible. A document check does not verify the final page's HTTP response or rendered website; use Site Audit after publication for that.

Review text and apply corrections

Choose Text → Preview content to inspect what is included without sending document text to SiteOS. Select Check text to run the explicit AI review using your Organization's SEO credits. For the same kind of review on published pages, use content checks.

Results show the source text, suggested correction and explanation. Apply correction updates only the selected plain-text draft field when its value is still current. Portable Text and related-document suggestions open their source for manual editing. The plugin never publishes a document automatically.

SEO and Text results have separate check times. They survive editor navigation and same-tab reload when browser storage is available. Changed document content or mappings mark previous evidence as outdated. These are local session results, not shared review history for all editors.

Review localized content

Map the root document's language and the fields that your website actually uses. Version 0.3.0 supports locale-aware mappings, explicit per-field fallbacks and a review-language selector for shared documents. Related content can inherit the page's language.

Configure resolve or localizedArrayPath where your schema needs them. An upgrade alone cannot determine translation or fallback rules. See the localization examples for the full configuration.