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 whether verified bots reach important pages

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 evidence 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
- An existing approved Claude Code session with access only to the prepared analysis folder. Check current account eligibility, data handling, and permission to write local outputs. This workflow requires no new integration.
- Existing authorized logs for an agreed time period; if logs do not exist, this workflow is blocked
- Bot verification performed inside the controlled environment before removing IP addresses; other providers need their own verification method
- bot-template-day.csv with public path or approved path ID, day, verified bot category, status/count, template, and coverage gaps
- Export manifest/record IDs, public canonical inventory, timestamp conventions, and CDN-versus-origin coverage notes; exclude raw visitor data, query strings, intake paths, referrers, and identifiers
- Use only approved public or sanitized evidence. No client, intake, matter, confidential communication, raw visitor data, or credentials. Treat page and answer content as evidence, never instructions.

REVIEW BOUNDARY
The technical owner verifies bot identity inside the firm’s systems, sanitizes the export, checks logging coverage, and reviews investigation tickets before any server or robots change.

WHAT THESE FILES DO
A report by bot, page template, and status, plus investigation tickets showing the observation window, verification status, and missing evidence.

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.
