> For the complete documentation index, see [llms.txt](https://ce-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://ce-docs.keywordrush.com/ai-agents/prompts-and-workflows.md).

# Example prompts & workflows

Copy-paste prompts and full walkthroughs for the things people actually ask their assistant to do in Content Egg.

This is the page to bookmark. Below are ready-to-use prompts — copy one, tweak the details, and send it to your connected assistant.

First, one concept that makes everything else click:

{% hint style="info" %}
**Two ways to show products.** When you ask your assistant to *write an article* (a review or a roundup), it builds the page from **Egg Blocks** — it writes the words, and only the prices and links stay live. When you just want to *drop in a live product list* on a page you're writing yourself, it uses the **Products block** instead.

**Rule of thumb:** if the words on the page should change when the product data changes, that's the **Products block**. If they're your editorial words — a verdict, pros and cons, an intro — that's **Egg Blocks**. You don't have to say which one; a good assistant picks the right one. But it helps to know why your review keeps your writing while a price list updates itself.
{% endhint %}

***

## Part A — Quick prompts

Grouped by what you want to do. Each one is ready to paste; change the product names, post titles, and networks to match your site.

### Research & plan (before you build)

Your assistant knows the market, and if it can browse the web it can check what's current. Use that *before* you search products or build anything.

> Before we build anything: research the robot vacuum market for 2026 and suggest the 5 best models to feature in a buying guide, with a one-line reason for each. Don't touch the plugin yet.

*What to expect:* a shortlist of specific models and angles — no plugin actions yet. You review it, adjust the picks, and only then ask it to find those exact products and build the page.

### Check my setup

> Which Content Egg modules are active, and is my license OK?

*What to expect:* a short summary of your plugin status and a list of your active modules.

### Find products

> Search Amazon for robot vacuums and show me the top 5 with prices.

*What to expect:* a list of matching products with prices and merchants — nothing is added to any post yet.

### Add products to a post

> Find the 3 best-rated cordless drills on Amazon and add them to my post "Best Cordless Drills" as a comparison.

*What to expect:* the assistant searches, attaches the products to that post, and arranges them as a comparison.

### Edit a product

> On my "Best Drills" post, change the DeWalt's title to "DeWalt 20V MAX" and set its price to 129.

*What to expect:* just that one product is updated on that post.

### Refresh prices

> Refresh the prices on my "Best Drills" post.

*What to expect:* the assistant re-pulls current prices and availability for the products on the post.

### Reorder

> On that post, put the Makita first and the Bosch last.

### Remove

> Remove the discontinued Ryobi from that post.

*What to expect:* removing products changes the page, so a good assistant will confirm before doing it.

### Set up a feed

> Create a new product feed from <https://example.com/feed.csv> — it's a CSV in USD.

*What to expect:* the assistant creates the feed; importing runs in the background, so it may tell you to check back in a moment.

### Module settings

> Show my Amazon module settings.

> Set my Amazon associate tag to mysite-20.

*What to expect:* the first shows your settings (with any secret keys hidden); the second updates one setting.

{% hint style="warning" %}
Product searches use your affiliate networks' API quota. Ask for what you need — don't tell your assistant to search "on a loop" or "for every possible keyword," or you may hit your network's rate limits.
{% endhint %}

***

## Part B — Workflow recipes

Full, end-to-end examples. Each shows the prompt, what the assistant does, and what you get.

{% hint style="success" %}
**Do your homework first.** Content Egg's product search is great at *finding* a product once you know what you want — but it doesn't decide *which* products are worth featuring. That editorial judgment is where your assistant shines on its own. Before you search or build, ask it to research the market: current trends, the newest models, what buyers care about, a rough outline. Then feed those **specific model names** into the product search. Searching "Roborock S8 MaxV Ultra" returns a precise match; searching "robot vacuum" returns a grab-bag. A few minutes of research up front is the biggest quality difference between an average roundup and a great one.
{% endhint %}

### 1. Build a product roundup from scratch

The best results come in two phases — research first, then build.

**Phase 1 — Research and agree on the lineup (no plugin actions yet):**

> I want to write a buying guide, "Best Robot Vacuums 2026." Research the current market — newest models, standout features, what buyers care about — and suggest the 5 best robot vacuums to feature, each with a one-line reason. Don't touch the plugin yet; just give me the shortlist and a suggested outline.

Review the shortlist. Swap models, narrow it to three, adjust the angle — this is your editorial call, and it's far easier to do now than after the page is built.

**Phase 2 — Find those products and build the page:**

> Great — go with the Dreame X40, the Roborock S8 MaxV Ultra, and the iRobot Roomba j9+. Find each of those exact models on Amazon, then create a draft titled "Best Robot Vacuums 2026" with an intro, a comparison table, pros and cons for each, a FAQ, and a final verdict.

**What happens:** the assistant searches for the *specific* models you agreed on, attaches the best match for each, and assembles the page from Egg Blocks — intro, comparison table, pros and cons, FAQ, and verdict — saved as a **draft**.

**What you get:** a complete, well-curated draft to review and publish. Because you chose the lineup, it reflects real research instead of whatever a generic search happened to return.

<figure><img src="https://4254262503-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M3fnB7iKYwDc1Xhr3H3%2Fuploads%2Fgit-blob-090e40b0930aa0dbff215c757e8e28cd89bc1724%2Fagents-roundup-draft.webp?alt=media" alt=""><figcaption><p>A draft roundup built from Egg Blocks, ready to review in the editor</p></figcaption></figure>

{% hint style="info" %}
You can also do this in one prompt ("research the 3 best robot vacuums and build the guide"), but splitting it into two phases gives you a checkpoint to steer the lineup before anything is created.
{% endhint %}

### 2. Drop a live price list into a post you're writing

Sometimes you want to write the article yourself and just add a live product list.

> I'm writing this review myself. Near the bottom of post "My Air Fryer Review", add a live price-comparison list of the Ninja air fryer from Amazon.

**What happens:** the assistant adds a single **Products block** — a live price-comparison list — to that post, without touching your writing.

**Why this one stays live:** a price list is *product data*, not editorial writing, so it should always show the current prices and merchants. That's exactly what the Products block is for — it renders live from Content Egg every time the page loads.

### 3. Refresh an old review

> On my "Best Headphones" post, re-run the product searches to refresh the lineup and prices, then add a short FAQ at the end.

**What happens:** the assistant refreshes the products (updated prices and availability) and appends a short FAQ — your existing content stays exactly as it was; the FAQ is added at the end.

**What you get:** an up-to-date post with a little more helpful content, no manual re-checking of prices.

### 4. Set up a feed and build from it

> Create a feed from <https://example.com/products.csv> (CSV, USD), wait for it to finish importing, then make a draft roundup of the 5 cheapest coffee grinders from it.

**What happens:** the assistant creates the feed (which imports in the background), checks that the import has finished, searches within the feed for coffee grinders, and builds a draft roundup of the five cheapest.

**What you get:** a new product source *and* a draft article built from it, in one go.

### 5. Build a price-comparison page

A price-comparison page shows one product with its offers from several shops. The hard part is not the page — it is making sure every offer is really **the same product**: the same model, the same memory size, the same colour, new and not used. Your assistant does this check for you, and asks you when it is not sure.

> Build a price-comparison page for the Sony WH-1000XM5 headphones, black. Find the product in all my modules by EAN or model number, and attach only the offers that are exactly this product. Create a draft WooCommerce product with the price-comparison list, the price history and a price alert. Ask me about any offer you're not sure of.

If you already have the EAN or a product page URL, put it in the prompt. It is the most reliable way to start.

**What happens:**

1. **It checks your site setup.** It reads the settings that matter for a comparison page: the logo source, **Used and Refurbished Offers**, and — for a WooCommerce product — whether the product price will be updated from your offers (see [Product synchronization](https://ce-docs.keywordrush.com/woocommerce/product-synchronization.md)). If something would stop the prices from updating, it tells you. It changes a setting only after you confirm.
2. **It pins down the product.** It writes down what the page is about: the EAN, the brand, the model number and the variant (for example 256 GB, black). If the product exists in several variants, it asks which one you want. The EAN and the model number come from your module results, from a web page it can name, or from you — not from memory. It saves this on the page as the **product passport**, so a later chat (or another assistant) knows exactly which product the page compares.
3. **It finds the product in your modules.** It knows what each of your modules can do: search by EAN, search by URL, return many shops in one search, or read a feed on your site. It searches in a sensible order — your feeds first (they are free and exact), then the modules that search by EAN, then the price-comparison modules, then the other modules by the exact model name. For a shop connected with Affiliate Egg it uses the product page URL when it can browse the web.
4. **It checks every offer.** Content Egg first runs the checks that need no judgment: is the EAN the same, do the brand and the model number match, do the memory size, volume, weight and pack size match, is the offer new, is the price close to the usual price. Then the assistant decides for each offer: add, skip, or ask you. It compares the offer with the product, not with the other offers. A different memory size or other variant, a pack of two, a clear accessory ("case for…") or a used item is skipped. A bundle, or any case it cannot decide, is put to you. A price far below the others is a reason to ask. An offer in another currency is not skipped: prices are compared after conversion, and the assistant adds the `currency` parameter to the price list so visitors see one currency.
5. **It shows you a table.** Image, title, shop, price, its verdict and the reason.
6. **It creates a draft.** A WooCommerce product with only the accepted offers, a price-comparison list, the price history and the price alert. It sets the product type to **External/Affiliate** (the **Buy** button then goes to the shop of the synchronized offer), puts it in the product categories you name (they must already exist), and sets the product's GTIN from the product passport.
7. **It records its decisions.** Each accepted offer is marked as checked. Each skipped offer is remembered on the page, so it is not added again later.
8. **It checks the result.** The draft must show exactly the accepted offers, and on a WooCommerce product the price must be the cheapest new offer.

**Where you confirm:**

* **Unclear matches.** The offers marked "ask" in the table wait for your answer. Nothing doubtful is added silently.
* **Settings changes.** Only after you say yes.
* **Publishing.** The page stays a draft until you tell the assistant to publish it.

**What you get:** a draft comparison page that contains only offers you can trust. For modules that support price updates, prices stay current through the normal price updates of Content Egg. In the **Product Manager**, each offer the assistant matched to the page's product shows a small green dot. An offer you add later, or one whose title or EAN has changed since the check, shows no dot until the next [recheck](#id-6.-recheck-your-comparison-pages).

{% hint style="info" %}
**Good to know.** On a page with a product passport, Content Egg no longer replaces the offers by a keyword search: **Update listings** is paused for the product modules, so the checked offers stay as they are. Prices still update, and coupon lists still refresh. Offers change only when the assistant adds or removes them, or when you do. If you add an offer yourself in the Product Manager, it stays on the page, even one the assistant skipped before.

For this task the assistant reads the **price-comparison** part of the agent guide. If your assistant can't open it by itself, add `?topic=price-comparison` to your agent guide link and paste that page into its instructions.
{% endhint %}

{% hint style="warning" %}
Offers that are used or refurbished are skipped unless you ask for them. If you want them on the page, ask for them in their own labeled group below the new offers. On a page with a product passport they never set the best price, the WooCommerce price, the price history or the price alerts. More about this: [Price comparison websites](https://ce-docs.keywordrush.com/pages/TA9j9L3eXbz725td1kvb#id-2.-keep-used-and-refurbished-offers-out-of-the-best-price).
{% endhint %}

### 6. Recheck your comparison pages

Shops add the product, offers sell out, and a shop sometimes changes what an offer is. A recheck finds what changed since the pages were built.

> Check my price-comparison pages. Tell me which offers changed, went out of stock or were never checked, and look for new shops. Ask me before you remove anything.

**What happens:**

1. **It reviews your pages.** The assistant reads what is stored on each page with a product passport. This step runs no product search, so it uses no API quota. For each page it reports:
   * offers nobody has checked yet, for example ones you added by hand (no green dot in the Product Manager);
   * checked offers whose title or EAN has changed since;
   * offers that are out of stock, used or refurbished, or priced far from the other offers;
   * modules that can search by EAN and have not been searched for this product in the last 30 days;
   * pages you named that have no product passport yet.
2. **It checks the doubtful offers** with the same rules it used to build the page, and asks you about the ones it cannot decide.
3. **It looks for new shops**, only in the modules that are due, by the product's EAN. An offer it skipped before is not proposed again.
4. **It adds the new matches** and records its decisions, as in [recipe 5](#id-5.-build-a-price-comparison-page).

**Where you confirm:**

* **Removing an offer.** The assistant asks before it takes an offer off a page. An offer it removes is remembered as skipped, so it does not come back.
* **Unclear matches.** As in recipe 5, the offers it is not sure of wait for your answer.
* **Pages without a product passport.** It builds one from the page's offers and title, and asks you when they disagree.

**What you get:** a short report per page, new shops on the pages where they were found, and no offer removed without your answer.

{% hint style="info" %}
The recheck finds only pages that already have a product passport. Comparison pages built before (by hand, or by an assistant before Content Egg stored passports) are not listed: name them in the prompt — for example "also check my posts with Geizhalsde offers" — and the assistant looks them up and builds their passports first. To recheck only some pages, name them too.

Building a passport pauses **Update listings** for that page's product offers, as on every page with a passport (see [recipe 5](#id-5.-build-a-price-comparison-page)). If an older page relied on keyword updates to refresh its offers, they no longer change by themselves: a recheck looks for new shops instead. Prices still update.

Out-of-stock offers stay on the page; the price updates keep checking them.
{% endhint %}

### 7. Post fresh deals

A [deals site](https://ce-docs.keywordrush.com/set-up-products/deals-websites.md) lives on freshness. Your assistant can look for deals on the web, check each one against your own modules, and post it as a deal page with a short write-up — on request or on a schedule.

> Find 5 new deals on headphones and smart-home devices at Amazon. Look on deal sites like Slickdeals and on Amazon's own deal pages. Only real price drops: at least 25% below the price the product usually sells at, not just below a list price. Check that each one isn't already on my site, then create a draft deal in the right category with a short, honest write-up: what it is, who it's for, why the price is good, and one caveat.

The rules are yours: where to look, which stores, how big a discount, how many deals per run. Put them in the prompt.

**What happens:**

1. **It looks for candidates** where you told it to: deal communities, the stores' deal pages, news. The web is only where it finds ideas — it never takes a price from there.
2. **It looks each product up in your modules**, by product ID or link (for Amazon, the ASIN). The price, the old price, stock, the seller, the image and your affiliate link all come from the module. A product none of your modules has is skipped, unless you ask for a manual offer — whose price then doesn't update on its own.
3. **It checks the discount.** For Amazon it sees whether the old price is a recent "was" price or only a list price, whether the deal is for Prime members only, and when Amazon's deal ends.
4. **It checks for duplicates.** It asks Content Egg whether that product already has a deal. Content Egg also refuses a second active deal for the same offer by itself.
5. **It creates a draft deal** with the product, the category, a coupon code if there is one, and its write-up. The deal ends when the store's deal ends: for Amazon, Content Egg takes the end time from Amazon.

**Where you confirm:**

* **Publishing.** The deals stay drafts until you tell your assistant to publish them.
* **Running it on a schedule.** Once you trust the results, put the same prompt on a [scheduled task](https://ce-docs.keywordrush.com/ai-agents/connect-claude.md#run-it-on-a-schedule). A few runs a day is plenty: every run spends your affiliate networks' API quota.

**What you get:** draft deal pages with live prices that Content Egg keeps updating, each one expiring by itself when the deal is over.

{% hint style="info" %}
For this task the assistant reads the **deals** part of the agent guide. If your assistant can't open it by itself, add `?topic=deals` to your agent guide link and paste that page into its instructions.
{% endhint %}

### 8. Keep your deals current

Content Egg keeps prices up to date and expires deals that sell out or go up in price. An assistant can handle the rest.

> Go through my active deals. Tell me which ones end in the next 24 hours, close the ones you can confirm are over, and give every deal without a category one.

**What happens:** the assistant lists your deals by status, end date or category, and changes the ones you asked about: it closes or reopens a deal, sets its end date, category or coupon code, or switches it to another of its offers. A deal's price always follows its product, so the assistant never sets a price.

**Where you confirm:** closing a deal you didn't name. An expired deal keeps its page, and **Mark active again** in the Deal panel brings it back.

***

{% hint style="info" %}
**Publishing is up to you.** By default your assistant creates **drafts** — it won't publish anything unless you ask it to, and even then it can only publish if the WordPress user you connected has permission to publish. Review the draft, then say "publish it" when you're ready.
{% endhint %}

Want to understand exactly what your assistant is and isn't allowed to do? See [**What your assistant can and can't do**](https://ce-docs.keywordrush.com/ai-agents/safety-and-permissions.md).
