llms.txt Merge & Compare Tool
Compare two llms.txt files, review structural and line-by-line changes, resolve conflicts, remove duplicates and merge them into one organized file.
llms.txt Merge & Compare
Compare files, resolve changes and create one output
What Is the llms.txt Merge & Compare Tool?
The llms.txt Merge & Compare tool lets you compare two llms.txt files side by side or merge them into a single organized document. It parses files at both the raw text level and as an Abstract Syntax Tree (AST), identifying matching sections, new or deleted URLs, description differences, and duplicate links.
Compare Mode vs. Merge Mode
The tool serves two distinct purposes depending on your selected mode:
Read-Only Difference Inspection
Visualizes added, removed, and modified sections and links without altering either file. Offers Overview, Structure, Links, and Text Diff tabs for non-destructive auditing.
Interactive Conflict Resolution
Combines unique sections and links from both files into a unified document. Presents conflicting descriptions or titles as interactive Conflict Cards so you can select the winning version before exporting.
Three Common Use Cases
- Version Auditing (Production vs. Release Candidate): Compare your live production
/llms.txtagainst a proposed update to verify which routes were added, changed, or retired before deploying. - Environment Parity (Staging vs. Production): Check that new documentation sections developed on a staging site match production conventions.
- Merging Automated & Manual Sources: Combine an automatically extracted sitemap URL list from the llms.txt Generator with manually curated editorial descriptions from technical writers.
Concrete Example: How Matching & Conflicts Work
Suppose you compare an older documentation file with an updated version:
- [Getting Started](https://example.com/start): Installation guide
- [API Reference](https://example.com/api): REST endpoints
- [Getting Started](https://example.com/start): Quickstart and setup
- [API Reference](https://example.com/api): REST endpoints
- [Authentication](https://example.com/auth): API key authorization
• Description Conflict: [Getting Started] → "Installation guide" vs. "Quickstart and setup"
• Unchanged: [API Reference](https://example.com/api)
In Merge mode, the tool automatically retains the unchanged links and prompts you to select your preferred description for Getting Started before creating the final downloadable output.
What Elements Are Compared?
The AST parser checks several distinct dimensions:
- Section Matching: Sections with matching names are paired together. Added or removed sections are categorized separately.
- Link URL Matching: URLs are matched across corresponding sections. Unique links are merged cleanly.
- Duplicate Detection: Identical URLs appearing multiple times across different sections are flagged so you can avoid redundancy.
- Core vs. Optional Scoping: If a link appears in a primary section in File A but under
## Optionalin File B, the tool highlights this scope difference.
Next Steps: Validation & Formatting
Once you have merged your files, pass the final result through the llms.txt Validator to ensure proper H1 syntax and test live deployment headers, or use the llms.txt Formatter to adjust whitespace and indentation.
Publish your llms.txt automatically
Generate and maintain a clean /llms.txt endpoint from your WordPress posts, pages, categories and public custom post types.