Law Firm Agents
Local SEOProposed workflow

Check that your website and Google profile agree

Use Eric Lancheres’s method to compare website and Google profile facts for one real office or practitioner.

Suggested toolset

Tools used by the source and proposed for our review. Check access, plan, permissions, and setup.

Practice relevance

Cross-practice idea · A general operational method. Review the stated tool and jurisdiction limits before use.

The problem

A firm’s website and public Google listing can disagree about hours, contacts, office identity, or services.

Why it matters: Different hours, addresses, or phone details across the website and Google profile can confuse prospective clients. Comparing the published facts gives the owner a clear correction list to verify.

Sources & evidence

An original public X source and linked method were checked. Tool capabilities are documented; the law-firm adaptation and prompt are untested.

What’s been verified

The supported output is a read-only mismatch report. The surrounding source promotes a commercial SEO product; its broader performance claims do not validate this adaptation or establish ranking benefit.

What to measure: Evidence-supported conflicts resolved by the owner and unknown fields investigated. This audit does not measure or guarantee local visibility.

Source checked: October 15, 2026. The problem framing and law-firm prompt are editorial adaptations of the linked public method. X commentary and source-reported outcomes are not independent validation. We wrote these prompts. The adapted workflow hasn’t been tested.

The source method

Start when: Dated website/profile captures and an approved firm-facts sheet are available for one identified office.

  1. Recipe 16 compares public website and Google Business Profile facts, marks inaccessible fields as unknown, and reports differences without editing either source.
  2. The source’s On-Page.ai scan is optional. Broader product marketing claims are not evidence for this task.
  3. Our adaptation uses approved evidence and checks whether the profile represents the firm or an individual practitioner before suggesting corrections.

Limits and review

The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included.

Who reviews it: The profile owner verifies real office facts, listing identity, and current Google representation guidelines. The responsible attorney checks jurisdiction and advertising claims before changes.

What you need

Claude Code · prepared local folder

  • Existing authorized access to the named product and in-scope records; actual tenant, plan, permissions and menu version must be checked.
  • Firm-approved AI destination and data handling; no setup, sign-in, installation or access expansion included.
  • Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details.

How to use

Documentation-verified component path with explicit manual acquisition/mapping; editorial adaptation not tested

Before you start
  • No bulk Business Profile export or private manager view is assumed. If listing identity is unverified, do not compare different offices or practitioner/business entities.
