Publishing integrations
FTP, SFTP and static sites
Connect by FTP, SFTP or to a static site — fields, what files get uploaded, and how unpublish works there.
If your site doesn't run a CMS at all — a static site, or hosting with no content API — Clodix can upload each published article as its own HTML page straight to your web host over FTP or SFTP.
Connect it
- Open Settings → Publishing integrations and click FTP / SFTP / Static site.
- Get the connection details from your hosting provider (Hostinger, GoDaddy, Bluehost, OVH and similar hosts all show these under "FTP accounts" or similar):
| Field | What to enter |
|---|---|
| FTP Host | Your host's FTP address, e.g. ftp.yoursite.com. |
| Username | Your FTP account username. |
| Password | Your FTP account password. |
| Port | 21 for FTP, 22 for SFTP (see below). Leave blank for the default (21). |
| Blog folder path | The folder on your server where article pages should go, e.g. /public_html/blog/. |
| Website URL (optional) | The public address of that folder, e.g. https://yoursite.com/blog — used to build each article's link and SEO tags (see below). |
- Click Connect. Clodix connects live and checks it can reach the folder before saving.
What gets uploaded
Each published article becomes one self-contained file, <slug>.html, written into your blog folder — for example best-pour-over.html. The page includes:
- Your article's title and body, with simple built-in styling (no theme or template needed).
- A proper
<title>and meta description. - Open Graph tags (for link previews on social media) and a Twitter card tag.
- A canonical URL and structured data (JSON-LD) for the article — but only when you've set a Website URL. Without one, Clodix has no true public address to declare, so these URL-dependent tags are left out rather than guessed.
Clodix doesn't generate an index or listing page — only the individual article pages. If you want a page that lists them, you'll need to link to each article yourself, or use the RSS feed to build one.
Updates and unpublish
- Editing the article later and republishing overwrites the same file —
<slug>.htmlis regenerated with your latest content, so there's never a second copy. - Unpublish deletes the file from your server. Unlike WordPress, Ghost, Shopify or HubSpot, there's no "draft" state on a plain file host — the article's real copy stays safe in Clodix, and republishing restores the exact same page.
Common problems
| Message | What it means | Fix |
|---|---|---|
| "Couldn't connect — check host, port, username, password and folder path" | The connection itself failed — most often a wrong host, port or credential, or the folder doesn't exist and couldn't be created. | Double-check each field against what your hosting provider shows you, and confirm the account has write access to that folder. |
FAQ
Do I need to set a Website URL?
It's optional, but without it Clodix can't generate a correct canonical link, Open Graph tags or structured data for the page — all of which matter for SEO and for how the page looks when shared. Set it to wherever that blog folder is actually served from.
What if my host only offers FTP, not SFTP?
Plain FTP (port 21) still works. Clodix tries a plain connection first and falls back to FTPS (encrypted) automatically if that's what your host requires.
Can I use this alongside a CMS integration?
No — a site can only have one publishing integration connected at a time. Connecting FTP replaces any CMS integration you had connected before, and vice versa.