Convert Organic Readers Into An Owned List

Search and social are rented, and most teams learn this during the update that halves their traffic rather than before it. The default response is a sitewide popup asking people to subscribe for updates, which converts badly because it is not a reason and damages the page it interrupts. Capture works when the offer is the obvious next step from the page the reader is already on, which means fewer capture points rather than more.

The skill file

---
name: email-capture-from-organic-readers
description: Use when every route to your audience runs through search or a feed, and one ranking drop or algorithm change would leave you unable to reach anyone.
---

# Convert Organic Readers Into An Owned List

Search and social are rented, and most teams learn this during the update that halves their traffic rather than before it. The default response is a sitewide popup asking people to subscribe for updates, which converts badly because it is not a reason and damages the page it interrupts. Capture works when the offer is the obvious next step from the page the reader is already on, which means fewer capture points rather than more.

## What you need first

- your top twenty organic landing pages by sessions, with time on page alongside
- something specific you can give per topic cluster: a dataset, a template, a checklist, a working calculator
- a sending platform and a named person who will actually send

## Method

1. Choose pages by intent rather than volume. A how-to page converts to a list several times better than a definition page with three times the traffic, and the definition page is where most popups end up.
2. Write the offer as the next step from that specific page. Someone reading a migration checklist wants the checklist as a file, not weekly tips.
3. Place the capture inline at the point the reader has got what they came for, usually straight after the main answer, rather than as a timed overlay that fires before they have read anything.
4. Ask for one field. Each extra field costs a measurable share of submissions, and you can infer role and interest later from which page they signed up on.
5. Measure conversion per page, not sitewide. A sitewide average conceals that two pages produce nearly everything while the rest are only interrupting people.
6. Send something within the first week. An unmailed list is not an asset, and warming a six-month-old cold list produces spam complaints that damage deliverability for everything after it.
7. Check the capture has not cost you the page: watch layout shift and dwell time on the pages you changed, because an interstitial that triggers a mobile usability problem costs more than the addresses are worth.

## What this produces

A handful of page-specific capture offers with per-page conversion rates and a sending schedule beginning immediately.

## Where this goes wrong

- one sitewide popup with a generic offer, which converts poorly and is the usual cause of a self-inflicted intrusive-interstitial problem on mobile
- collecting addresses with no plan to send, so the list is cold and unusable by the time anyone needs it
- reporting total signups only, which hides that most pages contribute interruption and nothing else

---

From the QuQi skill library - https://www.quqi.io/skills/email-capture-from-organic-readers

What you need first

• your top twenty organic landing pages by sessions, with time on page alongside
• something specific you can give per topic cluster: a dataset, a template, a checklist, a working calculator
• a sending platform and a named person who will actually send

Method

1. 01 Choose pages by intent rather than volume. A how-to page converts to a list several times better than a definition page with three times the traffic, and the definition page is where most popups end up.
2. 02 Write the offer as the next step from that specific page. Someone reading a migration checklist wants the checklist as a file, not weekly tips.
3. 03 Place the capture inline at the point the reader has got what they came for, usually straight after the main answer, rather than as a timed overlay that fires before they have read anything.
4. 04 Ask for one field. Each extra field costs a measurable share of submissions, and you can infer role and interest later from which page they signed up on.
5. 05 Measure conversion per page, not sitewide. A sitewide average conceals that two pages produce nearly everything while the rest are only interrupting people.
6. 06 Send something within the first week. An unmailed list is not an asset, and warming a six-month-old cold list produces spam complaints that damage deliverability for everything after it.
7. 07 Check the capture has not cost you the page: watch layout shift and dwell time on the pages you changed, because an interstitial that triggers a mobile usability problem costs more than the addresses are worth.

What this produces

A handful of page-specific capture offers with per-page conversion rates and a sending schedule beginning immediately.

Where this goes wrong

• one sitewide popup with a generic offer, which converts poorly and is the usual cause of a self-inflicted intrusive-interstitial problem on mobile
• collecting addresses with no plan to send, so the list is cold and unusable by the time anyone needs it
• reporting total signups only, which hides that most pages contribute interruption and nothing else

Use this skill in your own AI

The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.

Questions about this skill

More in Social & distribution