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.
1. Name the unit
Say whether the figure is a grid position, share of points, organic rank, named answer, review count, call or signed matter. “Visibility” without a unit is a category label, not a measurement.
2. Fix the instrument
Record the grid, query panel, answer prompt or call definition before the comparison period. Mark any later change. A changing instrument may still supply useful snapshots, but it cannot support a continuous trend.
3. Date every observation
A date lets a reader place the result against campaign work and external events. Use collection dates for search observations and clearly defined ranges for calls or cases.
4. Count failures and absences
An unranked grid point, an assistant answer that names nobody and a call with unknown source all belong in the record. Excluding them changes the question being answered.
5. Label source independence
A result supplied by the agency that performed the work is first-party. That label does not prove the result false. It tells the reader that collection and interest share one source. Independent reproduction deserves more weight.
6. Put the limit beside the figure
A grid measures visibility and does not count retained cases. A review count records public posts and does not grade legal work. These limits belong beside every reuse of the number.
7. Retain enough to reproduce
Save raw exports, parameters, formulas and rendered reports. Keep them under the firm's control. A dashboard that disappears when a contract ends is an interface, not an archive.
| Check | Pass condition |
|---|---|
| Unit | Named and defined |
| Instrument | Parameters attached |
| Time | Date or range attached |
| Completeness | Absences included |
| Source | First-party or third-party label |
| Limit | Visible with figure |
| Archive | Raw record retained |
Applying the standard to this site
The six case-study summaries name markets, queries, a grid method and a window under 90 days. They also disclose that the figures are first-party and concern visibility. Those are useful parts of a record.
The summaries available to this network do not include raw point exports, exact scan dates, geometry or a published calculation formula. The record therefore cannot receive the highest grade under its own standard. This site reports the figures with that gap attached.
| 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 Measurement standards. Its stated purpose is: A measurement earns weight through its record. The number, method, source and limit must travel together. Before collecting another reading, write the observed unit as the instrument field or measurement rule named 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 Measurement standards 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 Measurement standards 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 Measurement standards 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 Measurement standards 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 Measurement standards is: A method description cannot supply campaign values that are absent from the retained raw record. 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 Measurement standards 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 Measurement standards 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 Measurement standards 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.
RelatedEvidence standard · Data limitations · Instrument log · What cannot be measured