gaash.ai

Measurement & Reporting · 8 min read · September 26, 2026 · , gaash.ai

Through the moving year: AI readings beside your quote requests

Read the monthly panel against your own moving year. Set a busy-season month beside the same month a year earlier, not beside the quiet month before it, and put three counts of your own next to it: the source each quote request gives, AI referrals in analytics, and Google's generative AI impressions. None of them proves that an answer caused a booking.

What a monthly reading can show a mover, and what it cannot

The monthly reading is the panel set out in reading answers by route and move type, run on the same questions every month; the facts it tests are listed in the overview for moving companies. It shows how often the answers name you for each move, a mention rate by route, and whether they recommend you or put you first. It counts no bookings.

Your own records count other things. The quote form holds what customers say about how they heard of you, analytics holds the visits that arrived from an assistant's answer, and Search Console holds how often Google's AI features showed a link to your site. Each is partial. A household that reads your name in an answer and phones the office leaves no visit behind, the everyday form of zero-click search, and a customer who says "Google" may mean several things.

So say it plainly in any report built on these numbers: none of them proves that an answer caused a booking. They are four readings taken side by side. When they move together after a change you made, that is a reason to keep going, not proof.

The moving year has seasons, and the comparison has to allow for them

A mover's year is uneven, and your own booking history shows its shape: the months of the busy season, the quiet stretch, and, if your calendar has them, the peaks at the end of each month. The panel's questions do not change with the season, but your inquiry count does. A count from the middle of the busy season set beside one from the quiet months says the season arrived, and nothing more.

So compare like with like: from the second year on, this busy season with the last one, and a month-end week with a month-end week. That needs a panel left unchanged for twelve months, which is one more reason not to reword a question after a bad month. A new question can be added as a new line with its own start date, as the article on prompt monitoring explains.

Take the reading on the same days each month, such as the second week. We have not measured whether answers differ at the end of a month, when your calendar may be at its fullest, and a fixed date keeps that question out of the comparison. It also puts the reading in a week when someone in the office has an hour to read the answers with care.

Change the site in the quiet months

A change to your pages needs a reading before it and a few after it before anything can be said about it. Made in the quiet months, it gets a baseline and two or three readings before the busy season, and by the peak you can see whether the answers moved on the routes you rewrote. Made at the peak, it lands in the same weeks as the season's rise in inquiries, and your records cannot tell the two apart.

Keep a dated change log in the same sheet: what changed, on which page, on which day. The rewritten routes page, the new quote terms, the corrected license number. When a line of the panel moves, the log is the first place to look; without it, a movement in the readings has nothing to be set against.

The quote form: one question about the source, beside the move

Add one question to the quote form, and ask it on the phone too: how did you first hear of us? Offer the same choices every time, among them an AI assistant such as ChatGPT, Claude, Gemini or Perplexity, a search engine, a friend or past customer, a truck or a yard sign, and "not sure", with a line for the customer's own words. Suggest none of them.

A mover's quote form already asks for the origin, the destination, the move date and the size of the home. Each source answer therefore sits beside a route and a move type, and the inquiries that name an assistant for long-distance moves can be set beside the panel's long-distance lines rather than against the whole year's total.

Count each inquiry in the month it arrived, not the month of the move. A household may ask weeks or months before its moving date, and an answer it read, if it read one, was written in the month it asked; the panel reading from that month is the one to set it beside. Record the move month in its own column for scheduling.

Referrals and Google's AI report: two counts, each with limits

Visits from an assistant's answer reach analytics as referrals when the browser passes on where the visitor came from, and the article on AI referrals in analytics lists the hosts and how to group them. For a mover, the useful part is where those visits land and what they do next: the quote form, a routes page or the storage page, and whether the quote form was sent.

For Google's own AI features, Search Console's generative AI performance report counts impressions only: the times a link to your site was shown in AI Overviews or AI Mode, grouped by page, country, date and device. It has no query dimension, so it cannot say what was asked. Clicks from those features are counted with the rest of your organic traffic, in the Performance report under the Web search type, as Google's page on AI features says.

Two of the report's groupings suit a mover. By page, it shows which of your pages Google's AI features linked in a month, the routes page or the storage page. By country, it sorts impressions by the country where the search originated, which for a cross-border mover can include the country at the other end of the route. Neither says who searched, what they asked or whether they booked.

Four counts in one sheet, month by month

The four monthly counts a moving company can keep, what each one counts, what it cannot show, and what to read it beside.
CountWhat it countsWhat it cannot showRead it beside
Panel readingWhether answers to fixed questions name you, recommend you or put you first, by move type and routeAny inquiry or bookingThe change log, and the same month a year earlier
Quote requests by sourceWhat customers say about how they first heard of you, with the route and move typeWhether an answer caused the request, or which answerThe panel's lines for the same routes
AI referralsVisits that arrived from an assistant's answer with the referrer passed onHouseholds that read your name and phoned, or whose referrer was droppedThe page they landed on, and quote forms sent
Generative AI impressionsTimes Google's AI features showed a link to your site, by page, country, date and deviceThe question, the person, the click or the bookingThe page grouping, month on month

Give each month a season mark (busy, quiet, peak week) so a seasonal rise is never read as a change in the answers. When the panel's long-distance lines rise, and more long-distance quote requests name an assistant than in the same season a year earlier, two independent readings point the same way. That is the strongest statement the sheet supports, and it is still not proof that an answer caused a booking.

Which of these belong in a report, and how to set them out, is in the seven numbers worth reporting. If you would rather have a panel run for you, monitoring is $290 a month, which you can cancel in any month: twelve of your lines put to one assistant, Claude, each month, each set beside last month's, with every answer kept verbatim behind the reading.

Common questions

Should we skip the monthly reading in the busy season?

No. Take it on its usual days even when the office is stretched, because the busy-season reading is the one next year's busy season is compared with. If nobody can mark the answers that week, run the questions, keep the answers verbatim and mark them later. A gap in the busy months leaves out the year's most useful comparison.

Some quote requests reach us through a lead marketplace. How do we log their source?

Log two things: the channel the request came through, which is the marketplace, and what the customer says when asked how they first heard of you. The two can differ, since a household may read your name in an answer and then find you on a marketplace. Keep them in separate columns and never overwrite one with the other.

Can Google's generative AI report tell us which questions showed our pages?

No. It has no query dimension. It groups impressions by page, country, date and device, so it can show that your routes page was linked in AI Overviews or AI Mode a number of times in a month, but not what the person searched for. The questions you care about are the ones in your own panel.

Customers say they found us on Google. Could they mean an AI Overview?

They could, and they may not know themselves. Record their words as given and keep "not sure" on the list rather than pressing them. The generative AI report is a separate count of how often Google's AI features showed your pages; set it beside the source answers month by month, and read neither one as the other.

Sources

What Search Console reports is from Google's own help and documentation pages, linked where they are used. No figure on this page comes from our audit; every count in the sheet is your own.

Sources: Search Console Help, generative AI performance report · Google, AI features and your website · how the visibility score is measured

All articles