Diagnose the Search Problems on a DUI Defense Website Before Changing the Site

This audit is for a DUI defense practice that already has a live website and needs to understand why search visibility, qualified organic inquiries, or local discovery are not matching expectations. It is especially useful after a redesign, platform migration, substantial content change, unexplained decline in Search Console performance, or a material change to the firm's local business information.

Run it before commissioning a broad SEO rebuild. The useful output is not a list of generic tasks; it is a set of findings with evidence, severity, ownership, a proposed corrective action, and a validation method. That makes it easier to compare an agency scope or an internal work plan with the problems the site actually shows.

This remains a diagnostic companion to the DUI SEO checklist. The audit establishes why a condition matters on this site; the checklist can then help organize implementation. Do not mark an item as failed merely because a competitor uses a different tactic.

Common triggers include:

• SEO work has been underway for four to six months without a clear explanation of what changed in crawl, visibility, or conversion paths
• A local or organic competitor has displaced important DUI queries and the firm needs evidence before reacting
• A redesign or migration altered URLs, canonicals, internal links, templates, or mobile behavior
• Search Console reports a manual action, indexing problem, security concern, or another issue that needs direct investigation
• The firm is increasing search investment and needs a defensible baseline for later comparison

If search performance is stable, the same method can be used as a periodic health review. The point is still to detect meaningful change and verify causes, not to manufacture work from harmless differences.

The technical stage asks a narrow question: can search systems reliably fetch, render, understand, and index the DUI pages the firm actually intends to make public? Do not infer a technical failure from a ranking decline alone. Build an evidence set first.

Evidence

Use Google Search Console index reporting, URL Inspection, rendered page checks, server behavior, canonical output, redirect maps, robots directives, sitemap entries, HTTPS status, and representative mobile tests. Review the homepage, the principal DUI service page, attorney pages, and genuine location pages. For excluded URLs, record the stated reason and determine whether exclusion is intentional. For redirects, confirm the final destination and whether internal links point directly to it. For structured data, validate only markup that is actually present and eligible for the page; do not assume that adding LegalService or Attorney markup creates a ranking benefit or a special search feature.

Severity

Mark a finding critical when intended money or information pages are inaccessible, unintentionally non-indexable, routed to the wrong destination, or exposed to active browser security warnings. Mark rendering or performance problems by user impact and reproducibility. A mobile PageSpeed score below 50 can be logged as a diagnostic signal for investigation, not as proof that the score itself caused a ranking loss; compare the underlying field or lab findings with the site's real templates and the existing DUI search benchmarks without converting a benchmark into a guarantee.

Owner

Assign crawl directives, canonicals, redirects, template output, HTTPS, and rendering defects to the technical owner who can change the application or CMS. Assign content-dependent technical findings, such as an incorrect canonical chosen because two pages are near-duplicates, jointly to technical and editorial owners so the fix addresses the underlying duplication.

Corrective action

Make the smallest change that resolves the verified cause. Restore access only for URLs that should be indexed, point internal links to final destinations, consolidate accidental duplicates deliberately, remove mixed-content resources, and correct structured data only where the page truthfully supports it. Avoid large template changes while the evidence is still ambiguous.

Validation

Re-test the affected URL in the same tools and conditions used to establish the finding. Confirm the expected status code, robots directive, canonical, rendered content, HTTPS state, and structured-data validity. For index changes, distinguish successful technical correction from later search-engine processing; the audit closes the finding when the implementation is correct and re-checkable, not when a ranking outcome is assumed.

This stage determines whether the site's core DUI pages give a searcher enough accurate, jurisdiction-relevant information to understand the issue and the firm's role. It also checks whether multiple pages are genuinely distinct or are competing with near-duplicate copy. The audit should not reduce quality to a word-count target.

Evidence

Inventory the primary DUI service page, related charge or process pages, attorney pages, and any real location pages. Compare each URL with the queries and landing-page data available in Search Console, the page's actual title and headings, internal links, and the questions the page answers. If an older template treated a 300-word practice page as automatically too thin, keep that figure only as a historical screening prompt; the evidence that matters is whether necessary topics are missing, inaccurate, duplicated, or disconnected from the query.

Severity and priority

Separate visibility problems from content defects. For high-impression queries with weak clicks, inspect whether the search snippet and page intent align before declaring a title problem. For queries appearing in the 10-50 position range, treat the range as an observation that may identify an opportunity, not as proof that a dedicated page is required. A new page is justified only when the firm has a real service, jurisdiction, or location distinction and can provide useful unique information.

Owner

Assign legal accuracy and jurisdictional statements to the attorney or qualified reviewer responsible for the substance. Assign search-intent mapping, duplication, internal-link structure, headings, and snippet copy to the SEO or editorial owner. A genuine location page should have an owner who can supply useful location-specific facts; do not create a page for every nominal market or service area by default.

Corrective action and validation

Expand or restructure a page only where the audit shows a real information gap. Remove boilerplate that merely swaps place names, clarify which jurisdiction a legal explanation applies to, merge overlapping pages when they serve the same intent, and strengthen internal links where users and crawlers need clearer pathways. Validate by re-reading the corrected page against the recorded query set, confirming that the legal reviewer approved substantive claims, checking that each retained location page has unique useful information, and verifying that internal links and index directives now support the intended page hierarchy.

The local stage checks whether the firm's public business information is accurate, eligible, and consistent enough for a prospective client and search platform to understand the real practice. It should not assume that a profile field, posting cadence, photo upload, map embed, or review-response routine is an official ranking factor.

