Blog Content Settings
Explain every option in the Blog Content settings: image behavior, per-prompt article limits, and automatic product link insertion.
Blog Content (Settings → Project Configuration → Blog Content) controls how AI-written blog posts handle images, when a tracked prompt stops generating new articles, and whether published posts get product links inserted automatically. Changing these settings only affects content generated afterward — existing posts aren't touched retroactively.
Images
Include images in generated blogs — when off, new posts are written with no imagery at all: no inline images, featured image, or thumbnail. Turn this off for a pure-text writing style, or if you'd rather add images by hand after generation.
Use reference page images — nested under the option above, and only takes effect while it's on. When enabled, the AI may also pull images from the reference page it used for that article, in addition to your Image Library and Blog Design's default article image. Turn it off to keep every image sourced from your own library.
Content limits
| Field | What it does |
|---|---|
| Min paragraphs between images | The minimum number of paragraphs the AI must leave between two images in a generated post, so images don't cluster together. |
| Max articles per prompt | Once a tracked prompt already has this many articles (1–10), Auto-Generation and Generate Now stop writing new ones for it — raise the limit here if you want more generated automatically. |
Auto-insert product links
When on, every blog post is analyzed right after it's published and relevant product cards are automatically inserted into the body at fitting positions, linking out to your catalog. Off by default.
Product cards are built from your Product & Service Categories in Brand Kit — add services there first, or this has nothing to insert.
Every control here saves the moment you change it — unlike Project Information and AI Engine above on the same page, there's no separate Save button to click.
Changing these settings only affects posts generated afterward; it won't touch content that's already been written or published.