PageForge 1.3: check every run before it writes, update generated pages, spintax and resumable batches. See what changed
Account Get it free

For WooCommerce stores and ecommerce teams

Ecommerce landing pages at scale, one for every shopper you sell to

Shoppers search by need: rain jackets for bike commuters, trail shoes for beginners. Put each pairing and its buying advice in a CSV row, add a WooCommerce product grid to one template, and PageForge builds every page.

  • Free on WordPress.org
  • Live product grid per row
  • Preview every URL first
The sample spreadsheet feeds one template and becomes one page per row.

Why category pages fall short

A category page lists every jacket. It does not tell a commuter which one.

Your category pages already cover the product names. The searches you miss name a person or a use, and they need advice that a sorted product grid cannot give.

Building landing pages by hand

  • Duplicate a landing page, rewrite the intro, change the shortcode’s category, fix the slug, then repeat
  • Most pairings never get a page because each one takes an afternoon
  • Meta descriptions are copied from the category page, so every snippet looks the same
  • Summer pages stay live into November because nobody remembers which ones they were

With PageForge

  • One row per pairing, carrying what to look for, what to avoid and a care tip
  • Title, URL and meta description built from patterns you write once
  • The product grid filters to each row’s category, with live prices and stock
  • Edit the seasonal rows, run an update, and only those pages change

The data

One row per page, every detail that changes

Category and Audience build the title and URL. LookFor, Avoid and CareTip fill the advice sections, and CategorySlug tells the WooCommerce product grid which category to show.

ecommerce-landing-pages.csv7 rows · 6 columnsDownload the CSV
CategoryAudienceCategorySlugLookForAvoidCareTip
2Trail Running ShoesBeginnerstrail-running-shoesA cushioned midsole and a rock plateAggressive lugs if you mostly run on gravel pathsRinse off mud and air dry away from heaters
3Rain JacketsBike Commutersrain-jacketsA hood that fits over a helmet and reflective trimLong hems that catch on the saddleWash with a technical wash to keep water beading
4Hiking BackpacksDay Hikeshiking-backpacks20 to 30 liters with a padded hip beltFrame packs built for multi-day loadsEmpty and air out after every trip
5Sleeping BagsSummer Campingsleeping-bagsA 40F comfort rating and a full-length zipMummy bags rated for winterStore loose in a large cotton sack
6Trekking PolesKnee Supporttrekking-polesCork grips and quick flick-locksFixed-length poles if you share themDry each section before collapsing
7HeadlampsTrail RunnersheadlampsAt least 300 lumens and a rear red lightSeparate battery packs that bounceRemove batteries before long storage
8Water FiltersBackpackingwater-filtersA filter that screws onto standard bottlesRelying on tablets alone if you dislike the tasteBackflush after every trip

Placeholders

{Category} {Audience} {CategorySlug} {LookFor} {Avoid} {CareTip}

Patterns

Title{Category} for {Audience}

URL/{category}-for-{audience}/

Campaign size

12 categories × 6 audiences = 72 pages, keeping only the pairs you stock well

Pages this creates

  • Trail Running Shoes for Beginners
  • Rain Jackets for Bike Commuters
  • Hiking Backpacks for Day Hikes
  • Sleeping Bags for Summer Camping
  • Water Filters for Backpacking

How it works

From a merchandising sheet to live landing pages in four steps

01

List the pairings you stock well

One row per category and shopper. Leave out any pairing where you carry fewer suitable products than the grid has slots, or where you cannot say something the category page does not.

02

Build one landing template

Design the page in the block editor, Elementor, Divi or Avada. Put {LookFor}, {Avoid} and {CareTip} in the advice sections and add a Shortcode block with [products category=”{CategorySlug}” limit=”8″].

03

Check and preview

PageForge shows how many pages it will create, the first page’s title and URL, and any row whose URL repeats another. Nothing is written until you start the run.

04

Generate drafts, then update by season

Generate three rows as drafts and check that each grid shows the right products. When the season turns, edit those rows and run the same template in update mode.

Built for store campaigns

Everything a landing page needs, filled from your rows

The template carries your layout, sizing help and returns policy. The row carries the advice for that shopper. WooCommerce carries the products, prices and stock.

Live products on every page

