Audit law firm SEO with evidence, owners, pass-fail criteria, and validation

This checklist is designed for managing partners, in-house marketers, operations leads, and agency reviewers who need to determine what is actually working, what is unverified, and what requires correction on a law firm website. It can also be used to review an incumbent provider's scope because every item should produce evidence rather than a verbal assurance.

The same audit method can work for a solo practice or a firm with 50+ attorneys: define evidence, pass or fail, severity, owner, corrective action, and validation. The priority changes by practice area, office footprint, website history, and intake model, but the verification discipline stays the same.

Do not mark an item complete merely because a plugin is installed, a profile exists, a page was published, or an agency says the work was done. Keep screenshots, exports, crawl results, page examples, review notes, or other records that show the actual condition.

Some checks require a developer, some require an attorney or ethics reviewer, and others belong to marketing operations or intake. This content cannot guarantee compliance, and responsible legal, medical, or regulatory reviewers remain required where applicable.

Audit objective: Confirm that priority pages can be securely served, crawled, rendered, indexed when intended, and used on mobile. Severity is blocking when the condition prevents access or creates a material security or indexing defect.

Evidence, pass-fail, owner, correction, validation:

• HTTPS: Evidence is browser and crawl output. Pass when intended URLs resolve securely and redirect rules are consistent. Owner: developer. Correct certificate or redirect problems, then recrawl representative templates.
• Mobile access: Evidence is live-device testing and relevant search tooling. Pass when core content, navigation, and contact paths work without layout or interaction failure. Owner: developer or UX lead. Correct responsive defects and retest.
• Core Web Vitals: Record the source and field or lab context for LCP under 2.5s, the preserved historical FID under 100ms example, CLS under 0.1, and the TLS 1.2 reference elsewhere in the technical inventory. These figures are checkpoints from the source, not ranking guarantees. Owner: developer. Fix the measured bottleneck and validate on the same template and metric source.
• XML sitemap: Evidence is the generated sitemap and Search Console submission state. Pass when intended canonical URLs are represented and stale or noncanonical URLs are not used as the source of truth.
• Robots directives: Evidence is robots.txt, page directives, and crawl testing. Pass when important pages are not unintentionally blocked and excluded pages are intentionally excluded.
• Noindex and canonicals: Evidence is rendered source and indexation reports. Pass when indexable pages self-canonicalize or intentionally canonicalize elsewhere and do not carry unintended noindex directives.
• Internal crawl paths: Evidence is a site crawl. Pass when priority pages are reachable through crawlable links and no essential navigation depends on a broken interaction.
• Duplicate URL control: Evidence is crawl clusters and canonical behavior. Pass when protocol, host, parameter, and legacy URL variants resolve predictably.
• Redirect integrity: Evidence is redirect-chain reports. Pass when migrations and legacy URLs resolve to the intended destination without loops or unnecessary chains.

Record the failing URL or template, severity, owner, corrective action, and validation date. Technical eligibility is necessary for evaluation, but it does not guarantee ranking.

Audit objective: Confirm that each priority page communicates one coherent search intent and that visible content, metadata, headings, links, and structured data agree. The source preserves examples of title length at 50-60 characters, meta description length at 120-155 characters, and an H1 aligned to the page purpose; use these as editorial checks, not ranking thresholds.

• Title: Evidence is a crawl export. Pass when each important page has a distinct, descriptive title aligned to its actual service or informational purpose. The source also repeats under 60 characters as an editorial example.
• Meta description: Evidence is a crawl export. Pass when the description accurately previews the page without unsupported claims; the source repeats 120-155 characters as a drafting example.
• Primary heading: Evidence is rendered HTML. Pass when the H1 is unique on the page, accurately names the topic, and is not merely promotional.
• Opening relevance: Evidence includes the H1 and page copy. Pass when the service, jurisdiction where relevant, and reader purpose are clear within the first 100 words without forced repetition.
• Keyword use: The source uses 2-3 body mentions as an example. Pass or fail should instead be based on natural language, intent coverage, and absence of stuffing.
• Internal anchors: Evidence is the link graph. Pass when anchors describe useful destinations and connect related services, attorneys, resources, and genuine locations.
• Images: Evidence is rendered markup and accessibility review. Pass when alt text describes meaningful images without keyword stuffing.
• Heading hierarchy: Evidence is rendered structure. The source references H1, H2, and H3 order. Pass when headings express a logical document outline rather than decorative styling.
• Content sufficiency: The source preserves examples of 500 words and 800 words. Do not use them as minimum ranking thresholds. Pass when the page substantively answers the service or informational intent.

Structured data validation:

• Organization data accurately reflects the firm information visible on the site.
• LocalBusiness or related local markup reflects a genuine eligible office and does not invent location data.
• BreadcrumbList matches the actual navigation hierarchy.
• Reader-facing FAQ content may be useful, but do not add or rely on FAQPage markup to claim a Google FAQ rich result.
• Article data, where used, matches the visible author and publication information.
• Person or attorney-related data reflects real credentials and relationships that the firm can substantiate.

Owner: SEO or developer for implementation, with editorial and legal review for claims. Validation: test the rendered page, crawl output, and structured data for consistency. Missing markup alone is not a ranking failure, and valid markup does not guarantee an enhanced result.

Audit objective: Verify genuine office eligibility, accurate firm information, and consistent public data. Severity is high when prospective clients can encounter the wrong address, phone, office status, or service description.

Google Business Profile:

