integrations
Wix troubleshooting
When the connection or publish to Wix fails.
Most of the issues below are 5-minute fixes. If you'd rather hand it off, email support@quibo.cc and a real human answers within one business day.
"Wix rejected the API key (401)"
The key was copied incompletely, has been revoked, or belongs to a different Wix account than the one that owns the site. Site-level calls only work with keys generated by the account that owns the site.
Fix: open the API Keys Manager while signed in as the site owner, generate a new key with the Blog and Site Media permissions, 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.
"Missing a permission or access to this site (403)"
Either the key lacks a permission or its site access does not include this site.
- Publishing posts needs Blog (Manage Blog).
- Importing the cover and inline images needs Site Media (Manage Media Manager). Without it, posts still publish but go out without images.
- Listing member names needs Members (Read Members). Optional: without it Quibo shows member IDs and finds the owner through your existing posts.
Fix: permissions cannot be edited on an existing key. Generate a new key with the right permissions and the site selected under site access, then save it with Update credentials on the site page.
"Wix could not resolve the site (404 or 400)"
The site ID is wrong. It is the GUID in the dashboard URL, https://manage.wix.com/dashboard/<site-id>/home, not the site name and not the account ID.
Fix: copy the GUID again, then open the site page in Quibo and use Update credentials in the Credentials card; the new values are verified before they replace the old ones.
"Wix needs a member id to own the post"
Wix requires an owner for every post created through the API. Quibo could not detect one because the blog has no posts yet and the key cannot list members.
Fix: pick a Default author in the site's brand profile and save it, or generate a key that also has the Members permission and save it with Update credentials on the site page; the brand crawl runs again on its own.
The cover image is missing or shows as broken
Wix imports images asynchronously. Quibo waits up to 15 seconds for the import to finish and publishes anyway when it is still pending; Wix completes the import in the background, so the image usually appears within a minute.
If it never appears:
- The image URL must be publicly reachable: Wix fetches it from its own servers.
- The key needs the Site Media permission (see the 403 section).
- Check Dashboard, Media for a file named
quibo-cover-.... If it is there, edit the post and set it as cover.
Categories are not applied
Quibo lists your categories at connection time but does not assign categories to Wix posts yet. Add them in the Wix blog editor after publishing.
The post URL differs from the slug in Quibo
Wix derives the final URL from the requested SEO slug and changes it when that slug is already taken by another post. Quibo reads the real URL back after publishing and stores it with the article.
The post does not show up on the blog
- Check Dashboard, Blog, Posts: a post that is still a draft means the publish call failed and the article is in Failed in Quibo. Open it and click Publish now again.
- With the Multilingual app installed, a post whose language differs from the site language only appears in that language's feed. Set the output language of the site in Quibo to match your Wix blog.
Formatting looks different from the preview
Ricos, the Wix content format, has no inline code style: inline code is rendered in a monospace font. The FAQ stays visible as a heading, then each question in bold and its answer. The Article JSON-LD is sent in the post's SEO settings as a script tag; if Wix rejects the SEO settings, the post is published without them and Wix's own structured data applies.
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 site for 5 minutes is faster than debugging your prod site. Connect a new site