San Jose entry

Section context

A market entry is a bounded case note. Its percentage belongs to one city, one query panel, and one local baseline.

Market size, competition, starting visibility, and query mix can differ. The entries should not be sorted into a league table.

Review the San Jose entry entry

Open the San Jose entry workpaper with this exact question: What does the San Jose, CA grid comparison establish?

Apply the San Jose entry reading rule before collecting more material: Read the +316% total and its 5 named queries against the same local baseline.

Keep the San Jose entry evidence boundary beside the finding: The entry reports an under-90-day visibility comparison supplied by SBD Marketing; it contains no client intake or revenue record.

Assign the San Jose entry follow-up as a dated task: Obtain the San Jose before and after exports with the coordinate layout and scan dates.

Release record for San Jose entry

The reviewer starts from “What does the San Jose, CA grid comparison establish?” and records the disposition under “The entry reports an under-90-day visibility comparison supplied by SBD Marketing; it contains no client intake or revenue record.”; any conclusion that crosses that boundary returns to the workpaper.

The release owner then schedules “Obtain the San Jose before and after exports with the coordinate layout and scan dates.”; the San Jose entry entry remains open until that task has an owner, a due date and a retained result.

Market boundary

A city entry describes its own query panel and baseline. Market size, competition, starting visibility and query mix can differ. Use the entry to inspect a bounded observation, not to predict the result for another firm or location.

Before using a city note in a vendor decision, create a fresh baseline for the firm's own address and charges. Preserve the city entry as an example of the filed method. Do not treat its percentage as a forecast or a minimum result.

Query language

Retain every named phrase as published. DUI, DWI and OVI are market-specific terms, and a generic label can erase the difference the scan was designed to observe. Document why each phrase belongs in the panel before revising it.

Keep spelling, location words and “near me” forms in separate rows. A change in wording can alter the result even when the legal service is similar. When a panel changes, start a new version and do not splice its total into the earlier series.

Baseline rule

Compare an after observation only with its own before observation under the same settings. City totals start from different query panels and local conditions. Do not average them or turn their sum into a network-wide performance rate.

Write the baseline date, panel size and scanner settings beside the result. A weak starting position can produce a large percentage change from a small movement, so retain the underlying values whenever the record supplies them. Report an absent denominator as unknown.

Grid file

A reproducible grid comparison needs the before and after exports, map center, radius, spacing, query wording, scan dates and tracked listing. The public summaries do not supply those raw fields. Their absence stays visible until the original files are obtained.

Recalculate one percentage from the retained rows and note the formula. Confirm that the listing identity did not change between scans. If the geometry or query text moved, label the result as a different observation instead of forcing it into the old comparison.

Next check

Obtain the San Jose before and after exports with the coordinate layout and scan dates.

The current entry retains San Jose entry at the scope stated above.