Knowledge base

How to create many sites at once

On the Footprint-Free deploy form, choose Many sites, paste a list or upload a CSV, check the rows, and create them all in one go. Each site can have its own site type and CDN.

Zinn®, our Viking, reading his checklist beside an index of articles with one open.

On the Footprint-Free (PBN) line you can create a whole batch of sites in one go instead of filling in the form once per site. Each site can have its own name, WordPress title and subtitle, site type and CDN, including your own connected CDN account.

Create the sites

  1. Open Sites, press Add a site and choose your Footprint-Free plan.
  2. At the top of the form, switch How many sites? to Many sites.
  3. Paste your sites, one per line, or press Upload CSV. A plain list of domains is enough.
  4. Press Download example CSV for a file you can fill in.

  5. Under Settings for all sites, choose what every site gets unless its row says otherwise:
  6. site type, theme, CDN, DNS, HTTPS, www and so on. These are the same choices as for one site.

  7. Press Check rows. Nothing is created yet. Every row is checked and any problem is shown on
  8. its line: a domain that is not valid or is listed twice, a domain you already host, an unknown site type or CDN, an own CDN account that is not connected, or a row past your plan's free site slots.

  9. Press Next, then Create N sites. The sites are created one by one in the background, and
  10. you land on a progress page that shows each site, its line in your list and its result. A row that fails says why, and Try again retries the failed ones.

There is no limit on the number of rows: your plan's free site slots are the limit.

The columns

Only domain is required. Leave any other column blank to use the settings for all sites. Use commas, semicolons or tabs between columns. The first line can be a header naming the columns in any order; without a header, columns are read in this order:

  • domain: the site's domain, for example example.com.
  • name: the name shown for the site in your dashboard.
  • title and subtitle: the WordPress site title and tagline (WordPress sites only).
  • site_type: what to build, for example wordpress or static; the same site types as the
  • one-site form.

  • application: for an application site type, which application to install.
  • php_version: a PHP version, for example 8.4.
  • theme: a WordPress.org theme slug, or random to let us pick one.
  • plugins: WordPress.org plugin slugs, separated by |.
  • cdn: one of the CDNs offered on the form, or own for your own connected CDN account.
  • cdn_account: with own, the name of your connected CDN account as shown under Connections.
  • www: apex serves example.com, www serves www.example.com.
  • https: yes sends visitors to HTTPS, no leaves plain HTTP open.

The example file

domain,name,title,subtitle,site_type,application,php_version,theme,plugins,cdn,cdn_account,www,https
example-one.com,Example One,Example One,Reviews and guides,wordpress,,,random,classic-editor,,,apex,yes
example-two.net,Example Two,Example Two,,wordpress,,,,,,,www,
example-three.org,Example Three,,,static,,,,,,,,

Your own CDN account

To put sites on your own CDN account, choose it under Your own CDN account for all sites, or set cdn to own and cdn_account to the account's name on a row. Sites on one account of yours are linked to each other through that account, while our CDN pool spreads Footprint-Free sites across separate accounts. The form asks you to confirm this before those sites can be created. Point each domain at the nameservers of your account at your registrar.

Latest from the blog

What we have been writing about hosting, SEO and running sites at scale.

SEO and Link Building from the Hosting Layer: A 2026 Operator's View

How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.

Read the post →

Making WordPress Fast and Secure: A Performance and Plugin Checklist

A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.

Read the post →

How to Choose Managed Web Hosting in 2026: A Buyer's Guide

What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.

Read the post →

Read the blog →

Still stuck?

Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.

Contact support → All articles →