rca · hard
Reddit traffic dropped 5%: what do you tell the exec team?
Reddit traffic is down 5% week-over-week. What do you do, and what do you tell the exec team?
The exec question is the trap. Most candidates diagnose competently then collapse when asked what they’d actually say at 9am before the root cause is confirmed. A strong answer demonstrates the diagnostic and the communication in the same breath.
Before you walk into the room
Spend 30 minutes on three checks before you say anything to leadership.
Validate the measurement. A logging pipeline failure, a broken pixel, or an SDK regression looks identical to a real traffic drop. Pull the raw event counts, check the ingestion lag, and confirm your analytics platform is not sampling differently than last week. If the drop is a tracking artifact, that is your exec message and the diagnosis is done.
Segment by source and platform. Reddit’s traffic splits across at least four meaningfully different root cause trees: direct and bookmarked visits, Google organic (a large share of Reddit’s reach comes from ranking for “best X” queries), iOS and Android app sessions, and API-driven third-party clients. A 5% aggregate drop can mean very different things if it is concentrated in one segment. SEO organic dropping alone points toward a Google algorithm or AI Overviews change. App sessions dropping alone points toward a release regression or push notification issue.
Check the change log. Server deploys, policy changes, and subreddit governance decisions in the last 7 days are your first internal hypothesis candidates. The June 2023 blackout, when 8,000+ subreddits went private and traffic fell from 57.8M to 54.3M visits (about 6%), is the canonical example: a governance decision that changed the crawlable surface area of the site overnight.
The 2026 hypothesis you cannot skip
In 2026, the most probable external cause of a Reddit SEO traffic drop is not a Google penalty. It is Google AI Overviews, Perplexity, and ChatGPT Search surfacing Reddit thread content without sending the click. Reddit’s threads are the highest-signal source of authentic human experience, so AI search products cite them constantly while absorbing the click. A 5% organic drop with flat in-app engagement (comments, upvotes, time-in-app) is the fingerprint of this pattern. The strategic response is different from any internal bug: it is a distribution dependency to reduce, not a funnel to patch.
What to actually say to the exec team
Structure the communication in five moves, in this order:
- What we know with certainty. “Traffic is down 5% week-over-week as of [date]. The measurement is validated. This is a real drop, not a tracking artifact.”
- The leading hypothesis and confidence level. “Our leading hypothesis is [X]. The evidence pointing there is [specific data point]. We are treating this as probable, not confirmed.”
- What we have ruled out. “We have eliminated tracking failure and [specific internal change]. Here is why.”
- What we need to confirm. “To confirm [X], we need [specific data pull or external signal]. We will have that by [time].”
- What we are doing in parallel regardless. “Because [mitigation] is low-cost and addresses the most likely cause, we have already started it.”
Different execs need different emphasis. A CEO wants severity and timeline. A CFO wants the revenue implication (Reddit’s IAB-certified measurement ties directly to advertiser commitments, so a 5% drop has a quantifiable floor impact). A head of growth wants to know if the attribution model is intact. If the root cause is AI search suppression, shift the message: “This is an industry-level distribution shift, not a product failure. We are protecting traffic through owned channels: app deeplinks, push, and email.”
The weak pattern
weak
"I'd look at internal factors like a bad deploy or a policy change, and external factors like a Google algorithm update. I'd segment the data and then communicate clearly with data and be transparent with the exec team."
Reciting MECE categories without Reddit-specific hypotheses signals a generic playbook. Saying “communicate clearly” without showing the actual structure tells the interviewer the candidate has never had to brief a CFO on a moving situation.
strong
"Before I say anything to the exec team, I want 30 minutes to do three things: confirm the measurement is clean, segment the drop by traffic source, and check the change log. That 30-minute check tells me whether I walk in with 'the drop is real and here is the leading cause' or 'we had a tracking issue and traffic is fine.' Here is what I'd actually say to the exec team: 'Traffic is down 5% week-over-week. Measurement is validated. Our leading hypothesis is a Google AI Overviews suppression effect on organic search, based on the pattern of flat app engagement with concentrated SEO segment decline. We have ruled out a tracking artifact and any internal deploy. To confirm, we need to pull the GSC click data against the same period last year, which we'll have in two hours. In parallel, we have already flagged this to the growth team because the mitigation, shifting acquisition weight toward app and owned channels, is the right move regardless of confirmed root cause.'"
The PM judgment
The interviewer is checking whether you can hold diagnostic rigor and stakeholder communication at the same time under pressure. In 2026, a 5% Reddit traffic drop is more likely a search distribution story than a platform failure. Knowing that before you walk into the room, and knowing how to say “I suspect but have not confirmed” without losing exec confidence, is what separates a strong hire from a passing one. See also: RCA for Facebook Groups dropping 15% and when two metrics conflict.