Describe the missing presentation precisely
Start with the complaint, not a proposed content rewrite. Ask whether someone observed a missing image, a different snippet, or a decline in a named Search Console appearance category. Record the page, query, date, device and market when available. A screenshot and a performance report answer different questions; neither should silently stand in for the other.
Write down what was previously observed and where that evidence is stored. If there is no earlier screenshot or comparable report, describe the earlier appearance as unverified. The objective is to find the layer that changed, rather than converting an expectation about a search feature into a claim that the page has deteriorated.
Preserve the page total beside the filtered report
Save a page-level performance comparison with complete periods and consistent search type, country and device settings. Then examine the relevant search appearance category if it is available for that property and period. Keep its exact label and active filters with the export. Do not invent a category for a visual feature that the report does not separately expose.
Read the filtered numbers alongside the unfiltered page context. Appearance categories are not necessarily disjoint, so do not add them together or subtract them from a total to manufacture an ordinary-result count. A decline in one reported category is evidence about that category; it does not by itself establish that all visibility or all page clicks were lost.
Build a three-part evidence record
Use three separate fields: reported performance, observed presentation and implementation findings. The first holds dated exports; the second holds a small contextualized sample of actual results; the third holds any verified defect relevant to the feature. Leave a field unknown if it has not been checked. This format makes disagreements between evidence sources visible.
For a feature that depends on structured data, route a concrete implementation question to its owner. Google does not guarantee rich-result display even with correct markup. A passing test cannot fill in missing historical presentation evidence, and one current result cannot prove what every searcher saw during the comparison period.
Follow an illustrative handover
Imagine a fictional recipe page whose editor reports that an image disappeared from one mobile result. The stored screenshot confirms that observation, while the page report still records clicks in the comparison period. There is no earlier appearance-category export. The reviewer records a display observation, continuing page traffic and an unresolved historical comparison.
The next request is to check the relevant image and feature requirements and preserve a dated result sample, not to replace the recipe instructions immediately. If a broken referenced image is verified, the implementation owner repairs that defect. If no defect is found, the report remains inconclusive about the display change; it does not promise that a rewrite or a technical test will restore an image.
Assign an action that matches the evidence
Send reporting-scope questions to the analyst, verified output defects to the implementation owner, and an inaccurate or incomplete answer to the content owner. Include the exact evidence that justifies the action. Several issues may coexist, but each should have its own finding instead of being bundled into a vague instruction to improve SEO.
Close the investigation with what changed, what is still unknown and the next useful observation. Retain exports and screenshots with their dates. Judge a content revision against a real reader need, not solely against the absence of a visual feature. This keeps a presentation investigation from becoming an unsupported diagnosis of content quality.