Evidence

Compare the Google Business Profile with the firm's real-world name, address or service-area configuration, phone, website destination, hours, and currently available primary category options. Verify that the selected category truthfully reflects the practice. Record duplicates, suspensions, mismatched landing pages, stale hours, incorrect phone routing, and citation discrepancies. Check whether the profile links to a page that accurately represents the office or service context rather than a generic or fabricated location page.

Severity, owner, and corrective action

Prioritize eligibility, ownership, wrong contact information, suspended or duplicated profiles, and material identity conflicts above cosmetic completeness. Review history can be documented without turning it into a causal ranking claim: an older internal comparison might show one profile with 80 reviews, a latest review from 18 months earlier, and another profile with 25 reviews, but that observation does not prove why either profile ranked. The local or reputation owner should request honest feedback consistently from eligible clients without incentives, review gating, discouraging negative feedback, or selecting only satisfied clients. Any solicitation process also needs jurisdiction-specific ethics review, including applicable provisions such as Rule 7.2.

Validation

After corrections, confirm that the live profile shows the intended business data, the destination URL resolves correctly, and known duplicate or citation conflicts have been addressed at their source where practical. If legacy listings contain variants such as Suite 100 and #100, determine whether they refer to the same real address before changing them; consistency is useful, but do not manufacture a format simply to satisfy a tool. Re-check representative directories and the profile itself, document what changed, and keep unresolved third-party records as open evidence rather than declaring the local issue fixed prematurely.

This stage is educational and is not legal advice. Attorney advertising and solicitation requirements vary by jurisdiction and can change. This audit cannot guarantee compliance; responsible legal, medical, or regulatory reviewers remain required where their review is applicable.

For a DUI defense site, review public claims against the firm's current jurisdiction-specific rules and the legal ethics guidance that actually applies. ABA Model Rules 7.1, 7.2, and 7.3 can be useful reference points, but state adoption, wording, interpretations, filing duties, and required notices may differ. Search quality work does not replace that review, and a compliance concern should not be described as a Google penalty unless there is separate evidence of a search action.

Evidence

Collect the pages, ads, testimonials, badges, attorney bios, intake language, lead-generation disclosures, and calls to action that make factual or comparative claims. Flag outcome guarantees, unsupported superiority claims, statements implying improper influence, or other language that a responsible reviewer should assess under Rule 7.1. Record the exact text and page rather than labeling an entire site non-compliant from a single phrase.

Severity and owner

Assign potentially misleading claims, missing jurisdiction-required notices, testimonial presentation, and referral or lead-generation disclosures to the attorney or qualified ethics reviewer who can determine the applicable rule. The SEO or content owner can identify and inventory the language, but should not make the final legal determination. Severity should reflect the responsible reviewer's assessment and the scope of exposure, not an invented search-ranking consequence.

Corrective action

Revise or remove unsupported claims, add only the notices actually required for the jurisdiction and context, and make testimonial or review displays accurate and non-misleading. Do not use review gating or incentives. Where a lead-generation or referral arrangement exists, document how it operates and obtain appropriate review before publishing disclosures or changing the relationship.

Validation

Have the responsible reviewer confirm the revised language against current state requirements and the site's actual facts. Re-scan the templates and representative pages to ensure the approved language appears where intended, including mobile and dynamically generated views. If a paid referral or lead arrangement is part of the site, confirm that the final presentation reflects the reviewer's conclusion under applicable Rule 7.2 requirements and any state variation.

At the end of the audit, every open finding should have evidence, a severity rating, an accountable owner, a corrective action, and a validation step. Sort the backlog by what can block access, misstate the firm's legal or business information, expose material advertising risk, or prevent users from reaching the correct page. Ease of implementation is secondary.

Critical findings to resolve first

• Important public pages are unintentionally blocked, non-indexable, redirected incorrectly, or compromised by active security warnings
• The business profile is ineligible, suspended, duplicated, controlled by the wrong party, or showing materially wrong contact information
• A responsible legal reviewer identifies advertising language or missing notices that require prompt correction
• A migration or template defect sends users and crawlers to the wrong canonical or destination

High severity work for the 30-60 day window

Use this window only as an implementation stage after critical defects are controlled, not as a promise about ranking recovery. An older template may have flagged a principal DUI page with fewer than 800 words or a mobile score below 50; retain those values as screening heuristics, then verify the actual information gap, rendering problem, or user impact before prescribing work. Other candidates can include near-duplicate location pages, unresolved internal-link gaps, materially stale business information, or review-process weaknesses that need policy correction.

Ongoing validation and lower-risk optimization

• Re-check Search Console evidence after technical changes have been processed
• Monitor whether corrected pages continue to match their intended queries and legal scope
• Validate structured data when templates change, without treating markup as a guaranteed ranking mechanism
• Reconcile secondary citations where differences could confuse users or platforms
• Keep the business profile accurate and publish updates when they are useful to clients, not to satisfy an invented posting-frequency rule

If critical findings appear in three or more audit areas, coordinate the work across technical, editorial, local, and legal-review owners so fixes are sequenced and independently validated. A specialist can be useful when the firm lacks those capabilities, but the decision should be based on scope, risk, and expertise rather than an assumed speed or traffic outcome.

If the firm wants external help, use the audit record to define the engagement: require the specialist to map proposed work to the recorded findings, name who owns each correction, and state how completion will be validated. That makes the handoff testable without promising rankings, leads, or case outcomes.