Choose one answer and freeze its wording
Start with a paragraph that a buyer actually needs, such as an explanation of which data an export includes. Use the category answer gap workbook to select the question; the check here concerns whether that specific answer reaches the rendered page.
Copy the complete answer, including its conditions and exceptions. Record the page URL, heading, language, button label and capture time. Give the paragraph a local reference such as P1 so that later notes identify text rather than a whole page. Record whether the click expands text already present or requests text that was absent before it. These are different observations; the appearance of a button does not decide between them.
Compare three views paragraph by paragraph
Keep the page wording fixed across the comparison. The following is an anonymous hypothetical example, not a measurement of a published site. P1–P3 label the passages being compared.
| Reader sees without interaction | Text appears only after clicking | Google live test's rendered HTML |
|---|---|---|
| P1: “The export contains selected records.” | P1: No additional text | P1: The same sentence is present |
| P2: No answer text; a “Show limits” button is visible | P2: “Archived records are excluded.” | P2: Sentence not found |
| P3: No condition text | P3: “The date filter uses the workspace time zone.” | P3: Only “The date filter” is found |
Google's lazy-loading test instructions say "Check the rendered HTML" and recommend looking for the content there through URL Inspection. For a text answer, search the HTML for its sentences and read the surrounding passage. A screenshot can supplement that search; a screenshot of a closed panel cannot establish that its answer text is absent.
- Open the URL in a fresh reader session and capture the text visible without clicking, expanding, scrolling or submitting anything. Record the viewport and time allowed for loading so another person can reproduce the observation.
- Activate the specified control and capture the answer that appears. Retain the control label and, if available, the request associated with that action. Do not replace the first capture with this more complete version.
- For the same URL in Google's URL Inspection tool, run
Test live URL→View tested page→HTML. Save the rendered HTML from this live test and record the test type (live) and test time. Search that saved HTML for every selected paragraph. Keep the exact matched passage or record that no match was found. A shortened sentence requires a partial result, especially when its omitted words contain a limit.
In the example, P2 is missing and P3 is partial. Neither should receive a blanket “answer available” conclusion because P1 is present. If the inspected output cannot be obtained, mark the comparison unavailable rather than equating missing evidence with missing content.
Test candidate causes before assigning one
Google's troubleshooting guide says "While Google Search does run JavaScript" and immediately qualifies that capability with differences and limitations in how crawlers access and render content. It also identifies loaded resources, "JavaScript console output and exceptions", and the rendered DOM as evidence available through its inspection tools. Use those outputs to investigate a missing answer rather than infer its cause from the visible page.
A missing paragraph narrows the investigation but does not establish why it disappeared. Treat these three explanations as candidates requiring evidence:
- Loading dependency: the answer may depend on another step or request completing. Retain the observed request sequence and any relevant exception; ask the content maintainer which dependency supplies P2. A delay noticed in the reader session is a lead, not proof of the inspection result's cause.
- Resource problem: a needed resource may not have loaded or may have produced an error. Record its URL, the status or error actually reported by the inspection output, and the affected paragraph. A console error elsewhere on the page does not automatically explain this answer's absence.
- Interaction-only trigger: the answer request may begin only after the button action. Compare the no-interaction and clicked captures with the available request evidence. Google's lazy-loading guidance specifically discusses methods that avoid user actions, including scrolling or clicking, because Search does not interact with the page. If the trigger has not been established, leave this explanation open.
Multiple candidates can remain open together. Keep the missing text separate from its proposed cause, and ask for additional evidence when the output cannot distinguish them.
Hand over evidence and record the next check
Send the existing content maintenance owner a compact record for each missing or partial passage. Include the URL and language, paragraph reference, complete required answer, no-interaction capture, clicked capture, Google live-test rendered HTML file or retained output, test type (live), test time, search phrase and matched context. Add relevant resource or console evidence, candidate causes, unresolved questions and the named owner. The technical answer evidence brief can hold the answer's supporting material; this handover adds the evidence that its text was missing.
After the owner addresses the issue, rerun Test live URL for the same URL and open View tested page → HTML to compare the same passages again. Preserve the earlier captures and save the new live-test HTML, test type (live), test time, rendered passage and result: present in full, partial, missing or unavailable. Close the text-visibility issue only when the required answer and its qualifications are present in the new live test's rendered HTML. Record any remaining uncertainty explicitly.
This is a rendering check, not proof of indexing, citation or ranking. Content preparation for getting cited by ChatGPT is a separate question. Other crawlers need checks against their own documentation; Google's rendering behavior does not establish theirs.
Want to see how AI engines describe your brand today?
Get a free growth audit