A weekly website report that writes itself: your options, from free to automated
Short answer: The cheapest way to get a weekly website report is a calendar reminder plus a one-page checklist that pulls six numbers from Google Analytics 4 (Google's free website traffic tool) and Google Search Console (Google's free tool that shows how your site appears in search). If you want the summary written for you on a schedule, a paid tool such as Semrush (a search marketing software subscription) or a scheduled workflow in Ploy (an AI marketing platform that builds and runs websites) can do it, but both cost money and need a human to read the result.
You want to know what changed on your site last week without opening five dashboards. The real problem is not the data. It is that the weekly check slips the first busy week and never comes back.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
The direct answer: pick the smallest report you will actually read, and automate only the part that is boring. For most owners that is six numbers in one email or one page, checked on the same day each week. You can build that for free with Google's tools. A paid or AI tool earns its place only if writing the summary is the part you keep skipping.
This page gives you the six numbers, four ways to produce them from least to most effort, a sample digest you can copy, and a test plan with pass and fail rules. I also show where Ploy fits and when to skip it.
This page may contain affiliate links from which Blur Studio earns commissions.
What goes in a weekly report for an owner
Keep it to one screen. A report with 40 charts does not get read. These six items cover most small-business questions. They match the one-page monthly report idea in our guide to client reporting that ties leads to revenue, but cut to a week.
- Leads: form submits, calls and booking requests this week, counted from your own inbox or CRM (customer record tool), not only from analytics.
- Key events: the actions you told Google Analytics 4 to count as a win, such as a form submit or a click on the phone number. Google calls these key events.
- Top landing pages: the pages people first arrived on, from the Google Analytics 4 landing page report.
- Top search queries: the searches that showed your site, from the Search Console Performance report (clicks, impressions, click-through rate and average position).
- Speed pass or fail: whether the page passes Google's Core Web Vitals (three speed and stability measures) in PageSpeed Insights, Google's free page speed test. Google says a page passes when the 75th percentile of INP (how fast the page reacts to taps), LCP (how fast the main content shows) and CLS (how much the layout jumps) are all in the Good range: INP 200 milliseconds or less, LCP 2,500 milliseconds or less, CLS 0.1 or less. The field data covers the previous 28 days.
- Broken pages: new "Not found" (404) pages listed in the Search Console Page indexing report.
Add one line at the top: "Better, same or worse than last week, and the one thing I will do about it." That line is the report. The numbers just back it up.
Two limits to know. Search Console data reaches Google Analytics 4 about 48 hours after Search Console collects it, and the link keeps up to 16 months. So a report run on Monday morning should treat the weekend as the freshest data you can trust. And analytics undercounts: ad blockers and cookie consent choices hide some visitors, so compare week to week, not against your form inbox to the digit.
Four options from least to most effort
| Option | Cost | What you do each week | Best for |
|---|---|---|---|
| Calendar reminder and checklist | Free, plus about 20 minutes | Open three Google tools, copy six numbers, write one line | Owners who want the habit first |
| Google Analytics 4, Search Console and Looker Studio (Google's free dashboard builder) | Free | Build one dashboard once, open it weekly | Owners comfortable with a one-time setup |
| Semrush | Paid, check the vendor page | Set up a project and its reports once, then review | Teams that already pay for it for search research |
| Ploy scheduled workflow (Ploybook) | Uses AI credits on a paid plan or the Free plan's daily credits | Write the task once, review each output | Owners who want a written summary, not a dashboard |
Option 1: a calendar reminder and a checklist
This is the option people sneer at and the one that works. Pick a weekday and a time. Create a recurring calendar event called "Site check" with the checklist in the event description. Each week, open Google Analytics 4, Search Console and PageSpeed Insights, write six numbers and one sentence in a note or spreadsheet, and close the tabs. It takes about 20 minutes once you know where the numbers are. The cost is your time, and the risk is that the event gets dismissed. If you dismiss it twice in a row, move to option 2 or 4.
Option 2: Google Analytics 4, Search Console and Looker Studio (free)
Looker Studio is Google's free dashboard builder. You connect Google Analytics 4 and Search Console as data sources, drag charts onto one page and share the link. The product is free, so a dashboard needs no paid plan for this job.
Setup takes an afternoon. Build one page with the six items, name it "Weekly", and bookmark it. The honest limit of a dashboard is that it shows numbers and says nothing. You still have to read it and write the one line.
Option 3: Semrush
Semrush is a paid software subscription for search marketing: keyword research, rank tracking, site checks and reports. Its price page showed tiers from a Free plan (10 reports a day) through SEO at $139 a month ($117.33 a month billed annually), Starter at $199 and Pro+ at $299 a month, with Advanced and Enterprise by quote, as of November 2026. The page does not name the currency, and prices change, so check the vendor page. See our Semrush alternatives page for more on what it covers.
Semrush fits when search ranking is the point of the report and you want position tracking across many keywords. It is more tool than a six-number owner report needs, and it does not know your leads. If you do not already pay for it, do not buy it just to get a weekly email.
Option 4: a scheduled workflow in Ploy
Ploy is an AI marketing platform from Ploy, Inc. You chat with an AI agent that builds and updates pages, hosts the site and connects tools. Its reusable workflows are called Ploybooks. Ploy's Ploybooks page lists 47 of them in groups such as SEO and AEO (answer engine optimization, meaning being named in AI answers) and Analytics and Insights, and custom Ploybooks are allowed on every plan. Our Ploybooks explained page covers what they are.
For this job, you describe the report in plain words, for example "every Monday, summarize last week's visits, top pages, top searches and any new broken pages, and flag anything that dropped more than 20 percent", and Ploy runs it on a schedule. Google Analytics 4 and Search Console connect on every plan, including Free, per Ploy's integrations docs (the pricing page's Google row covers Google Workspace tools from Starter, so check the card in your account). The plan facts to know, as of November 2026 on ploy.ai/pricing:
- Free is $0 with 500 AI credits a day up to 2,000. Starter is $50 a month ($480 billed yearly) with 4,000 credits a month. Pro is $300 a month ($2,880 billed yearly) with 24,000 credits a month. Enterprise is by quote and adds done-for-you Ploybook setup.
- Scheduled Ploybook runs use AI credits, and credits do not roll over.
- New schedules end after 90 days by default, with a reminder three days before. You extend them yourself.
- Ploy does not publish a credit cost per run. Its changelog says you can see the expected credits before turning on a recurring Ploybook, so read that number before you switch it on.
Ploy also drafts rather than decides. AI-written summaries need a human to check them before you act on them, especially any "this dropped because" explanation. A model can state a cause with confidence that the data does not support.
A sample weekly digest (numbers are made up)
Here is the shape to copy. The figures below are invented to show the format, not real results.
| Item | This week | Last week | Note |
|---|---|---|---|
| Leads (from inbox) | 9 | 11 | Two form emails landed in spam, check |
| Key events (GA4) | 14 | 16 | Phone clicks down on mobile |
| Top landing page | /services/roof-repair | / | Service page moved up |
| Top query | roof repair near me | roof repair near me | Position 6.2 to 5.8 |
| Speed (PageSpeed Insights) | Pass | Pass | No change |
| New 404s | 1 | 0 | Old /promo page, add a redirect |
One line on top: "Slightly down on leads. Fix the spam issue on the contact form and redirect /promo." That is a useful report in under a minute. Notice that nothing in it needs a paid tool. The automation only saves the 20 minutes of gathering and the effort of writing the line.
Step by step: build the weekly report
- Pick one weekly task. Not "do my marketing". One task: "send me the weekly digest". If you automate three things at once you will not know which one broke.
- Write exactly what it should do. List the six items, the source for each, the day and time, and where the result goes. A sentence like "summarize my site" gives a different answer every week. A list gives the same shape every week.
- Run it once by hand and review. Compare the output with the real Google Analytics 4 and Search Console screens. If a number is off, fix the instruction, not the report.
- Switch on the schedule and note the end date. In Ploy, new schedules end after 90 days by default. Put the end date in your calendar so the report does not silently stop.
- Review for four weeks, then decide. Keep it, trim it, or go back to option 1.
Test plan with pass and fail rules
- Accuracy (pass): in week one, every number matches the source screens within about 5 percent, allowing for the 48-hour Search Console delay. Fail: two or more numbers are off, or a cause is stated that you cannot verify.
- Reading habit (pass): you open the report in at least three of four weeks. Fail: you skip two weeks in a row. Shorten it before blaming the tool.
- Action (pass): the report led to at least one real fix in the month, such as a redirect or a form check. Fail: nothing changed, so the report is decoration.
- Cost (pass): the monthly cost, counting your review time at a rate you choose, is lower than doing it by hand. Fail: credits run out before month end and the schedule stops.
What goes wrong
- Silent stop. A schedule that ends at 90 days or a dashboard whose Google connection expired. Add a weekly "report arrived" check to the calendar.
- Too many numbers. If you have not changed anything for three weeks after reading the report, it has too much in it.
- Wrong numbers trusted. An AI summary can mix up weeks or round badly. Spot check one number each week.
- Analytics blind spots. Ad blockers and consent choices hide some visitors, so trends matter more than totals. See our page on ad blockers and traffic counts.
- No owner for the follow-up. A report that names a problem nobody owns is worse than none. Put a name next to each action.
When to skip the tool
Skip Ploy for this job if you do not otherwise want an AI platform to build or host your site. Paying $50 a month only for a weekly summary is poor value next to a free Looker Studio dashboard. Skip it if credits matter and you cannot afford a schedule that burns them on a quiet site. Skip scheduled runs entirely if you will not review them, because an unread report is a cost with no benefit. Skip Semrush if you do not need rank tracking. If you only need a monthly check, the routine in keeping your website fresh is enough.
A tool is not the better pick if your real problem is that nobody acts on the findings. Fix that first.
How I'd approach this
I would start with option 1 for two weeks, even if I planned to automate. Doing it by hand teaches you which numbers you care about, and that is the part an AI tool cannot choose for you. After two weeks, I would build the free Looker Studio page if I want charts, or try one scheduled workflow in Ploy if I want a written summary, starting on the Free plan so the first test costs nothing. Whichever you pick, review the first four reports against the real screens.
If you need a custom version, with AI agents that use your business knowledge, connections to your CRM and calendar, a half-built flow finished, or ongoing care, Blur Studio builds that. See what the business work includes.
First-week plan. Day 1: decide the six numbers and the weekday. Day 2: find each one in Google Analytics 4, Search Console and PageSpeed Insights and write down the click path. Day 3: build the sheet or the Looker Studio page. Day 4: run the first report and compare it with the real screens. Day 5: decide whether automation is worth testing, using the pass and fail rules above. If you also keep a site health list, a site health audit you can hand to a client shows the less frequent check.
For the leads side of the report, see how to check if your website has SEO problems.
A closely related page covers the same ground from another angle: Bot Traffic Inflating Your Numbers? How to Filter It Out.
Related guide: Search Console and GA4 in One Place: Options.
Questions people ask
How do I get an automatic weekly report of my website traffic?
The free route is a Looker Studio dashboard fed by Google Analytics 4 and Search Console, plus a recurring calendar reminder to open it. A paid route is a tool such as Semrush, or a scheduled workflow in Ploy that writes a summary. Start with the six numbers listed above.
Is Looker Studio free?
Looker Studio itself is free. For a six-number weekly report the free version is enough.
What does a scheduled Ploy workflow cost?
Ploy's plans, as of November 2026, are Free at $0, Starter at $50 a month, Pro at $300 a month and Enterprise by quote. Scheduled runs use AI credits, Ploy does not publish a credit price per run, and credits do not roll over. Check the expected credits shown before you turn on a recurring workflow. See Ploy pricing.
Why did my scheduled Ploy workflow stop?
New schedules end after 90 days by default, and Ploy sends a reminder three days before. You extend the schedule yourself. It can also stop if credits run out, since runs draw from your credit balance. Put the end date in your calendar.
Can I trust an AI-written weekly summary?
Trust the numbers only after you compare them with Google Analytics 4 and Search Console in the first few weeks, and treat any stated cause as a guess to check. AI summaries can mix up date ranges or give a reason the data does not show. A human should read it before acting.
What should a weekly website report include?
Six items are enough for most small businesses: leads from your own inbox, Google Analytics 4 key events, top landing pages, top search queries, a speed pass or fail from PageSpeed Insights, and new broken pages from Search Console. Add one line on what changed and what you will do.
Do I need a weekly report if my site rarely changes?
A monthly check may be enough. The monthly routine in keeping your website fresh covers it. Go weekly when you run ads, publish often, or just changed the site and want to catch problems quickly.
Does the report miss visitors?
Yes, some. Ad blockers and cookie consent choices hide part of your traffic from analytics, so judge direction week to week rather than exact counts. See ad blockers and traffic counts.
More in this topic: Websites: simple stats and reports for owners and clients (9 guides) →