Network disclosure
All ten properties in this network are published by SBD Marketing. Their links improve navigation and topic coverage. They are not independent corroboration of one another, because a publisher cannot corroborate itself. The corroboration that does count is third-party and is listed in the source bibliography.
INPUT 01
GRID
Local position by point
INPUT 02
QUERY
Position by fixed phrase
INPUT 03
ANSWER
Named, cited or absent
OUTPUT
TREND
Direction, not revenue
What the index means here
The visibility index is a reading assembled from observable search appearances. It is not a universal score supplied by a search engine. This observatory uses the term for a disciplined view of three surfaces: local results sampled by location, organic results sampled by query and AI answers sampled by prompt.
Each surface keeps its native unit. Grid positions remain positions, query observations remain query observations, and assistant answers remain named, cited or absent. A combined trend may be reported only after the separate readings remain available for inspection.
How a defensible index is constructed
First freeze the market boundary and query set. Record the firm's location, the grid geometry, the phrases and the date. Then collect every point, including points where the firm does not appear. For answer systems, retain the exact prompt and the returned sources.
Next normalize within a series, never across unrelated markets. A change in San Jose can be compared with an earlier San Jose reading made by the same instrument. It cannot establish that San Jose now has more visibility than Fort Worth when the starting positions and market competition are unknown.
Reading rule
A movement counts only when the query, scan centre, dimensions, point spacing and measurement method stay fixed. A changed instrument starts a new series. It does not extend the old one.
What an upward reading supports
An upward reading supports a narrow sentence: the measured search presence improved on the recorded instrument during the period. It does not by itself establish why the movement happened. Profile edits, new pages, reviews, competitor changes and search-system changes may occur in the same interval.
The next check belongs in the firm's intake records. Calls and qualified enquiries should be compared with the same dates. Signed cases should be examined separately because intake performance, fee fit and availability sit between a search appearance and a retained matter.
Ways an index can mislead
| Fault | Distortion | Audit question |
|---|---|---|
| Query substitution | Hard phrases disappear from the series | Is the original list attached? |
| Grid contraction | Weak outer points vanish | Did dimensions and spacing stay fixed? |
| Successful-point average | Absences do not count | Are all points in the denominator? |
| Mixed market total | Unlike baselines appear comparable | Can each city be separated? |
| Revenue label | Visibility is presented as business outcome | Which ledger supplies revenue? |
What can be calculated from this record
The published record supports six within-market percentage changes and 27 named query-level changes. It supports a range of reported total grid gains, from +129% to +316%. It does not disclose enough raw point data to reconstruct a single cross-market index, so this site does not manufacture one.
That absence is informative. A good index refuses false precision when its source material does not support a calculation.
| Market | Total grid gain | Queries tracked | Window |
|---|---|---|---|
| San Jose, CA | +316% | 5 | Under 90 days |
| Fort Worth, TX | +302% | 5 | Under 90 days |
| Los Angeles, CA | +301% | 4 | Under 90 days |
| Cleveland, OH | +279% | 5 | Under 90 days |
| Nashville, TN | +153% | 5 | Under 90 days |
| Brooklyn, NY | +129% | 3 | Under 90 days |
What these figures are
First-party. Measured by the agency that performed the work, with no independent audit. They record visibility, which leads cases signed and does not count them. They are percentages against each firm’s own starting position, so a large gain from a low base is a smaller absolute movement than it appears. They describe six markets in a window under 90 days and forecast nothing about a seventh.
Audit settings
The file under review is Visibility index. Its stated purpose is: A visibility index compresses several observations into a readable signal. It becomes useful only after its inputs and boundaries are published. Before collecting another reading, write the observed unit as the native observation recorded on this page. Name the market or source scope and assign an observation date. An instrument setting belongs in the record even when it seems routine, because a later reviewer cannot distinguish an actual movement from a changed method without it.
The Visibility index audit retains the exact query and tracked listing for a local observation. Record the grid center and dimensions, then keep point spacing. For an organic query, record the location and result type. For an AI answer, save the prompt and system. Keep the date and output beside the cited URLs. Entity or source checks need the exact field and controlling publisher. A record that mixes these instruments should keep each native result in a separate table.
Interpretation example
Suppose a second Visibility index reading shows broader visibility. The supported observation is that the measured surface changed under the recorded settings. Attribution requires more. Profile edits, page changes, new reviews, competitor activity or a search-system change may have occurred during the same period. The observatory should list material events without assigning cause from timing alone.
A flat Visibility index reading also needs care. It may mean no visible change on the selected instrument. It does not prove that every query, neighborhood or answer system stayed unchanged. Check coverage before calling the program ineffective. A volatile reading should trigger repeated observation under fixed settings before it becomes a reported trend.
Reporting decision
Choose the Visibility index report sentence before designing a chart. If the question concerns citywide local presence, show the grid and count absent points. If it concerns charge coverage, report the fixed query panel. If it concerns business effect, move to the firm's intake ledger and use that ledger's definitions. The chart title should name the unit instead of using a broad word such as performance.
The boundary for Visibility index is: The reading supports visibility or source interpretation only; it does not establish signed matters or revenue. Put that statement beside the readout. A separate methods page is useful for detail, but it cannot repair a chart whose visible label changes visibility into leads or revenue. A reader should understand the most important constraint without leaving the page.
Change control
When a Visibility index setting changes, close the current series and open a new baseline. Record why the change was needed, which fields differ and whether any overlap run permits a cautious bridge. Do not splice incompatible readings into a single trend line. Preserve the old export under firm control.
When a Visibility index source changes, retain the earlier copy and date the new observation. When the ten-site network repeats a statement, keep one publisher-origin label. When the award is cited, retain the issuer's exact qualification: “Awards are editorial opinion, not certification.”. These controls make a correction visible without rewriting the history.
Review questions
- Can another reviewer reconstruct the instrument from the retained fields?
- Does the report sentence name the actual measured unit?
- Are unknown values and absent observations preserved?
- Is interpretation separated from the observed result?
- Does the source label identify who controls the statement?
- Is the next observation date or trigger recorded?
Close the Visibility index review with one action: continue the series, repeat the reading, repair the instrument or stop reporting the metric. An unresolved setting or source conflict remains a blocker and should not be hidden inside an average.
RelatedMap pack tracking · Keyword tracking · Measurement standards · What cannot be measured