PageForge fills the category in WooCommerce’s products shortcode from each row, so prices and stock come from your store each time the page loads.

Advice that changes per shopper

Every column is a placeholder. {LookFor} and {Avoid} make a beginner’s page different from a trail runner’s, even when both sell from the same range.

Duplicate URLs caught before writing

Check and preview builds each slug first. Two rows that clean up to the same URL are flagged, and the second is skipped with its row number.

Seasonal changes in one update run

Edit the rows, upload the file and choose update mode. Pages a merchandiser edited by hand are skipped unless you choose to overwrite them.

Pro

AI buying advice per row

Pro can ask your own AI provider to draft a section for each page from that row’s columns, for you to edit before publishing. Every Pro plan.

Pro

Featured image per row

Pro sets each page’s featured image and alt text from columns, such as your own photo of the product in use. Every Pro plan.

A page generated from the first row of the sample spreadsheet.

One generated page

What a beginner sees on Trail Running Shoes for Beginners

The page opens with the advice a first-time buyer needs: look for a cushioned midsole and a rock plate, and skip aggressive lugs if most of the running is on gravel paths. A grid of trail shoes with live prices follows, then care, sizing and returns. The shopper gets a short list and a reason to trust it, which is what earns the click through to a product.

  • Advice from LookFor and Avoid sits above the grid
  • The grid shows the trail-running-shoes category, live
  • Care, sizing and returns answer the last doubts
The same template works as a Gutenberg, Elementor, Divi or Avada layout.

Page builders

Use the builder your store theme already runs on

Design the landing page once in the block editor, Elementor, Divi or Avada, and choose it as the Base Layout to Clone. Placeholders inside builder widgets are filled from each row, and every generated page opens in your builder for later edits.

  • A Shortcode block or widget holds the product grid
  • Advice sections take placeholders like any text
  • New pages take the layout’s featured image
When the CSV changes, generated pages are updated in place while pages edited by hand are skipped.

Seasons change

Swap summer advice for winter advice without rebuilding pages

Edit the rows for the season, upload the new CSV and run with Update it from the CSV and current template. PageForge refreshes the pages it generated, keeps their URLs and status, and skips any page a merchandiser rewrote by hand.

  • Rows that did not change are reported as unchanged
  • URLs and publish status stay as they are
  • Hand-edited pages are skipped unless you overwrite

Compared

PageForge versus building store landing pages by hand

The shopper sees the same kind of page. The work behind thirty of them is not the same.

PageForgeBuilding pages by hand
Advice specific to each shopperFilled from your columnsWritten page by page
Live prices and stockWooCommerce shortcode, category from the rowShortcode set by hand on each page
Title, URL and meta descriptionBuilt from patternsTyped per page, often skipped
Duplicate URL check before writingYesNo
Changing seasonal advice on 20 pagesOne update run20 separate edits
Featured image per pageFrom a column on ProSet by hand
Rows per runUp to 100 in Free, no limit in ProOne at a time
Get PageForge free

Ecommerce landing pages at scale: what you are building

Ecommerce landing pages at scale are one page per shopper need, each built from a row of data and each showing a grid of live products that suit that need. “Rain jackets for bike commuters” is one page. “Trail running shoes for beginners” is another. Your category pages already cover the product names. These pages cover the searches that name a person, an activity or an occasion.

In PageForge the rows live in a CSV, the design lives in one WordPress template, and each row becomes a real WordPress Page with its own title, URL and meta description. The product grid comes from WooCommerce itself, so prices and stock are never copied into the page.

The sample on this page is a hypothetical outdoor store. Every number below is worked out from its seven rows.

The searches a category page misses

Shoppers who know the product search for it by name. Shoppers who do not know yet search by need:

  • “rain jacket for bike commuting”
  • “trail running shoes for beginners”
  • “sleeping bag for summer camping”
  • “headlamp for trail running”

A category page answers none of these well. It lists every rain jacket you sell, sorted by price or popularity, and leaves the commuter to work out which ones fit over a helmet. A landing page for that need does the sorting for them: what matters, what to skip, and the handful of products that pass.

That is the test for every row. If the page would not help a shopper choose faster than your category page does, it does not need to exist.

What goes in each row

The sample CSV has six columns. Each one has a job on the page.

