> This page is for Product.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.feedonomics.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.feedonomics.com/_mcp/server.

# Where enriched fields go

> Which fields enrichment generates for storefront, SEO, AEO, and each marketplace or ad channel, how Feedonomics channel best practices are applied when they are generated, and how the feed build determines what ships.

FDX Enrichment's superpower is breadth: one run produces content for your storefront, your SEO, AI answer engines, *and* your channel feeds. This page maps what gets generated to where it can go.

## The field families

* **Brand copy** — short and long descriptions, feature bullets, care instructions. Destined for storefronts and anywhere shoppers read.
* **SEO and discovery** — meta descriptions, image alt tags, and discovery tags. (Deliberately *not* written into meta keywords — search engines have ignored those for years, so we don't waste your allotment on them.)
* **AEO** — AI descriptions and conversational Q\&A, structured so answer engines like ChatGPT and Perplexity can understand and cite your products.
* **Marketplace and ad channels** — channel-shaped copy for each destination, generated with Feedonomics channel best practices already applied.

For the field-by-field breakdown of what each of these contains and why — including a diagram of all four families and their destinations — see [Fields in an enrichment run](/product/enrichment/fields).

## Channel fields come with Feedonomics best practices built in

This is the part worth understanding, because it's what separates channel-shaped copy from copy that merely got copied into a channel field.

Feedonomics has spent years running feeds into these destinations, and the conventions that come out of that work — how each channel's requirements are structured, what its listing formats expect, the formatting that performs and the formatting that gets rejected — are **applied when the channel fields are generated**. You aren't getting a generic description dropped into a Google title slot. You're getting copy written against what that channel actually rewards.

In practice that means you spend less time writing per-channel transformer logic to reshape content after the fact, because the content arrives shaped.

#### Google

Titles and descriptions written to Shopping feed conventions — the attribute ordering and structure that Shopping surfaces favor.

#### Meta

Copy for Facebook and Instagram catalog surfaces, written in a social-native register rather than a search register.

#### TikTok

Short-form copy for TikTok Shop, built for a browse-and-discover surface rather than a keyword-search one.

#### Amazon

Titles, descriptions, and feature bullets following Amazon listing conventions, where format compliance directly affects visibility.

#### eBay

Listing copy written to eBay's structure and formatting expectations.

#### Walmart

Copy shaped to Walmart Marketplace listing requirements.

## You choose what gets generated

Your generation config determines which fields each run produces. Only paying for what you'll use is the point: if you're an ads-first team, generate the channel fields and skip the storefront copy — or vice versa.

## The feed build decides what actually ships

Generating a field and sending it to a channel are two different steps, and it's worth being precise about the second one.

**The exact fields that end up in a given feed are determined during the feed build process.** Enrichment produces the content and applies it as a raw data override; your feed build is what assembles each channel's output and decides which fields go into it. Enrichment doesn't publish anything on its own.

That separation is what gives you control:

* **Roll out per channel.** Enrich once, then bring channels online one at a time — A/B test enriched titles on Google before your Meta feed changes at all.
* **Roll out per field.** Take enriched titles now and hold descriptions until you've seen the numbers.
* **Keep your existing logic.** Transformers and transformed data overrides still run over enriched content during the build, so anything you've already built continues to apply.

See [Enrichment, transformers, and exports](/product/enrichment/transformers-and-exports) for the pipeline order and [A/B testing](/product/enrichment/ab-testing) for the rollout playbook.