Funnel content for e-commerce stores

In an online store, the bottom of the funnel is already built: it is the product page, with category pages close behind. Funnel content for e-commerce exists to help shoppers choose and then route them to the right product or category. A buying guide, a comparison or a fit guide earns its place when it answers a question your product and category pages can't, and hands the shopper to them.

TOFU (top of funnel) content explains terms, features and problems shoppers don't understand yet. MOFU (middle of funnel) content compares product types and helps them choose. BOFU (bottom of funnel) is the product page and the category page, where accurate price, availability, shipping and returns matter most. Around all three sit rules that are easy to break: Google's documentation on product structured data and the FTC's rule on fake reviews.

This playbook covers shopper questions by stage, how guides and category pages divide the work, product markup as Google documents it, review rules, and measurement. It goes deeper than the e-commerce section of how the content funnel differs by business type.

Shopper questions at each stage

The table uses a hypothetical store that sells hiking backpacks.

Pull your own list from site search terms, customer service tickets, product questions and the reasons in your returns data. Returns are a good signal: if many returns say "too small," a sizing guide may help shoppers more than another TOFU post.

Guides vs category pages: who does what

One planning mistake to avoid is a guide that duplicates a category page. A post titled "best hiking backpacks" that lists the same products as the hiking backpacks category gives a search engine two pages answering one question, and can give the shopper a page that is less useful than the category itself.

Give each page a separate job:

Before writing any guide, check its category and product pages. If the category page already answers the question, improve that page (a short intro, better filters, a size chart) instead of publishing a competing post. eSEOspace found this on one custom awards company's plan: a planned comparison post would have competed with a product page that already had a comparison table and five FAQs. The plan went stale against its own money pages a second time later, which is why plans are rechecked before each batch. The method is in how to map every article to a money page without cannibalization.

What each stage needs

TOFU: only where questions are real

Write explainers when shoppers genuinely don't know the terms or the problem. A store selling technical gear may need several. A store selling simple products may do better improving product and category pages first. Every explainer should end with a next step: the fit guide, the comparison or the category.

MOFU: buying guides, comparisons and fit guides

This is the stage where a store's guides have the clearest job. A good buying guide is written from real product knowledge: what your team measures, tests or hears from customers. Comparisons should say who each option suits, including when a cheaper or different type is the better choice. Fair structure is covered in comparison and "vs" pages done right.

If a "best" list ranks products you sell, base the order on stated criteria. In an example in the FTC's Endorsement Guides, rankings that payments from manufacturers determine are deceptive, and a disclosure of those payments doesn't fix it. This is not legal advice.

BOFU: the product page

Product pages carry the decision. Shoppers need price, availability, sizes or variants, materials, shipping cost and timing, and the return policy, all accurate. Shipping promises matter: the FTC's Mail, Internet, or Telephone Order Merchandise Rule (16 CFR Part 435) requires a reasonable basis to expect you can ship within the time you state, or within 30 days if you state none. AI-generated product copy needs care too: Google notes that under Merchant Center policy, AI-generated product data such as title and description attributes "must be specified separately and labeled as AI-generated." Product page writing is covered in how to write AI-friendly product pages.

Product structured data, as Google documents it

Google documents two classes of product markup, and the difference matters for planning:

• Merchant listings are for "pages where customers can purchase products from you." Google's merchant listing documentation says "Only pages where a shopper can purchase a product are eligible." Required properties include the product's name and image, and an Offer with a price and currency. The merchant must be the seller.
• Product snippets are "For product pages where people can't directly purchase the product." They need a name plus "either review or aggregateRating or offers." Google says only editorial product review pages are eligible for pros and cons, "not merchant product pages or customer product reviews."

Rules that affect funnel planning:

• One product per page. Product rich results "only support pages that focus on a single product (or multiple variants of the same product)." Google recommends "adding markup to product pages instead of pages that list products or a category of products." Buying guides and category pages are not where product markup belongs.
• Variants. Use ProductGroup "with associated properties variesBy, hasVariant, and productGroupID" for sizes and colors.
• Dated prices. "Your listing may not display if the priceValidUntil property indicates a past date."
• Shipping and returns. Google documents ShippingService and MerchantReturnPolicy under Organization for store-wide policies. When policies are defined in several places, product-level Merchant Center feeds are the strongest source and Organization-level markup the weakest.
• Match the page. Google's general rule: "Your structured data must be a true representation of the page content."
• No guarantee. Google says it "does not guarantee that features that consume structured data will show up in search results."

For AI features, Google says "Structured data isn't required for generative AI search," while calling it "a good idea" for rich result eligibility. Separately, Google says Merchant Center feeds "can help your products and services to be visible in both AI responses and other Google Search results." More on that side is in GEO for e-commerce stores.

Reviews: what the FTC rule and Google's rules say

Reviews sit on BOFU pages and often appear in markup, so both sets of rules apply. The FTC's Rule on the Use of Consumer Reviews and Testimonials went into effect on October 21, 2024. It is a binding rule, and the FTC says it "authorizes courts to impose civil penalties for knowing violations." In summary, it covers:

The rule does not ban all incentivized reviews, only incentives tied to a particular sentiment, and it carves generalized requests asking buyers to post reviews out of some of its provisions. Google's review snippet rules add their own requirements for marked-up reviews: ratings "must be sourced directly from users," "Don't aggregate reviews or ratings from other websites," and, since July 24, 2026, "Don't include fake or undisclosed incentivized reviews on your page or in your structured data markup." This section is not legal advice. Ask an attorney about your review program.

Hub and article structure for a store

One workable structure for a store guide is one hub per major category, with articles in reading order:

1. Learn: terms, features and common problems, each linking to the matching guide.
2. Compare: buying guides, type comparisons, fit and sizing guides, each linking to the category with the right filter applied and to a few specific products.
3. Decide: the category page and product pages, plus shipping, returns and warranty pages that answer last-minute doubts.

Link back up as well: product pages can link to the fit guide for shoppers who aren't sure of their size. Keep the number of guides tied to real questions. Google's scaled content abuse policy covers "Using generative AI tools or other similar tools to generate many pages without adding value for users," and a guide for every product variation adds pages without adding help.

Measuring a store's funnel content

• Purchases. GA4 marks purchase as a default key event. With Ads Personalization and a linked Google Ads account, it also marks events such as add_to_cart, begin_checkout and view_item as key events.
• Content groups by stage. Tag guides as Learn or Compare with GA4 content groups. Using them for funnel stage is your own convention, not a Google feature.
• Paths to purchase. GA4 path exploration supports backwards pathing from an event such as a purchase, so you can see which pages shoppers viewed before buying.
• Landing pages. The Landing page report shows the first page of each session, which tells you which guides start shopping visits.
• Search Console. Filter pages by URL folder to compare guides with category and product pages.

Guides may assist more often than they close. A shopper who reads a fit guide may buy days later through a branded search. The full approach is in how to measure a funnel content guide.

Conclusion

For an online store, funnel content is a set of guides that help shoppers choose and then step aside for the product and category pages. Give guides and category pages separate jobs, base "best" lists on honest criteria, keep product markup on single-product pages that match Google's documentation, and run your review program within the FTC rule and Google's review guidelines. A funnel is a planning tool; anyone promising a fixed number of sales from a number of articles is selling something they can't deliver. The full method is in our guide to TOFU, MOFU and BOFU content strategy, and our content marketing services start from customer-journey topic mapping for your catalog. More guides are in our GEO and AEO Guide.

Frequently asked questions