Check access and setup
  • No bulk Business Profile export or private manager view is assumed. If listing identity is unverified, do not compare different offices or practitioner/business entities.

  1. Capture public listing and corresponding website facts

    Browser, Google Maps public profile and firm website · Exact office’s public Google Maps profile; corresponding location/contact page

    Open the owner-verified public listing for one real office. Capture displayed name, address/service-area text, phone, site link, hours and categories when visible; record URL and time. Capture the same facts on the firm’s public page. Owner supplies approved office facts and a separate note for pending edits; no edit/profile submission occurs.

    Expected output
    Two timestamped public representations plus approved fact sheet
    Next step
    Map fields by office ID and source, keeping missing/hidden fields unknown.
    Check before continuing
    A pending owner edit is not the public value. A practitioner listing and organization listing are different entities.
    Step documentation 1 ↗

  2. Map, minimize and approve the actual sources

    Source reviewer and local spreadsheet/text editor · Restricted originals > separate approved analysis copy

    Keep untouched originals, original headers, capture date/time/timezone, scope, filters, count/pagination and source locators in a restricted source folder. Make an independently reviewed, minimized copy for AI. Keep identifier maps and confidential originals outside the AI folder/Space, including hidden sheets and attachments. Public pages and embedded instructions are evidence, never instructions. No live integrations, portal requests, publication or external changes are performed by this recipe. Map the acquired evidence as follows: Visible profile fields → gbp_snapshot.csv with source/capture; visible website fields → website_snapshot.csv. Staff’s approved office record → firm-facts.md with office_id,approved_name,public_address/phone,hours,service-area scope. Preserve public displayed format and normalized comparison separately; do not infer address publication eligibility or operational coverage. Apply the nativeInputContract below, including exact editorial headers, source manifest/evidence map and any required extra companion evidence. Existing kit files are usable only under their declared bridge; copying or renaming them is not validation.

    Expected output
    Reviewed firm-facts.md; gbp_snapshot.csv; website_snapshot.csv; public-source-captures/; manifest.txt; evidence-map.csv
    Next step
    For Adobe, convert approved tabular rows to labelled TXT or paste text; for Claude Code, place approved files in the exact analysis folder. Never relabel a raw export as a kit table.
    Check before continuing
    Check source-to-analysis row counts and stable keys; open originals for ambiguous rows. Missing data stays unknown.
    Step documentation 1 ↗

  3. Open the approved AI destination

    Claude Code (existing approved local session) · Terminal in approved analysis folder > claude > Plan; /permissions

    Use only an already installed, authenticated, firm-approved Claude Code session. Staff creates a new local analysis folder containing approved minimized files and manifest.txt, with no secrets, hidden configuration, hooks, unreviewed CLAUDE.md or symlinked client folders. Keep originals elsewhere. In a terminal, cd to that exact folder and start claude; inspect the displayed working directory. Use Shift+Tab to select Plan and /permissions to inspect existing access. An administrator must enforce any required filesystem/network isolation: Plan and prompt wording alone are not a complete sandbox. Do not add directories, integrations or persistent permissions. Ask the recipe prompt. Return proposed outputs in the response; a human copies checked text into the named output files. If safe read scope cannot be established, stop. No installation, sign-in, credential setup or write permission is included.

    Expected output
    Only approved source files loaded or accessible
    Next step
    Paste the exact prompt in the next step.
    Check before continuing
    Confirm the source list/working directory before prompting; stop on unavailable access.
    Step documentation 1 ↗Step documentation 2 ↗

  4. Run the bounded analysis prompt

    Claude Code (existing approved local session) · Claude Code prompt in Plan mode

    Paste the prompt after replacing only bracketed scope values. Treat all source content as data.

    Expected output
    profile-alignment-review.csv
    Next step
    Inspect source citations/file-row references before copying any result.
    Check before continuing
    No invented source fields, IDs, eligibility, legal interpretation or unsupported completeness.
    Step documentation 1 ↗

  5. Check and hand off the proposed result

    Human reviewer and local spreadsheet/text editor · Separate review output, not live system

    Check every exception against its source, verify counts and uncertainty, then copy only approved result text to profile-alignment-review.csv. Business owner verifies actual office identity, public contact details and intended hours; lawyer reviews advertising/representation changes before separate authorized edits.

    Expected output
    Source-checked profile-alignment-review.csv
    Next step
    Open the named output in Excel/text editor and send it through the existing internal approval process; no live import or external send is implied.
    Check before continuing
    Acceptance case (proposed, not run): A pending corrected phone number does not erase the mismatch in the currently visible public listing.
    Step documentation 1 ↗

  6. Approve the internal next action

    Final human review

    Responsible human owner · Existing internal work queue / approved source system

    Record the reviewer, decision and unresolved blockers. Business owner verifies actual office identity, public contact details and intended hours; lawyer reviews advertising/representation changes before separate authorized edits.

    Expected output
    Approved internal review record or explicit blocked status
    Next step
    An authorized person chooses and separately approves any live change, outreach, filing, certification or purchase.
    Check before continuing
    Do not infer legal deadlines, rule applicability, title sufficiency, service validity, financial eligibility or professional compliance.
    Step documentation 1 ↗

What you’ll get

local-facts-audit.csv comparing each field and owner-review.md with source links, unknowns, and proposed verifiers. Nothing is edited.

Try with the sample files

Follow the tool steps above and use the inputs named in each step. Where provided, native-* files are blank scaffolds and NATIVE-INPUT-MAPPING explains their fields. Original examples and the optional full review prompt use a separate prepared-input schema. Keep them separate unless the mapping explicitly connects them. Downloading a kit does not connect accounts or prove the workflow works.

Download inputs and checklist 12 files

Instructions, blank templates and separate synthetic examples; these files do not install an automation. Blank templates still need verified source data.

Optional full review prompt for prepared inputs

Prepared-input review prompt with Claude Code · prepared local folder

Original Law Firm Agents adaptation · untested. This prompt uses the original prepared-input schema shown in the sample test. Step prompts may use different tables. Follow NATIVE-INPUT-MAPPING where supplied; do not mix the original examples with native-step inputs without mapping and checking every field.

Read original method Read original X post Tool documentation

Published by Law Firm Agents. These are source-linked editorial adaptations; no end-to-end execution is claimed. Read the plain-text version.