Run 47 DUI SEO Checks With Evidence, Accountability, and Closeout Proof

This checklist is designed for solo DUI attorneys, criminal defense firms, and practice groups that need a repeatable way to decide which search problems are real, which claims lack support, and which changes deserve an accountable owner. It is especially useful when important local queries tend to appear around page 2 or 3, when a vendor report lists activity without showing evidence, or when a redesign, migration, profile edit, or content expansion was completed without a formal verification pass.

Use the related diagnostic audit when the question is why a visibility or indexing problem exists. Use this checklist when the next decision is whether a specific condition passes, fails, or needs corrective work. Every applicable item should identify the evidence reviewed, the pass or fail rule, severity, owner, corrective action, and validation step. Verbal confirmation is not closeout evidence.

DUI search work can touch attorney advertising, solicitation, testimonials, case results, credentials, fees, and jurisdiction-specific statements. Review those subjects against ABA Model Rules 7.1-7.3 and the rules that actually apply to the lawyer and location. An SEO owner can surface a risk and document the evidence, but the legal judgment belongs with the responsible reviewer.

Treat the 47 entries as controlled tests rather than suggestions. Create one row for each applicable check and require the same decision fields: evidence reviewed, explicit pass or fail condition, severity, owner, corrective action, validation method, reviewer, and closeout status. That structure makes disagreements visible because the team can compare evidence instead of arguing from impressions.

Begin with work that can be verified in under 1 week, including firm-profile identity data, core contact information, indexability, visible metadata defects, obvious mobile failures, and review-request controls. After those fast confirmations, move to technical foundation work planned across 1-4 weeks when changes may require development, hosting, template, redirect, rendering, or information-architecture ownership.

Validate local corrections at the system where the data actually lives. Confirm the public profile, the relevant citation source, the website, and Search Console rather than assuming that an edit caused a search response. If the team uses an internal 2-3 week comparison window for visibility observations, label it as an observation period. It is not a promised processing or ranking timeline.

Content and authority work can be managed across a 3-6 month operating horizon because research, attorney review, publishing, outreach, indexing, and later measurement are separate stages. Keep those stages separate in the evidence log. Publication can prove that an editorial task was completed; a later change in impressions or position is a different observation that may have multiple causes.

Run advertising-risk review alongside technical and editorial work. When a testimonial, fee statement, credential, comparative statement, solicitation method, or case-result claim lacks documentary support or legal approval, the SEO owner should flag the item and assign it to the responsible attorney or ethics reviewer rather than treating optimization approval as legal sign-off.

Use the evidence log to report decisions. A useful status record explains which items passed, which failed, what evidence caused the decision, what corrective work was completed, who approved it, and what still needs validation. That record helps firm leadership decide what to fund or defer without relying on generic activity reports.

Google Business Profile identity and category accuracy. Evidence required: the live public profile, authoritative firm records, website contact information, and the current category configuration. Review the 3-5 categories already associated with the profile and confirm that the primary choice truthfully describes the law practice. Pass condition: the displayed firm name, address or permitted service configuration, phone, hours, website, and categories correspond to the real firm and do not add marketing language to identity fields. Fail condition: any core field is false, stale, misleading, or inconsistent with the real business. Severity: high when identity or contact data can misdirect a prospective client, otherwise based on reach. Owner: authorized profile manager or local SEO lead. Corrective action: update inaccurate fields using supportable business information and avoid keyword stuffing. Validation: reopen the public profile after the change and preserve dated evidence of the final values. Category edits should be treated as data corrections, not as guaranteed Map Pack ranking levers.

Firm name, address, and phone consistency. Evidence required: the website, Google Business Profile, state bar listing, the firm's phone and listing data, and the top 10 directory or citation records that materially represent the practice. Pass condition: each reviewed record describes the same real entity and legitimate location or service configuration, while obsolete duplicates are documented for correction. Fail condition: conflicting primary data, false office information, disconnected phone routing, or duplicate records that can confuse users or platforms. Severity: high for conflicting authoritative records and lower for harmless formatting differences. Owner: local SEO lead or operations owner. Corrective action: correct inaccurate records, request duplicate cleanup where appropriate, and document sources that cannot be edited. Validation: revisit the same sources and retain the confirmed final values. Consistency is an entity-data quality objective, not a guarantee of local search movement.

