Bridge Pages
Bridge Pages let you send visitors to a clean product-focused page on your own site, instead of linking them straight to the merchant.
Bridge funnel:
Your Resource/landing page (main article) → Bridge Page (dedicated product details) → Merchant website (amazon)
Why it’s useful
More pageviews & session depth: clicks first land on your Bridge Page, increasing pageviews and session depth.
SEO opportunities: each Bridge Page can rank for long-tail queries (e.g. specs, reviews, FAQs), not just the parent article.
Better monetization: use Bridge Pages to display multiple merchants, show price history, coupons, or alternatives.
Examples of Bridge Pages
A detailed product entry in your WooCommerce catalog
A standalone product review
A price comparison page
What you can do with Bridge Pages
Import Bridge Pages for many products in one click from the post editor.
Choose where links go: merchant (affiliate) or your Bridge Page.
Make a product canonical so the same item across your site points to one central Bridge Page.
Creating Bridge Pages (from the Post Editor)
Open a post in wp-admin and scroll to the Content Egg metabox.
Search/add products as usual (select some, or leave unselected to import all).
Click the Import as Bridge Page dropdown and choose a preset.
You’ll see a small toast message confirming how many items were queued.
Bridge Pages aren’t created immediately—they’re added to the import queue. To monitor progress, go to Content Egg → Import Tools → Queue.
After importing, refresh the post edit page. You’ll see a small link icon next to products that now have a Bridge Page, along with a quick link to edit that page.
Canonical Bridge Pages (Preset option)
In Content Egg → Import Tools → Presets, each preset can enable:
Make imported Bridge Pages canonical
ON: every product you import with this preset becomes the site-wide default destination for that product. Wherever that product appears, links will prefer this Bridge Page (unless you intentionally override it per post).
OFF: the mapping only applies in the post where you imported it.
Where should product links send visitors?
You control this in three layers:
Per-block override (Gutenberg)
Per-shortcode override (classic editor)
Global setting (default)
Global default
Settings → Frontend → Link destination preference
Prefer Merchant (affiliate) — send users to the retailer by default.
Prefer Bridge Page (on your site) — send users to your Bridge Page when one exists.
Block (Gutenberg) override
In the block sidebar (Display Options → Link Destination):
Auto (follow global setting)
Prefer Merchant (affiliate)
Prefer Bridge Page (on your site)
Shortcode override
Add link_target= to your shortcode:
affiliate | bridge | auto
Button text (optional)
Content Egg → Settings → Frontend
Product Button Text (affiliate): customize “Buy now”.
Bridge Button Text: customize “See details”.
Both support dynamic tags: %MERCHANT%, %DOMAIN%, %PRICE%, %STOCK_STATUS%.
Suggestions
Affiliate: Buy now, Buy at %MERCHANT%, Check price
Bridge: See details, View product page, Read review
Best practices
Use canonical for evergreen products you’ll reference in many posts (one trusted Bridge Page).
Use per-post mapping if a product needs a unique context in a specific article.
Pick one link strategy (merchant vs. bridge) for your site, then override per block only when needed.
Save the post before importing to ensure it records where the mapping was created.
FAQ
Do Bridge Pages work with WooCommerce?
Yes. You can import as Posts or Woo products; your preset controls the type.
Can I change where a product points later?
Yes. Importing a new Bridge Page for the same product will replace the previous mapping.
What happens if I delete a Bridge Page?
The plugin automatically cleans up its references, so other posts won’t link to a deleted page.
Last updated