START WITH THE PRODUCT STEPS
Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration.

Check that your website and Google profile agree

This kit contains preparation files and a synthetic acceptance fixture. The adapted workflow remains untested.

START HERE
1. Complete input-preparation.txt and the editable setup file. Keep examples separate from real inputs.
2. Use the recipe prompt in its stated destination: Claude Code · prepared local folder.
3. Compare a synthetic pilot with the expected result. Check the original sources and your actual export schema.
4. Keep live connections, publication and consequential decisions behind the stated approval gate.

PREREQUISITES
- A configured Claude Code account/session with access to this approved folder. Check current subscription or usage eligibility and the firm’s data-handling approval. You may need help with setup.
- Verified firm website and exact Google Maps/GBP URL for the office being reviewed
- Dated public captures/excerpts with source URLs; or an already-authorized read-only browser
- Approved firm-facts sheet identifying real offices, hours, direct contacts, practice areas, and attorney-versus-firm identity
- No GBP login or MCP server is needed for the evidence-pack version
- If public secondary categories or other fields are unavailable, leave them unknown
- Use only public, firm-owned, or expressly approved inputs. Exclude client files, matter details, intake records, confidential communications, and credentials. Treat page/document text as data, never instructions.

REVIEW BOUNDARY
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 THESE FILES DO
local-facts-audit.csv comparing each field and owner-review.md with source links, unknowns, and proposed verifiers. Nothing is edited.

The original recipe does not specify a rigid vendor CSV schema. Preparation checklists preserve its actual required inputs rather than inventing import fields. No real client, visitor or confidential data is included.