A working button is only a starting clue
Imagine a page whose visible “Read the security answer” control opens /answers/security/. Its HTML contains only <button onclick="openAnswer()">Read the security answer</button>. This is a placeholder example, not a test result from a live site.
The reader has demonstrated that a click works. The saved snippet has demonstrated a button and a handler; it has not demonstrated an anchor with a destination in href. Record those observations separately. A screenshot of the button or a screen recording of the successful click can identify the entrance being discussed, but neither shows its underlying link markup.
The discussion in From Google Rankings to ChatGPT Answers connects buyer questions, website evidence and paths between existing pages and answers. Add the exact source page and control location to your own record for the answer page so another person can reproduce this entrance check.
Compare the forms Google documents
Google's supported examples include <a href="/products/category/shoes"> and an anchor that retains that destination while also having onclick. Its examples without a supported link shape are <a routerLink="products/category">, <span href="https://example.com"> and <a onclick="goto('https://example.com')">. It also discourages <a href="javascript:goTo('products')"> and <a href="javascript:window.location.href='/products'">, whose values are scripts rather than web addresses. Google preserves the possibility of attempting to parse or resolve these discouraged forms; they do not establish reliable extraction.
JavaScript itself does not settle the result. Google's JavaScript guide allows injected links that meet its crawlable-link guidance and explains that Googlebot extracts links from both the response HTML and, after rendering, the rendered HTML. Therefore, absence from a curl response is a finding about that response; further HTML evidence is needed before concluding that a generated entrance also lacks the anchor.
Capture the HTML behind each entrance
Use one record per source-page entrance, even when several controls share a destination. Save the response HTML with curl and label its retrieval time and URL. Keep a generated HTML capture separately identified so that reviewers know which version supports the finding.
| Field to save | Evidence to inspect | Finding to record |
|---|---|---|
| Source URL and capture method | Full source address, time, response or rendered HTML | Exact capture used for this entrance |
| Element and HTML snippet | The control's surrounding markup | Anchor with href, button, or another form |
Literal href and resolved target | Attribute value and the web address it resolves to | Requestable destination or unresolved value |
| Target response | Requested address, response status, redirect chain and final address | Accessible answer, different destination or failed request |
| Intended answer | Final page title and answer identity | Whether it reaches the expected answer page |
| Visible text and source paragraph | Text and surrounding paragraph retained with the snippet | Which entrance the evidence belongs to |
For a Google-side check, Search Console's URL Inspection live test offers View tested page with raw HTML, headers and other response data. Those additional data are available only when its status is “URL is available to Google” or “URL is available to Google, but has issues.” Retain the test type and time alongside the HTML.
Treat the table as an evidence checklist, not a link-count target or an anchor-writing exercise. A successful destination response cannot fill a missing source-markup field. Equally, a correctly shaped anchor can point to the wrong answer. Keep each discrepancy attached to the field that revealed it.
Keep the sitemap finding separate
Google's sitemap overview describes a sitemap as information about site files that supports more efficient crawling. It helps search engines discover URLs but does not guarantee that listed items will be crawled and indexed. A sitemap entry and an extractable source-page anchor are therefore separate findings.
Keep the sitemap's URL and the listed answer URL in one record. Keep the source-page snippet and destination check in another. If the sitemap entry exists but the entrance remains unresolved, preserve both findings. Repeating “the sitemap was submitted” does not answer what HTML the button provides.
Hand over the unresolved entrance
Package the material so that another person can reproduce the observation.
- Identify the source URL, control location and expected answer URL.
- Attach the dated HTML snippet, literal
hrefif present, resolved target and destination response record. - State the narrow finding: supported anchor markup observed, discouraged form observed, wrong destination, or generated-link evidence still missing.
- Attach a later capture separately and compare the same fields before closing the issue.
Give implementation questions to the site's technical team. A technical answer evidence brief can retain this entrance record alongside the answer's supporting material. The result of this check is evidence about link extraction and its destination; it makes no promise about indexing, citations, rankings or appearance in an AI feature.
Want to see how AI engines describe your brand today?
Get a free growth audit