Turning visibility findings into engineering tickets
A finding names a mechanism the business controls and the evidence that it is failing. A recommendation tells the business what to say. The record produces the first and leaves the second to the business.
Quick answer: A visibility finding carries a stable key, severity, evidence row, mechanism and owner; the line between a finding and a marketing recommendation is the mechanism, and a ticket closes only when the next measurement shows the mechanism works.
- Measurement
- AI Search Visibility
- Technical SEO
Quick answer
What separates an engineering finding from a marketing recommendation?
An engineering finding names a mechanism the business controls and the evidence that it is failing: a fact an assistant cannot read, a page that redirects in a loop, two copies of the address that disagree. A marketing recommendation tells the business what to say. Only the first becomes a ticket.
Additional Context
A weekly record produces findings in volume. Without a fixed shape and a fixed line about what counts, the action list fills with opinions about copy and the engineering never starts.
Sources
- Google Search Central - Introduction to structured data
Google's description of structured data as a standardised format for providing information about a page and classifying its content.
- Google Search Central - JavaScript SEO basics
How Google processes JavaScript in three phases, and why content that only appears after script runs can be missed.
The action list
The shape of a finding
A finding has a stable key, so that the same fault found in three consecutive weeks is one finding. It has a severity, so that the list can be read from the top. It has the evidence row, which is the line in the record that showed it: the answer with the wrong fee, the transcript where the agent hit a challenge page, the crawl row with the two-hop redirect. It has the mechanism, which is the thing on the site or on a surface that produced the evidence. It has the proposed change and the owner. And it carries forward week to week until the record shows that the mechanism works, at which point it closes with the date.
The ranking is by what fixing the finding is worth. A fee that two assistants quote wrongly from a third-party page ranks above a missing description tag, because one of them sends customers away with a wrong number and the other does not. The ranking is a judgement, made by an engineer reading the record, and it is written down so it can be argued with.
Three findings and their tickets
A clinic's fee schedule is a PDF linked from the services page. Two assistants quote the fee from a comparison site that copied an old version. Evidence: the answer rows and their cited sources. Mechanism: the fact is not in HTML on the clinic's own page. Ticket: publish the fee table on the service page as HTML with structured data, keep the PDF as a download, and watch the cited list.
A retailer's product page shows delivery times in a tab that renders from script. The agent test fails the task of finding delivery to a regional postcode on every run. Evidence: the transcript and the fetched HTML, which contains no tab content. Mechanism: client-side rendering of the tab. Ticket: render every tab's content in the HTML and let script switch the view.
A firm's opening hours differ between the Business Profile and the contact page after a seasonal change. One assistant gives the old hours and another hedges. Evidence: the surface diff and the two answer rows. Mechanism: two copies, edited separately. Ticket: make the CMS record the source, generate the structured data from it, and push the profile from it through the API.
What is not a finding
Writing more pages about a topic, targeting a particular search term, changing the tone of the service description and getting links from a particular kind of site are marketing decisions. The record can inform them, because it shows which questions the assistants answer from other people's pages, and the business may act on that however it chooses. The engineering service does not make those decisions and does not write that copy. When a fact is missing from the site altogether, the finding says so and hands the question back. Publishing the fact is the business's call. Publishing it in a form a machine can read is the ticket that follows.
Closing the loop
The next week's measurement is the test. A ticket closes when the record shows the mechanism works: the fetch returns the fact in HTML, the agent completes the task, the surfaces agree. Whether an assistant's answer then changes is recorded on the same series, with the date of the change marked, and it is never promised, because the assistants and their sources change for reasons nobody controls. That is the discipline that keeps the list honest. The sources that feed it are described across the assistant answer record, the agent test and the weekly crawl, and the whole of it, with the engineering days attached, is AI Visibility Management.
Key Takeaways
What makes a finding actionable
- A finding carries a key, a severity, the evidence row, the mechanism and an ownerCritical
The same fault found in three weeks is one finding, and it carries forward until the record shows the mechanism works.
- Rank by what fixing it is worth, and write the ranking downImportant
A wrongly quoted fee outranks a missing tag because of what it costs a customer, and a written ranking can be argued with.
- The line is the mechanismCritical
A finding names something on the site or a surface that produced the evidence. Advice about what to say, which terms to target or where to get links is a marketing decision the record informs and the engineering does not make.
- A ticket closes on the measurement and never on the promiseImportant
A ticket closes when the next measurement shows the mechanism works, and whether an answer changes afterwards is recorded with a date.
Findings with a stable key, a severity, an evidence row, a mechanism and an owner turn a weekly record into an engineering backlog. The line between a finding and a recommendation is the mechanism, and a ticket closes when the next measurement shows the mechanism works.
Questions about findings and tickets
Who decides the severity?
A senior engineer reading the record, and the reasoning is written beside the ranking. The business can disagree, and the list is then reordered with a dated note.
What happens when the finding is that a fact is not published anywhere?
The finding records it as unverifiable and hands the question to the business. Whether to publish the fact is a business decision. Once the fact exists, publishing it in HTML with structured data is the ticket.
Can a finding ever be about our copy?
It can be about whether a fact in the copy matches the same fact elsewhere, or whether a machine can read it. It is never about what the copy should say, how it should sound, or which terms it should target.
How do we know a ticket worked?
The next weekly measurement. The crawl row no longer shows the chain, the transcript shows the task completed, the surface diff is empty. An assistant's answer changing afterwards is recorded with the date, and the record is read as a series with the change marked on it.
