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.

Investigate indexing by page template

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.
- Authorized Search Console access or owner-supplied dated exports; no API connection required
- Existing public sitemap index/children, URL-to-template mapping, and an approved intended-indexable list
- Representative URL Inspection notes and a healthy comparison cohort; keep unavailable evidence distinct from zero
- If a child sitemap is missing from the selector, its authorized owner handles any submission separately; do not submit children indiscriminately
- 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 confirms canonical/indexing intent and approves any sitemap or website changes separately. A lawyer reviews later changes affecting legal meaning.

WHAT THESE FILES DO
A diagnostic matrix, up to three possible causes linked to evidence, a comparison cohort, and the next inspection needed to test each cause.

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.
