A small business dashboard can be one sheet with seven rows: clicks and impressions from Search Console, views, calls, messages and directions from the Google Business Profile, website clicks from the profile set beside key events on the site, and enquiries by source from your own ledger. Fill it once a month in a fixed order and you can answer "what changed, and where did the trail go cold" in half an hour. If you run a studio, a class-based business or any local service where people ring, message or walk in, this is a practical way to see search, maps, calls and messages together.
Questions first, numbers second
A dashboard that starts from available metrics drifts into a pile of charts. Start from the questions the owner actually asks and keep only the numbers that answer them.
- Are people finding us on Google Search and on the map?
- When they find us, do they act: call, message, ask for directions, open the site?
- Once on the site, do they use the enrolment form, the phone button or the message button?
- How many of those actions end in a person who actually joins?
Example scenario: a small dance school sees fewer sign-ups for its autumn beginner classes. Without a sheet, the owner blames the weather or the timetable. With one, the rows might show that searches and profile views held steady while calls fell, which points to the profile or the phone line and not to demand. The sheet does not prove the cause, it narrows where to look.
A rule for adding a row
Before any new metric earns a row, write what you would do differently if it moved up or down. If you cannot name an action, the metric stays out.
Seven rows on one page
| Row | Number | Source | What it tells you |
|---|---|---|---|
| 1 | Clicks from search | Search Console | Visits that began on Google Search |
| 2 | Impressions in search | Search Console | The number of times a link to the site was seen |
| 3 | Profile views | Business Profile | How many people viewed the profile on Search and Maps |
| 4 | Calls and messages from the profile | Business Profile | Taps on the call button, and message conversations when the profile shows them |
| 5 | Direction requests | Business Profile | People who asked for directions |
| 6 | Website clicks from the profile, beside site key events | Business Profile and Analytics | How many crossed to the site and how many acted there |
| 7 | Enquiries by source, and who joined | Your ledger | Real people and where they heard of you |
Messages share row 4 with calls and appear only when they apply to your business; write "n/a" if the profile does not show them. Bookings are an optional extra: add them to row 6 as a note if you use them.
Search: taking only what you need from Search Console
The Search Console performance report help page (Opens in a new tab) describes impressions as the times a user has seen, or potentially seen, a link to your site in Search, Discover or News. A click is a click that sends the user to a page outside Google Search, Discover or News. Click-through rate is clicks divided by impressions. Average position is a relative ranking where 1 is the topmost position. The page says you can add a filter to split the data by device or another category, and that clicks, impressions and position are assigned to a canonical URL.
The page does not set out date ranges or how long the data is kept in the section reviewed here, so read those in the product itself and use the same date range for every pull.
Two numbers are enough to start
Clicks and impressions give you click-through rate for free. Average position is a blended number that is hard to act on for a small local business. For a deeper reading of queries and pages, see the Search Console performance report guide.
Split brand searches from the rest
Practical suggestion: note how many clicks come from queries that contain the school's name and how many do not. People who type the name already know you. People who type a class name are the new-visibility signal. The query list in the report allows this split to be done by hand once a month.
Maps and profile: views, calls, directions, website clicks
The Business Profile performance help page (Opens in a new tab) says you can reach performance by going to your profile in Search and choosing "Performance", or in the Maps app by tapping "Business" and then "See more" next to "Performance". If your interface is not in English, the labels may differ. It states that performance data is available only for verified profiles and that you must be signed in to the Google Account tied to the profile.
| Metric | Definition on the page | Reading note |
|---|---|---|
| Views | How many people viewed the profile on Search and Maps | The page says this can be lower than the view numbers seen elsewhere on the profile and in email notifications |
| Calls | Times a customer clicked the call button | A phone number must be added to track it |
| Messages | Number of different conversations through messages | Shown only if it applies |
| Bookings | Bookings people completed | The page says they must be managed through a booking provider |
| Directions | How many people asked for directions | Meaningful for a place people visit |
| Website clicks | Times people clicked the website link on the profile | Compare with key events on the site |
The page adds that a person is counted once a day for unique counts, that the searches metric is updated at the start of each month and can take up to 5 days to appear, and that insights may not be available for every profile. Pull the month-end numbers a week into the next month.
What a dance school should expect from the profile
Example scenario: a dance school has a studio people visit, so direction requests matter, and parents phone to ask about class levels, so the call tap matters. Parents also message to ask about class levels, so the message count sits beside the call count in row 4. Parents also message to ask about class levels, so the message count sits beside the call count in row 4. Parents also message to ask about class levels, so the message count sits beside the call count in row 4. A school that mainly teaches online would find direction requests close to meaningless and could leave the row empty with a note.
The website: key events and source tags
The Google Analytics key events page (Opens in a new tab) defines a key event as an event that measures an action particularly important to the success of your business. You create or identify an event for the action and mark it as a key event, and any event you collect can become one. Treat the enrolment form, the call button and the message button as key events. For the phone and chat taps, see GA4 click to call and chat key events.
Source tags that stay readable
The Google Analytics manual tagging page (Opens in a new tab) lists utm_id, utm_source, utm_medium, utm_campaign, utm_source_platform, utm_term, utm_content, utm_creative_format and utm_marketing_tactic. It says you should always use utm_source, utm_medium and utm_campaign, and that missing parameters produce (not set) values in reporting. Parameter values are case sensitive, so utm_source=google and utm_source=Google differ. The parameters start after a question mark and each pair is separated by an ampersand.
Practical suggestion: keep a one-page list of every tag you use, always in lower case. A flyer link, a newsletter link and a social bio link then show up under names you can recognise at month end.
The ledger row: from enquiry to a person in class
The last row decides whether the first six matter. It counts real people. For a dance school it can be as simple as a notebook or sheet column set.
| Column | Values | Use |
|---|---|---|
| Date | Day of first contact | Month grouping |
| First contact | Call, message, form, walk-in | Type of action |
| Heard from | Map, search, friend, flyer, social, other | Source share |
| Trial class | Booked, attended, no show | Mid-funnel check |
| Outcome | Enrolled, undecided, declined | Real conversions |
If the answer is blank
Record "unknown" and do not assign it to a source. A large unknown share means the source split is weak, and the sheet should say so.
A thirty minute month-end routine
- Wait until the first week of the new month, so the monthly search data in the profile has appeared.
- Copy the Search Console clicks and impressions for the previous calendar month.
- Copy profile views, calls, messages, directions and website clicks for the same dates.
- Copy the key event counts for the site.
- Count enquiries and enrolments from the ledger by source.
- Write an arrow next to each row: up, down or flat.
- Pick at most two rows that moved and note a likely cause.
- Choose one action for next month.
Decision rules: which movement opens which question
| Pattern | First place to look |
|---|---|
| Impressions and clicks both down | Search visibility: recent site changes and the titles people see |
| Impressions flat, clicks down | How the result appears in search |
| Profile views flat, calls down | Opening hours, phone number, profile details |
| Website clicks up, key events flat | The site itself: does the form open, is the number tappable |
| Key events up, enrolments flat | Response speed and the trial class process |
| Everything flat | Plan one small test for next month |
A note to the team after each review
Send one short note after every month-end review: which number moved, the one action chosen and who owns it. Keep it to three sentences. A note shared with the instructors and the front desk turns the ledger from a chore into something with a visible purpose.
A decision log under the sheet
Add a small log: date, action taken, expected effect and the number to watch next month. After three months the log shows which action was tied to which movement. Without it, the sheet only records history and cannot be used to trace decisions back.
A term in the life of the sheet
Example scenario: the dance school opens the sheet in the first week of October. Search clicks rose, profile views held, calls fell, and the ledger shows fewer trial class bookings. The owner follows the decision table, checks the profile and finds the listed weekday opening hours no longer match the new timetable. The chosen action for November is to correct the hours and note the date. In December the calls row is read again. The owner writes only that calls recovered after the change, not that the hours were definitely the cause.
When two sources disagree
Website clicks on the profile and sessions in Analytics are measured by different systems. Do not force them to match. Read each one as a direction and look at how large the gap between them is, month to month.
Where to go next: reports and tools
When the sheet outgrows copy and paste, the same seven rows can move into a dashboard tool. For connecting Search Console and Analytics there, see the Looker Studio SEO dashboard guide. For a fuller monthly SEO report, see the monthly SEO report template. The row layout stays the same, only the copying is automated.
Reading small counts without fooling yourself
A studio may log a few calls and a few enrolments in a month. Ratios built on counts that small jump around. If two of three trial class visitors enrolled, writing "sixty-six percent" suggests a stable rate that does not exist. Write the raw counts: three trial classes, two enrolments. A single month supports no claim of statistical significance, and a three-month total is a steadier basis.
A sentence template for each row
Give every row one sentence that carries both the observation and its limit: "Calls from the profile fell against last month, but the counts are small, so we are not drawing a conclusion yet." The sentence keeps the sheet honest when the numbers are tempting.
Is this a good number or a bad one
The first filled sheet raises the question of whether the numbers are good. The answer lies in your own history, not in an outside average. Month one is a starting point, month two shows direction and month three shows a pattern. The documentation offers no benchmark by business type, so compare your numbers only with your own earlier months. Another studio's numbers may be interesting, but they are not a target.
A fall in a number is not always bad news either. If impressions fall while clicks hold, the link may be reaching people with more relevant searches. That is one reading among several, so write it in the notes column as a possible explanation and not as a finding.
Keep observations apart from explanations
Begin each note with the word "observation" or "possible explanation". "Calls from the profile fell" is an observation. "Calls fell because the opening hours were out of date" is a possible explanation. Separating the two at month end stops a guess from being read as a fact the next time someone opens the sheet.
Last, remember that the main output of the sheet is the decision it produces. If the table does not tell you what to do next month, redesign it. At each month end, one action should be chosen, dated and assigned to a named person.
A tag list that stays tidy
The parameter names here come from the Google Analytics tagging page. The values are your choice, all in lower case, and each place always uses the same tag.
| Place | utm_source | utm_medium | utm_campaign |
|---|---|---|---|
| Studio flyer | flyer | autumn-classes | |
| Email signature | signature | general | |
| Social bio link | social | profile | general |
| Partner school poster | partner-poster | autumn-classes | |
| Newsletter | newsletter | term-start |
Because parameter values are case sensitive, the lower-case rule in the table has to hold across every link, or one source appears as two rows in the report.
The front desk script
The ledger works only if someone asks. Give the front desk one sentence to use with every new enquiry: "How did you hear about us?" Record the answer in the ledger in the person's own words, then group the answers at month end. When the answer is "I saw you on the map", file it under the map and not under search.
Building the sheet in stages
You do not need a perfect sheet in month one. Practical suggestion: build it in three passes.
| Month | What you do | Purpose |
|---|---|---|
| First | Fill the seven rows, write "none" where a source is missing | Fix the layout and the rhythm |
| Second | Add the arrow and note columns | Start comparing months |
| Third | Read the three-month pattern and choose one action | Tie decisions to the numbers |
Term timetables and seasons
A class-based business works to terms and school calendars. Write the term dates in the note column: start of term, half-term, holidays, showcase week. A month with a holiday should be compared with the same holiday period in an earlier year, not with the month before. The documentation offers no seasonal calendar for studios, so your own previous terms are the only valid reference.
Who owns the accounts
Write down which Google account owns the profile, Search Console and Analytics. If a previous employee or a freelancer set them up, move ownership to a business account. The Business Profile page says you must be signed in to the Google Account associated with the profile to check performance, so an unreachable account means a dashboard with a hole in it.
A quarterly look back
Once a quarter, put three months side by side. The purpose is to see patterns that a single month hides. Check whether any row moved in the same direction for three months, whether enquiries and enrolments rose or fell together, and whether any source in the ledger is shrinking or growing. Then decide one larger change for the coming quarter, such as rewriting a class page or updating profile photos. Record the decision and the date so that the next quarter can check it.
Questions for the quarterly look
- Which row moved the same way for three months in a row?
- Did enquiries and enrolments move together?
- Which source in the ledger grew and which shrank?
- What did we change in the quarter, and on which date?
- What is the one larger change for the next quarter?
When a row stays empty
Empty rows are normal in the first month. Use this table to find out why.
| Empty row | Likely cause | Check |
|---|---|---|
| Calls from the profile | No phone number on the profile | The help page says a phone number must be added to track this metric |
| All profile metrics | The profile is not verified | The page says performance data is available only for verified profiles |
| Messages and bookings | Not applicable to the business | The page says only metrics that apply to your business appear |
| Key events on the site | Event not marked | Mark the event that measures the action as a key event |
| Clicks from search | Site not added in Search Console | Confirm the property exists and the report opens |
| Enrolments | No ledger | Add a "heard from" column today |
Limits and mistakes
Mixing date ranges
One month as a calendar month and the next as thirty days breaks the comparison. Use calendar months from every source.
Reading tiny movements as trends
A studio with a handful of calls a week can see large swings from a single afternoon. Group three months before calling anything a trend, and avoid claims of statistical significance.
Untidy source tags
Mixed case in tags splits one source into two rows. Fix the casing rule once.
Counting taps as people
A call tap shows interest, not a student. The ledger row is the check on that.
Handing over the reading
If an agency or friend built the accounts, make sure the business owns them. Reading the sheet stays with the owner.
What the sheet cannot do
The sheet does not prove cause and effect. Two numbers that move together may be unrelated. It raises questions, and your own observation and small changes provide the answers.
Checklist
- Seven rows and their sources are written on one page.
- The profile is verified and has a phone number.
- Calls, form submits and message taps are key events and have been tested.
- Tags are lower case and listed in one place.
- The ledger has a "heard from" column.
- Every pull uses the same calendar month.
- The review happens in the first week of the month.
- One action is chosen each month.
Frequently Asked Questions
How many numbers should a small business dashboard have?
The documentation gives no count. Keep a number only if you can say which action you would take when it moves. Seven rows is a workable start.
Where do I find Business Profile performance?
According to the Business Profile help page, go to your profile in Search and choose Performance, or in the Maps app tap Business and then See more next to Performance. Labels may differ in other interface languages.
Why are my profile views lower than I expected?
The help page says the number of views in the Performance report might be lower than the number of views you find on your profile and in email notifications.
Can I treat calls from the profile as new students?
No. The metric counts taps on the call button. Use the ledger to see who actually joined.
What do missing UTM parameters do?
The Google Analytics help page says missing UTM parameters result in (not set) values in reporting, and it advises always using utm_source, utm_medium and utm_campaign.
When should I pull the month-end numbers?
The profile help page says the searches metric is updated at the start of each month and can take up to 5 days to show up, so a pull in the first week of the new month is a practical choice.
Conclusion
A one-page dashboard for a small business holds seven rows: Search Console clicks and impressions, profile views, calls, messages and direction requests, website clicks beside site key events, and enquiries by source from your ledger. Pull the same calendar month from each source in the first week of the next month, read movements as patterns and pick one action. Small counts carry uncertainty, so write that on the sheet.
If the review points to pages or articles that need to be written, see the content writing service.
Post a comment
Please log in to leave a comment. Login