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.

Which listings are worth having

Table. The directory layer for a defense practice, in priority order.
Tier	Examples	Why
Bar directories	State bar, county bar association	Authoritative about licensure and standing; the strongest signal available
Legal verticals	Avvo, Justia, FindLaw, Martindale, Super Lawyers	Structured, widely mirrored, and frequently cited by assistants
General aggregators	Apple Maps, Bing Places, Yelp, Yellow Pages	Feed other systems; correcting them corrects downstream copies
Local civic	Chamber of commerce, local business associations	Genuine local relevance where the firm is actually a member
Everything else	Bulk directory packages	Adds nothing; mismatched details actively subtract

Volume is not the goal

Two hundred listings on directories nobody reads add no prominence. A scattering of them with mismatched details is worse than not having them, because each inconsistency weakens the entity the firm is trying to establish.

The productive version of this work is narrow and finishable: claim the bar listings the firm is entitled to, correct the legal verticals, fix the aggregators, and stop. Where an old office address survives across forty sites, clearing that up is worth more than any number of new listings.

Duplicate profiles

This is the failure worth hunting for specifically. Firms that have moved, merged or changed name often have two or three live Google profiles competing with each other, splitting reviews and confusing the location signal.

Google also suppresses listings it reads as the same entity, so duplicates can cause a profile to vanish from the pack while remaining findable by exact-name search. Where a profile is absent from the pack but appears when searched by name, duplication rather than ranking is usually the cause.

Consolidating duplicates is a single afternoon that sometimes produces more movement than a quarter of content work. Merge rather than delete where possible, so reviews follow.

On directory packages

Services selling hundreds of citations are selling volume in a market where volume does nothing. Worse, bulk submissions frequently introduce variants, because a form field truncates a firm name or guesses at a suite format, and the firm ends up paying to damage its own consistency.

Where a firm has already bought one, the remedy is the audit in chapter 16: find the variants and correct them.

Start with your own phone number

Search your main telephone number in quotes. Every result is a citation, and the ones showing an old address or a misspelled firm name are your work list.

Chapter assignment

The assignment for The directory layer is to turn the chapter's advice into a firm-controlled local asset and its public fields. 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: A citation is any mention of the firm's details on another site, whether or not it links. For law firms the useful layer is narrow, and volume past a point does nothing at all.

For The directory layer, 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 before-and-after captures plus a local change log.

Set up the working file

Create the The directory layer 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 The directory layer 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

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

The The directory layer failure to guard against is changing several profile or directory fields without retaining the earlier state. 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 The directory layer 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 The directory layer 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 The directory layer: Recheck the listing from more than one point in the intended market. 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 The directory layer 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 The directory layer 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 The directory layer 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 The directory layer 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 The directory layer 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 The directory layer 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 The directory layer 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 The directory layer

Reopen The directory layer with before-and-after captures plus a local change log in view. Apply this review: Recheck the listing from more than one point in the intended market. Record whether the file answers “A citation is any mention of the firm's details on another site, whether or not it links. For law firms the useful layer is narrow, and volume past a point does nothing at all.” at its stated market and date. A different question gets a new assignment and cannot borrow the approval attached to The directory layer.

Return The directory layer when it shows changing several profile or directory fields without retaining the earlier state. Keep the rejected copy and name the record needed for another pass. Acceptance means the firm controls a firm-controlled local asset and its public fields, can recover the earlier state and has dated the next check.