Save project analyses with a title, kind, structured body and provenance. Reopen findings and proposed next steps without losing the source dates, coverage or limitations.
Saved project history · Structured reports · Access-controlled links
Acme · Fictional sample project
External analysis · 08 Oct 2026
The sampled repair page is missing a meta description.
Review the page metadata. No change has been executed.
Sample states only. These controls do not run research or contact a provider.
Read business context and the available search or audit evidence. Name the date and scope of the observations you use.
Create an external report in the app or from an agent. Separate findings from proposed actions, and include source provenance and uncertainty.
Browse saved reports and open their bodies and provenance. Copy a project link for another member with access.
The report body can retain structured findings and proposed next steps. Provenance records where the analysis came from; it is not a substitute for the original observations.
AI research and Site Audit save application-generated reports. Agents can also save external analyses through the same project API.
Yes. The create_agent_report MCP tool and research-workspace REST API accept an external kind, title, structured body and optional provenance. Creating a report requires project write access.
No. Read its underlying source dates, sample coverage and limitations. An agent's interpretation does not create new provider observations.
Brand Visibility, Prompt Playground and Site Audit save their analyses in the project. Agent Reports provides a place to revisit them.
Read the workflow guide, then use the same project context and saved results across the app and connected agents.