Search titles and description copy. Evidence required: current title tags, rendered page content, search snippets where available, and Search Console query context for the homepage and top 10 landing pages. Use 60 characters as an editorial review ceiling for titles and 120-155 characters as a practical description range, not as guaranteed display limits. When wording such as 24/7 availability appears, verify that the firm can factually support it. Pass condition: each priority page has unique, accurate metadata that matches the page's real service, jurisdiction, and visible content. Fail condition: missing or misleading titles, scaled duplication, unsupported urgency language, or metadata that promises something the page does not provide. Severity: medium by default and higher when the wording materially misleads. Owner: SEO editor, with attorney review when legal or advertising claims are implicated. Corrective action: rewrite the title or description to reflect actual page intent and supportable firm facts. Validation: inspect the rendered HTML, confirm the intended tags are deployed, and observe how Google elects to display the result without assuming that supplied description text will be used.

Review-request process. Evidence required: the written invitation, delivery method, eligibility rule, operational workflow, and applicable platform policy. A previously published internal observation compared firms around 30 reviews with competitors around 5; because the source JSON contains no supporting source URL, preserve that only as a historical observation requiring source reconciliation, not as a ranking benchmark. Pass condition: eligible clients are asked consistently for honest feedback without incentives, review gating, discouraging negative feedback, outcome-conditioned selection, or requests limited to satisfied clients. Fail condition: any selective, incentivized, deceptive, or unsupported process. Severity: high when the workflow creates advertising, platform, or reputation risk. Owner: firm operations and responsible attorney. Corrective action: replace selective logic with a neutral eligibility rule and revise invitation language as needed. Validation: review a sample of actual invitations and confirm that the same eligibility rule is applied in practice.

Core citation quality. Evidence required: live listings and a maintained citation inventory. Review 5-10 established legal, professional, or local sources that are genuinely relevant to the firm, rather than submitting to every directory available. Pass condition: each selected listing is accurate, belongs to the firm, and does not imply an office, jurisdiction, or service presence that does not exist. Fail condition: inaccurate identity data, false location claims, uncontrolled duplicates, or irrelevant listings created only for volume. Severity: high for misleading location information and medium for missing but useful records. Owner: local SEO lead. Corrective action: claim, correct, merge, or request removal according to the evidence and platform process. Validation: revisit each reviewed record and log the final status. The decision standard is accurate entity representation, not a directory-count quota.

Mobile rendering and contact usability. Evidence required: representative practice, attorney, location, and contact pages tested on real devices or dependable browser emulation, plus Search Console and browser diagnostics when they add useful context. Pass condition: primary navigation, forms, tap targets, phone links, text, and critical content remain usable without broken interaction or layout obstruction. Fail condition: a prospective client cannot reliably read, navigate, or contact the firm from an affected template. Severity: high when essential paths are blocked and otherwise based on scope. Owner: developer or front-end owner. Corrective action: repair responsive layout, scripts, components, and interaction defects supported by the test evidence. Validation: repeat the same test cases after deployment and record the result.

Performance triage. Evidence required: PageSpeed Insights or comparable lab and field evidence for representative templates, plus direct observation of real page behavior. The source version used a mobile score above 50 as an operating threshold; retain it as a triage reference rather than a Google quality guarantee. Pass condition: material bottlenecks affecting important templates are understood, assigned, and either corrected or consciously accepted with documented rationale. Fail condition: significant delays or rendering defects remain unexplained or block essential use. Severity: based on user impact, affected templates, and traffic exposure. Owner: developer or performance specialist. Corrective action: optimize images, scripts, fonts, caching, server behavior, or rendering only where evidence supports the intervention. Validation: rerun the same diagnostic under comparable conditions and confirm that the targeted defect changed as intended.

