# Bridge Pages

{% hint style="info" %}
**Recommended Reading.** For step-by-step instructions, best practices, and SEO tips, read the full guide: [How to Build Bridge Pages for Affiliate Marketing](https://www.keywordrush.com/blog/how-to-build-bridge-pages-for-affiliate-marketing/)
{% endhint %}

**Watch Bridge Pages in Action**

{% embed url="<https://www.youtube.com/watch?v=N4QbbYcBu_k>" %}

**Bridge funnel:**

Your Resource/landing page (main article) → Bridge Page (dedicated product details) → Merchant website (amazon)

<figure><img src="/files/hy0oe7O7gD66rV1y83eQ" alt="" width="375"><figcaption></figcaption></figure>

### Why it’s useful

* **More pageviews & session depth**: clicks first land on your Bridge Page, increasing pageviews and session depth.
* **Reduced “thin affiliate” signals**: Pages overloaded with outbound affiliate links can sometimes be flagged by Google as low-value. Moving most links into Bridge Pages distributes them more naturally.
* **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)

1. Open a post in wp-admin and scroll to the Content Egg metabox.
2. Search/add products as usual (select some, or leave unselected to import all).
3. Click the **Import as Bridge Page** dropdown and choose a preset.
4. You’ll see a small toast message confirming how many items were queued.

<figure><img src="/files/xlQBCnTTZeA4ofSxRfzL" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Bridge Pages aren’t created immediately—they’re added to the [import queue](/set-up-products/import-tools/import-queue.md). 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.
{% endhint %}

<figure><img src="/files/4MGNU86f2ZOm6deDmghT" alt=""><figcaption></figcaption></figure>

### Canonical Bridge Pages (Preset option)

In Content Egg → Import Tools → [Presets](/set-up-products/import-tools/import-presets.md), 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.

<figure><img src="/files/amX2lUdxuOOkIairU49Q" alt="" width="563"><figcaption></figcaption></figure>

### Where should product links send visitors?

{% hint style="info" %}
**Downside of Bridge Pages:** Some visitors just want to buy right away. Forcing them through a Bridge Page can sometimes lower conversions.

That’s why it’s often smart to keep your **top product blocks linked directly with affiliate URLs**, while using Bridge Pages for secondary products or deeper comparisons.
{% endhint %}

<figure><img src="/files/AuJWqrCsGdnPlp5vgaTz" alt="" width="375"><figcaption></figcaption></figure>

**You control this in three layers:**

1. Per-block override (Gutenberg)
2. Per-shortcode override (classic editor)
3. 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)

<figure><img src="/files/QGxT14u6464KrjtSORSn" alt="" width="563"><figcaption></figcaption></figure>

#### Shortcode override

Add `link_target=` to your shortcode:

* `affiliate | bridge | auto`

<figure><img src="/files/0OLkdRM4niIyFwZm7azq" alt="" width="563"><figcaption></figcaption></figure>

### 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%.

<figure><img src="/files/T5P3IDOeajVknrzNOxUT" alt=""><figcaption></figcaption></figure>

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.


---

# Agent Instructions: 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:

```
GET https://ce-docs.keywordrush.com/set-up-products/import-tools/bridge-pages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.