Duda integration
No native Duda connector, here is what does work.
We import posts into Duda client sites as drafts, with publish and unpublish as separate controlled calls.
How it works
Duda's Partner API authenticates with Basic credentials and includes blog endpoints that are full CRUD and purpose-built for automated publishing. Import Blog Post lands content in draft, and separate publish and unpublish endpoints control the live state. Among the platforms we integrate, this is one of the best-fit APIs for the job: the draft-then-publish flow we want is exactly the flow Duda designed.
Two access realities apply. The Partner API requires a Duda agency or API plan, which we detect at connect rather than letting calls fail mid-setup. And because Duda is a multi-site agency platform, credentials and permissions apply per site, so our setup verifies access against each specific site you connect, which is what agencies managing many client sites need anyway.
Best forAgencies on Duda publishing content across client sites who want drafts imported per site and publishing kept under explicit control.
Setup, step by step
- Confirm your Duda account is on an agency or API plan, which the Partner API requires.
- Generate Partner API credentials in your Duda dashboard.
- Add the credentials to SearchHandled's Duda connector.
- Select the client sites to connect, and we verify API access against each site individually.
- Choose per-site defaults, draft-only delivery or publish-on-approval.
Best practices
Connect sites explicitly, not wholesale
In an agency account, each client site is its own publishing destination with its own cadence and approvals. Connecting sites one by one keeps a client's content plan from ever touching another client's site.
Use draft imports as the client review step
Import lands posts in draft, which maps neatly onto client approval workflows. Let clients or account managers review drafts in Duda, then publishing is a single deliberate call.
Keep per-site voice separate
Multi-site publishing tempts template reuse. We maintain separate voice and topic settings per connected site so each client's blog reads like that client, not like the agency.
Watch plan status on renewals
API access rides your Duda plan. If the account moves off an agency or API plan, the Partner API stops answering, and our connector will report that as the cause rather than a generic failure.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Agency or API plan required
Partner API calls fail outright on accounts without an agency or API plan, since the API is a plan feature.
How we handle itWe detect plan-gated access at connect time and say so plainly, before any site mapping or content work is spent on a connection that cannot publish.
developer.duda.co
Per-site permissions in a multi-site model
Credentials valid for the account can still lack access to a specific client site, so a connector that checks only the account level fails later on individual sites.
How we handle itWe verify API access against each site you connect, site by site, so scope problems surface during setup with the specific site named.
developer.duda.co
Questions teams ask
- Is Duda a good platform for automated publishing?
Among the platforms we support, yes, it is one of the best fits. The blog API is full CRUD with draft import and separate publish endpoints, which is exactly the shape a controlled pipeline wants.
- Can different client sites have different workflows?
Yes. Delivery defaults are per site, so one client can run draft-only with manual approval while another runs publish-on-approval, and cadence and voice settings are separate per site too.
- What happens if our Duda plan changes?
The Partner API requires an agency or API plan, so losing that plan stops API access. Our connector detects it and reports the plan as the cause, and content holds in the queue until access returns.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Duda matters moves it up the rollout.