Ask your Search Console
what happened
Search Console shows that clicks are down 21%. It does not say why. Connect it to Hi, Moose and ask the question in plain words. Moose pulls the rows and runs the same comparisons an analyst would. The answer names the cause and shows the numbers it came from.
Sam, looking across your Google Search Console performance data for the last two months, the drop in Google traffic is driven primarily by planting season seasonality, specifically the close of the spring planting window in late June.
Brand queries remain steady, but non-branded search volume for planting terms dropped sharply as the season moved past transplanting.
Comparing the prior 28 days against the recent 28 days:
Spring planting terms were 6 of your 10 best-performing keywords in the earlier period.
- Spring planting queries fell 61% between the two periods, with the window closing in late June.
- Brand queries held within 2%, so demand moved and rankings did not.
- Fall planting and cover crop queries are climbing, two weeks behind last year's curve.
Questions you can ask
For each one, Moose works out which date ranges, filters and comparisons to pull from Search Console. You only type the question.
Connect once, then ask
Search Console connects through your own Google account. The rows come down to your computer, and Moose answers from those rows.
Sign in with Google once under Connections. Hi, Moose asks for read access only. Pick the property, and Moose ties it to that project.
Moose turns your question into Search Console queries and pulls the rows. If the first set does not answer the question, it pulls more.
The chat stays in your chat history with the tables intact. Ask the same question next month and compare the two answers.
Six checks before it answers
A traffic drop has a handful of usual causes. Moose checks each one and tells you which check gave the answer.
If impressions fell and position held, fewer people searched. If impressions held and clicks fell, your snippet or a competitor above you is the reason. The chart looks the same either way, and the fix is different.
Searches with your brand name in them follow your marketing. The rest follow your SEO. Moose reports them separately, because a drop in one and not the other is most of the answer.
A 21% drop is rarely spread evenly. A few groups of queries or pages usually carry most of it. Moose ranks them by clicks lost, so you start with those.
A drop on one date points at a Google update, a site migration or a release. A slide over three weeks points at a season or slow decay.
The most common cause of an alarming chart is the calendar. Moose pulls the same weeks from last year and shows whether the drop happened then too.
Queries that had impressions last period and none this one. Sometimes that is noise, and sometimes a page fell out of Google's index and nobody noticed.
Questions people ask
Is it making the numbers up?
No. Every figure in an answer comes from a Search Console API response Moose received during that chat, and the tables are printed from those rows. If a query returns nothing, Moose says so instead of estimating.
How does it know my business well enough to say "seasonality"?
From the query data and from Context, where you have told Moose what you sell, who buys it and what your year looks like. A drop that lands the week a season ends, on plant-name queries only, with brand queries flat, has one likely reading. Moose names it and shows the numbers, so you can disagree.
What about the 16 month limit and data delay?
Both are Google's limits and both apply. Search Console holds 16 months, and the last two or three days are usually incomplete, so a year-over-year question works and a three-year one does not. Every table names the date range it used.
Does this work with a local model?
Yes. With a local model your query data never leaves your computer. A small local model handles the pulls and comparisons well, and a cloud model writes a clearer explanation of what it found. You switch per chat from the model picker.
Can I run this for several sites?
Yes. Each project holds its own property, its own context and its own chat history, and you switch with the project picker at the top of the sidebar. Agencies run one project per client.
Do I need a paid plan?
No. Search Console chat works on BYOK Free with a local model or your own key. The connection is your Google account, so there is nothing for us to meter.
More things to ask Moose
All use casesThe searches Google writes for itself before it answers, and the domains it cites.
Twelve searches behind one prompt, including the site: queries naming brands it trusts.
One question, five engines, about a minute. Free on every plan.
A semantic index of every page, built and kept on your computer.
Share drops past your threshold, Moose finds the page, prepares the fix, waits for you.
The full list, and what Moose does step by step in each one.
Connect Search Console,
then ask.
Download Hi, Moose and connect Search Console. Then ask the question you were about to spend an hour on.