Start with the decisions the report needs to support

Agree on the brand, products, market, language and AI platforms before collecting answers. Include the website pages and buying decisions that matter to the project. Keep brand questions separate from questions that ask about a need or a type of service.

The scope record should identify the question-list version, collection period and channel used for each observation. Record the model or product tier when available. This gives the reader enough context to interpret a result and repeat the same check later.

Connect each finding to an evidence record

Keep the original response alongside the exact question. For each source link, record the URL actually cited, the statement it supports and the page you inspected. A report reader should be able to open the evidence behind a finding rather than work backwards from an aggregate score.

Question and capture
Exact wording, platform, collection channel, market, language, time and question-list version.
Answer evidence
The saved response and a reference that opens the original capture.
Source evidence
The cited URL, relevant passage and source-check record.
Observed signals
Brand mention, owned-site citation, third-party citation and recommendation, recorded separately.
Page finding
The page concerned, the information to improve and the evidence supporting that decision.

An owned-site citation links to your website. A third-party citation links to another publisher. A recommendation presents the brand as an option for the buyer's need. Keep these observations in separate fields so that the report answers a clear question about each.

Illustrative page work item

Use this work item to connect the existing optimization workflow article with the evidence a buyer needs when deciding who will implement a website change.

Buyer question
Who can implement website changes after an AI visibility audit?
Page task
Add a visible link to the report example and the measurement method beside the article's improvement workflow. Retain its existing body and link destinations.
Content owner
Content editor: place the links and write the short explanation connecting them to the workflow.
Reviewer
Project owner: confirm the resource links and explanation fit the agreed page scope.
Publication owner
Release owner: publish the approved update and record the live page URL and publication time.
Acceptance
Both links are visible in the article's HTML and resolve to their expected canonical URLs: /sample-report/ and /methodology/. The original article body and links remain available.
Retest record
After release, repeat the buyer question through the same collection channel. Record the platform, market, language, capture time, original answer and actual cited URLs alongside the earlier observation.

Attach the before and after page captures, link checks and publication record as the work progresses. Keep the answer observations connected to the same work item for the subsequent review.

Make the action list usable

Each action needs an affected URL, a finding, a reason for its priority, an owner and an acceptance check. A factual correction might require confirmation from the product owner. A missing use-case explanation might require an agreed audience, relevant capabilities and a clear next step.

Keep the proposed change, approval and publication record together. Verify the resulting page separately: its agreed facts should be visible, its links should work, and its layout and search metadata should remain usable. Link to the measurement method for the subsequent AI-answer comparison.

Finish with a reviewable handover

The handover connects the scope, evidence index, page findings, approved work items, release checks and retest records. Keep the same identifiers across these parts so that a reader can trace a finding through the work.

Review observed AI-answer changes alongside their original captures. Record identified website referrals and enquiries in their own sections when those records are available. This keeps the report useful for both the team improving the website and the team reviewing what happened next.