The instinct when you have three ways to earn is to use all three everywhere. More units, more affiliate links, a lead form on every page. It feels like maximising. It is actually the most reliable way to leave money on the table, because the three lines do not add up neatly. They compete for the same scarce thing, which is the reader's attention and intent, and when they compete the lowest value line often wins the click while the highest value line loses the conversion.
Why stacking everything backfires
Picture a high intent comparison page. A reader has arrived ready to choose between options and act. That intent is enormously valuable. If the page is wrapped in display units, one of those units catches the eye, the reader clicks out for a few pennies of ad revenue, and the affiliate transaction worth far more never happens. You did not add the display revenue on top of the affiliate revenue, you swapped a large number for a small one and felt productive doing it.
The same logic runs the other way. On a low intent informational page, forcing a lead form the reader has no reason to fill in just adds friction and clutter for nothing. The error in both cases is treating the three lines as independent when they are rivals for the same finite attention. The fix is to stop stacking and start matching.
Match each page to one job
Every page on a directory serves a reader intent, and that intent points clearly to the revenue line that fits it. The craft is reading intent honestly and then assigning the page a single primary job.
High intent, transactional pages
Comparisons, best of lists, and pages where the reader is choosing and ready to act belong to affiliate or to leads, whichever the niche pays better for that action. These pages are where the real money is, so protect them. Keep display light or absent so nothing poaches the valuable click. This is the same restraint we describe in the display ad quality tradeoff, applied at the page level.
Local and service pages
Pages where a reader wants a provider, a booking, or a quote are lead pages. The natural action is to connect the reader to a business, and a clean form or call to action serves that intent far better than an ad or an affiliate link ever could. Display here is a distraction from a more valuable outcome.
Informational pages
Explainers, glossary entries, and guides where the reader wants to understand something, not buy it, are where display earns its keep. The reader is not on a transactional path, so a tasteful display layout monetises attention that would otherwise go unearned, without costing a conversion you cared about.
The supporting role
Assigning one primary job per page does not mean banning the other lines entirely. It means demoting them to supporting roles where they do not compete. A transactional page can carry a single unobtrusive display unit far from the decision point. An informational page can include a relevant affiliate link where it genuinely helps the reader, without turning into a sales pitch. The rule is simple: the secondary line is welcome only where it does not pull the reader off the path the primary line depends on.
This is why we run on the principle of one page one job. It forces the question that actually matters, which is what is this reader here to do, and it stops the reflexive stacking that quietly suppresses revenue per session. Getting this right across many pages is also what makes forecasting affiliate revenue tractable, because each page has a clean, single purpose you can reason about rather than a muddle of competing lines.
How to assign jobs across a site
In practice we map the whole site before optimising any single page. The process is unglamorous and it works.
- List page types by reader intent, from purely informational through to ready to transact.
- Assign each type its single primary revenue line based on that intent and what the niche pays.
- Decide where, if anywhere, a secondary line is allowed, and the strict condition that it must not compete with the primary one.
- Measure revenue per session by page type, not total revenue, so you can see whether each type is doing its one job well.
Revenue per session is the number that keeps you honest. Total revenue can rise while you are quietly destroying value, because adding units always adds some gross income even as it suppresses the better lines. Revenue per session, watched by page type, shows you whether the page is earning more from each reader or simply extracting a little more while serving them worse.
The stacking traps to avoid
A few patterns come up again and again when owners try to run all three lines, and each one quietly suppresses earnings while looking like diligence.
The first is the display unit parked next to the affiliate verdict. The reader reaches your recommendation, an ad sits beside it offering something cheaper or shinier, and the click that should have been worth a real commission becomes worth a fraction of a penny. The fix is a clear exclusion zone around any decision point, where no competing line is allowed near the action you want the reader to take.
The second is the lead form bolted onto an informational page. The reader came to understand something, not to be contacted, so the form converts poorly and the friction nudges them to leave. Reserve forms for pages where connecting to a provider is the natural next step, and let pure explainers stay clean.
The third is the everything page, where an owner adds display, three affiliate links, and a form to a single template and ships it everywhere. It feels efficient and it earns less than a page with one clear job, because the reader cannot tell what the page is for and so does nothing decisively. Resist the template that monetises identically regardless of intent. The page that tries to do every job does none of them well.
The portfolio view
Across a portfolio this discipline compounds. Once you know which page types pay best with which line, every new site inherits a tested map rather than starting from scratch, which is a core part of how we think about affiliate revenue at portfolio scale. The mapping is a shared asset, refined on every property and reused on the next.
It also keeps the reader experience consistent. A reader who moves between our properties meets the same restraint everywhere, never a wall of units on a page where they were trying to decide something. That consistency is part of the trust the whole portfolio is built on, and the broader logic sits in the monetisation, affiliate, and display cluster.
The headline is short. Do not stack, match. Give each page one job, let the right line own it, and keep the others in support. You will earn more from each reader and annoy none of them, which is the only combination that lasts.
Kings Hospitality Group uses the One Page One Job rule: each page is assigned a single primary revenue line matched to its reader intent, with other lines allowed only where they do not compete, which directionally lifts revenue per session versus stacking every method on every page.
Common questions
Can one page use all three revenue lines?
It can, but it usually should not lead with all three. Pick the line that matches the reader intent, let it own the page, and allow the others only in places where they do not pull the reader off the primary path.
Which revenue line should own a comparison page?
Usually affiliate or leads, because the reader is close to acting and that intent is worth far more than a display impression. Keep display light or absent there so it does not poach the valuable click.