HTTPS and redirect integrity. Evidence required: browser checks, crawl output, certificate state, mixed-content inspection, and redirect behavior for representative legacy and current URLs. Pass condition: public pages resolve securely, certificates are valid, essential resources do not create security warnings, and intended legacy locations route cleanly to the correct secure destination. Fail condition: certificate warnings, mixed-content failures, redirect loops, chains that obstruct use, or redirects to irrelevant destinations. Severity: critical for security warnings and high for widespread routing defects. Owner: developer, hosting administrator, or infrastructure owner. Corrective action: repair certificate, resource, host, and redirect configuration according to the observed defect. Validation: recrawl and manually test representative URLs after deployment.

Sitemap and robots controls. Evidence required: the XML sitemap, robots file, Search Console submission state, canonical behavior, and a crawl sample. Pass condition: canonical pages intended for search discovery are not accidentally blocked and the sitemap reflects the current site rather than retired or redirected inventory. Fail condition: priority practice pages are unintentionally excluded, blocked, or absent because of configuration defects. Severity: critical for broad unintended exclusion and lower for stale entries with little user impact. Owner: technical SEO or developer. Corrective action: adjust directives, canonical handling, and sitemap generation to match the intended index state. Validation: retest affected URLs and confirm the corrected submission or discovery state where appropriate.

Crawl and index diagnostics. Evidence required: Search Console page indexing information, representative URL inspection, crawl evidence, and server or rendering data when available. Pass condition: important pages can be discovered, rendered, and indexed unless a documented editorial or technical reason calls for exclusion. Fail condition: unintended noindex directives, blocked resources, broken canonicals, redirect errors, soft errors, server failures, or orphaned priority content prevent the intended state. Severity: critical for broad unintended exclusions and high for a priority page that cannot be processed. Owner: technical SEO with developer support. Corrective action: resolve the evidence-backed cause, whether internal linking, canonical configuration, redirect logic, rendering, or server behavior. Validation: inspect the corrected URLs and record later index state without treating recrawl timing as guaranteed.

Structured data fidelity. Evidence required: rendered markup, visible page content, and a schema validator or Google's supported testing tools. Pass condition: any LocalBusiness or attorney-related structured data accurately mirrors visible, supportable facts and does not invent credentials, locations, ratings, or services. Fail condition: markup conflicts with the page, contains unsupported properties, or is invalid in a way that obscures intended meaning. Severity: high for misleading markup and medium for non-critical technical invalidity. Owner: developer with editorial and attorney review where claims are involved. Corrective action: correct or remove unsupported properties rather than adding markup only to pursue visibility. Validation: rerun the validator and compare the markup against the visible page. Structured data can help systems understand content, but this checklist does not treat it as a guaranteed ranking factor or rich-result entitlement.

Internal linking to priority destinations. Evidence required: crawl data and manual review of the homepage, navigation, practice hubs, attorney pages, and genuine location pages. Confirm that the homepage and relevant hubs expose the top 3-5 priority service destinations through descriptive anchors where the relationship is useful to a reader. Pass condition: important pages are reachable through sensible navigation or contextual links and anchors describe the destination without manipulative repetition. Fail condition: priority pages are orphaned, buried behind broken paths, or linked with misleading or excessively repetitive anchor text. Severity: high for orphaned priority pages and medium for weak context. Owner: SEO editor or information-architecture owner. Corrective action: add, remove, or revise links based on user utility and page relationships. Validation: recrawl and confirm the intended paths and anchors are present after publication.

Genuine location-page usefulness. Evidence required: proof of a real office, a legitimate jurisdiction or service relationship, attorney availability where relevant, and useful information that is actually specific to the place. A previously published operating expectation used 2-4 months as an observation window for some location-page work; retain that only as a historical observation period, not a ranking promise. Pass condition: the page has a genuine reason to exist, answers location-specific questions a prospective DUI client may reasonably have, and does not imply an office or presence the firm lacks. Fail condition: the page is a city-name swap, materially duplicates another page, or misrepresents the firm's footprint. Severity: high for false location claims and medium for thin duplication. Owner: attorney editor and SEO lead. Corrective action: substantively improve, consolidate, redirect, or remove the page according to the evidence. Validation: review the live page for local usefulness, factual accuracy, and linkability, then treat later search behavior as a separate observation.

