Duda SEO

A technical SEO guide to Duda — the agency-focused website builder. What Duda handles automatically (HTTPS, CDN, SSR, sitemap, canonical tags, llms.txt, IndexNow, Blog/Product schema), what you configure manually (titles, redirects, robots.txt, Local Business and FAQ schema, custom JSON-LD), and the hard limits no setting changes: locked canonical tags, a 1,000-page / 1,500-blog-post cap, single-location schema, and no X-Robots-Tag header. Plus Dynamic Pages for programmatic SEO and the agency/white-label workflow.

First published: Jun 27, 2026 · Last updated: Jul 25, 2026 · Advanced
demand #7 in Website Builders#36 in Platform SEO#257 in Technical SEO#357 on the site

Duda is a website builder for agencies and web pros, not DIY consumers — and that shows in its SEO controls. It handles the technical baseline automatically: HTTPS on an Amazon CloudFront CDN, server-side rendering, an auto-generated sitemap, self-referencing canonical tags, llms.txt on publish, IndexNow to Bing and Yandex, and automatic Blog and Product schema. Unlike most builders, it lets you edit robots.txt (via Site Configuration Files), manage 301/302 redirects in a built-in redirect manager with bulk CSV and wildcards, inject custom JSON-LD, and auto-generate hreflang for multilingual subdirectory sites. Its Dynamic Pages feature powers programmatic SEO for multi-location and franchise work. The hard limits: you can't override canonical tags, there's a 1,000-page and 1,500-blog-post cap per site, native LocalBusiness schema is single-location only, blog URL patterns are limited, and there's no X-Robots-Tag header (noindex goes through meta robots).

TL;DR — Duda is an agency-first builder, and its SEO surface reflects that. It auto-handles HTTPS, an Amazon CloudFront CDN, server-side rendering, an XML sitemap, self-referencing canonical tags, llms.txt on publish, IndexNow (Bing + Yandex, since Nov 2021), and automatic JSON-LD for Blog and Product. Unusually for a builder, it exposes real technical controls: a replaceable robots.txt via Site Configuration Files, a built-in redirect manager (301/302, bulk CSV up to 200, wildcards), custom JSON-LD injection, automatic hreflang for multilingual subdirectory sites, and Dynamic Pages for programmatic SEO. The hard limits are specific: canonical tags can’t be overridden (locked by design), a 1,000-page / 1,500-blog-post cap per site (roughly 200 total pages once you add languages), single-location LocalBusiness schema only, limited blog URL patterns, and no custom HTTP response headers — so no X-Robots-Tag (noindex goes through meta robots). One caveat worth flagging: Google pulled the FAQ rich result from Search entirely as of May 2026, so Duda’s FAQ schema toggle no longer earns that SERP feature on Google, even though it still outputs valid markup. Duda’s own pitch is that “SEO isn’t a separate task — it’s part of the website-building process.”

Evidence for this claim The article's described duda-seo capabilities must be evaluated against the platform's current documentation rather than assumed to be search-engine behavior. Scope: Platform-specific capability documentation. Confidence: high · Verified: Duda: SEO overview Evidence for this claim Regardless of platform, Google needs crawlable URLs, accessible rendered content, descriptive metadata, and valid search directives. Scope: Google requirements independent of platform. Confidence: high · Verified: Google Search Central: SEO Starter Guide

Who Duda is actually for

Duda is positioned against WordPress-plus-agency-stack, not against Wix-for-grandma. More than 22,000 organizations manage over a million live sites on it. The platform ships a REST API, granular team and client permissions, a white-label editor, and a multi-site dashboard. When you evaluate Duda’s SEO, evaluate it the way you’d evaluate an agency tool: can it manage SEO metadata at scale across many client sites? Mostly yes — with a handful of hard ceilings worth knowing before you commit a portfolio to it.

