In short. Custom root configuration files are documented for Classic and Editor 2.0, not for Duda Vibe projects.
Definition: No. Duda's documentation makes custom root configuration files available in Classic and Editor 2.0, while the same feature is unavailable for Duda Vibe projects.
Key facts
- Duda's Site SEO/AEO Settings documentation lists custom sitemap, robots.txt, and other files under a heading limited to Editor 2.0 and Classic.
- The same documentation says that the file feature is not available for Duda Vibe projects.
- Duda's Site Configuration Files guide says published sites include default
sitemap.xml,robots.txt, andllms.txtfiles. - The configuration guide supports site configuration file types such as
.txtand.xml, with custom files uploaded through URL Redirect settings.
What can a Vibe project configure?
Duda Vibe has an SEO/AEO path in the product. The documentation directs a Vibe user to open the Manage tab, expand Optimization Center, and select Additional Settings. That screen includes site-wide search settings such as a no-index control, a site meta title, and a site meta description. Duda suggests limiting the title to 60 characters and the description to 160 characters.
The availability boundary appears inside the same settings documentation. Its section heading is Custom sitemap, robots.txt, and other files (Editor 2.0 and Classic Only), followed by the note: “Not available for Duda Vibe projects.” This separates Vibe's documented SEO settings from the root-file upload feature.
Which editors support custom root files?
Duda documents the upload feature for Classic and Editor 2.0. It describes these files as files served from the root of the domain, so a configured file can use a path such as /ads.txt on the published site. The broader configuration guide says custom files, including other types, can be uploaded to the root, but its supported examples are site configuration files such as .txt and .xml.
The documented boundary is about editor availability. It does not describe a Vibe control that enables the feature, and the configuration guide repeats that custom configuration files are not available for Vibe projects yet. A Vibe project therefore uses Duda's generated root files where the platform provides them, while custom root-file replacement belongs to the other documented editors.
How is a custom file uploaded where it is supported?
In Classic or Editor 2.0, Duda's procedure starts in More, then Settings, followed by URL Redirect and Add New Redirect. Enter the desired root path in Source URL, choose File, upload the file, set the redirect type to 2xx OK (Redirect), and add the redirect. Duda says to publish or republish the site for the change to become live.
For example, Duda describes an uploaded ads.txt file as a root path like this:
www.mydomain.com/ads.txt
The same guide states that Duda does not validate custom files, so a corrupt file is still served. It also states that a custom robots.txt file does not override Duda's security systems. Those operational details apply to the documented Classic and Editor 2.0 workflow; they do not create an upload route for Vibe.
Related terms
FAQ
Can a Vibe project replace its robots.txt with an uploaded file?
No. Duda's SEO/AEO documentation marks custom sitemap, robots.txt, and other files as unavailable for Vibe projects, and its configuration guide repeats that custom configuration files are not available for Vibe projects yet.
Does Vibe lack all root files?
No. Duda says published sites include default sitemap.xml, robots.txt, and llms.txt files. The documented restriction concerns custom configuration files.
Where should a custom file be configured in Classic or Editor 2.0?
Use More, Settings, URL Redirect, and Add New Redirect, then choose File and publish or republish the site after adding it.
Sources
Check how a page reads to answer engines. Open the GEO score analyzer