OWLRAG notices every change and answers your team right in Claude or ChatGPT – with sources.
- Do we already have a page on the warranty?
- Where does the old delivery time still appear?
- Which pages still use the old slogan?
- What do we tell French customers about shipping?
- Which products are missing in Switzerland?
- What changed on the site this week?
- Since when does the new price apply in Austria?
- Is there a page for beginners?
- What do our terms say about returns?
- Which pages mention sustainability?
The situation
Your content is bigger than any one memory.
- 01
Nobody knows what exists.
Thousands of pages, several markets, changing authors. Whoever needs something asks around – or writes it again.
- 02
Changes go unnoticed.
A page disappears, a price drifts, one market lags behind. Usually the customer notices first.
- 03
Writing without context.
New content gets written without a view of the existing – and contradicts it.
Product
Four capabilities. One index.
01 Find
Ask in full sentences.
Semantic search finds pages by meaning, not keyword – with URL and excerpt as evidence.
semantic_search
›semantic_search("return policy mentioned")
◆shop.example/en/service/returns
"30-day returns on all products …"
◆shop.example/en/terms
"… return within 30 days of receipt …"
◆shop.example/en/faq/shipping
"… return shipping is free …"
02 Understand
Read the whole page, not just the hit.
Pull the full text and compare the same product across every market.
get_full_page · compare_markets
›get_full_page("shop.example/en/service/returns")
# Returns & exchanges
1,842 words · last changed 12 Oct 2026
›compare_markets(sku="X-100")
+live
+live
+live
−404 – missing
03 Watch
The owl never sleeps.
Every working day OWLRAG diffs the sitemap: new, changed, removed. Removed pages stay retrievable in the archive.
get_changes
›get_changes(since="7d")
+new pages
~content changed
−removed → archive, still retrievable
~ /en/service/returns · text changed
− /fr-ch/shop/x-100 · archived
04 Act
Work directly in Claude or ChatGPT.
Briefs, content gaps, consistency checks – as skills in Claude and ChatGPT, usable without a developer.
Skills
›/content-gap audience="beginners" market="en"
214 pages read
~topics without a page of their own
Brief created → brief-beginners.md
How it works
From sitemap to answer.
- 01
Crawl
Sitemap · every working day
Reads every public page your sitemap lists – in every market.
- 02
Embedding
768 dimensions
Turns each page into a vector that captures its meaning.
- 03
Vector index
pgvector · HNSW · Zurich
Orders pages by meaning: similar content sits close together.
- 04
MCP server
Streamable HTTP
Makes the index queryable through the open Model Context Protocol.
- 05
Claude · ChatGPT
Connector
Your team asks where it already works – and gets answers with a source.
Standard building blocks, not a black box.
In practice
From campaign plans to price checks.
Plan campaigns
“What have we already published on sustainability – and in which markets?”
Compare markets
“Which products are live in Germany but missing in Switzerland?”
Check changes
“Which pages were removed since the relaunch?”
Look up prices
“What does the X-100 cost in Austria?”
Your own workflows
Any recurring task becomes a skill: we set it up, or your team creates it in Claude or ChatGPT.
Case · International DTC brand
- 6,745 live pages in the index
- 5 markets
- 2,249 archived, still retrievable
In the rollout test, the index surfaced 15 products that were live in one market and missing in another – found without opening a single page.
As of 15 Oct 2026. Name withheld at the client’s request.
FAQ
Common questions.
Where is my data stored?
Only publicly accessible pages of your website are processed. Index and embeddings are stored in a database in Switzerland (Zurich); the server for Claude and ChatGPT runs in the EU (Amsterdam). To create embeddings, page text and search queries are sent to the Google API (paid tier, not used for training).
What content is covered?
Today: all public pages via your sitemap. Further sources such as strategy and persona documents are planned.
Which AI is behind it?
The index is connected through the open MCP protocol. Today we work with Claude and ChatGPT.
How does the pilot work?
Short call, your sitemap gets indexed, your team tests in Claude or ChatGPT. Setup typically takes one to two weeks.
What does it cost?
Individual during the pilot, depending on scope and markets. After a short call, you'll receive a quote.
Pilot
Secure a pilot spot.
We are taking a small group of companies into the pilot. Tell us your website – we'll show you what it looks like in the index.
Ask your entire website.
Join the waitlistAlso from UHLER AI
- AI training & onboarding
- Process analysis & optimisation
- Enterprise applications