What Duda handles automatically (zero config)

  • HTTPS / SSL — free certificates, automatic, on every site.
  • CDN — Amazon CloudFront, global, with image optimization (responsive sizes, WebP serving, lazy loading).
  • Server-side rendering (SSR) — every page renders server-side, so crawlers get HTML and there’s no JavaScript-rendering dependency. This is a genuine technical edge over JS-heavy builders.
  • XML sitemap — auto-generated, including store and multilingual pages. You can upload a custom sitemap to override it.
  • Canonical tags — auto-generated and self-referencing. You cannot override them (more on that below).
  • llms.txt — auto-generated on publish; lists live URLs and meta descriptions in a token-efficient format, and excludes noindex pages and drafts. Duda rolled this out across all of its published sites.
  • IndexNow — enabled for all sites since November 2021; submits to Bing and Yandex on publish or update. (Google has not adopted IndexNow, so this is a Bing/Yandex freshness signal, not a Google one.)
  • Blog schema — automatic JSON-LD for every blog post.
  • Product schema — automatic for active native-store catalog products.
  • Core Web Vitals tuning — templates and widgets are continuously optimized (ETag headers, bfcache, unused-CSS removal, WebP, lazy loading on top of the CDN and SSR). Duda reports 82% of its sites passed all three CWV metrics as of May 2025 — a platform-wide median, not a guarantee for your specific site.

What you configure manually

  • Meta titles and descriptions — per page; the AI Assistant can bulk-generate them, but you set and review the values.
  • H1 and heading hierarchy — entirely manual. Duda doesn’t auto-assign H1s.
  • Image alt text — the AI suggests; you apply.
  • 301 / 302 redirects — via the built-in redirect manager UI or bulk CSV upload (up to 200 URLs at once). Wildcard rules (* and **) are supported. If you leave the type blank, it defaults to 301.
  • Page- and blog-level noindex — controllable per page and per blog post, plus a site-wide option. (Set via meta robots — there’s no header-level option.)
  • Open Graph tags — per page, manual.
  • Local Business schema — enabled through Content > Business Info; it auto-populates from your stored business data once activated.
  • FAQ schema — a per-widget toggle in the Accordion widget’s Content Editor. Worth knowing before you flip it on for the SERP payoff: Google narrowed FAQ rich results to a small set of authoritative government and health sites back in 2023, then removed the feature from Search results entirely starting May 7, 2026. The toggle still adds valid structured data other engines and AI parsers can read — it just won’t earn a Google rich result anymore.
  • Video schema — manual title, description, and upload date in the Video Content tab.
  • Custom JSON-LD — added via Header HTML injection on individual pages or site-wide. Duda warns that incorrect code will be stripped, and the head section only accepts <link>, <script>, and <meta> tags (no <img> or <iframe>).
  • robots.txt — you can replace the auto-generated default with a custom file via Site Configuration Files. This is the differentiator: most builders won’t let you touch robots.txt at all.
  • Google Search Console — manual verification and integration; the GSC connection powers Duda’s “SEO Opportunities” suggestions.
  • Google Tag Manager — natively integrated through SEO & Site Settings, no-code.

Duda’s hard limits — what you cannot control