• Ownership: Evidence is administrator access. Pass when the firm retains appropriate access and the listing represents an eligible office.
• Business name: Evidence is firm records and Google's live listing. Pass when the name follows platform rules and matches the firm's legitimate public identity.
• Address: Evidence is office records. Pass when the location is genuine, eligible, and consistently represented.
• Phone: Evidence is a test call and public listings. Pass when prospective clients reach the correct office or intake path and tracking does not corrupt business identity data.
• Website: Evidence is the live destination. Pass when it points to a relevant firm-controlled page and tracking parameters do not break canonical handling.
• Service areas: Pass only when they reflect where the firm genuinely serves clients and comply with Google's current rules; do not list nominal markets solely to target rankings.
• Categories: Evidence is the live profile. Pass when available categories accurately describe services the office genuinely provides.
• Posts and photos: Treat them as information and reputation assets. Do not use posting or photo cadence as a pass-fail ranking condition.
• Reviews: The source used 3 days as a response-time example. Do not use that cadence as an official ranking factor. Ask eligible clients consistently for honest feedback without incentives, discouraging negative feedback, or selecting only satisfied clients. Do not use review gating.

Directories and citations:

• Audit name, address, and phone consistency across the top 15 relevant listings identified by the source, then prioritize authoritative or client-used sources.
• Correct obsolete or materially inaccurate listings.
• Do not add directory links to the firm's footer merely to manufacture a search signal.

The source also references checking the top 5 directories. Use that as an audit-scope example, not an algorithmic threshold. Owner: local SEO or operations. Validation: compare live records with the firm's office source of truth.

Audit objective: Verify that legal-service content reflects matters the firm actually handles, has a responsible attorney or editorial owner, accurately states jurisdiction and limitations, and answers prospective-client questions without unsupported promises.

Practice-area pages:

• Pass when each distinct service intent has a useful page or is intentionally consolidated with a closely related service.
• Pass when service pages explain scope, process, relevant local or jurisdictional context, attorney responsibility, and material limitations instead of relying on generic promotional language.
• Pass when related pages link contextually because the services are genuinely related.
• Pass when the H1 accurately names the service and jurisdiction where relevant rather than forcing a location term onto a page with no genuine local purpose.

Supporting content:

• Pass when articles answer documented client questions or legal-information needs tied to the firm's real practice areas.
• Pass when supporting articles link to relevant service pages and attorney or office context where useful.
• The source uses a minimum 1 post per practice area per quarter as an operating example. Do not use that cadence as a ranking rule.
• Pass when older legal content is reviewed when law, facts, attorneys, services, or material source information changes.

Attorney advertising review: Use Model Rule 7.1 only as a reference point and apply the current rules that actually govern the communication. Claims about results, success, expertise, comparisons, testimonials, fees, and specialization require appropriate review. Owner: attorney or designated legal reviewer with editorial support. Validation: retain a review record showing what was checked and approved.

Do not attempt all 67 items as an undifferentiated sprint. Sequence them by severity, dependency, and the ability to verify completion.

Blocking and high-risk work, source example weeks 1-2: The source gives 1-4 hours per item and a 4-6 week movement example. Treat those timings as planning observations, not promises.

• Verify Google Business Profile eligibility, ownership, and factual business information.
• Fix any mobile usability errors in Google Search Console.
• Correct material business-data inconsistencies in the top 5 relevant directories from the source example.
• Add missing title tags and meta descriptions to the top 20 priority service pages identified for the audit.
• Verify authoritative professional listings only where the firm is eligible and the information is accurate.

Coverage and authority work, source example weeks 3-8: The source gives 4-16 hours per item and a 2-4 month observation. Use these as resource-planning examples, not outcome guarantees.

• Audit the 3 highest-priority service pages using evidence of intent, attorney responsibility, jurisdiction, and usefulness. The source includes 500-1000 words as an example range; do not treat it as a quality threshold.
• Implement or correct Organization and LocalBusiness schema across the site only where it accurately describes visible firm and office information.
• Add an ethical review-generation process without incentives, discouraging negative reviews, or selecting only satisfied clients.
• Create one substantial supporting resource where the evidence shows a real client question. The source's 1500+ word example is not a ranking requirement.

Ongoing operating work, source example months 3+:

• Publish or update content when there is a documented question, legal change, service need, or performance gap.
• Review older pages when law, attorneys, office information, or material evidence changes.
• Maintain Google Business Profile information and visuals when there is something accurate to update.
• Monitor reviews and responses with confidentiality and attorney-advertising safeguards.

Owner: the person responsible for each workstream. Validation: no item leaves the matrix until evidence shows the underlying condition is corrected.

Use the full 67-point checklist as an audit register rather than a decorative download. Every row should contain the evidence required, pass-fail condition, severity, owner, corrective action, validation method, and status.

How to operate the checklist:

1. Assign every applicable item to an accountable owner, whether internal, agency, or specialist.
2. Use the source's 2-3 week and 8-12 week planning ranges only for scheduling categories, not as promises of search movement.
3. Repeat the audit after 90 days or after a material site, office, tracking, or legal-content change, using the same evidence definitions.
4. Keep deferred items visible with a reason, risk owner, and trigger for reconsideration.

A status such as complete should mean the validation step passed. In progress means the condition is not yet verified. Deferred means the firm consciously accepted the current risk or dependency. These definitions make agency and internal reporting comparable.

Scope boundary: The checklist is a general audit structure. Priorities depend on the firm's practice areas, genuine locations, technical baseline, existing authority, regulatory obligations, and intake model. If another audit reaches a different conclusion, compare the evidence and assumptions rather than forcing both lists to match.