> For the complete documentation index, see [llms.txt](https://ae-docs.keywordrush.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ae-docs.keywordrush.com/keeping-products-fresh/autoblogging.md).

# Autoblogging

Autoblogging creates posts for you automatically. You point it at a shop's catalog page — ideally one that lists **new products**, like a "New arrivals" section — and Affiliate Egg checks it on a schedule and publishes a post for each new product (or batch of products) it finds. It's a hands-off way to publish fresh offers as they appear.

{% embed url="<https://www.youtube.com/watch?v=yi45evBGxjY>" %}

## Setting up a task

Go to **Affiliate Egg → Autoblog → Add Autoblog** and configure:

* **Url of catalog** — the shop catalog or category URL to watch. Choose one that updates with new goods (for example, a "new products" page).
* **Handle products** — how many products to process on each check.
* **Products in one post** — how many products to merge into a single post (use 1 for one product per post).
* **Post status** — publish immediately, or save as a **draft** to review first.
* **Author** — the WordPress user the posts are published under.
* **Category** — the category new posts go into.
* **Template for title** — the post-title pattern. You can use these tags: `%PRODUCT.TITLE%`, `%PRODUCT.PRICE%`, `%PRODUCT.OLD_PRICE%`, `%PRODUCT.CURRENCY%`, `%PRODUCT.MANUFACTURER%`.
* **Template for storefronts** — the output template the products use inside the post.
* **Duplicate check** — how Affiliate Egg avoids posting the same product twice: **By URL** (default), or **Determined by parser** for catalogs that change a product's URL over time.
* **Task status** — **Works** (running) or **Stopped** (paused).

## How it runs

Tasks run on **WordPress Cron** — the same schedule that powers [price updates](/keeping-products-fresh/priceupdate.md) — so they depend on your site getting traffic (or a real server cron). Each run makes a request to the shop, so the usual [blocking](/getting-data-reliably/blocking.md) notes apply: point tasks at catalogs that don't mind being read, and don't run too many too aggressively.