Monthly website report: what you should get every month

You pay for website maintenance every month. The invoice arrives right on time. What almost never arrives is the answer to a simple question: is the site better or worse than last month?

At most companies, that answer only shows up when something breaks. The form stopped sending three weeks ago, the site got slow after an update, Google traffic dropped, and nobody said a word. The monthly report exists so you find out first. In this guide I show what it needs to include, which numbers to ask for, and how to tell when the report is hiding more than it shows.

Why most reports are useless

The most common report I see is a task list: “plugins updated,” “backup done,” “footer tweak.” It proves someone worked. It doesn't prove the site is in good shape.

A useful report answers business questions, not backstage ones. Did the site stay up? Was it fast for mobile visitors? Did it show up for people searching for what you sell? Did it bring in leads? For each answer: a number, last month's number, and what comes next.

The difference seems small. In practice, it's the difference between paying for hours and paying for a site that works. A task list measures effort. A compared number measures results.

The 5 blocks every monthly website report needs

A good report fits on one or two pages. It has five blocks, always in the same order, so you can compare one month to the next without effort.

1. Uptime. How long the site was down this month, how many times it went down, and how long it took to come back.
2. Speed. Google's three Core Web Vitals metrics on mobile, with the status of each.
3. Maintenance and security. What was updated, what's still pending and why, when the last backup was tested, and when the security certificate expires.
4. Search and AI. Google impressions and clicks, the pages that brought in the most visits, and the site's presence in Google's AI answers.
5. Leads. How many forms, WhatsApp clicks, or quote requests the site generated, and whether any of those paths failed this month.

At the end, a paragraph on what happens next month and what depends on you. That's where the report stops being an account of the past and becomes a plan.

Speed: the number that slips without anyone noticing

Sites don't get slow all at once. They get slow little by little: a heavy image up top, a new plugin, one more ad script. Each change seems small. Together, they make visitors give up before the page loads.

Public data shows this is a common problem. According to HTTP Archive's Web Almanac 2025, published in January 2026, only 48% of sites pass Core Web Vitals on mobile. On desktop, 56%. The number has improved: in 2021 it was 32% on mobile. But it still means more than half of sites deliver an experience Google itself rates below good on small screens.

The weakest metric is LCP, the time until the largest element on screen appears, usually the main photo or the headline. According to the same study, only 62% of sites have good LCP on mobile. The other two metrics do better: 77% have good tap responsiveness (INP) and 81% have a stable layout (CLS).

What to ask for in the report: all three metrics, with real user data. The Search Console Core Web Vitals report uses Chrome data from the last 28 days and defines good as an LCP of up to 2.5 seconds, an INP of up to 200 milliseconds, and a CLS of up to 0.1. If any metric drops out of “good,” the report needs to say which page got worse and what will be fixed. I showed how much speed affects sales in landing page speed and conversion.

Search and AI: the block that changed in 2026

Until last year, the search block was simple: impressions, clicks, and position on Google. That still matters. But a growing share of searches ends in an answer written by Google's AI, and until recently site owners had no way of knowing whether they showed up in it.

That changed. On June 3, 2026, Google announced generative AI performance reports in Search Console, with separate views for AI Overviews, AI Mode, and Discover's AI features. The report shows how often your site's pages appeared in those answers, which pages, in which countries, and on which devices. According to a note in the same announcement, the feature has been available to every site worldwide since August 31, 2026.

One important caveat: the announcement talks about impressions, not clicks. The report tells you whether your site appeared in the answer, not how many people clicked through from it. Still, it's Google's first official number on AI visibility, and it needs to be in your monthly report from now on.

What to ask for: Google impressions and clicks compared to the previous month, the five pages that brought in the most visits, and impressions in AI answers, with the pages that appeared. If visits dropped while AI impressions went up, that's a different conversation, as I explained in site traffic dropped because of Google's AI.

Leads: the only number that pays the bills

Speed and Google rankings are the means. The end is the lead: the form submitted, the WhatsApp click, the quote request. It's the block most often missing from reports, and the one that matters most to whoever is paying.

It has two parts. The first is the count: how many leads the site generated this month and which pages they came from. The second is the check: someone tested whether the form reaches the right inbox, whether the WhatsApp button opens the chat, and whether the phone number is correct. A broken form doesn't show an error on screen. It just stops delivering, and you only find out when you notice the phone has gone quiet.

If the report shows visits but not leads, ask for them. If the vendor says they can't measure it, that's the first problem to solve.

Signs the report is hiding something

A few patterns come up often and deserve a direct question:

• Only tasks, no numbers. You know what was done, not what changed.
• Numbers without comparison. “5,200 visits” means nothing without the previous month.
• Only the numbers that went up. If everything improves every month, someone is choosing what to show.
• Nothing pending. Every site has something waiting: an update that breaks a plugin, a slow page. A report with nothing pending is an incomplete report.
• Tools in the vendor's name. If Search Console and your analytics are under the agency's email, you can't verify anything and you lose the history if you switch companies.

That last point is the most serious. Access needs to be in your company's name. The report summarizes, but the source needs to be in your hands. I wrote more about what goes into the contract in how much website maintenance costs per month.

How we do it at the Studio

At the Studio, code, files, and access stay in the client's name, including the domain, hosting, and Google tools. That way, any number we show can be checked at the source. The maintenance price is fixed after discovery, and the deadline is written into the contract.

The sites we build in custom code ship with SEO and GEO from day one: structured data, sitemap, llms.txt, and robots that let AI crawlers in. One example is the Conversão Visual sales page, which scored 99 out of 100 on Google Lighthouse in October 2026. A high score at launch is the starting point. The monthly report is what makes sure it doesn't drop without anyone noticing.

And every system we deliver ships with an AI agent that runs daily, flags failures, suggests improvements, and checks that the data makes sense. It's the kind of watch that catches a page that got slow or a form that stopped working before the month is over.

If you pay for website maintenance today and can't say whether the site got better or worse, that's exactly what our maintenance and evolution service is for.