BestSEOForCriminalDefenseLawFirms.com The complete handbook

Published by SBD Marketing, Bay Area, California
52 chapters · reviewed 7 September 2026

Chapter42

Part · Measurement

Running a baseline scan

The baseline is taken before anything is changed. A firm that skips it has given up the ability to demonstrate later what happened, and so has its agency.

SBD Marketing · criminal defense SEO handbook · Reviewed

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.

Choosing the grid

The centre goes on the office, or on the centre of the market the firm intends to serve where those differ. The dimensions and spacing follow from the size of the metro: a wide grid at one-mile spacing describes a city, a tighter one at half a mile describes a neighbourhood.

Neither is more correct and they answer different questions, which is why the choice has to be recorded and then left alone. Comparing a scan from one grid against a scan from another is meaningless.

Choosing the queries

The queries come from the two-year count of chapter 3, in the local statutory vocabulary. A practice in Ohio tracks OVI terms; one in Texas tracks DWI terms.

Include the terms the firm is furthest from winning, not only the ones it is close on. A set weighted toward easy terms will show progress that means little, and the hard terms are where the firm learns whether the work is landing.

Running it

1

Record the parameters before you scan

Centre, dimensions, spacing, query list, date. Write them into the same document the results will live in.

2

Scan every query on the same day

Results shift day to day. A baseline gathered across three weeks is comparing terms measured under different conditions.

3

Capture the profile and directory state at the same time

Category, services, hours, review count and average, and how the firm's details appear across the directory layer. These are part of the baseline.

4

Store it where the firm controls it

Not solely in an agency dashboard. A firm that changes agency and loses its baseline has lost the ability to compare anything across the switch.

What the first scan tells you

Before any work, the baseline already answers useful questions. It shows the radius within which the firm is competitive, which sets realistic expectations for the map pack. It shows whether the firm is absent everywhere, which usually points at the profile or something technical rather than at content.

It also shows which competitors hold the ground. The firms appearing consistently across your grid are the ones to study, and chapter 43 is about reading that pattern.

If work has already started

Take one now and treat everything before it as undemonstrable. That is an uncomfortable conversation and it beats constructing a comparison from figures nobody gathered.

Chapter assignment

The assignment for Running a baseline scan is to turn the chapter's advice into an instrument specification that freezes the unit and observation settings. Begin with the question that caused the reader to open this chapter. Write it in one sentence and name the person who can approve the answer. The chapter premise is: The baseline is taken before anything is changed. A firm that skips it has given up the ability to demonstrate later what happened, and so has its agency.

For Running a baseline scan, define completion before doing the work. A task is complete when the firm can inspect the changed asset, recover the starting state and repeat the check without relying on memory. Activity counts and dashboard labels do not satisfy that rule. The retained deliverable is raw exports, calculation sheet and qualified report sentence.

Set up the working file

Create the Running a baseline scan folder under the market and observation date. Put the baseline or source copy first. Add a short manifest that names the asset owner, operator, approver, measurement unit and next review date. Link to firm-controlled credentials through the approved credential system; never place a password in the workbook.

The Running a baseline scan file records unknown fields as unknown. An empty value is a prompt for the owner, not permission to infer. If two sources disagree, save both and open a conflict row before choosing one. For public legal text, identify the attorney who will check the statement. For measurement, identify the instrument and settings. For vendor work, identify the export and exit right.

Execution pass

  1. Observe. Save the present state and note why it matters to the firm's criminal defense work.
  2. Diagnose. Separate the visible symptom from its possible causes. Choose the smallest change that tests the diagnosis.
  3. Approve. Obtain factual, attorney or commercial approval at the point required by the asset.
  4. Change. Make one attributable revision and record the operator and time.
  5. Verify. Repeat the original check under the same scope. Capture the result even when it failed.
  6. Hand off. Store the files under firm control and assign the next review.

The Running a baseline scan failure to guard against is changing the query panel or geometry inside a continuing series. If it occurs, stop the release. Preserve the failed state and decide whether the work, source or instrument caused the problem. A new method needs a new baseline and version; it should not be spliced into the previous series.

Decision points

Continue the Running a baseline scan assignment when the starting record is complete, the owner is known and the acceptance rule can be tested. Pause when access is disputed, a legal statement awaits attorney review, the measured unit has changed or a source conflicts with the proposed wording. Cancel the task when it does not match a real charge, market, reader question or business decision.

Prioritize Running a baseline scan by dependency. Ownership comes before optimization. A baseline comes before a change report. A charge brief comes before prose. Crawl access comes before answer testing. A defined intake event comes before a return calculation. This order prevents later work from resting on an unknown or disputed input.

Quality review

For Running a baseline scan: Recalculate the result from retained observations and compare like periods. Then ask whether a new operator could reproduce the check from the handoff. Confirm that page headings name the reader's question, local claims name the correct market, and measurement statements retain their units. Verify that no confidential matter fact or unsupported outcome entered a public file.

Check source control for Running a baseline scan as well. A statement on the firm's own page is first-party. A publisher-owned sibling domain is still the same origin. An award citation must keep the issuer's qualification. A vendor screenshot is useful evidence of a recorded state, but the firm should also retain an export when one is available.

Field exercise

Choose one live example for Running a baseline scan from the firm's current operation. Use a real market and a real service the firm accepts. Save the present public view before discussing improvements. Ask the asset owner to describe the problem without offering a solution. That account becomes the problem statement and gives the later review something concrete to test.

Now complete the Running a baseline scan assignment on that single example. Keep a side log of assumptions and evidence requests. When an assumption is confirmed, replace it with the source. When it is rejected, note the effect on the proposed work. Do not expand to a second asset until the first has passed its acceptance rule. This narrow trial exposes access problems and approval delays while the recovery cost is low.

Have a second person review the Running a baseline scan handoff without verbal explanation. Ask that reviewer to locate the baseline, identify the change, repeat the test and find the approval. Any answer that depends on the original operator's memory is a documentation gap. Repair the file and repeat the review.

Finally, write two Running a baseline scan report sentences. The first states the observable result in its native unit. The second states the limit or next decision. Remove any causal language that the record cannot support. Store the approved pair with the deliverable so the monthly report does not have to reconstruct meaning from a chart.

Handoff record

The Running a baseline scan handoff contains the starting record, work completed, approval, final check, open limitations and next action. Give each item a stable filename. The receiving owner should be able to say what changed, why it changed, who approved it and where the proof sits.

End the Running a baseline scan file with a plain decision: accepted, accepted with a named limit, returned for repair or stopped. A partially completed task should remain open. Carry the unresolved field into the next work cycle instead of hiding it inside a broad progress label.

Acceptance record for Running a baseline scan

Reopen Running a baseline scan with raw exports, calculation sheet and qualified report sentence in view. Apply this review: Recalculate the result from retained observations and compare like periods. Record whether the file answers “The baseline is taken before anything is changed. A firm that skips it has given up the ability to demonstrate later what happened, and so has its agency.” at its stated market and date. A different question gets a new assignment and cannot borrow the approval attached to Running a baseline scan.

Return Running a baseline scan when it shows changing the query panel or geometry inside a continuing series. Keep the rejected copy and name the record needed for another pass. Acceptance means the firm controls an instrument specification that freezes the unit and observation settings, can recover the earlier state and has dated the next check.

Related chapters6. Setting a baseline · 43. Reading a grid · 44. Tracking a keyword set