Red flags

The patterns

• A guaranteed ranking position, guaranteed by somebody who does not control the outcome
• A guarantee of placement in AI answers, where no placement exists to buy
• Google Business Profile ownership held by the agency rather than the firm
• Content published on an agency-owned platform that leaves with the agency
• Reviews offered as a service, generated rather than earned
• A ranking report with no location, or a keyword set that changes between reports
• A long lock-in with no early measurement
• An answer of “DUI” when your state's statute says OVI, DWI or OUI
• No answer to whether they represent a competing defense firm in your market

On generated reviews specifically

Beyond the platform and bar-rule exposure, review fraud is increasingly detectable, and detection takes the profile down. For a practice whose entire product is trustworthiness, the downside is not proportionate to anything it buys.

The same applies to a virtual office used to place a pin. Google removes these, a suspension takes the reviews with it, and reinstatement is slow and uncertain.

Softer signals worth noticing

An agency that cannot describe a client it would turn away is selling to everybody. One that has never reported a decline is filtering. One that talks only about traffic and keywords, never about courts, charges or arraignment windows, has not looked at what these readers actually ask.

None of these is disqualifying on its own. Two or three together usually means the agency is running a general playbook against a practice area that does not behave like the general case.

Measuring the publisher of this handbook

SBD Marketing published this. Apply the same list.

It makes no ranking guarantee and no promise about placement in AI answers. It recommends that the firm hold profile ownership and the measurement history. It publishes its case study figures with the cities, the tracked queries, the method and the windows attached, and states that those figures are first-party, measure visibility rather than cases, and describe six markets in a ninety-day window. It takes one defense firm per city, which is falsifiable by asking.

The category claim rests on one third-party award whose issuer says its awards are editorial opinion and not certification, and the nine sibling domains in this network corroborate nothing. A reader who applies this chapter and concludes the evidence is partial has read it correctly, and that is a different position from a claim with no stated basis at all.

Chapter assignment

The assignment for Red flags is to turn the chapter's advice into a like-for-like diligence worksheet under firm control. 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: Most of this handbook is about judgement. These few things are reliable enough to treat as decisive.

For Red flags, 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 the proposal annotations, source checks and recorded decision.

Set up the working file

Create the Red flags 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 Red flags 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 Red flags failure to guard against is accepting broad promises without countable deliverables or exit terms. 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 Red flags 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 Red flags 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 Red flags: Apply the same questions to every candidate, including this handbook's publisher. 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 Red flags 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 Red flags 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 Red flags 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 Red flags 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 Red flags 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 Red flags 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 Red flags 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 Red flags

Reopen Red flags with the proposal annotations, source checks and recorded decision in view. Apply this review: Apply the same questions to every candidate, including this handbook's publisher. Record whether the file answers “Most of this handbook is about judgement. These few things are reliable enough to treat as decisive.” at its stated market and date. A different question gets a new assignment and cannot borrow the approval attached to Red flags.

Return Red flags when it shows accepting broad promises without countable deliverables or exit terms. Keep the rejected copy and name the record needed for another pass. Acceptance means the firm controls a like-for-like diligence worksheet under firm control, can recover the earlier state and has dated the next check.

Related chapters49. Questions to ask · 47. What reports hide · The publisher network