Wix integration
Approved work lands in Wix, without copy-paste.
Push structured drafts to Wix Blog through the Draft Posts API, with publishing kept under your control.
How it works
SearchHandled connects to Wix as an authorized app or with an API key and writes through the Blog's Draft Posts API. Wix stores post content as Ricos JSON, a structured rich-content format, so we convert our content into validated Ricos nodes (paragraphs, headings, lists, images with explicit dimensions) before sending. Because Wix requires third-party apps to attribute content to a member, drafts are created under a member identity you designate.
The Wix flow is draft first, then a separate publish call. We create every post as a draft so it appears in your Wix dashboard for review, and publishing happens either when you approve in SearchHandled or manually inside Wix, whichever you prefer. We keep the canonical version of each piece on our side, so refreshes and corrections do not depend on round-tripping content back out of Wix.
Best forBusinesses on Wix who want real blog drafts appearing in their dashboard instead of documents to copy and paste.
Setup, step by step
- Create an API key in your Wix account (or authorize the SearchHandled app) with blog permissions for the target site.
- Provide the site ID and select or create the member account that delivered posts will be attributed to.
- Run the connection check, which performs a dry-run draft to verify scopes and identity context.
- Set default categories and whether approved posts publish automatically or wait in drafts.
- Send a test draft and review it in the Wix dashboard.
What lands in Wix
| Element | How it lands |
|---|---|
| Title and body | Converted to the native format, then verified by reading the entry back. |
| SEO metadata | Mapped to the platform's own fields, and flagged where it has none. |
| Images | Uploaded to your media storage with alt text. Never hotlinked. |
| Internal links | Rewritten to your live URLs and checked against redirects. |
| Publish state | Draft and published. |
Field mapping is confirmed against your own content model during setup. Connectors are on every plan; the number of connected sites is what varies.
Best practices
Set up a clear author member
Wix requires a memberId on third-party posts. Create or pick a member whose name you want as the byline, rather than letting posts attach to whatever account created the API key.
Review drafts in the Wix editor initially
Ricos rendering has its own rules, so open the first few drafts in Wix and check headings, images, and spacing. Once your template settles, approval from the SearchHandled queue alone is enough.
Keep edits flowing through one side
Because Wix rich content does not round-trip reliably, decide whether ongoing edits to a post happen in Wix or through SearchHandled refreshes, and stick with it per post to avoid divergence.
Scope the API key to what the integration needs
Grant blog permissions explicitly rather than using an all-access key. It keeps the connection auditable and means a revoked key affects only content delivery.
Use it in the full SEO workflow
The connector is the last mile, not the strategy. Read the Wix SEO automation workflow for the evidence gates, draft state, review rules, publish checks, and measurement loop that surround this integration.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Content must be valid Ricos JSON
Wix has no official HTML conversion endpoint, drafts with invalid node nesting are rejected, and images without explicit dimensions cause problems.
How we handle itWe maintain a validated HTML-to-Ricos converter that enforces legal node nesting and always supplies image dimensions, so drafts arrive well-formed.
forum.wixstudio.com, dev.wix.com
Errors reading rich content back
Reading posts back through the API can return 400 errors on rich content, which breaks integrations that rely on round-tripping content out of Wix.
How we handle itWe keep the source of truth for every delivered piece on our side, so refreshes and edits never depend on successfully reading content back from Wix.
forum.wixstudio.com
403 PERMISSION_DENIED from scopes or identity context
Requests fail with PERMISSION_DENIED when blog scopes are missing or the request runs in the wrong identity context, which is easy to get wrong with Wix's app and member model.
How we handle itWe use an admin key with explicit blog scopes and verify the whole path with a dry-run draft at connect time, so identity problems show up during setup, not delivery.
dev.wix.com
Questions teams ask
- Why do posts arrive as drafts instead of publishing directly?
Wix's API model is draft first with a separate publish step, and we treat that as a feature. Drafts land in your dashboard for review, and publishing happens on your approval, either from SearchHandled or inside Wix.
- What is Ricos and why does it matter?
Ricos is the JSON format Wix uses to store rich content. There is no official HTML converter, so we built and maintain our own validated conversion. Practically, it means your content arrives as properly structured Wix content, not a fragile HTML blob.
- Can my team edit delivered posts in Wix?
Yes, drafts and published posts are normal Wix Blog posts and fully editable. Just note that if a post is heavily edited inside Wix, later refreshes from our side are based on our stored version, and we flag conflicts rather than overwriting silently.
Connect Wix
One tested path from approval to publish.
Bring your content model to setup. We will map the destination and validate a draft before anything goes live.