When an AI assistant reads unsiloed.ai, every URL returns the same 124,000-character article index: the homepage, /pricing, /parse, /unsiloed-vs-reducto, /unsiloed-vs-llamaparse, /careers, even individual blog posts. The index links to "Pricing", which returns the index again. Nothing in it covers the plans, the five product pages, the four comparison pages, the testimonials or SOC 2 and HIPAA. Developers now pick infrastructure by asking an assistant questions like "Unsiloed vs Reducto pricing", and the answer it gets from Unsiloed's own site is a list of blog titles. The docs at /docs read normally, which shows the problem is only how the marketing pages are served to AI readers.
First action
Change the routing so /pricing returns the pricing page's own text to AI readers, then re-run the same request and check.
How to measure it
AI-assistant referrals to sign-up or demo
- Now
- –
- Target
- 3x the current baseline
- By
- 90 days
Steps
Record the baseline
Ask five AI assistants ten buyer questions (pricing, vs Reducto, vs LlamaParse, SOC 2, on-prem, ACORD forms) and save the answers.
Founding GTM Lead 2 hours
Find the rule
Locate the edge or middleware rule that returns the index to AI readers on every path.
Founder/CTO 2 hours
Serve per-page text
Return each page's own text (or its .md twin) at the same URL. Keep the index only at /llms.txt.
Founding Software Engineer, Backend and Infrastructure 2 days
Rebuild llms.txt
Products, Pricing, Compare, Benchmarks, Security and Docs first, then the guides by topic.
Founder/CEO 1 day
Add page summaries
A 3-line plain-text summary at the top of each product and comparison page.
Founder/CEO 1 day
Verify
Fetch every sitemap URL as an AI reader and confirm each one returns its own content.
Founding Software Engineer, Backend and Infrastructure half a day
Re-ask and track
Repeat the ten questions monthly and tag AI-assistant referrers in analytics.
Founding GTM Lead monthly
Why it works
Keep the llms.txt and the agent storefront, but stop returning the index for every URL. Serve each page's own content to AI readers: /pricing returns the plans and what a credit buys, /parse, /extract, /split, /classify and /ocr return their own capabilities and limits, and each /unsiloed-vs-* page returns its comparison table. Publish a .md version of each page and link it from the HTML. Rebuild llms.txt so it opens with Products, Pricing, Compare, Benchmarks, Security and Docs, then the guides. Then ask the main assistants the ten questions buyers ask and record the answers before and after.
AI assistants and their crawlers mostly read text without running JavaScript, and they answer from what a page returns. Today the most persuasive pages (pricing, comparisons, the #1 benchmark) are invisible to them. Fixing it is routing work, not new content, and every future page benefits.
Ready to use
ChecklistAI-reader fix list
[ ] /pricing returns plans, credits and the free tier, not the index [ ] /parse, /extract, /split, /classify, /ocr return their own content [ ] /unsiloed-vs-azure, -textract, -llamaparse, -reducto return their tables [ ] Blog posts return the post, not the index [ ] .md twin for every page, linked from the HTML head [ ] llms.txt: Products, Pricing, Compare, Benchmarks, Security, Docs at the top [ ] Agent storefront still linked from llms.txt [ ] Every sitemap URL re-checked as an AI reader [ ] Ten buyer questions re-asked monthly
Risks and how to handle them
The agent storefront loses visibility
Keep it linked at the top of llms.txt and in a footer link on every page.
AI readers and humans see different claims
Generate the AI version from the same source as the HTML page.
Evidence
- Your websiteAI-reader view (fetched twice on November 10, 2026): /, /pricing, /parse, /unsiloed-vs-reducto, /unsiloed-vs-llamaparse, /careers and a blog post all return the same 124,000-character article index that opens "# Unsiloed AI" and "Technical guides on document AI". It lists about 93 blog articles plus an "Agentic commerce" storefront; its only site links are Pricing and API documentation, and the Pricing link returns the same index. No plans, product pages, comparison pages, testimonials or SOC 2/HIPAA appear in it. The docs at /docs read normally.Source
- Your websiteSitemap (118 URLs, checked November 10, 2026): 96 blog posts (latest November 9, 2026); product pages /parse, /extract, /split, /classify and /ocr; four comparison pages (vs Azure, Textract, LlamaParse and Reducto); a /demo playground and /book-demo; more comparisons filed as blog posts (unsiloed-ai-vs-extend, -pulse, -docsumo, -unstract, -unstructured, -airbyte, -snowflake-ai-extract, -docparser, docling-vs-unsiloed) and "alternatives" posts; document-type guides (ACORD forms, loss runs, bank statements, pay stubs, prior authorization, lab results); no industry, customer, security or case-study pages; five root-level posts about AI coding tools.Source
- PressShow HN (May 25, 2026): "Unsiloed AI – #1 on olmOCR-Bench": Parser v3.1 scored an 88.0 strict pass rate across 1,403 PDFs and 8,413 unit tests with the unmodified Allen AI scorer; the HN post drew 9 points and 4 comments. A public GitHub harness lets anyone reproduce the run.Source
- HiringFounding GTM Lead (San Francisco, $120K–$200K): runs "outbound, inbound qualification, discovery calls, POCs, pricing, procurement, and closing" with the founders; success at 6–12 months is "Consistent pipeline generation outside founder networks" and a "Repeatable POC and qualification process"; channels named are "Outbound email, founder-led content, partnerships, communities, events"; buyers are in financial services, legal, insurance and healthcare, with "loan files, broker statements, insurance claims, medical records, contracts, and financial reports", deployed as a managed API, in private VPCs or fully on-prem.Source