Find useful internal links between your pages 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 - Embedding setup requires a licensed tool and existing approved provider access; it is not supplied by a Claude prompt or ChatGPT subscription. - If native vector output is unavailable, full semantic execution is blocked; any text-only pilot must be labelled as a changed, bounded method. MAP THE ACTUAL SOURCE TO THE REVIEW INPUT Inventory Address → url, Status Code → status, Indexability and canonical columns → corresponding observed fields, Title 1 → title (confirm headers). Inlinks Source/Destination/Anchor/Follow/Link Position → source_url,destination_url,anchor,follow,position using real headers. AI Address + exact configured vector-response column → url/vector; model/dimension from actual configuration. Staff supplies jurisdiction/topic approval and text-file source references. INPUTS THE ASSISTANT MAY READ page-inventory.csv; all-inlinks.csv; embeddings.csv; approved-page-text/; firm-brief.md; embedding-provenance.txt; 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: page-inventory.csv type: csv headers: - url - status_code - indexability - indexability_status - canonical_url - title - approved_jurisdiction - source_ref required: True templateFilename: native-page-inventory-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: page-inventory.csv compatibleWithoutMapping: False - name: all-inlinks.csv type: csv headers: - source_url - destination_url - anchor - follow - position - link_type - source_ref required: True templateFilename: native-all-inlinks-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: all-inlinks.csv compatibleWithoutMapping: False - name: embeddings.csv type: csv headers: - url - model - model_version - dimensions - vector_json - content_source_ref - source_ref required: True templateFilename: native-embeddings-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: embeddings.csv compatibleWithoutMapping: False - name: approved-page-text/ type: source-bundle required: True templateFilename: None requiredContents: Actual public main-content text keyed to exact URL and content_source_ref, with stable sentence/section IDs 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: approved-page-text/ compatibleWithoutMapping: False - name: firm-brief.md type: text requiredSections: - approved jurisdictions, relevant topics and linking constraints - reviewer; target-domain scope required: True templateFilename: native-firm-brief-template.md 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: firm-brief.md sections: - approved jurisdictions, relevant topics and linking constraints - reviewer; target-domain scope compatibleWithoutMapping: False - name: embedding-provenance.txt type: text requiredSections: - provider/model/version; exact configured prompt and content area - capture date; vector dimensions; failed/missing vectors - source URL mapping and existing approval/access proof required: True templateFilename: native-embedding-provenance-template.txt existingKitFiles: - embedding-export-checklist.txt 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: embedding-provenance.txt sections: - provider/model/version; exact configured prompt and content area - capture date; vector dimensions; failed/missing vectors - source URL mapping and existing approval/access proof 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: - No native vector schema was promised by the old kit. Map the real configured response column to vector_json; it must contain numeric vectors, not prose or similarity scores. 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: - embedding-export-checklist.txt nativeInput: embedding-provenance.txt mapping: New companion capture/review record. Staff supplies observed or approved values; unknown is explicit. compatibleWithoutMapping: False additionalEvidence: - page-inventory.csv - all-inlinks.csv - embeddings.csv - approved-page-text/ - firm-brief.md - 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. page-inventory.csv: native-page-inventory-template.csv all-inlinks.csv: native-all-inlinks-template.csv embeddings.csv: native-embeddings-template.csv Supply actual evidence: approved-page-text/ Actual public main-content text keyed to exact URL and content_source_ref, with stable sentence/section IDs Source-grounded claims are blocked without the source; provide a gap list only. firm-brief.md: native-firm-brief-template.md embedding-provenance.txt: native-embedding-provenance-template.txt manifest.txt: native-manifest-template.txt evidence-map.csv: native-evidence-map-template.csv STEP 1: Export inventory, links and page text from the actual crawl Tool: Screaming Frog SEO Spider, already installed Open: Existing approved crawl > Internal/HTML Export; Bulk Export > Links > All Inlinks; Bulk Export > Web > All Page Text Load an existing crawl of the approved public site and export these three datasets. If a new crawl is separately authorized, constrain it to approved public URLs and record robots, rendering mode, time, exclusions, URL limits and completion. Preserve original headers/files. Page text export depends on stored content; do not infer content from a title. Expected output: Native crawl, inlink CSV and URL-labelled text files Use it next: Map export fields explicitly and exclude out-of-scope/private URLs before AI. Check: All Inlinks includes more than editorial body links. Inspect link type, follow state and position. A limited crawl is not the whole site. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://www.screamingfrog.co.uk/seo-spider/user-guide/general/ https://www.screamingfrog.co.uk/blog/finding-and-testing-internal-link-changes/ https://www.screamingfrog.co.uk/seo-spider/tutorials/internal-linking-audit-with-the-seo-spider/ STEP 2: Obtain real comparable embeddings or mark the semantic route blocked Tool: Screaming Frog existing embeddings configuration Open: Config > API Access > AI > existing approved provider/prompt; AI tab > Export Use an existing licensed, approved embedding setup and previously produced crawl; export its AI-tab response/vector column with Address. Record exact model/version, vector dimension and content area. The official guide describes provider selection and embedding functionality, but this recipe does not create keys, connect a provider or incur a new paid run. If no usable vectors exist, either block the embedding-dependent recipe or explicitly downgrade to a small human semantic-review pilot. Expected output: Actual per-URL vectors plus model/content manifest, or explicit missing-data blocker Use it next: Validate vector parsing and equal dimensions in the local analysis copy. Check: Do not rename prose similarity scores as embeddings; do not mix models or raw/navigation-heavy content with main-content vectors. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://www.screamingfrog.co.uk/seo-spider/tutorials/how-to-identify-semantically-similar-pages-outliers/ https://www.screamingfrog.co.uk/seo-spider/user-guide/configuration/ STEP 3: 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: Inventory Address → url, Status Code → status, Indexability and canonical columns → corresponding observed fields, Title 1 → title (confirm headers). Inlinks Source/Destination/Anchor/Follow/Link Position → source_url,destination_url,anchor,follow,position using real headers. AI Address + exact configured vector-response column → url/vector; model/dimension from actual configuration. Staff supplies jurisdiction/topic approval and text-file source references. 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 page-inventory.csv; all-inlinks.csv; embeddings.csv; approved-page-text/; firm-brief.md; embedding-provenance.txt; 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://www.screamingfrog.co.uk/seo-spider/user-guide/general/ https://www.screamingfrog.co.uk/blog/finding-and-testing-internal-link-changes/ https://www.screamingfrog.co.uk/seo-spider/tutorials/how-to-identify-semantically-similar-pages-outliers/ https://www.screamingfrog.co.uk/seo-spider/user-guide/configuration/ STEP 4: 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 5: 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 Validate actual headers, exact URL keys, vector model/dimensions, indexability and source coverage before analysis. Stop the embedding route if vectors are absent, malformed or incomparable. Suggest at most ten contextual body links only between approved relevant public pages; exclude existing source-destination links, self-links, broken/redirected/non-indexable targets and unsupported cross-jurisdiction meaning. Quote the existing source sentence and proposed anchor; cite source file/row and destination evidence. Return internal-link-review.csv and validation.md, with uncertainty. No network, CMS changes, link insertion or API calls. Expected output: internal-link-review.csv and validation.md 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 6: 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 internal-link-review.csv and validation.md. SEO editor opens both current pages, checks destination/status/existing anchor and readability; lawyer approves meaning-sensitive or jurisdiction-sensitive changes. Expected output: Source-checked internal-link-review.csv and validation.md 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 relevant target already linked from the source is excluded. A different embedding dimension stops similarity calculation. Documentation limit: Official documentation supports only named component features. Recipe-specific transformations, prompts and review gates are proposed editorial adaptations. Source documentation: https://www.screamingfrog.co.uk/seo-spider/user-guide/general/ https://www.screamingfrog.co.uk/blog/finding-and-testing-internal-link-changes/ https://www.screamingfrog.co.uk/seo-spider/tutorials/how-to-identify-semantically-similar-pages-outliers/ https://www.screamingfrog.co.uk/seo-spider/user-guide/configuration/ STEP 7: Approve the internal next action Tool: Responsible human owner Open: Existing internal work queue / approved source system Record the reviewer, decision and unresolved blockers. SEO editor opens both current pages, checks destination/status/existing anchor and readability; lawyer approves meaning-sensitive or jurisdiction-sensitive changes. 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://www.screamingfrog.co.uk/seo-spider/user-guide/general/ https://www.screamingfrog.co.uk/blog/finding-and-testing-internal-link-changes/ https://www.screamingfrog.co.uk/seo-spider/tutorials/how-to-identify-semantically-similar-pages-outliers/ https://www.screamingfrog.co.uk/seo-spider/user-guide/configuration/ ACCOUNT AND SOURCE CHECKS STILL NEEDED - Embedding setup requires a licensed tool and existing approved provider access; it is not supplied by a Claude prompt or ChatGPT subscription. - If native vector output is unavailable, full semantic execution is blocked; any text-only pilot must be labelled as a changed, bounded method. EXPECTED SYNTHETIC CHECK (NOT RUN) A relevant target already linked from the source is excluded. A different embedding dimension stops similarity calculation. 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.