> ## Documentation Index
> Fetch the complete documentation index at: https://docs.siftly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Duda Integration

> Publish GEO-optimized content from Siftly to your Duda website via Zapier.

<Frame>
  <img src="https://mintcdn.com/siftly/IwND2vAxRbhCiRev/images/cms-integrations.svg?fit=max&auto=format&n=IwND2vAxRbhCiRev&q=85&s=2704e9affce00587d23137bf707339c7" alt="Supported CMS platforms including Duda" className="rounded-xl" width="900" height="280" data-path="images/cms-integrations.svg" />
</Frame>

## Overview

This guide walks you through connecting Siftly to Duda using Zapier as a bridge. After following it, you'll be able to publish GEO-optimized content from Siftly directly to your Duda blog with a single click.

**Difficulty:** ✅ Non-tech friendly — no coding required. Setup takes about 10 minutes.

Duda's direct API requires an enterprise-tier plan. Zapier is the only automation platform with a native Duda "Create Blog Post" action, so Siftly uses a Zapier webhook to bridge the connection. One Zapier account can handle all your Duda sites.

***

## How it works

<Steps>
  <Step title="Siftly sends content to Zapier">
    When you click **Publish → Duda** in Siftly, it sends your article (title, body, description, author, site name) to a Zapier webhook URL.
  </Step>

  <Step title="Zapier creates the post in Duda">
    Your Zap receives the data and uses Duda's "Create Blog Post" action to create the post on your Duda site.
  </Step>

  <Step title="Post appears on your Duda site">
    The blog post is created on your Duda website. You can edit slug, tags, and SEO fields in the Duda editor if needed.
  </Step>
</Steps>

***

## Prerequisites

Before starting, you'll need:

