# Content and where people come from

> Keep a list of every page, post and card your church publishes, give each a tagged link, and see search clicks, visits from AI assistants and people who reached out for each.

For: Leader, Pastor, Admin, Owner
Canonical: https://emmauos.com/docs/content-and-where-people-come-from

Your **content** is what your church publishes so people can find it: a page on your website, a blog post, a set of questions and answers, a post on a map listing, a social post, a printed card, an email. EmmauOS keeps a ledger of each piece, with who published it and when.

## Where it lives

**Reach → Where people come from**, under [Be found](/docs/be-found): one row per [source](/docs/sources), with the pages and posts that brought people in under it. Open a row to see them. **Manage every source and piece** shows the whole ledger, drafts and retired pieces included. Reach shows in the menu once an admin turns on **Outreach** in Settings. Links to the old places still open it.

## Add a piece

**Add a piece** asks for a title, its kind, its channel (search, AI assistants, maps, social or print) and its address. EmmauOS checks that the address loads. Then it asks **Who published this?**, with you chosen. A named person is recorded on every published piece. EmmauOS publishes a piece by itself only when an admin has chosen automatic publishing for that kind of page, and then records that admin's name.

A draft can wait in the ledger without an address. **Mark published** asks who published it. **Retire** takes a piece out of use; its link keeps working.

## The tagged link

Each piece gets a tagged link: your assessment link with a source code (`?s=`) and a content code (`?c=`). Use it wherever the piece points people to the assessment. Someone who arrives through it and takes the assessment keeps both: their page says **Came through: Your content** (or the source you chose) and **First read: What to expect on a first visit**. The first piece stays; a later one never replaces it.

The [embed](/docs/your-website-and-embed) carries the codes too, from its `data-emmauos-content` setting or from the address of the page it sits on.

## The three numbers

Each row shows **Search clicks** (from [Google Search Console](/docs/connect-google-search-console), once connected), **AI visits** (from the [site snippet](/docs/add-the-site-snippet)) and **Reached out** (people whose first piece it is). Open a row for the address, the tagged link, a chart of the last 90 days, where visits came from and the top search questions.

- **Counts under five show as "Fewer than 5"**, here, in the apps and through AI agents. No list of visitors exists anywhere.
- **AI visits are undercounted.** Many assistants and apps send no referrer, so those visits count as direct.
- **Search Console runs two to three days behind.**
- No piece gets a score. It gets counts.

## What people see

Nothing. A member is never told what they clicked or read. **First read** is for the team, on the person's page and in the apps, and is cleared if the person is erased.

## With an AI assistant

`list-content` reads the ledger (leaders and up). `get-content-performance` gives the counts, with under five hidden and no names (pastors and up). `record-published` records a piece the caller published themselves, under their name, after checking the address is on your site or a listed profile; it publishes nothing. See [AI agents](/docs/ai-agents).
