Dated SERP or answer capture
Save a screenshot or note with date, market, device, query wording, and visible source links. Treat location and personalization as caveats.
AI search reporting template
AI Search Visibility Log Template
Keep a weekly, evidence-first record of AI search and GEO visibility observations: answer mentions, page changes, Search Console context, crawlability checks, and safe next actions. The log is for review and prioritization, not for claiming guaranteed AI answer placement.
Copyable Weekly Visibility Log
Paste this markdown into a site operations note, GitHub issue, or agent workflow. Fill it with real evidence only: dated screenshots, public URL checks, Search Console rows, reviewed page changes, and visible answer observations.
# AI Search Visibility Log
Week of:
Site:
Reviewer:
Pages reviewed:
Search Console range:
Known site changes:
## 1. Weekly Summary
- Main observations:
- Strongest evidence:
- Weakest or uncertain evidence:
- Pages that need review:
- Safe next action this week:
## 2. Evidence Register
| Date | Query or prompt | Platform or search surface | Page observed | Evidence link or file | Mention, citation, or answer note | Confidence | Follow-up |
| --- | --- | --- | --- | --- | --- | --- | --- |
| | | | | | | Low / Medium / High | |
## 3. Page Change Log
| URL | Change made | Reason | Published date | Reviewer | Evidence to compare later |
| --- | --- | --- | --- | --- | --- |
| | | | | | |
## 4. Crawlability And Indexability Checks
| URL | Status | Canonical | Robots/indexing note | Sitemap present | Structured data note | Issue |
| --- | --- | --- | --- | --- | --- | --- |
| | 200 / redirect / blocked / error | | | Yes / No | | |
## 5. Answer Quality Review
- Does the page answer the main question directly?
- Is the evidence visible and original where possible?
- Are limitations and assumptions clear?
- Is the author, publisher, or editorial context easy to inspect?
- Is there a useful asset such as a tool, template, checklist, table, or example?
- Are related pages internally linked?
## 6. Safe Next Actions
| Action | Owner | Evidence | Risk | Due date | Status |
| --- | --- | --- | --- | --- | --- |
| | | | Low / Medium / High | | |
## 7. Blocked Or Rejected Actions
- No artificial pageviews.
- No ad clicks, ad tests, or click requests.
- No fabricated screenshots, rankings, AI answer mentions, customer data, or analytics.
- No claims that a change guarantees rankings, AI Overview inclusion, chatbot answers, revenue, or AdSense approval.
- No bulk query-variant pages or unreviewed AI publishing.
## 8. Next Review
- What to compare next week:
- URLs to recheck:
- Evidence still missing:
- Issue or PR links:What To Treat As Evidence
AI search visibility is noisy. Personalization, location, freshness, query wording, and retrieval systems can change what a user sees. Use the log to preserve evidence and uncertainty before deciding whether a page needs content, technical, or internal linking work.
Search Console row
Record query, page, clicks, impressions, CTR, position, date range, and comparison range when traffic behavior is part of the observation.
Published page change
Keep the exact URL, publish time, change summary, reviewer, and PR or issue link so later movement is not guessed from memory.
Crawlability check
Confirm status code, canonical, robots access, sitemap inclusion, and visible structured data before treating visibility as a content problem.
Weekly Review Workflow
| Step | Operator check |
|---|---|
| Capture evidence | Log only observations you can point to: screenshots, Search Console exports, public URL checks, PRs, or dated manual notes. |
| Separate signal from hypothesis | Label uncertain AI search or GEO observations as hypotheses until you have repeated evidence or supporting Search Console movement. |
| Review the page | Check whether the page has a direct answer, visible evidence, limitations, trust context, crawlable structure, and a useful next action. |
| Choose safe work | Turn the log into small page improvements, internal links, metadata reviews, or crawl fixes. Keep ranking and AI placement claims out of the task. |
Safe Use Boundaries
GEO here means generative engine optimization readiness: making pages clearer, more trustworthy, easier to crawl, and more useful to people. Do not turn the log into proof of placement or a reason to publish thin query variants.
Allowed
Clarify answer sections, add original examples, document limitations, improve internal links, fix crawl blockers, and open small issues with evidence.
Needs review
Title rewrites, page merges, schema changes, template changes, monetization changes, and any conclusion based on a single AI answer observation.
Blocked
Fake analytics, fabricated screenshots, invented AI mentions, artificial traffic, ad clicks, guaranteed placement claims, and bulk pages made only for query variants.
Related Tools And Templates
Start page-level review with the GEO Readiness Checklist, compare Search Console periods with the AI Overview CTR Impact Tracker, verify sitemap access with the Sitemap Checker, and draft cautious review prompts with the Hermes SEO Agent Prompt Pack.
FAQ
What is an AI search visibility log?
It is a weekly record of AI search and GEO observations, supporting evidence, page changes, crawlability checks, answer mentions, and safe follow-up actions. It helps operators avoid guessing from memory.
Does this template prove AI Overview or chatbot visibility?
No. The log preserves evidence and uncertainty. It cannot prove that an AI Overview, chatbot answer, or search feature caused a traffic change by itself.
What evidence should I record?
Record dated screenshots, query wording, visible source links, Search Console rows, page change notes, crawlability checks, and issue or PR links. Do not add fabricated rankings, screenshots, mentions, or analytics.
How often should I update the log?
A weekly cadence is usually enough for small publisher sites. Add an extra note when a major page change, indexing issue, or unusual Search Console pattern needs evidence preserved.
What should I do after finding a weak AI search signal?
Improve the page for humans first: clarify the answer, add visible evidence, explain limits, fix crawl blockers, add useful templates or tools, and strengthen relevant internal links.
Last updated: May 20, 2026.