Rémi KokabiOctober 26, 20268 min read

Website traffic signals (sell when a prospect's traffic spikes or drops)

A website traffic signal flags when a target company’s estimated website visits rise or fall sharply over a defined period, usually a month or a quarter. It’s built from third-party traffic estimators, since you don’t have access to a prospect’s actual Google Analytics account. What you’re really looking at is a trend line, not an exact visitor count.

Say an ecommerce brand’s estimated traffic jumps sharply after a product goes viral. That’s the kind of moment a traffic signal is designed to catch, and noticing it before a competitor does gives you a real reason to reach out.

Item

Detail

What triggers it

Estimated website traffic rises or falls beyond a set threshold

Signal level

Company

What it tells you

Growth to support, or a problem to fix

Best window to act

Within a few weeks of the change

Who typically uses it

SEO agencies, CRO tools, hosting providers, performance vendors

What is a website traffic signal

Beyond the raw trend, traffic data can also show where visits come from (direct, search, social, paid) and whether a change is a one-off spike or a sustained movement over several months.

For outbound sales teams, this matters because traffic changes tell a story. A company whose monthly visits doubled likely launched a campaign, raised a round, or went viral. A company whose traffic dropped sharply might be losing to a competitor or recovering from a Google algorithm penalty.

Organic trends and keyword rankings add another layer. A company pushing hard on SEO for specific keywords is telling you where it wants to grow. That context gives you a reason to reach out that’s grounded in something real.

Why website traffic signals point to a buying window

Most intent signals (job changes, funding rounds, tech stack updates) are well-known. Website traffic changes are still underused in outbound, which is exactly why they work.

Growth creates capacity problems

When traffic surges, so does pressure on everything downstream: conversion rates, page speed, infrastructure, and support volume. A company whose monthly visits multiplied in a single quarter is almost certainly stretching its current stack. If you sell CRO, analytics, hosting, or CDN services, that gap is your opening.

Drops create urgency

A sustained traffic decline usually means lost revenue. On its own, it’s a reason to look closer. Combined with a new SEO hire or a job posting for a “growth marketer” paints a very clear picture: they know something is broken and are actively trying to fix it.

Both are visible from the outside

Unlike internal metrics (pipeline, churn, NPS), traffic changes are observable without access to a prospect’s analytics. Traffic estimators model a domain’s monthly visits from panel data, search rankings, and statistics. That makes traffic one of the few signals where you can spot the trend and build a message around it before anyone fills out a form.

Where website traffic data comes from

You might assume these numbers come from something precise, like server logs. They don’t. Most estimates rely on panels of users who agree to share their browsing data, and statistical models extrapolate from that sample to the whole web.

Tools like Similarweb, Semrush, and Ahrefs each take a different approach. Similarweb models total traffic from panel data, while Ahrefs and Semrush estimate organic traffic from keyword rankings and click-through-rate models. All of them are useful for trends and comparisons, none of them is exact.

That means you’re better off reading the trend (clearly up, clearly down) than quoting a visitor count. Estimates are also more reliable on large sites, where the underlying data is richer. The smaller the site, the more you should treat a neat figure as a rough band.

Who benefits from tracking this signal

Not every team will find traffic signals relevant. But for specific sellers, they’re one of the highest-context triggers available.

If you sell

What the signal tells you

Angle for the first message

SEO services

A drop after an algorithm update

Recovery audit

CRO or A/B testing tools

A spike in visitors with flat conversion

Convert the new traffic

Hosting or CDN

Fast traffic growth

Scale before slowdowns hit

Analytics or BI platforms

Channel mix is shifting

Help them understand why

Paid media agencies

Organic traffic declining

Fill the gap with paid

The common thread: the signal tells you something changed, and your product addresses the consequence of that change.

How to turn a website traffic signal into a meeting

Seeing the signal is the easy part. Turning it into a reply takes a repeatable workflow. Here’s one that works well for signal-based outreach.

1. Set thresholds that filter out noise

Small fluctuations happen constantly. The signal becomes useful when you see sustained growth or decline over several months, or a sudden spike that crosses a meaningful threshold. The same percentage swing means very different things on a large site and a small one.

2. Check the cause before you write

Look at publicly available context: recent blog posts, product launches, new campaigns, Google algorithm updates, or seasonal patterns. A traffic spike during Black Friday for an ecommerce brand is expected. A spike in March with no obvious cause is worth investigating.

3. Pick the right angle

If traffic is growing, your message focuses on capitalizing and scaling. If traffic is dropping, your message focuses on diagnosis or recovery. The tone changes entirely.

4. Reach the person closest to the problem

For traffic-related signals, the right contact is usually a Head of Growth, VP of Marketing, SEO Manager, or Ecommerce Director. Reaching C-level works for smaller companies. At larger orgs, go functional.

5. Share one insight they can verify

Your opening line references something the prospect can check themselves. That builds trust immediately because the recipient knows you did real research, not a template swap.

Tip: lemlist doesn’t have a native website traffic signal, but you can describe this trigger with AI Signals, or import traffic changes from your own estimator as Company external signals. Each signal then feeds its own watch list and campaign.

Example multichannel sequence triggered by a traffic signal

Here’s a sample five-touch sequence for a prospect whose traffic grew significantly over the past quarter:

Day

Channel

Action

Goal

0

Email

One observation about the traffic trend and a hypothesis about what’s driving it

Open a conversation

2

LinkedIn

Visit their profile

Warm them up before the connect

4

LinkedIn

Send a connection request (no note)

Get accepted without friction

7

Email

Share a short, relevant resource (case study, guide)

Add value

10

Call

Reference the earlier email and ask a question

Book the meeting

You can build sequences like this in lemlist using conditional logic, so if a prospect engages on LinkedIn, the next step adapts. If they don’t, the sequence keeps going through email and phone. One campaign, multiple channels, all synced.

Message examples for traffic signals

Writing signal-based messages is straightforward when you follow one rule: reference the trend, never the exact number.

Traffic growth message

Subject: Nice quarter

Hi {{firstName}},

Noticed {{companyName}}'s web traffic has been climbing steadily this quarter. Usually that means a campaign or launch hit its stride.

We’ve helped teams in {{industry}} convert traffic surges into pipeline before the momentum cools. Thought it might be worth a quick look at what’s working and where you could push it further.

Worth 15 minutes this week?

Traffic drop message

Subject: Quick thought on {{companyName}}

Hi {{firstName}},

Looks like {{companyName}}'s organic visibility may have shifted recently. That sometimes follows an algorithm update or a technical issue that’s hard to spot internally.

We recently ran a quick diagnostic for a similar company and found a couple of fixable issues. Happy to share what we’d look at for you, no strings attached.

Both messages let the prospect verify what you’re saying. They’re specific without being invasive.

Mistakes to avoid when using traffic signals

  • Quoting exact traffic numbers: These are estimates. Saying “your traffic dropped to 47,231 visitors” sounds like surveillance and is probably wrong. Stick to directional language: “traffic has been trending down.”

  • Ignoring seasonality: Compare year-over-year, not just month-over-month. A Q4 spike for a retail brand is normal, not a buying signal.

  • Alarmist tone on drops: “Your traffic crashed” will get you blocked. Let the signal shape the timing and angle of your message, without making it sound like you’ve been watching their website.

  • Acting on a single signal alone: A traffic change on its own is a weak predictor. Combine it with a second signal before you treat the account as a priority.

Combine traffic signals with other intent data

One signal gives you a reason to reach out. Two signals give you a priority account. Here are combinations that work well together:

  • Traffic increase + new job posting for a marketer: They’re growing and hiring to sustain it. Your offer fits the growth plan.

  • Traffic drop + recently hired an SEO lead: They’ve diagnosed the problem. Your tool or service helps the new hire succeed faster.

  • Traffic surge + funding round: Fresh capital plus visible momentum. The budget exists and the urgency is real.

  • Traffic decline + competitor traffic rising: Market share is moving. This is the highest-urgency combo for competitive displacement plays.

A traffic change tells you where to look first. It works best combined with ICP fit and what you already know about the account.

In lemlist, each signal type lives in its own watch list. When the same account shows up in several of them, you move it up your priority list manually, so you stay in control of which combinations matter.

How to track website traffic signals in lemlist

lemlist doesn’t track website traffic changes as a native signal, but you can still build this workflow:

  1. Create a watch list with AI Signals and describe the trigger in plain words, such as SaaS companies showing a sharp rise in website traffic.

  2. Or use Company external signals to bring in traffic changes you spot in your own estimator.

  3. Add related native signals in separate watch lists, like Company is hiring or Fundraising, to spot accounts showing several signals.

  4. Set your ICP filters and persona so only relevant leads surface.

  5. Link each watch list to a campaign so new contacts enter an outbound sequence built around that trigger.

Contacts are enriched through waterfall enrichment across 14+ providers, giving you verified emails and phone numbers without manual lookup. AI variables can then turn the signal context into a personalized first line.

Build your first signal-based sequence in lemlist

Reach buyers at the right time

Spot buying signals and trigger personalized outreach when it matters.

Frequently asked questions

Not very, in absolute terms. Estimates from tools like Ahrefs, Semrush, or Similarweb can be far off a site’s real numbers, so treat them as directional. Use them for trends and relative comparisons, not absolute visitor counts.

No. Website visitor identification reveals which companies visit your website (lemlist tracks this natively with the Website visitors signal). A website traffic signal, by contrast, tracks changes in traffic on their website, based on third-party estimates.

For traffic-related signals, the best contacts are Heads of Growth, VPs of Marketing, SEO Managers, or Ecommerce Directors. At smaller companies, founders and CEOs are often the right target.

Yes, partly. In lemlist, you can describe the trigger with AI Signals or import it as an external signal, then link the watch list to a campaign so new contacts enter your sequence.
Rémi Kokabi

Rémi Kokabi

Co-founder @GTM Club

Share this post