SEO reporting means recording, on a fixed schedule, where your website stands in search, what changed since the last period and why. A useful weekly report fits on one page: clicks and impressions, positions for your business terms, the pages that moved most, indexing, new errors, and every notable change with its cause. An AI employee builds it by pulling the data read-only from the Search Console API, the Bing Webmaster Tools API and your analytics, saving every raw response and tying each statement to it. Two limits belong in every report: per Google, Search Console data normally arrives after two to three days, and not every query is shown.
At my business, Sebastian, my AI employee for SEO and GEO, reads Search Console and Bing Webmaster Tools through their interfaces, read-only, and files every raw output in a dated job folder. Setup is covered in Setting Up Google Search Console and Submit Your Site to Bing: Setup and IndexNow; everything on SEO and AI search is on AI SEO for Google and AI Search.
What an SEO report should contain
A good report tells you whether you need to act.
The last row separates a report from a data dump. "Clicks down 18 percent" is a number. "Clicks down 18 percent, almost all of it on one page whose title changed on Tuesday" is a finding. Without evidence, the line reads "cause unknown".
Search Console stops at the click; what search visitors do next comes from analytics. I run Umami myself, without cookies; how to tag traffic sources cleanly is in UTM Parameters: Examples and Common Mistakes.
What stays out: vanity metrics
Vanity metrics look good and support no decision. Four common ones:
- Site-wide average position. Google itself calls position "a complex metric that can be misleading if you don't understand the subtleties". Add new queries at position 40 and the average drops, although the site grew.
- Impressions without clicks or cause. An impression only means your link was on a results page.
- Third-party estimates for your own site, such as estimated traffic or "ranking keywords". In my SE Ranking test, the German database knew 19 search terms for kevinwelter.com, while Search Console counted 8,144 in the 28 days to 16 October 2026.
- Total pageviews. They mix search, newsletter, social and direct visits.
The rule behind it: every number in the report answers a question that was set before the data came in.
Data sources and how an AI employee reads them
Grant an AI employee the smallest access that does the job, enforced technically, not just by instruction. Documentation as of November 2026.
Google Search Console API. Search Analytics returns clicks, impressions, CTR and position grouped by date, query, page, country or device, up to 25,000 rows per request. The API can also submit and delete sitemaps and remove sites, but only with the full webmasters scope; webmasters.readonly blocks that. With dataState: "all" you also get fresh, unfinished days, and the response marks the first incomplete date. The quota is 1,200 queries per minute per site; Google names page plus query grouping, long date ranges and repeated requests as the expensive ones. So pull the week once and store it.
URL Inspection. The same API checks the index status of individual URLs, up to 2,000 a day per site, but only for the version in Google's index; there is no live test. Requesting indexing for regular pages only works in the interface; when that helps is in Google Indexing Request: When It Helps.
Bing Webmaster Tools API. Access via OAuth, which Microsoft recommends, or an API key issued per user for all their verified sites. Read-only means OAuth with the Webmaster.read scope; with Webmaster.manage the same interface can also submit URLs. The report needs query stats, page stats, the click and impression trend and crawl issues.
Web analytics. One Umami stats request returns pageviews, visitors, visits, bounces and total time, optionally against the previous period and filtered by referrer.
SE Ranking. A third-party database adds search volume, competitors and other sites' backlinks. For your own positions Search Console stays the source; in my test, the rank tracker was off by 7.6 places on average for 11 comparable terms. The numbers are in SE Ranking Review: API, MCP and Real Numbers.
SEO automation: the weekly run, step by step
SEO automation pays off where work repeats under fixed rules, with decisions left to a person. The weekly report is that kind of work.
- Set the window. Seven full days ending at least three days ago, against the seven days before.
- Pull and store raw. Every response saved as a dated file before any calculation.
- Check totals. The reference is the query without the query dimension. Grouped by query, anonymised queries are missing, so the row sum is lower. Say so in the report.
- Find the changes. Pages and terms with the biggest gap to last week. On a small site, three fewer clicks is noise.
- Check the cause. Your own change, per the change log? A ranking update on the Status Dashboard? Page still indexed? A holiday?
- Write it up. Finding, evidence, cause, consequence. Guesses are labelled as guesses.
- Propose, don't ship. Nothing goes live without me.
How findings like these turn into a full audit is in How to Run an SEO Audit With AI.
Before and after: the change log
The weekly report shows what moved. Whether a change worked shows only in a measurement planned beforehand. The change log records:
- Go-live date and time, plus which pages changed and how.
- Test pages and a control page that stays unchanged and gets no new links. What counts is the change on the test pages minus the change on the control page.
- Locks. Testing content? Title, description and main heading stay as they are. Testing the snippet? The content stays. Change two things at once and you won't know which worked.
- Window, query and hypothesis, fixed before the start. No effect is a result too.
That is how AI Employee With and Without an SEO Tool runs: three test pages, one control page, title, description and main heading unchanged, 28 days of measurement starting on the third day after go-live. Every running test gets its own line in the report, so nobody edits a test page in passing.
SEO report template with sample numbers
Made-up numbers for a hypothetical painting business with about 40 pages. Copy the structure, not the values.
Weekly SEO report example.com, 26 Oct to 1 Nov vs. 19 to 25 Oct (sample numbers)
Finding 1: 24 of the 29 lost clicks come from /exterior-painting; "exterior painting cost" went from 4.1 to 7.8. Cause unknown: no change of ours, nothing on the Status Dashboard. Proposal: watch two weeks.
Finding 2: Since the rebuild on 28 Oct, /interior-painting shows "Crawled - currently not indexed" in URL Inspection. Proposal: check internal links, request indexing (needs approval).
Running test: title test on /gutters since 20 Oct, control page /fences, evaluation from 17 Nov. Do not edit either page.
Limits: data final up to 1 Nov. Grouped by query, 31 % of clicks are missing.
Limits that belong in every report
- Delay: Search Console data normally arrives after two to three days; the newest values can be preliminary.
- Gaps: rare queries are left out of the table for privacy, but counted in the totals.
- Retention: 16 months in Search Console, up to six months in Bing. Store your exports.
How AI answers differ from search results is explained in What Is Generative Engine Optimization?. How to measure citations in AI answers is in AI Visibility Tracking: How I Measure It.
SEO reporting tools or your own AI employee?
Upfront: I have a partnership with SE Ranking, and I earn a commission through my link to SE Ranking*. According to SE Ranking, its report generator builds reports from templates, sends them to clients on a schedule and exports PDFs, and it is available in all pricing packages (November 2026). That fits if you report to clients and your tracking data already lives there. An AI employee does something different: it reads raw data, checks totals, looks up causes in the change log and writes the finding. The two combine well.
* Affiliate link: if you subscribe or buy credits through this link, I earn a commission. Your price stays the same. I have a partnership with SE Ranking.
Frequently asked questions
What should an SEO report include?
Clicks and impressions against the previous period, key term positions, the pages that moved most, indexing, new errors, and a documented cause for each notable change.
How often should you run an SEO report?
Weekly for errors and unusual changes, monthly for trends. Daily data from a small site is mostly noise.
Can AI automate SEO reporting?
Yes, with read-only access to Search Console, Bing and analytics, if every number comes from a stored raw response. Without access, it guesses.
What permissions does an AI employee need?
Read-only: webmasters.readonly for Google, OAuth with Webmaster.read for Bing, an analytics account without write access. Submitting and changing settings stay with you.
Where to go from here
List the ten to twenty terms that matter to your business, start a change log, and build one report by hand from the template. To hand the routine to an AI employee: Sebastian's template is in my community AI Employee Framework, and his page shows how he works. To look at your site together, book a strategy session on the contact page. A common finding is pages nobody links to: Internal Linking: Finding the Links You Miss. To make the report show topics rather than single pages: Pillar Pages and Topic Clusters. Structured data errors are covered in Schema Markup Checker: Which Tool Tests What. If the report flags a thin page: SEO Content Writing with AI. Why llms.txt has no place in the report: llms.txt: Hype vs. Evidence.
