SEO

Investigate an organic traffic drop

Find out why organic clicks or traffic fell, exactly when it started, and whether the cause is a ranking loss, a demand change, a technical problem, a Google update or a tracking gap, using Search Console and GA4 evidence instead of guesswork.

The playbook

"Traffic is down" is a symptom with at least five different causes, and each one needs a different fix. The job here is to establish the date, the segment and the mechanism before anyone rewrites a page.

Steps

  1. Establish the timeline. google_search_console.query with dimensions: ["date"] over the last 16 weeks ending 3 days ago. Compute a 7-day rolling average of clicks and impressions and find the inflection: the first day the average leaves its prior baseline. Say whether the shape is a step (sudden, one day) or a slope (gradual, over weeks). A step points at a technical change or an update; a slope points at decay or seasonality.

  2. Confirm the drop is real, not a tracking change. google_analytics.run_report with dimensions: ["date", "sessionMedium"], metrics: ["sessions"] over the same window, and keep organic. If Search Console clicks are flat but GA4 organic sessions fell, the cause is tagging, consent or a filter change, not SEO. Stop and say so.

  3. Isolate the segment. Take the 28 days before the inflection and the 28 days after. Run google_search_console.query for each window with dimensions: ["page"], then again with ["query"], ["device"] and ["country"]. Compute the delta per row. The question is whether the loss is concentrated in a few pages or queries, or diffuse across everything in proportion.

  4. Diagnose from the pattern.

    • Concentrated, position worse on those pages: ranking loss. Content was overtaken, or those pages changed. Continue with content-decay-audit and keyword-cannibalization-check.
    • Concentrated, impressions near zero: the pages left the index, were redirected, or were noindexed. Continue with technical-crawl-audit.
    • Diffuse, position worse everywhere: site-wide. Either a Google core update or a site-wide change (template, robots, Core Web Vitals). Fetch Google's Search Status Dashboard with your browsing and check whether an update started within a few days of the inflection.
    • Diffuse, impressions down, position flat: demand. Seasonality or the market. Compare against the same weeks last year before calling it a problem.
    • Impressions flat or up, CTR down: the search results page changed shape. AI overviews or new features are absorbing clicks. Continue with ctr-underperformers.
    • Brand queries down: brand demand or a tracking issue, not SEO. Split brand from non-brand with a filters entry on query and report the two separately.
  5. Report. Lead with the inflection date, the magnitude (clicks per week before and after), and whether the loss is concentrated or diffuse. Give the diagnosed cause with the evidence pattern that supports it, list the causes you ruled out and why, and name the one playbook to run next. One cause, one next step.

Gotchas

  • The last 3 days always look like a drop. Search Console has not finished processing them. End every window 3 days back or the timeline will show a cliff that does not exist.
  • An update is not the cause unless the dates line up. A drop that started two weeks before an update was not caused by it. Correlation with a dated event is the strongest evidence this playbook can offer; it is still correlation.
  • Migrations reset everything. A move from a URL-prefix property to a domain property, a domain change, or a redesign that changed URLs will look like catastrophic loss on one property and growth on another. Ask whether anything moved.
  • Sixteen weeks is not enough for seasonal businesses. If the drop lines up with the same weeks last year, it is seasonality. Pull the year-ago window before diagnosing.
  • Total impressions can rise while clicks fall. That is not contradictory; it is the signature of a results page that answers the query without a click.

Sequel CLI

Install Sequel skills into your agent

One command connects your agent to Sequel and installs the Sequel skill, so it knows this playbook exists and reads it when a question matches. The CLI signs you in, provisions a scoped API key and writes the config for you.

Already have an MCP client?

https://api.sequel.sh/mcp

Point it at this URL and sign in when prompted, or send an API key from Settings as a Bearer token. Skills come with it; nothing else to install. Manual setup per client

  1. 1

    Install the Sequel CLI

    One line installs the latest CLI with whatever package manager you have.

    curl -fsSL https://sequel.sh/install | sh
  2. 2

    Sign in

    Authenticate in your browser and pick an organization.

    sequel login
  3. 3

    Install into your agent

    Writes the MCP config and installs the Sequel skill file for agents that support skills. Pick an agent from the list, or target one directly by its slug.

    sequel install
    • Claude Code
      sequel install claude-code
    • Claude
      sequel install claude
    • Cursor
      sequel install cursor
    • VS Code
      sequel install vscode
    • Windsurf
      sequel install windsurf
    • Zed
      sequel install zed
    • Codex
      sequel install codex
    • OpenClaw
      sequel install openclaw
    • Hermes
      sequel install hermes

More like this

Other SEO skills

Analyze high-ranking landing pages

See which pages perform best in organic search: the landing pages that earn the most clicks and impressions, the queries behind each one, and how they compare with competitor estimates from Ahrefs.

Audit internal links to important pages

Audit the site's own internal linking: crawl navigation and body links between the site's pages to find valuable pages with too few inbound internal links, orphan pages, and the handful of cross-links that would lift striking-distance rankings.

Audit or draft an llms.txt

Check whether the site has an llms.txt, whether it follows the spec and points at the pages that matter, and if it is missing draft one from the pages Search Console shows people actually find, so AI assistants get a curated map of the site instead of guessing.

Audit redirect chains and loops

Follow every redirect on the URLs Search Console still sends traffic to, on the sitemap, and on backlinked pages, to find chains, loops, redirects to the homepage, and temporary redirects that should be permanent, so link equity and crawl budget stop leaking.

Audit referring domain quality

Grade the domains linking to a site by authority, traffic and link count, spot concentration risk and link-farm patterns, and separate the referring domains that carry weight from the ones that are noise.

Audit titles and meta descriptions

Compare the title and meta description of each top page against the queries it actually ranks for in Search Console, and find missing, duplicate, truncated or misaligned metadata on the pages where a rewrite would earn the most clicks.

Put this playbook to work

Connect a source, ask the question, and the agent follows these steps. Free to start.