Distinct topic coverage. Evidence required: Search Console queries, intake questions, practice knowledge, existing page inventory, and applicable legal review. A practical content cluster may contain 4-6 closely related pages when the questions genuinely deserve separate treatment; that is an editorial planning model, not a ranking formula. Pass condition: each page answers a distinct user need, avoids duplicating another URL's purpose, and connects naturally to the broader DUI topic. Fail condition: pages compete for the same intent, repeat generic text, or publish jurisdiction-sensitive explanations without adequate review. Severity: medium for coverage gaps and high when conflicting or inaccurate content may mislead readers. Owner: content strategist and reviewing attorney. Corrective action: expand, merge, redirect, update, or restructure based on the evidence. Validation: confirm each retained page has a distinct purpose, appropriate review status, and a discoverable path from a relevant hub.

Sustainable editorial workflow. Evidence required: a publishing calendar, research inputs, attorney review capacity, update ownership, and performance evidence from existing content. An internal operating cadence of 1-2 posts per month may be manageable for some firms, but posting frequency itself should not be described as an official ranking factor. Pass condition: the schedule can be sustained without sacrificing factual accuracy, legal review, source quality, or maintenance of older pages. Fail condition: volume goals cause thin, repetitive, outdated, or unsupported legal content. Severity: low for a missed schedule and high for inaccurate or misleading published material. Owner: editor and responsible attorney. Corrective action: reduce volume, consolidate topics, improve sourcing, or prioritize updates where needed. Validation: verify the completed article's sources, legal review status, internal links, visible claims, and indexability before closeout.

Professional citations and earned mentions. Evidence required: a list of relevant bar, legal, local, civic, or professional sources and the live destination pages for any obtained listing or mention. Pass condition: each source is legitimate, relevant, accurately represents the firm, and exists for an editorial, professional, or community reason rather than pure link volume. Fail condition: paid or deceptive placement is undisclosed, business details are false, or the source is irrelevant to the practice. Severity: high for deceptive tactics and medium for stale but correctable records. Owner: outreach or local SEO lead. Corrective action: correct firm information, pursue credible references, or discontinue low-quality placement activity. Validation: inspect the live source and confirm that the final representation of the firm remains accurate.

Review quality and testimonial controls. Evidence required: the review-request policy, public review profiles, and the process used to select or display testimonials on the website. A prior internal note mentioned inquiry changes once review counts exceeded 25, but the source URL required to verify that observation is absent here; keep it only as historical material requiring source reconciliation. Pass condition: eligible clients are asked consistently for honest feedback and the firm does not gate, incentivize, script, suppress, or selectively request reviews based on expected sentiment. Fail condition: review collection or display uses deceptive selection, unsupported editing, or claims that imply guaranteed results. Severity: high for selective or misleading practices. Owner: operations and responsible attorney. Corrective action: standardize the neutral invitation process and remove unsupported outcome claims tied to review volume. Validation: audit the live request flow and a sample of displayed testimonials against the documented policy.

Relevant earned-link outreach. Evidence required: target relevance, editorial rationale, outreach record, claim support, and the final live source if a reference is earned. The earlier version contrasted one authoritative editorial link with 20 low-quality citations; retain that only as an illustrative quality-over-quantity principle, not a measured equivalence. Pass condition: outreach is relevant, transparent, and based on real expertise, commentary, public resources, or newsworthy firm information. Fail condition: the tactic relies on fabricated cases, hidden paid endorsements, manipulative link schemes, or unsupported legal claims. Severity: high for deception or platform-policy risk. Owner: outreach lead with attorney review for legal statements. Corrective action: stop the problematic tactic and replace it with supportable, editorially relevant outreach. Validation: inspect the live reference and confirm that it accurately describes the firm and the cited contribution.

Boundary for this checklist: This material is educational and cannot guarantee compliance; responsible legal, medical, or regulatory reviewers remain required where applicable. DUI lawyer advertising and solicitation should be evaluated against ABA Model Rules 7.1-7.3, governing state rules, and current ethics guidance before publication, distribution, or outreach.

