Connect your website or blog

byline watches a usable public sitemap for article pages and extracts readable text. It queues new or updated pages for processing, rather than importing every page on a site immediately or guaranteeing that its whole archive will appear.

Connect your site

1. Open Sources in your dashboard and expand Website / blog.
2. Enter your public site URL, such as https://yourname.com. byline looks for a sitemap listed in robots.txt or at /sitemap.xml and checks that it can reach and parse it before connecting.
3. Choose Add website for your own site. The first read is queued; check Your sources and your library later.

If the site has no usable sitemap or cannot be reached, the connection will not be created. If you have a single public article URL rather than a connectable site, use Read a single URL on Sources. That queues one page, not a feed. A private or login-only document is not supported by this form.

What comes in

byline fetches eligible sitemap URLs and extracts their main article text, title, and available date or author metadata. Menus and page chrome are normally excluded, but extraction is best effort: paywalls, blocked or oversized pages, client-only rendering, and pages without extractable article text may not be read. A sitemap does not supply comments, page views, or traffic analytics.

Successfully processed writing may inform your voice and profile. Reading is subject to your plan allowance and safety limits, and a large archive is not a promise that every page will be ingested.

Back-catalogue and edits

My-content sitemaps are processed in batches over successive reads, so a large archive can take time. The watcher uses each URL and its sitemap lastmod to find later changes. If an edit does not advance the sitemap's change marker, or a page is not listed in the sitemap, byline may not notice it. A page that stays unreadable may be skipped; there is no guarantee that nothing is missed.

New sitemap entries and detectable edits are picked up on scheduled checks. To request another check, choose Resync on the connected source. This queues work, not an immediate completed refresh; production limits manual resync to roughly once per source per 30 minutes, with shared limits too.