ColumnWhere it appearsRow 1 value
CategoryTitle, heading, URLTrail Running Shoes
AudienceTitle, heading, URLBeginners
CategorySlugThe product grid’s category filtertrail-running-shoes
LookFor“What to look for” sectionA cushioned midsole and a rock plate
Avoid“What to skip” sectionAggressive lugs if you mostly run on gravel paths
CareTipCare and storage sectionRinse off mud and air dry away from heaters

Prices, stock counts and product names stay out of the file. They change too often, and WooCommerce already knows them.

Columns worth adding once the pilot works:

  • Intro: two sentences written for that shopper, in the voice your best floor staff would use.
  • SizingNote: fit advice that differs by audience, such as how a shoe should fit for long descents.
  • ProductIDs: a hand-picked list of products for the grid, when the category alone is too broad.
  • Season: so you can find seasonal rows quickly before an update run.

Worked example: seven landing pages from the sample CSV

The sample has seven rows, seven categories and seven audiences, with no category repeated. With the Title Pattern {Category} for {Audience} and the Slug Pattern {category}-for-{audience}, PageForge produces seven Pages:

RowPage titleURL
1Trail Running Shoes for Beginners/trail-running-shoes-for-beginners/
2Rain Jackets for Bike Commuters/rain-jackets-for-bike-commuters/
3Hiking Backpacks for Day Hikes/hiking-backpacks-for-day-hikes/
4Sleeping Bags for Summer Camping/sleeping-bags-for-summer-camping/
5Trekking Poles for Knee Support/trekking-poles-for-knee-support/
6Headlamps for Trail Runners/headlamps-for-trail-runners/
7Water Filters for Backpacking/water-filters-for-backpacking/

Check and preview would report Ready: 7 new, 0 to update, 0 skipped. with “Trail Running Shoes for Beginners” at /trail-running-shoes-for-beginners/ as the first page.

The meta description test

Try the Meta Description Pattern {Category} for {Audience}. What to look for: {LookFor}. What to skip: {Avoid}. The seven results run from 136 characters (Trekking Poles) to 157 (Water Filters). Row 7 lands at 157 and row 1 at exactly 155, so both risk being cut short in search results. Shorten those two Avoid cells, or drop the Avoid clause from the pattern and keep it on the page.

Every LookFor value also starts with a capital letter. After a label and a colon that reads fine. Inside a sentence such as look for {LookFor} it produces “look for A cushioned midsole”, which looks careless in a snippet. Write the pattern around the data as it sits in the cell.

The product grid

Each page’s grid uses the row’s CategorySlug: [products category="{CategorySlug}" limit="8"]. In the sample every category appears once, so that filter is enough.

The front-matter math is 12 categories × 6 audiences = 72 pages. In that full grid each category appears on up to six pages, and a category filter would show the same eight products on all six. Hiking backpacks for day hikes and hiking backpacks for thru-hikes should not share a grid. Add a ProductIDs column for those rows and use [products ids="{ProductIDs}"]. Wrap the IDs in quotes in the CSV, such as "412,418,431,440", because they contain commas.

Rows that need more work

  • Row 5, Trekking Poles for Knee Support, names a body part. Keep the page to product facts, such as adjustable length and grip material, and do not promise relief or recovery.
  • Row 4, Sleeping Bags for Summer Camping, is seasonal. Decide now what the page says in winter, or when you will unpublish it.
  • Rows 1 and 7 need shorter Avoid text for the meta description, as above.
  • All seven rows lack sizing, delivery and returns information. That is store-wide, so it belongs in the template, not the CSV.

What the SEO plugin receives

The sample has no Service or City columns, so the SEO title is the page title, “Trail Running Shoes for Beginners”, and the focus keyphrase falls back to that SEO title. Set Business Type (Schema) to Store and each page gets a Store item and a WebPage item in one JSON-LD block. No Service item is added, and no Product item either, because these are Pages, not products. More on schema markup.

What to put on every page

Each line should hold on all seven pages, not only the first one you check.

  • A heading that names the product and the shopper, from the Title Pattern.
  • Two to four sentences on what matters for this shopper, from LookFor and an Intro column.
  • What to skip and why, from Avoid.
  • A product grid of at least four suitable products, with live prices and stock.
  • Care or storage advice, from CareTip.
  • Sizing and fit help, written once in the template or taken from a SizingNote column.
  • Delivery, returns and exchange terms, written once in the template.
  • A link back to the full category, and to one or two related landing pages.
  • A meta description under about 155 characters that names the shopper.

