Importing your existing posts and pages

When you add a site, Blog AI imports your published posts and pages. The import is what lets it learn your voice, audit every post, match your posts to their Google numbers, suggest links to your other posts, and avoid writing about something you've already covered.

What gets imported

Posts

Every published post on your site, in batches, newest first. For each post Blog AI keeps:

• the title, text, web address and publish and update dates
• categories and tags
• the featured image
• the excerpt
• the SEO title, meta description and canonical address, where your site exposes them (Yoast SEO or Rank Math on WordPress need the Blog AI Connector plugin for this; Strapi's seoTitle and seoDescription fields are read directly)

Drafts, private posts and trashed posts aren't imported.

Imported posts show on the Posts page labelled Imported, alongside posts Written by AI and Written by hand.

Pages

Your site's published pages, such as services, pricing and about, are imported separately and read-only. They never appear in your Posts list, and Blog AI never writes them back to your site. They're there for one reason: the content audit can check them too. For example, it can tell you "your services page is shown in Google for vat registration threshold but never mentions it".

• WordPress: pages import automatically. With the connector plugin, their Google title and description are read too; without it, the audit doesn't comment on missing descriptions, because it can't see them.
• Strapi: there's no standard pages collection, so pages import only if you name yours. In Settings, open Sites & writing style, click Fix connection and enter the collection's API name (for example pages) under Pages collection (optional). Without it, the import says pages weren't imported and why, and posts import as normal.

Watching the import

The site's card on Sites shows progress: "Checking your posts and pages…", then "Importing posts…" and "Importing pages…", and finally a line such as "40 of 40 posts imported · 12 pages imported".

A large blog imports in batches. If you close the page part-way, the card shows how far it got and offers Import the rest, which carries on from there. Show import history lists each run with how many rows were added and how many posts were matched to Google data.

Importing again

Use Import posts and pages on the site's card whenever you've published or edited posts directly on your site and want Blog AI to see the changes. Running it again:

• adds posts and pages that are new since last time
• refreshes Blog AI's copy of imported posts and pages that changed
• never overwrites posts Blog AI published. For those, Blog AI's own copy is the one it keeps, so a later import can't quietly replace your edits in the editor
• never deletes anything, in Blog AI or on your site

How imported posts are used

• Your voice. Blog AI learns how you write from up to 20 of your published posts. It needs at least 3 posts of 250 words or more. See Set your writing voice.
• The content audit gives each imported post findings and one recommended action.
• Google matching. Each post is matched to Search Console and Analytics pages by its web address, so it gets its own chart and numbers.
• Internal links. When Blog AI writes a new post, it can link to your real posts, because it knows which exist and where.
• Refreshes and merges work on imported posts too, once they're live on your site.

Common problems

Some posts are missing

Only published posts are imported. If a post is published but missing, check its address loads publicly. On WordPress, a plugin that hides posts from the REST API can also stop them importing.

The import stopped with "Import failed"

The message gives the reason. Usually the connection needs fixing (see Fix a broken connection), or your site was slow to answer; try Import the rest again.

Strapi posts have the wrong web address

Blog AI builds each Strapi post's public address from the post address pattern you gave when adding the site. See Connect a Strapi site.

An imported post has no text

Some sites store post content in a format the REST API doesn't return (for example, page builders that keep layouts elsewhere). Blog AI imports what the API gives it. The audit then skips checks that need the text, rather than reporting something false.