These aren’t settings you’ve missed; they’re platform constraints:

  • Canonical tag override — there isn’t one. Duda’s stated policy is that it sets canonicals correctly on your behalf so they “don’t get out of sync with the actual page URLs.” For the overwhelming majority of sites (self-referencing canonicals following the URL structure) this is a reasonable guardrail, not a problem. It only bites if you need a cross-domain canonical, a syndication setup, or any non-self-referencing pattern — and there, Duda simply can’t do it.
  • Custom HTTP response headers — not user-configurable. Most importantly, there is no X-Robots-Tag header, so noindex/nofollow must be set via meta robots tags. Duda sets Vary: User-Agent automatically, and you can’t add your own Cache-Control or Vary headers.
  • Page and blog post caps — a maximum of 1,000 site pages and 1,500 blog posts per site (blog posts don’t count toward the 1,000-page limit). Dynamic Pages count against neither.
  • Single-location LocalBusiness schema — native Local Business schema at the site level supports only one location. Multi-location businesses have to inject manual JSON-LD per page or drive schema through Dynamic Pages.
  • Blog post URL patterns — limited customization compared to WordPress, and blog posts imported via RSS arrive as HTML only (the drag-and-drop editor doesn’t apply to imported content).
  • No third-party SEO plugin ecosystem — there’s no Yoast / RankMath / SEOPress equivalent. Everything goes through Duda’s native UI or its API.
  • No URL parameters for page routing — query-string routing isn’t supported. The upside: Duda’s native store can’t spin up the parameter-based faceted navigation that wrecks crawl budget on larger platforms. The downside: filtered states can’t be indexed.
  • Root-domain SSL — Duda issues SSL for the www version automatically; publishing to the bare root domain can cause SSL issues without careful DNS setup.
  • Multi-language page cap — a site with additional languages enabled tops out around 200 total pages, and it’s per-site, not per-language: if a site already has 100 pages, you can only add one more language before hitting the ceiling. Page titles, meta descriptions, and image alt text also aren’t auto-translated — you have to translate each of those manually per language, even though hreflang tags themselves are generated automatically.
  • FAQ rich results are gone from Google — Google removed the FAQ rich result feature from Search entirely starting May 7, 2026 (after restricting it to authoritative government/health sites in 2023). Duda’s Accordion-widget FAQ schema toggle still works and still outputs valid markup, but it no longer buys you that SERP feature on Google.

Dynamic Pages: programmatic SEO on Duda

Dynamic Pages is where Duda’s agency DNA pays off for SEO, and it’s separate from the 1,000-page limit. You connect a page template to a data source — Duda’s internal Content Library, or an external collection like Google Sheets, Airtable, or your own database via API — and each row generates a unique page with its own URL, title, meta description, and OG image.

The SEO-relevant part: you can map title, meta description, Header HTML (for per-page custom schema), and noindex status to data fields, which means fully automated per-page SEO at scale. Agencies use this for multi-location landing pages, franchise sites, real estate and other listings, service-area pages, and staff directories. The third-party tool SEOmatic offers a deeper Duda integration for location- and keyword-targeted programmatic pages from structured data.

The agency / white-label workflow

This is the part generic builder reviews miss:

  • White-label editor — custom branding, a custom editor domain, and client-facing dashboards on the White Label plan.
  • Multi-site dashboard — every client site in one view with filters, labels, usage tracking, and permission controls.
  • REST API — programmatic control over accounts, sites, and content. The Pages endpoint exposes an SEO object for updating title, meta description, OG image, and index status — which makes CRM-to-website SEO sync and bulk metadata pushes realistic.
  • SEO Opportunities — Duda’s GSC-powered feature that surfaces prioritized optimization suggestions based on rankings and CTR.

Duda vs. WordPress for SEO

Honest version: it depends on the metric. Duda wins for Core Web Vitals out of the box (SSR + CloudFront + image optimization with no plugin tuning), fast launch, and agency multi-site workflows. WordPress wins for extensibility — custom canonical patterns, custom HTTP headers, log-file analysis integrations, and the Yoast/RankMath plugin ecosystem. If you need to override a canonical or set an X-Robots-Tag, that decision is made for you: Duda can’t, WordPress can.

Duda and AEO (Answer Engine Optimization)

Duda has leaned hard into AI search, rebranding its SEO hub to foreground AEO. Its native AEO surface is the llms.txt file, full structured-data support for AI parsing, IndexNow for freshness signaling, an “Area Served” schema field for service-area businesses, and a Site Audit “Blog Content Freshness” theme that flags stale or missing blog content. Duda’s internal study (across 850,000+ sites and 69M AI crawler visits) reported that AI-crawled sites see 3.2× more human traffic than uncrawled ones — directional vendor data, but it points the right way: structured, fresh, well-marked-up content is what AI crawlers reward.

Worth keeping straight: llms.txt is a community proposal, not a confirmed Google ranking signal — Google’s own AI-search guidance names it as a tactic you can ignore for traditional rankings. Its value is for non-Google AI platforms that read it for content discovery.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin an expert quote first.