Skip to content

SEO by platform

SEO for Duda

Articles arrive in your Duda site's blog through the Duda Partner API, with body, description and hero image, as drafts you can open in Duda's blog editor. Duda's own import rule helps here: an imported post always lands unpublished, and going live is a separate call we make only when the connection says so.

Beta. This connector was built from Duda's API reference and has not yet been watched importing a post into a live Duda site, which is why this page carries the beta label. The tile stays greyed on the Publishing grid until that happens. If you are on Duda and want to be the first, tell us.

How publishing works on Duda

The connection publishes through the Duda Partner API with an API user and password from your Duda account, addressed by the site name from the editor URL. New connections publish as drafts by default. The article's hero image is passed as the post's main image and thumbnail so the post shares with a picture, the edited SEO title goes into Duda's own meta title field, and the meta description goes into the post description. One more thing has to be true before a reader sees anything: the site itself must be published in Duda, and the connection test tells you if it is not.

Drafts land in Duda's own blog editor

Articles arrive with their body, description and hero image as drafts you open in Duda's blog editor. Going live is a separate call, made only when the connection says so.

Help centre: Duda
  • The hero image and meta fields travel

    The article's hero image is passed to Duda as the post's main image and thumbnail, the edited SEO title goes into Duda's meta title field, and the meta description goes into the post description, the one description-shaped field Duda has.

  • One API user serves the whole account

    Duda hands out API access per account rather than per site, so one API user can serve every site in the account. Each site is still its own connection here.

  • Published means the public URL answered

    After every publish we fetch the public URL and record what came back. Published shows only when the page was found, a fresh 404 waits out a grace window, and a server error never concludes the page is missing.

  • Articles come off a planned calendar

    Plan items on the content calendar and write them two ways: click Write on a card, or let Auto-write pick each one up at midnight on its calendar date. Both run the same researched pipeline, which drafts the article and then revises it against the content score across sweeps.

What this connection will not do

Stated up front, because finding out after the first publish costs more. Each line is a fact about what we send Duda, not a guess about the platform.

  • Re-publishing an article creates a new post. Duda's API can update a post's title and metadata but not its body, so there is no honest way to update in place. Documented: Duda

  • Whether Duda keeps a script tag in an imported post is not something we have verified yet, so treat structured data in the body as unproven on Duda. Documented: Duda

  • Posts are reachable only once the site itself has been published in Duda. The connection test tells you if it is not. Documented: Duda

Connect it in three steps

The same fields the connect wizard asks for, in the order it asks.

  1. Get API access from Duda

    In your Duda dashboard, request API access under the account settings, or through Duda support if the option is not shown. Copy the API user and the API password, the password is shown once.

  2. Copy the site name

    Open the site in the Duda editor and copy the site name from the address bar, the short code after /site/, which is different from the site's domain.

  3. Connect and test

    In the project's Publishing tab, choose Duda, paste the site name, API user and password. Set the region to eu only if your dashboard lives at my.eu.duda.co. Send a test publish and check the draft in Duda's blog editor.

Questions people ask

The ones that decide whether this fits, answered with the verdict first.

Why is this page marked beta?
Because the connector was built from Duda's API reference and has not yet been watched importing a post into a live Duda site. The tile stays greyed on the Publishing grid until that happens, and the label drops the day it does.
Can it update a published article in place?
No. Duda's API can update a post's title and metadata but not its body, so a re-publish creates a new post rather than pretending to update.
The test says there is no site with that name. What is wrong?
The site name is the short code from the editor URL rather than the site's domain. And if your dashboard lives at my.eu.duda.co, the region has to be eu as well.

Other platforms

Same pipeline, different door. Every platform page states what its connector sends and what it will not.

  • Wix

    Wix stores posts in Ricos, its own structured editor format, rather than HTML. So each article is converted, headings, lists, links and images, into that format before publishing, and posts open cleanly in the Wix editor as if written there.

  • Snapps

    Articles land in the Snapps blog with their structure and images mapped to Snapps' blog fields, as drafts by default until you switch the connection to publish live.

  • Framer

    Framer does not expose a public API that lets an outside service create CMS items on any site, so there is no direct connector to pretend with. What Framer does offer is two doors we already serve: it imports a CMS collection from an RSS feed, and its official Zapier and Make integrations create CMS items from a webhook.

SEO by platform

See it on your own site

A free audit grades your site A+ to F, then the calendar, the writer and the Duda connection do the week's work. No card required.