Review solicitation. Evidence required: the exact invitation language, delivery method, eligibility rule, any incentive logic, and any filtering or escalation steps. Pass condition: eligible clients are asked consistently for honest feedback without incentives, review gating, discouraging negative feedback, or selecting only satisfied clients. Fail condition: the workflow steers sentiment, hides negative options, conditions requests on satisfaction, or otherwise creates deceptive or rule-sensitive behavior. Severity: critical when the process may violate governing rules or materially mislead. Owner: responsible attorney and operations lead. Corrective action: remove incentives and selective criteria, replace them with a neutral eligibility process, and revise the invitation. Validation: review the final template and sample workflow before use and retain the approval record.

Outcome and performance claims. Evidence required: the exact public claim, underlying records, calculation basis if applicable, context needed to avoid a misleading impression, and attorney approval. A statement such as 'we win 95% of cases' should not appear unless it is accurate, properly substantiated, and permitted under the applicable rules; this checklist does not establish those conditions. Pass condition: the final wording is factually supportable, appropriately contextualized, and approved under governing advertising requirements. Fail condition: the statement guarantees an outcome, omits material context, or cannot be substantiated. Severity: critical for guarantees or materially misleading implications. Owner: responsible attorney. Corrective action: remove, qualify, or replace unsupported wording based on documentary evidence and applicable rules. Validation: compare the deployed copy with the approved evidence record and attorney review.

Case-result disclaimers. Evidence required: the jurisdictions involved, the exact result references, current state guidance, and the placement of any required disclosure. Pass condition: required disclosures are present where required, readable in context, and do not contradict or cure an otherwise misleading claim. Fail condition: a required disclosure is absent, inaccurate, or too detached from the claim to perform its intended role. Severity: high when a mandatory disclosure is missing. Owner: responsible attorney or ethics counsel. Corrective action: add, revise, relocate, or remove result language based on governing requirements rather than copying a generic disclaimer from another jurisdiction. Validation: obtain attorney sign-off on the final published wording and placement.

Testimonials and case examples. Evidence required: authenticity, source, consent where required, edit history, context, and the rules governing publication. Pass condition: each testimonial or example is genuine, accurately represented, and accompanied by any disclosure actually required. Fail condition: content is fabricated, misleadingly edited, paid without appropriate treatment, or published without required permission or context. Severity: high for fabricated or materially misleading material. Owner: responsible attorney and content owner. Corrective action: remove unsupported material or obtain the permissions, context, and disclosure required for publication. Validation: compare the live presentation with the retained evidence and approval record.

Credentials and comparative statements. Evidence required: current certificates, awards, memberships, rankings, or other documentary support, plus the exact comparison being made. Pass condition: every credential is current and every comparative statement can be supported under the rules that apply. Fail condition: a credential is expired, invented, overstated, or presented in a way that creates an unsupported superiority claim. Severity: high for false credentials or unsubstantiated superlatives. Owner: attorney profile owner and compliance reviewer. Corrective action: remove, update, or precisely qualify unsupported language. Validation: retain the support record and recheck the live profile or page after publication.

Fees and payment language. Evidence required: current engagement terms, conditions, exclusions, payment arrangements, and applicable advertising rules. If a page uses wording such as affordable, identify what the term is intended to communicate and whether the firm can substantiate the impression it creates. Pass condition: fee language is current, accurate, and not misleading about scope, conditions, or availability. Fail condition: omitted conditions materially change what a prospective client would reasonably understand. Severity: high when public wording can create a false expectation about cost or representation. Owner: responsible attorney. Corrective action: clarify, qualify, or remove unsupported fee wording. Validation: compare the live statement with approved engagement terms and the attorney's final review.

Immediate defects with clear user or legal risk. Evidence required: live proof of inaccurate firm data, blocked or broken priority pages, misleading claims, unusable mobile paths, or another defect that can be reproduced. An internal comparison period of 2-3 weeks may be used to observe local visibility after a correction, but that window is not a guaranteed search response time. Pass condition: the defect is corrected and the source of truth confirms the intended state. Fail condition: the problem still reproduces or supporting evidence remains unresolved. Severity: critical or high when the issue can misdirect users, block contact, expose unsupported claims, or prevent discovery of essential pages. Owner: the person who controls the affected system, with attorney review where legal claims are involved. Corrective action: repair the specific defect and document what was changed. Validation: retest the original failure condition and save the confirming evidence.

