Can we keep one domain per export market?
Yes. Each project supports its own custom domains, and binding a Cloudflare zone writes the DNS record for you, so a regional site can live on the address buyers already expect.
Use case
For manufacturers whose buyers check tolerances, materials and lead times first. CloudSite generates series pages, specification tables and enquiry forms in up to four languages, with a separate domain for each export market.
No credit card needed to try the generator.
Capabilities
Publish multilingual product catalogues with specification tables, model pages and enquiry forms, then deploy one domain for each export market.
Parameters are written as real tables rather than images, so buyers can compare models, print a page and search engines can read the values.
Every product family gets a category page and a stable URL per model, each ending with a quantity and certification enquiry form.
Generate the catalogue in English, then add up to three more languages in the same project instead of maintaining separate builds per region.
| Area | What you get |
|---|---|
| Languages | Up to four locales per site, each with hreflang, its own canonical URL and sitemap entry. |
| Deploy | Cloudflare Pages or Firebase Hosting; bind_domain writes the DNS record for you. |
| Editing | Chat edits or direct file writes through 75 MCP tools, all on the same project. |
| Audit | Built-in SEO and GEO audit for metadata, structured data and AI crawler access. |
| Preview | Shareable preview links that expire after 1 to 72 hours. |
One project state for generation, chat edits and deploys, so nothing drifts out of sync.
Give CloudSite the product, the audience and the languages. A complete first draft arrives in about 1 to 3 minutes.
Ask for a calmer hero, a spec table or another locale. Files update in place and stay deploy-ready.
Publish to the edge, bind the domain, then read traffic, leads and chat in the same console.
Yes. Each project supports its own custom domains, and binding a Cloudflare zone writes the DNS record for you, so a regional site can live on the address buyers already expect.
They are ordinary files in the project. Change a value by chat or write the file directly through the tools, with a two megabyte limit per file, then publish again.
Inquiry forms post into the console lead list, where quantity, model and certification fields arrive as structured records. Newsletter forms write into subscribers separately, so both lists stay clean.
Maintained by the CloudSite team for industrial exporters and their marketing partners. This page explains how generated catalogues handle specifications, locales and regional domains. Send a product brief through cloudsite.editorapi.com and we will point you to the right project setup.
CloudSite is a website platform at cloudsite.editorapi.com. You describe a business, or upload an existing static site, and CloudSite writes, edits, deploys and hosts it. Every console action is also an MCP tool, so agents can run the same lifecycle end to end.
Twenty sites, twenty angles, all served from the same platform.