Skip to main content

Website

Connecting a website lets Kinn read the pages of your own site or blog — docs, blog posts, changelog, release notes, landing and marketing pages — and fold them into what it can search. Where your other integrations capture what other people say about your product, your website is what you've published about it, so Kinn can answer questions using your own words and link back to the source page.

Because this is first-party content, Kinn treats it as reference material rather than feedback. Your pages aren't scored for sentiment — they're context Kinn can quote and cite, not a crowd whose mood it gauges.

Kinn reads your website's published pages only and makes no changes to your site.

What it pulls in​

Once connected, Kinn reads the readable main content of your pages:

  • Blog and news posts
  • Documentation and help articles
  • Changelog and release notes
  • Landing and marketing pages

Before anything is stored, Kinn strips the boilerplate — navigation, footers, sidebars, and scripts — and keeps only the meaningful body text of each page.

It does not read:

  • Pages your site disallows in robots.txt
  • Pages on other domains your site links out to — indexing stays on your site's own host
  • Thin or empty pages with too little real content to be useful (link hubs, redirects, placeholder shells)
note

Kinn does not crawl your site link by link. It discovers pages from your sitemap and any RSS/Atom feeds — the same maps search engines use — and fetches only what those list. If your site has no sitemap, Kinn looks for the conventional /sitemap.xml.

How to connect​

There's no account to connect or authorize — you simply point Kinn at your site by its URL.

  1. From your dashboard, go to Settings → Integrations → Add Integration → Website.
  2. Enter your site's URL (for example, https://example.com). Kinn keys the site by its origin, so https://example.com and https://example.com/blog resolve to the same site.
  3. Wait for the initial index to finish. Indexing runs in the background and may take a few minutes. Once it's done, you can run your first query.

You can also connect a site straight from chat — just paste the URL and ask Kinn to index it. See Managing sources from chat.

tip

If your site publishes a sitemap or feed, you don't need to do anything special — Kinn finds it automatically. Pointing Kinn at the site that has your docs and blog tends to give the richest results, since those pages carry the most substantive text.

Access​

Kinn only ever reads the pages of the site you connect, and only the pages your site makes publicly discoverable:

  • Public pages only — Kinn fetches pages listed in your sitemap or feeds and honours your site's robots.txt. Anything you disallow there, Kinn won't fetch.
  • Read-only — Kinn never submits forms, logs in, posts, or changes anything on your site. It only reads what's already published.

Kinn re-indexes your site periodically so new and updated pages get picked up; unchanged pages are skipped, so re-indexing stays light.

What you can now ask​

Once your website is connected and indexed, try:

  • What does our blog say about the 2.1 release?
  • Summarize our latest changelog entries.
  • Do our docs cover how to connect a new source?
  • What have we published about pricing?
  • Find the blog post where we announced cross-platform support.

Because your pages are first-party context, they're especially useful alongside your feedback integrations — Kinn can compare what users are saying with what you've actually documented or announced.

See Queries for how to get sharper answers, and Example queries for a fuller library grouped by what you're trying to do.