Near-term foundation defects. Evidence required: the most relevant 5-10 citation records, representative performance diagnostics, HTTPS state, sitemap and robots controls, crawl evidence, structured data, and internal linking. Pass condition: the identified technical or entity-data defect has been corrected and the same diagnostic no longer reproduces it. Fail condition: the issue persists, the fix introduces a new problem, or the team cannot produce evidence of the intended state. Severity: set from user impact, site reach, and risk rather than from the existence of a tool warning alone. Owner: technical SEO, developer, or local SEO lead as appropriate. Corrective action: address the evidence-backed cause rather than chasing every diagnostic suggestion. Validation: rerun the same check under comparable conditions and record the post-fix result.

Coordinated technical implementation block. Evidence required: a scoped remediation list, owners, dependencies, deployment records, and acceptance tests. A 2-4 week implementation block can be used when multiple templates or systems need coordinated changes. Pass condition: the agreed technical scope is deployed, tested, documented, and no critical acceptance failure remains open. Fail condition: required work is incomplete or validation cannot reproduce the intended behavior. Severity: inherit the highest unresolved defect in the scoped work. Owner: technical project lead. Corrective action: resolve failed acceptance items and update dependencies or scope where evidence requires it. Validation: complete the agreed acceptance checks after deployment. Keep implementation duration separate from search-engine reprocessing time.

Longer content and authority program. Evidence required: research briefs, attorney review records, genuine location evidence, topic inventory, citation status, outreach records, and follow-up measurement. A 2-6 month operating horizon can accommodate those production and review stages without implying a ranking forecast. Pass condition: each underlying task meets its own evidence and validation criteria. Fail condition: work is published without required review, remains duplicative or misleading, or lacks the evidence needed for closeout. Severity: based on the risk and reach of each underlying item. Owner: content, attorney, local SEO, or outreach owner according to the workstream. Corrective action: correct the specific failed item rather than treating the whole program as passed by activity volume. Validation: close each task independently and record later search changes only as observations.

Avoidable deceptive tactics. Evidence required: site content, profile records, review workflows, link records, and any third-party instructions relevant to the suspected tactic. Pass condition: the firm is not using fake reviews, fabricated offices, keyword stuffing, cloaking, undisclosed manipulative link schemes, or unsupported legal claims. Fail condition: any such tactic is present or actively being directed. Severity: critical when the conduct creates legal, platform, or user-deception risk. Owner: firm leadership and the responsible channel owner. Corrective action: stop the tactic, remove affected material, preserve a remediation record, and obtain appropriate legal or policy review where needed. Validation: recrawl affected pages, recheck profiles and workflows, and confirm that the problematic material or process no longer exists.

Create a shared tracker with Task ID, evidence, pass or fail condition, severity, owner, corrective action, validation method, target date, reviewer, and final status. For workload planning, Quick Wins can be grouped into a 1 week block, while a broader Foundation pass may be scheduled across 3-4 weeks. Treat those as management windows, not promises of search movement. If content production is included, an internal cadence such as 1-2 posts per month can be used only when research, attorney review, and maintenance capacity can support the quality.

Review unresolved high-severity items in a recurring team meeting and require a reason whenever an item remains open. The prior version used 3-4 weeks as an observation window for some early technical and local changes and 8-12 weeks for some content and authority observations. Retain those only as historical operating windows. Search systems may process changes sooner or later, and movement cannot be guaranteed.

Use Search Console and the live search experience to compare impressions, clicks, indexing, and query visibility after implementation. The earlier source mentioned a 20-40% traffic increase in months 2-3; because no supporting source URL appears in the source JSON, treat that figure as a previously published internal observation requiring source reconciliation, not as an expected result, forecast, or causal estimate.

Report evidence rather than attribution claims. A status note might record that firm data was corrected across 6 directories and that 8 new reviews were received through a neutral, non-incentivized request process. The closeout question is whether each task passed its stated validation check. A later ranking or inquiry change should be recorded separately because multiple factors may contribute.