Import Content

What it is

Import brings content you already have somewhere else into a site you have already built here. You give it a WordPress site address or a feed URL, and it copies the entries across into your Articles and Content Types.

It is a one-time copy. Once content is imported, Zitegen owns it — you edit it here, and the original can be retired. Nothing stays connected, and re-running an import never overwrites edits you have made since.

Find it under a site's Workspace, in the sidebar as Import Content.

Import, or connect?

These are different intentions and it is worth being deliberate about which one you want, because they pull in opposite directions.

• Import — a migration. The content becomes yours, lives in Zitegen, and is edited here. The source can be switched off.
• Connect — a live source. Your WordPress stays in charge, you keep editing there, and Zitegen renders its content at build time. Nothing is ever copied across. That is the WordPress integration, not this page.

Running an import

1. 1

   Open Import Content

   From your site's Workspace sidebar. Imports always land in the site you are in.

2. 2

   Choose the source

   WordPress site for a full site — it brings custom post types, categories, tags and custom taxonomies across. RSS / Atom feed for a blog, which carries posts and nothing else.

3. 3

   Paste the address

   For WordPress that is the site itself, not its feed — https://example.com. For a feed it is the feed URL, usually at /feed/, /rss/ or /feed.xml. Ghost, Squarespace and Medium all publish one.

4. 4

   Watch it run, then read the report

   Larger sites take a few minutes and keep counting up as they go. When it finishes, View report shows what happened to every entry — and what was left behind.

What comes across

• Posts become blog articles, with their title, body, excerpt, author, publish date and featured image.
• Custom post types become Content Types of their own — a WordPress “Recipes” type arrives as a Recipes content type with its entries inside.
• Categories and tags map onto Zitegen’s own, and custom taxonomies are created and attached to the type that uses them.
• Advanced Custom Fields are brought across as real custom fields where the site exposes them — see below.

Everything arrives as a draft. Nothing you import is live until you publish it, so a large import can be reviewed at your own pace.

What does not

Import is deliberately honest about its limits — the report names every one of these as it happens, rather than quietly dropping things.

• WordPress pages are design, not content, so they are not imported as entries. Rebuild them as Zitegen pages, where you can actually lay them out.
• Embeds — YouTube, Maps, chat widgets — cannot be carried across, and the report says which entries had them.
• Tables inside an article body are removed. Tables on a page are fine; the article editor has no table.
• Code blocks keep their text but lose their formatting, and image captions become an ordinary paragraph underneath.

Advanced Custom Fields

ACF fields import as real Zitegen custom fields — text, numbers, dates, links, images, galleries and repeaters all map across, and a Field Group is created for them automatically before any entry is written.

Fields that point at other WordPress content — relationship, post object, user — are not imported, because they reference WordPress IDs that mean nothing here.

Running it again

Re-running the same source is safe. Every imported entry remembers where it came from, so a second run skips anything already imported rather than creating a duplicate — and it leaves your edits alone.

That makes it reasonable to import, review, publish a few, and re-run later to pick up whatever was added in the meantime.