---
prompt: why-did-traffic-drop
title: Find out why your traffic dropped
description: Your agent finds the day views fell, then looks for what changed on your site around then.
category: Growth
products: Stats, Activity log
mode: reads only
tools: statistics.get, activity.get, settings.get, monitor.status, scan.status
url: https://jetpack.com/prompts/why-did-traffic-drop/
updated: 2026-10-25
---

# Find out why your traffic dropped

Your agent finds the day views fell, then looks for what changed on your site around then.

## Prompt

> My traffic seems to have dropped. Compare my weekly views for the last [4] weeks, then find the day it started. Check my activity log around that day for plugin, theme or setting changes. Check that search engines can still see my site, and that it’s up and clean. Tell me the most likely cause.

Square brackets are placeholders. Ask the user to fill them in if they did not.

## Steps for your agent

1. Call statistics.get once per week for the period the user gave (default 4 weeks), each with a 7-day start_date and end_date. Then call it once per day only inside the week where views fell, to find the day the drop started.
2. Call activity.get for 3 days either side of that day. List plugin, theme and settings changes in plain words.
3. Call settings.get with include_reading true. If blog_public is 0, say search engines are blocked: that alone can explain a drop.
4. Call monitor.status and scan.status (action "status"). Skip Scan if it isn’t on the plan.
5. Give the most likely cause, how sure you are, and one next step. Say clearly when nothing on the site explains it.

## Tools

- `statistics.get` (reads only, through `wpcom-mcp-site`): Read views and visitors, week by week, then day by day.
- `activity.get` (reads only, through `wpcom-mcp-site`): See what changed around the day traffic fell.
- `settings.get` (reads only, through `wpcom-mcp-site`): Check search engines can still see your site.
- `monitor.status` (reads only, through `wpcom-mcp-site`): Check that your site is up.
- `scan.status` (reads only, through `wpcom-mcp-site`): Check for security threats, if your plan has Scan.

Run each tool through the WordPress.com MCP server tool named next to it, with `action: "execute"`, `operation` set to the tool name, `wpcom_site` and `params`. Set `user_confirmed: true` only after the user approves a change.

## Before you start

- Uses Jetpack Stats, free on every site. The malware check needs a Jetpack plan with Scan.
- The free activity log shows the latest 20 events.
- You need to be an administrator.

## Safety

Reads only. Nothing on your site changes.