Sanity troubleshooting

"Insufficient permissions" on publish

Your token doesn't have the Editor permission. Viewer tokens can't create documents or upload assets.

Fix: re-issue the token with the Editor permission at sanity.io/manage, then open the site page in Quibo, use Update credentials in the Credentials card, and the new values are verified against your CMS before they replace the old ones.

CORS error from the studio

Quibo talks to Sanity from its own servers, so it never triggers CORS. If your Studio shows a CORS error, add the Studio URL to the CORS allowed origins at sanity.io/manage, Project, API, CORS origins.

Documents land as post, or in the wrong type

Quibo picks the post type from the documents already in the dataset (post, article, blogPost, blog, news, story, entry, page, then the most common non-system type). An empty dataset gives it nothing to go on, so it falls back to post with the canonical fields (title, slug, language, metaTitle, metaDescription, coverImage, body, faq, schemaJsonLd, publishedAt, aiAssisted).

Fix: create one document of your real post type in Studio (a title and a body are enough), then click Re-crawl brand on the site page. The next publish uses the discovered type and field names.

Fields stay empty in Studio

Quibo only writes fields it has seen on your existing posts, matched by name (for example seoTitle or metaTitle, coverImage or mainImage, faq or faqs, schemaJsonLd or jsonLd). A field that no sampled post has ever filled, or that uses a name outside those aliases, is left alone.

Fix: fill the field on at least one existing post, click Re-crawl brand, then publish again. If the field name is unusual, email support with the name and we add the alias.

Default author dropdown is missing

The dropdown appears only when your post type has a reference field named author and at least one existing post references an author document.

Fix: set the author on one existing post in Studio, then click Re-crawl brand on the site page.

PortableText looks broken in studio

We render to a standard PortableText shape (block + span + marks + listItem, plus code blocks). If your body field only allows custom block types you need to register the standard block type in your schema. Sanity's PortableText docs cover this. Inline images from the article body are not sent, only the cover.

Cover image doesn't appear

The cover is uploaded as an image asset and referenced from the first image field named coverImage, cover, featuredImage, mainImage, heroImage, image or thumbnail. Sanity assets need a serializer in the front-end to render: make sure your front-end resolves asset._ref via @sanity/image-url.

Published posts have no live link, or no Search Console data

Quibo learns a post's live address from the Post address pattern on the site page (see Connect Sanity). Without it a published post has no live address, so the article page has no link to the live post and Search Console data cannot be matched to the article.

Fix: open Sites, then your site, and in the Post address card tap Use this pattern if a suggestion is shown, or type the address of one post with {slug} where its slug goes. Every published post gets its address at once.

No Open in Sanity Studio link, or it opens the wrong place

The link appears only once the Post address card has your Studio address, and it opens the post under that address.

Fix: open your Studio and copy its address from the browser, without the tool name at the end (such as /structure, /content or /dashboard). Save it under Link to your Sanity Studio in the Post address card. Then use Open your newest post in Sanity Studio to check it opens the post.

The live link opens the wrong page

The pattern does not match how your front end builds addresses (a missing /blog, a trailing slash, a different domain).

Fix: open a post on your site, copy its address, replace the slug with {slug} and save it in the Post address card. Posts the old pattern addressed move to the new one. A post whose slug was changed in Studio after publishing keeps the address built from its original slug: email support and we correct it.

Still stuck?

Email support@quibo.cc with the organization ID shown in Settings, Account. Business plans get priority routing, with a typical response under 8 business hours.

If you'd rather start clean: connecting a fresh test dataset for 5 minutes is faster than debugging your prod schema. Connect a new site