Targeting Broad Debt Terms Instead of Filing-Intent Questions
Observable evidence: Search Console and intake notes show traffic arriving on generic debt topics while pages about urgent filing decisions receive few qualified visits. The source copy previously estimated that 20-40 percent of traffic in one such mix was ready to convert, but it provides no supporting source URL, so treat that figure as a historical internal observation rather than a verified benchmark.
Consequence: A firm can spend editorial and link-acquisition effort on queries that do not match the reader's immediate legal decision, while the pages that explain Chapter 13 repayment concerns and Chapter 7 asset questions remain underdeveloped.
Correction: Build an intent map from real search queries and intake language. Separate informational education from pages designed to explain a specific bankruptcy service, filing concern, or next step. Do not promise outcomes, eligibility, discharge, asset protection, or timing that depends on case facts.
Owner: The SEO lead owns query mapping; the bankruptcy attorney or designated legal reviewer owns the accuracy of procedural explanations and claims.
Verification: Compare query-to-page alignment, consultation quality, and cannibalization before and after the rewrite. A previously published Chicago example in the source associated a targeting change with a 30 percent increase in qualified leads, but the JSON contains no source URL for that example, so it should not be treated as causal or externally verified.
Severity: high
Publishing Legal Content Without Clear Expertise, Review, or Support
Observable evidence: Practice pages have no named author or reviewer, attorney biographies are disconnected from the articles they substantively reviewed, important legal statements lack primary-source support, or the copy reads like a generic summary that could belong to any jurisdiction.
Consequence: Readers cannot easily judge who stands behind consequential legal information, and search systems receive weaker signals about the relationship between the firm, its attorneys, and the content. The larger risk is editorial: inaccurate or overbroad bankruptcy guidance can mislead a person making a serious financial decision.
Correction: Give substantive pages a real author or qualified reviewer, maintain complete attorney biographies, cite controlling or authoritative sources when the page makes a legal proposition, show an appropriate editorial date, and remove claims that the firm cannot substantiate. Use disclaimers where counsel determines they are appropriate, but do not treat a disclaimer as a substitute for accurate content.
Owner: The managing attorney or assigned legal reviewer owns factual and ethics review; the content lead owns attribution, citation hygiene, and revision workflow.
Verification: Sample published pages and confirm that the named reviewer actually reviewed the current version, that cited authorities support the nearby proposition, and that firm credentials displayed on the page match the firm's current records.
Severity: critical
Treating Local SEO as a Profile Checklist Instead of a Location-Accuracy Problem
Observable evidence: The firm's name, address, phone information, categories, or office details conflict across the website and major listings; the profile points to a weak or irrelevant landing page; or location pages exist for markets where the firm has no genuine office or useful location-specific information. The source previously used a 20-30 mile travel range as a planning assumption, but no supporting URL is included, so it should not be presented as a universal client-behavior benchmark.
Consequence: Prospective clients may encounter conflicting contact information or pages that do not explain whether the firm actually serves their situation. That creates avoidable friction and can weaken the consistency of the firm's local presence.
Correction: Reconcile business information across owned properties and important listings, confirm profile eligibility and verification status, connect the profile to the most useful genuine office page, and create a dedicated location page only when there is a real location and enough location-specific information to help a reader. Ask eligible clients consistently for honest feedback without incentives, review gating, discouraging negative feedback, or selecting only satisfied clients.
Owner: The local SEO operator owns listing accuracy; firm operations owns the underlying office and contact data; counsel should review any advertising or testimonial language that could trigger professional-responsibility concerns.
Verification: Recheck the live profile, website, and priority listings after corrections and document any conflicts that remain. The source also described an internal example that coincided with a 50 percent increase in phone calls after profile work, but no supporting source URL is present, so that result should be treated as an unverified observation, not a promised effect.
Severity: critical
Writing for Legal Formality Instead of the Reader's Immediate Decision
Observable evidence: Pages open with doctrine, defined terms, or dense statutory summaries before answering the practical question a distressed reader came to resolve. Mobile sessions show repeated backtracking, shallow scroll depth, or abandonment around long blocks of unexplained legal language.
Consequence: A reader may leave without understanding whether the page is relevant, what information they need to gather, or how to contact the firm for case-specific advice. High friction can also make otherwise accurate content less usable.
Correction: Lead with the decision the reader is trying to make, explain terms in plain language, separate general information from case-specific advice, and provide a clear contact path without fear-based or guaranteed-outcome language.
Owner: The content strategist owns readability and page structure; the bankruptcy attorney owns legal accuracy and the boundaries between general education and advice.
Verification: Run moderated or internal usability reviews on mobile, then compare reading patterns and qualified inquiry behavior. The source described a prior rewrite that coincided with 45 additional seconds of on-page time, but no source URL is supplied, so treat that figure as a historical observation rather than evidence of causation.
Severity: medium
Using Structured Data as a Shortcut for Trust or Search Features
Observable evidence: Markup names people, services, reviews, or business details that are not visibly supported on the page, validation errors are unresolved, or the team treats FAQ markup as a way to force a search feature. FAQ content can still help readers, but it should not be implemented on the assumption that FAQPage markup will earn a Google FAQ rich result.
Consequence: Inaccurate structured data can create conflicts between machine-readable information and the visible page, while an overemphasis on markup diverts attention from stronger fundamentals such as authorship, factual support, service clarity, and local accuracy.
Correction: Use only schema types and properties that accurately describe the entity and visible content. For pages comparing Chapter 7 and Chapter 13, keep the questions and answers useful in the rendered page first, then mark up only what the implementation and current eligibility rules support.
Owner: The technical SEO or developer owns implementation; the content owner verifies that marked-up statements match the page; legal review remains responsible for the accuracy of bankruptcy claims.
Verification: Validate the deployed code, inspect rendered output, compare machine-readable values with the visible page, and review Search Console enhancement reports where applicable. The source cited a boutique-firm example with a 15 percent increase in organic click-through rate after FAQ-related work, but without a supporting source URL that observation should not be treated as verified or caused by the markup itself.
Severity: high
Compressing Distinct Bankruptcy Questions Into One Generic Practice Page
Observable evidence: A single page tries to cover Chapter 7, Chapter 11, and Chapter 13 while offering only brief, interchangeable summaries. A reader researching Chapter 13 repayment issues reaches the same generic page as someone evaluating liquidation options, and internal links do not signal which page should answer each question.
Consequence: The site can create self-competition, weak topical depth, and a poor match between the query and the information presented. The problem is not the absence of more URLs; it is the absence of distinct, useful answers where the underlying legal questions materially differ.
Correction: Build separate pages for Chapter 7 and Chapter 13 only when each page can provide genuinely distinct information, attorney-reviewed explanations, and a clear relationship to broader bankruptcy resources. Add or consolidate pages based on reader need, not a quota.
Owner: The SEO strategist owns the topic map and internal linking; the bankruptcy attorney owns the substantive boundaries and jurisdiction-sensitive explanations.
Verification: Check for overlapping query sets, duplicate introductions, near-identical headings, and internal-link ambiguity. The source describes an internal example in which a 10-page cluster on Chapter 7 eligibility later outranked the homepage within 60 days, but no supporting URL is provided, so it should be treated as an unverified historical observation rather than a repeatable timeline.
Severity: high
Allowing Mobile Friction and Performance Problems to Block Urgent Inquiries
Observable evidence: The mobile layout shifts during load, the call action is difficult to use, forms require unnecessary fields, intrusive overlays cover substantive content, images are oversized, or important text is hidden behind interaction patterns that fail on smaller screens.
Consequence: A person trying to understand a bankruptcy option or contact counsel may abandon the page before completing the task. Search performance can also be constrained when technical quality, crawlability, or mobile usability problems remain unresolved.
Correction: Compress and appropriately size media, remove blocking scripts that are not necessary, simplify the mobile contact path, keep primary content accessible, and fix layout instability or interaction defects. Evaluate a content delivery network or caching changes only when the technical diagnosis supports them.
Owner: The developer owns front-end performance and interaction fixes; the SEO lead owns diagnostics and measurement; the intake owner validates that the contact flow works for real users.
Verification: Re-test the same templates and devices after deployment and verify both field performance data and task completion. The source's previously published example described a PageSpeed score change from 40 to 90 alongside a 20 percent lower bounce rate, but no source URL is present, so the relationship should be treated as observational rather than proof that the score change caused the behavior change.
Severity: critical
