How to Edit a Website in Sanity Studio: A Practical CMS Guide

March 17, 2026

Web Design

4 Minutes

If you already have a website connected to Sanity, you usually do not need to rebuild it to change the text. You need access to the correct Studio, the content record behind the page and the publishing workflow your developer configured.

That distinction is worth making first. Sanity Studio is the editing interface. Your public website is a separate application that reads the content. A saved edit, a published document and a refreshed public page are related steps, but they are not always the same moment.

This guide starts with changing an existing website. If you are setting up a new project, there is a separate route at the end. The interface can vary because each Studio is configurable, so use the labels and permissions in your own installation.

How to use Sanity Studio to make changes to a website

Open the Studio your team uses. Ask for its actual address and the appropriate account access. Do not create an unrelated new project simply because you cannot find the existing editor.
Find the content document. Search for its title or browse the configured content types. A website section may draw on a programme, project or settings record rather than a document literally named homepage.
Make a focused change. Update the relevant field and complete required information. When you edit published content, Studio creates a draft. Check whether a referenced record is reused elsewhere before changing shared information.
Preview if your project supports it. Confirm the actual page, image crop, links and narrow layout. Follow any approval process your team has agreed.
Publish the document, then check the website. Studio publication makes the content available, but the website may also need a rebuild or cache refresh according to its implementation. Ask the developer how that route works.

Change the right piece of information

Imagine a programme deadline appearing on a listing card and a detail page. If both use one reference, updating the source record can keep them consistent. If the developer duplicated the text in several places, those copies need attention too. The public layout alone cannot tell you which arrangement you have.

Before a substantial edit, identify where the content appears. Keep names, dates and eligibility information consistent. Replace an image through the appropriate field, check any descriptive text your schema provides and inspect the public crop. Avoid assuming that replacing one asset should alter every use of that image.

For an article, work through the title, introduction, headings, links and images as one piece. A shorter title may improve a card, but it should still describe the subject accurately. A preview is useful because a valid field can still produce an awkward page.

Why a published change might not appear

First, confirm that you edited the correct project, dataset, workspace and document. Then check whether you published or only saved a draft. If the public page remains unchanged, the next question belongs to the website implementation: does it read content live, rebuild when a document changes or serve a cached version?

Do not keep publishing random documents to force the page to refresh. Send the developer the page URL, document title, intended change and time of publication. That is more useful than a vague report that the CMS is broken.

Correcting a mistake

Studio provides document history and revision tools. Review the earlier version and the changes before restoring it, especially when other editors have been working. A focused correction may be safer than reverting a whole document. Avoid deletion as a routine way to hide a page; discuss the appropriate unpublish or archive workflow with the team.

Building a new Sanity website

A new project needs a content schema, Studio configuration, public interface and deployment plan. The official Next.js quick start is the appropriate technical starting point. Decide who will maintain those parts before choosing the architecture. Editing an existing site should not require the content team to repeat the initial installation.

If you are deciding how your business should manage its website, see my website design and CMS service. My GROW project shows a real Webflow content workflow, rather than a claim that every project needs the same CMS.

A useful editor lets the team change the information with confidence. The handover should explain that route clearly enough that the next correction feels ordinary.

Official sources

Updated 14 October 2026 against official documentation. Images are the existing Sanity Studio illustration and Sanity logo; interfaces vary by configuration.

Official sources

Updated 14 October 2026 against official documentation. Images are the existing Sanity Studio illustration and Sanity logo; interfaces vary by configuration.