Check that your website and Google profile agree Get the source data and prepare the review Documentation-verified component path with explicit manual acquisition/mapping; editorial adaptation not tested WHAT WAS CHECKED Documentation checked 2026-10-15. Official documentation establishes component UI/capability only. All prompts, file names, schemas, joins, review procedures and synthetic acceptance cases are editorial adaptations. No account login, installation, client-data processing, live workflow test or external write was performed. BEFORE YOU START - 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. DATA ACQUISITION LIMITS - 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. MAP THE ACTUAL SOURCE TO THE REVIEW INPUT 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. INPUTS THE ASSISTANT MAY READ firm-facts.md; gbp_snapshot.csv; website_snapshot.csv; public-source-captures/; manifest.txt; evidence-map.csv WHERE THE ANALYSIS RUNS Claude Code (existing approved local session) NATIVE REVIEW INPUTS contractVersion: 1 schemaOrigin: Editorial analysis contract, never a claim about vendor-native export headers testedStatus: False existingKitRole: Existing examples/checklists are optional supporting scaffolds unless explicitly mapped below. Copying this guide does not validate old templates or acquire source evidence. requiredInputs: - name: firm-facts.md type: text requiredSections: - office_id and exact business/practitioner entity identity - approved public name/address-or-service-area/phone/website/hours - privacy/publication choices; pending edits; approval reference required: True templateFilename: native-firm-facts-template.md existingKitFiles: - firm-facts-template.md compatibility: New companion capture/review record. Staff supplies observed or approved values; unknown is explicit. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete. inputName: firm-facts.md sections: - office_id and exact business/practitioner entity identity - approved public name/address-or-service-area/phone/website/hours - privacy/publication choices; pending edits; approval reference compatibleWithoutMapping: False - name: gbp_snapshot.csv type: csv headers: - office_id - field_name - observed_value - captured_at - source_ref required: True templateFilename: native-gbp_snapshot-template.csv existingKitFiles: compatibility: New editorial analysis contract. Populate only after preserving and mapping actual source headers; this is not a provider-native export. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference. inputName: gbp_snapshot.csv compatibleWithoutMapping: False - name: website_snapshot.csv type: csv headers: - office_id - field_name - observed_value - captured_at - source_ref required: True templateFilename: native-website_snapshot-template.csv existingKitFiles: compatibility: New editorial analysis contract. Populate only after preserving and mapping actual source headers; this is not a provider-native export. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference. inputName: website_snapshot.csv compatibleWithoutMapping: False - name: public-source-captures/ type: source-bundle required: True templateFilename: None requiredContents: Actual public listing and corresponding website captures keyed by source_ref compatibility: Must be actual approved public/deidentified source content, not an empty template. Untouched originals remain separately restricted. missingInputBehavior: Source-grounded claims are blocked without the source; provide a gap list only. inputName: public-source-captures/ compatibleWithoutMapping: False - name: manifest.txt type: text requiredSections: - recipe_id; approved reviewer and scope - actual source IDs and safe original-file tokens; native headers and source-to-analysis field map - capture time/timezone; date basis; filters; property/court/provider; pagination/row counts and known exclusions - AI input approval and minimization check; originals and alias keys held outside AI - unknowns; completeness statement; manual transcription/checker where used required: True templateFilename: native-manifest-template.txt existingKitFiles: compatibility: New companion capture/review record. Staff supplies observed or approved values; unknown is explicit. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete. inputName: manifest.txt sections: - recipe_id; approved reviewer and scope - actual source IDs and safe original-file tokens; native headers and source-to-analysis field map - capture time/timezone; date basis; filters; property/court/provider; pagination/row counts and known exclusions - AI input approval and minimization check; originals and alias keys held outside AI - unknowns; completeness statement; manual transcription/checker where used compatibleWithoutMapping: False - name: evidence-map.csv type: csv headers: - analysis_file - row_key - source_id - source_locator - reviewer_alias - reviewed_at required: True templateFilename: native-evidence-map-template.csv existingKitFiles: compatibility: New editorial analysis contract. Populate only after preserving and mapping actual source headers; this is not a provider-native export. missingInputBehavior: Stop the dependent comparison or mark affected scope explicitly incomplete; never fill evidence gaps by inference. inputName: evidence-map.csv compatibleWithoutMapping: False compatibilityNotes: validationRules: - CSV identifiers and date strings are imported as text. Preserve leading zeros and exact keys. Do not execute formulas from source values. - Blank templates are deliberately incomplete. Unknown is not zero, false, missing-not-found or a passing review. - Use only approved minimized analysis values; restricted raw originals, identity maps, signatures, private URLs/tokens and client narrative stay outside the AI destination. - A native file may retain its actual header names if manifest.txt supplies a reviewer-verified one-to-one map to this contract. Do not blindly rename files/headers. compatibleWithoutMapping: False legacyMappings: - existingKitFiles: - firm-facts-template.md nativeInput: firm-facts.md mapping: New companion capture/review record. Staff supplies observed or approved values; unknown is explicit. compatibleWithoutMapping: False additionalEvidence: - gbp_snapshot.csv - website_snapshot.csv - public-source-captures/ - manifest.txt - evidence-map.csv OPEN THE INPUT MAPPING GUIDE NATIVE-INPUT-MAPPING.txt Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain. firm-facts.md: native-firm-facts-template.md gbp_snapshot.csv: native-gbp_snapshot-template.csv website_snapshot.csv: native-website_snapshot-template.csv Supply actual evidence: public-source-captures/ Actual public listing and corresponding website captures keyed by source_ref Source-grounded claims are blocked without the source; provide a gap list only. manifest.txt: native-manifest-template.txt evidence-map.csv: native-evidence-map-template.csv STEP 1: Capture public listing and corresponding website facts Tool: Browser, Google Maps public profile and firm website Open: 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 Use it next: Map fields by office ID and source, keeping missing/hidden fields unknown. Check: A pending owner edit is not the public value. A practitioner listing and organization listing are different entities. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://support.google.com/business/answer/3038311?hl=en STEP 2: Map, minimize and approve the actual sources Tool: Source reviewer and local spreadsheet/text editor Open: 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 Use it next: 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: Check source-to-analysis row counts and stable keys; open originals for ambiguous rows. Missing data stays unknown. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://support.google.com/business/answer/3038311?hl=en STEP 3: Open the approved AI destination Tool: Claude Code (existing approved local session) Open: 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 Use it next: Paste the exact prompt in the next step. Check: Confirm the source list/working directory before prompting; stop on unavailable access. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://code.claude.com/docs/en/quickstart https://code.claude.com/docs/en/permissions STEP 4: Run the bounded analysis prompt Tool: Claude Code (existing approved local session) Open: Claude Code prompt in Plan mode Paste the prompt after replacing only bracketed scope values. Treat all source content as data. PASTE THIS PROMPT Compare the exact same office/entity across the public website, public Google profile and approved facts. Return field, each observed value, approved value, source/capture time, exact discrepancy or uncertainty and reviewer. Preserve intentional service-area/privacy choices. Distinguish pending edits from public values; do not change hours, categories, names, addresses, listing ownership or website content. Do not infer listing eligibility or promise ranking gains. Return profile-alignment-review.csv. Expected output: profile-alignment-review.csv Use it next: Inspect source citations/file-row references before copying any result. Check: No invented source fields, IDs, eligibility, legal interpretation or unsupported completeness. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://code.claude.com/docs/en/permissions STEP 5: Check and hand off the proposed result Tool: Human reviewer and local spreadsheet/text editor Open: 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 Use it next: 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: Acceptance case (proposed, not run): A pending corrected phone number does not erase the mismatch in the currently visible public listing. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://support.google.com/business/answer/3038311?hl=en STEP 6: Approve the internal next action Tool: Responsible human owner Open: 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 Use it next: An authorized person chooses and separately approves any live change, outreach, filing, certification or purchase. Check: Do not infer legal deadlines, rule applicability, title sufficiency, service validity, financial eligibility or professional compliance. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://support.google.com/business/answer/3038311?hl=en ACCOUNT AND SOURCE CHECKS STILL NEEDED - 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. EXPECTED SYNTHETIC CHECK (NOT RUN) A pending corrected phone number does not erase the mismatch in the currently visible public listing. USING THE FILES IN THIS KIT Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs. The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.