> For the complete documentation index, see [llms.txt](https://tmniche-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://tmniche-docs.keywordrush.com/content-egg-integration/overview.md).

# Why TMN needs Content Egg

Too Much Niche requires the **Content Egg** plugin — installed, active, and up to date alongside it. It isn't optional: Content Egg renders the building blocks of every article and supplies the product data TMN works with.

## What Content Egg does for TMN

* **Renders the blocks.** Every article is assembled from **EggBlocks** — product cards, comparison tables, CTAs, pricing, and the rest. Content Egg turns those blocks into what readers see, and keeps their product and profile data **live at view time** (so prices, links, and contact details stay correct after publishing).
* **Supplies product data.** Its modules find and store products: **affiliate-network search** (Amazon, Walmart, eBay, …), the **Feed module** for your own catalog, and the **Offer module** that holds AI-synthesized products for non-affiliate models.

## Free or Pro?

The **free** version is enough for most models. **Affiliate** product search needs **Content Egg Pro**, and **e-commerce** uses the **Feed module** (included in both Free and Pro). See [Free vs Pro](/content-egg-integration/free-vs-pro.md) for the details.

## Set it up

1. **Install the latest Content Egg** alongside TMN — both install the same way; see [Requirements & installation](/getting-started/installation.md).
2. **Enable the modules for your model:**
   * **Affiliate** — turn on and configure the affiliate-network modules you'll use (Amazon, Walmart, eBay, …) in Content Egg's settings. These power automatic product search and need **Content Egg Pro** with an active Content Egg license. Configuring a module — for example, entering Amazon credentials — is done inside Content Egg; see the [Content Egg docs](https://ce-docs.keywordrush.com/).
   * **E-commerce** — set up the **Feed module** with your catalog; see [Set up product feeds](/content-egg-integration/product-feeds.md).
   * **Lead generation, SaaS, display** — nothing to configure; the free blocks are all you need.
   * **Featured images** — enable one or more **stock-photo modules** (**Pixabay**, **Pexels**, **Unsplash**) in Content Egg, then set *Featured image source → Stock photo* in your Generation Preset. TMN searches every active module, lets the AI pick the image that best fits each article, and avoids repeats across a plan. **Activating all three gives the best, most varied results.**
3. **Confirm TMN sees it.** Configured modules appear in the plan wizard as **Affiliate networks**, and on a plan as its **Product source**.

## Bundle

You can get Too Much Niche and Content Egg Pro together as a money-saving 2-in-1 bundle — see the [TMN + Content Egg bundle](https://www.keywordrush.com/bundles?cycle=year#tmn-ce-starter).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tmniche-docs.keywordrush.com/content-egg-integration/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.