Ecommerce landing pages at scale, without thin pages

Google’s spam policies describe two patterns that matter here: pages made in bulk that add little value, and pages built to rank for close variations of a search that all lead to the same place. Read them once before you plan the full grid.

For a store, that comes down to three rules:

  1. Different advice per row. Two audiences in the same category must get different LookFor and Avoid text. If they would not, keep one page.
  2. A grid worth showing. If you carry two products that suit a shopper, you do not have a landing page yet. Set a floor, such as four suitable products, and drop rows below it.
  3. One page per intent. “Rain jackets for cycling” and “rain jackets for bike commuters” are the same search. Pick one.

Google’s ecommerce guidance covers site structure and product data in more depth. For patterns from other industries, see programmatic SEO examples.

Building the product grid

PageForge fills placeholders in your template content, so a shortcode inside the template becomes a different shortcode on each page. In the block editor, add a Shortcode block:

[products category="{CategorySlug}" limit="8" columns="4"]

On the Trail Running Shoes page that becomes [products category="trail-running-shoes" limit="8" columns="4"], and WooCommerce renders the current products when the page loads.

A few practical notes:

  • Check every CategorySlug against Products > Categories before you run. A typo gives an empty grid, not an error.
  • The shortcode takes a category slug, which is why the sample carries a CategorySlug column. Use the Shortcode block or widget rather than a product block you configure by clicking.
  • Pages at the root, such as /rain-jackets-for-bike-commuters/, sit alongside your product and category URLs without changing them.
Before a run, PageForge shows how many pages it will create, update or skip, previews the first page, and flags placeholders that have no matching column.

Linking the pages into your store

PageForge Free adds no automatic links between generated pages, so plan the links yourself:

  • From each landing page to its category. Write a link into the template built from the slug, for example /product-category/{CategorySlug}/ if your store keeps WooCommerce’s default category base.
  • From each category to its landing pages. Add a short “Shop by need” line to each category description in WooCommerce. It takes a few minutes per category and puts the landing pages where shoppers already browse.
  • A hub. Create a “Shop by activity” page and add the PageForge Sitemap block, or [pageforge_sitemap post_type="page" group_by="none" style="compact"]. Group headings in Free come from City, State or Service columns, and this CSV has none, so use group_by="none". The list includes every published Page PageForge generated, so other campaigns you run as Pages appear there too.

More patterns are on the internal linking page.

Seasonal pages and updates

Outdoor, fashion and gift stores run on seasons. The summer sleeping bag page that worked in June needs different advice, or a rest, by October.

When the advice changes, edit those rows, upload the new CSV on PageForge > Data Sources and run the same template with Update it from the CSV and current template. PageForge refreshes the title, content and meta description of the pages it generated, keeps their URLs, status and publish date, and reports untouched rows as unchanged. A page your merchandiser rewrote by hand is skipped unless you tick the overwrite option. See Update pages you already generated.

Changing a Category or Audience value changes the URL, so PageForge treats that row as a new page and leaves the old one in place. Redirect the old URL yourself.

To retire a seasonal page, switch it to draft in Pages, or set noindex in your SEO plugin until next season. Update runs never remove pages.

Common mistakes

  • Prices in the CSV. The first sale makes every page wrong.
  • One grid on six pages. A category filter shared by several audiences shows identical products. Use ProductIDs.
  • Advice that only swaps the audience name. “Great for beginners” and “great for experts” make the same page.
  • Health or performance promises. “Poles that fix knee pain” is a claim no product page should make.
  • Capitals in the wrong place. Write sentences that read well with each value exactly as it sits in the cell.
  • Two URLs for one search. Read your pairing list for near-synonyms before you run.
  • No way back to the category. Every landing page should link to the full range.