* A **Duda** website with a blog enabled (Agency plan or higher)
* A **Zapier Pro** account (\$30/month — [start a 14-day free trial](https://zapier.com/app/pricing))
* About 10 minutes for the one-time setup

<Note>
  Zapier Pro is required because the "Webhooks by Zapier" trigger is a premium feature. One Zapier Pro account covers **all** your Duda sites — no per-site cost.
</Note>

***

## Step 1: Create a Zap in Zapier

<Steps>
  <Step title="Create a new Zap">
    Log in to [zapier.com](https://zapier.com/app/zaps) and click **Create Zap**.
  </Step>

  <Step title="Set the Trigger">
    1. Search for **"Webhooks by Zapier"** as the trigger app
    2. Choose **"Catch Hook"** as the trigger event
    3. Click **Continue** — no configuration needed
    4. Zapier shows your webhook URL:

    ```
    https://hooks.zapier.com/hooks/catch/123456/abcdef/
    ```

    5. **Copy this URL** — you'll paste it into Siftly in Step 2
    6. Click **Continue** (skip the test for now — Siftly will send test data when you connect)
  </Step>

  <Step title="Set the Action">
    1. Click the **+** to add an action step
    2. Search for **"Duda"** and select it
    3. Choose **"Create Blog Post"** as the action event
    4. Click **Continue**
    5. Click **Connect Account** — a Duda login popup opens
    6. Log in with your **Duda Agency credentials**
    7. Authorize Zapier and click **Continue**
  </Step>

  <Step title="Configure the Duda action">
    Zapier shows the Duda blog post fields. Map them to the webhook data:

    | Duda Field                 | Select from trigger                                                                            |
    | -------------------------- | ---------------------------------------------------------------------------------------------- |
    | **Site Name** (required)   | Select `site_name` from the dropdown — OR hardcode your site name (e.g., `www.srgaglobal.com`) |
    | **Title** (required)       | Select `title`                                                                                 |
    | **Description** (required) | Select `description`                                                                           |
    | **Content** (required)     | Select `content`                                                                               |
    | **Author** (optional)      | Select `author_name`                                                                           |
    | **Thumbnail**              | Leave empty                                                                                    |
    | **Main Image**             | Leave empty                                                                                    |

    <Tip>
      **Multi-site tip:** Map **Site Name** to the `site_name` field from the webhook data instead of hardcoding it. This way, one Zap handles all your Duda sites — Siftly sends the correct site name with each publish.
    </Tip>

    <Warning>
      The webhook fields may not appear in the dropdown until Zapier receives at least one payload. Complete Step 2 first (connect Siftly), then come back to Zapier and re-map the fields.
    </Warning>
  </Step>

  <Step title="Turn on the Zap">
    Click **Publish** to activate the Zap. It's now waiting for data from Siftly.
  </Step>
</Steps>

***

## Step 2: Connect Duda in Siftly

1. In Siftly, go to **Settings → Integrations**
2. Click **Connect** next to **Duda**
3. Paste the **Zapier webhook URL** from Step 1
4. Enter your **Duda Site Name** (e.g., `www.srgaglobal.com`) — this is sent with each publish so the Zap knows which site to create the post on
5. Optionally enter your **Blog Base URL** (e.g., `https://www.yoursite.com/blog`) — used to show the published post link in Siftly
6. Click **Connect Duda**

Siftly sends a test payload to verify the webhook is active. If your Zap is turned on, you'll see a success confirmation.

<Note>
  After connecting, go back to Zapier and edit your Zap's action step — the webhook fields (title, content, description, site\_name, author\_name) will now appear in the mapping dropdowns.
</Note>

***

## Step 3: Publish from Siftly

1. Open any content piece in Siftly's content editor
2. Click **Publish → Duda**
3. Click **Publish**

Siftly sends the content to Zapier, which creates the blog post in Duda within seconds.

***

## Multiple Duda sites

One Zapier Pro account handles all your client sites:

**Option A — One Zap for all sites (recommended):**

* Map the **Site Name** field in Zapier to `site_name` from the webhook
* Each Siftly org stores its own Duda site name
* One Zap dynamically routes to the correct site

**Option B — One Zap per site:**

* Create separate Zaps for each site, each with its own webhook URL
* Hardcode the site name in each Zap's Duda action
* Each Siftly org connects with its site-specific webhook URL

***

## Fields sent to Duda

Siftly sends these fields automatically on every publish:

| Field         | Description                                  |
| ------------- | -------------------------------------------- |
| `site_name`   | Your Duda site name (for multi-site routing) |
| `title`       | Article title                                |
| `content`     | Full HTML body                               |
| `description` | Meta description / excerpt                   |
| `author_name` | Content author                               |

<Note>
  Duda's Zapier action does not support slug/path, meta title, tags, or draft/published status control. Posts are created with Duda's default settings. Edit slug, tags, and SEO fields directly in the Duda editor after publishing.
</Note>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Webhook URL rejected — 'timed out' or 'unreachable'">
    Your Zap may not be turned on. Go to Zapier → your Zap → check it shows **ON** (green). If you just created it, click **Publish** to activate.
  </Accordion>

  <Accordion title="Publish succeeds in Siftly but no post appears in Duda">
    Check Zapier's **Zap History** (Zapier → your Zap → History tab). If the trigger fired but the action failed, common causes:

    * Duda account disconnected in Zapier — reconnect it
    * Site not selected — edit the Zap and hardcode or map the site name
    * Field mapping is empty — re-map the fields after Siftly sends a test payload
  </Accordion>

  <Accordion title="Fields don't appear in Zapier's mapping dropdown">
    Zapier needs at least one webhook payload to detect the field structure. Connect Siftly first (sends a test), then go back to Zapier → edit the action → fields will now appear.
  </Accordion>

  <Accordion title="I want to change the webhook URL">
    Go to Siftly → **Settings → Integrations → Duda** → **Disconnect**, then reconnect with the new webhook URL.
  </Accordion>

  <Accordion title="Do I need a separate Zapier account per client?">
    No. One Zapier Pro account (\$30/month) covers all your Duda sites. Use the `site_name` field to route content to the correct site dynamically.
  </Accordion>
</AccordionGroup>

***

## Difficulty & setup recap

<Card title="Duda Setup Summary" icon="webhook">
  | Aspect                 | Rating                                             |
  | ---------------------- | -------------------------------------------------- |
  | **Initial setup**      | ✅ Easy — paste a webhook URL, no coding            |
  | **Zapier setup**       | ⚠️ One-time 10-minute setup + Zapier Pro (\$30/mo) |
  | **Ongoing publishing** | ✅ Easy — one-click publish from Siftly             |
  | **Multiple sites**     | ✅ One Zap handles all sites via `site_name`        |
  | **JSON-LD**            | ❌ Not supported via Duda's Zapier action           |
  | **Developer needed?**  | No                                                 |
</Card>

***

## Related

<CardGroup cols={2}>
  <Card title="CMS Integrations Overview" icon="grid-2" href="/integrations/overview">
    Compare all supported platforms and the unified field mapping system.
  </Card>

  <Card title="Quickstart Guide" icon="rocket" href="/quickstart">
    Set up your brand and run your first GEO analysis.
  </Card>

  <Card title="Content Generation" icon="file-pen" href="/features/content-generation">
    How Siftly generates GEO-optimized content and recommendations.
  </Card>

  <Card title="Choosing a CMS for AI Visibility" icon="book" href="https://siftly.ai/blog/cms-and-ai-visibility">
    Our guide to picking the right CMS for GEO optimization.
  </Card>
</CardGroup>