How to run it in PageForge

  1. Upload the data. Open PageForge > Data Sources, choose the CSV under CSV Upload and click Upload CSV. See Prepare your CSV.
  2. Design the layout. Build a draft Page in the block editor, Elementor, Divi or Avada with the advice sections, the Shortcode block and a placeholder for every column.
  3. Create the template. In PageForge > Templates, click Add New Template. In PageForge Template Settings, set Target Post Type to Page, the Title Pattern to {Category} for {Audience}, the Slug Pattern to {category}-for-{audience} and your Meta Description Pattern. Choose the draft as Base Layout to Clone.
  4. Set schema. In PageForge > Settings, set Business Type (Schema) to Store. Target Country (Schema) only feeds the Service item, which these pages do not get.
  5. Check. On the Generate screen, choose the template and the CSV, set Post Status to Draft and click Check and preview. See Check and preview a run.
  6. Generate and review. Click Generate 7 pages now, then open each draft and confirm its grid shows the right products.

Free or Pro for store landing pages

The free plugin covers this whole workflow: CSV upload, the template, Check and preview, update mode, schema, SEO plugin fields and the Sitemap block, up to 100 rows per run. The sample’s full 72-pair grid fits in one run.

PageForge Pro adds what larger catalogs ask for:

You needPro featurePlan
More than 100 rows in a runNo per-run row limitEvery Pro plan
A lifestyle image per pageFeatured image and alt text from columnsEvery Pro plan
A first draft of buying advice per rowAI content per page, with your own AI keyEvery Pro plan
Better titles and descriptions on existing product pagesBulk AI metaEvery Pro plan
Pages going live a few a dayQueue and drip publishingEvery Pro plan
Merchandisers editing pairings in one sheetGoogle Sheets syncProfessional and Enterprise

AI-written advice needs the same review as anything else on a product page, because it can contain claims you cannot support. See the AI content generator and compare editions on Free vs Pro. If you also publish buying guides that compare brands, the affiliate and comparison use case covers that pattern.

Questions

Ecommerce landing page questions

Still unsure? Ask in the chat or read the docs.

Will these landing pages compete with my category pages?

Not if each one answers a narrower need than the category does. The category page covers the product name, such as rain jackets. The landing page covers a person or a use, such as rain jackets for bike commuters, and links back to the category. Skip any pairing whose search is really the category itself, or two of your pages will chase the same query.

Does PageForge create or edit WooCommerce products?

No. PageForge builds Pages, Posts or its own content type around your products and never changes the products themselves. The products appear through WooCommerce’s own shortcode in your template, with the category filled from each row. Your product titles, prices, stock and product pages stay exactly as they are in WooCommerce.

How do prices and stock stay current on the landing pages?

Keep them out of the CSV. The products shortcode renders the grid each time the page loads, so a price change or a sold-out item shows on every landing page without an update run. A price typed into a row goes stale the first time you run a sale, and then the landing page and the product page disagree.

Will Google see 72 similar landing pages as thin content?

It can, if only the heading changes from page to page. Google’s spam policies cover pages made in bulk that add little value and pages built to catch close variations of a search. Publish a pairing only when its advice differs from its neighbors and its grid holds products that genuinely suit that shopper. Fewer, better pages are the safer start.

How many landing pages should I start with?

Start with five to ten pairings that already sell, generated as drafts. Read each one as a shopper would, check the grid, and publish them before you add the next group. The free plugin runs up to 100 rows per run, so the sample’s full 72-pair grid would fit, but a pilot tells you which pairings deserve advice before you write it for all 72.

Do the landing pages get Product schema?

No, and they should not. PageForge adds a basic Product item only on content types whose name includes product, such as WooCommerce products. Your landing pages are Pages, so they get your business item, using Store or the type you pick in Settings, and a WebPage item. Product structured data belongs on the product pages themselves.

Can each landing page have its own featured image?

Yes, on PageForge Pro. Every Pro plan reads a Featured Image column holding an image URL or a media library ID, with alt text from a Featured Image Alt column. Each image is downloaded once and reused on later runs. In the free plugin, new pages take the featured image of the base layout you clone.

Can AI write the buying advice for each page?

On PageForge Pro, yes. AI content per page sends each row’s columns to your own AI provider and places the returned section where you put {seo_content}. Each row is a paid request on your provider account, and the text can contain errors, so read every page before publishing. The free plugin builds pages from your template and data only.

Give every shopper a page that answers their need

Install the free plugin, upload the sample CSV and generate the seven outdoor pages as drafts. Check every grid, title and URL before anything goes live.

↑↓ to move↵ to open