Use `/news.xml` for new briefs and current updates without waiting for an email list or social algorithm.
RETURN PATHFollow
Make the next reader action clear before broadening reach. Page follows, feed saves, bookmarks, and referrals only count when a current source supports the result.
Use `/feed.xml` for case-file updates and archive changes that readers may want to revisit.
Use `/answers.xml` for stable source questions, caveats, and follow paths without relying on a social feed.
Use `/feeds.opml` to import news, case, and answer feeds into a reader or curator workflow in one step.
Bookmarkable routes help repeat visits, but a bookmark is not traffic until the reader returns.
Email signup stays closed until the mailbox, sender identity, and unsubscribe path are verified.
READER RETURN PATH
Evidence onlyTurn useful reads into a way back
Use current visible Facebook Page counts or account-side receipts when tracking outcomes. Do not infer results from likes, views, drafts, or copied posts.
Use current visible Facebook Page followers as one audience signal; keep numeric targets in the internal receipts.
Every useful exchange should offer one follow, feed-save, share, or referral path before repeating broader posting volume.
Send first-time readers here so the next visit does not depend on a single social post or comment thread.
The 10,000-view month still needs 334 real page views a day. Follows help create a return path; they are not page views by themselves.
Ask for the follow
Owner-runCapture: Use the Inner Circle Ledger Facebook Page link where a reader already found a useful source route.
Proof: Count only the current visible Page follower number or a current Page insight receipt. Do not infer follows from likes, views, or copied text.
If this source route helped, follow the Page so the next update reaches you: https://innercircleledger.com/fb/
Offer RSS as the backup
LiveCapture: Use the news RSS feed for readers who do not want Facebook or who want a direct update stream.
Proof: A feed URL copied or saved is retention setup. Count only later returning visits, visible mentions, or accepted feed/listing placements.
Follow Ledger updates without waiting on an algorithm: https://innercircleledger.com/news.xml
Send one source route
Manual shareCapture: Use the Share Hub to match one accurate Ledger route to one reader question, group rule, or curator request.
Proof: Count only a live URL, visible reply, accepted listing, referral source, or measured visit.
Use the Share Hub to pick one source-linked Ledger route before posting: https://innercircleledger.com/share/
Ask for one qualified referral
Owner-runCapture: Ask readers to send one Ledger route to a person who already tracks public records, not to blast private contacts.
Proof: Count only a visible share, accepted link, referral URL, reply, or measured return visit.
If the Ledger is useful, send this follow route to one person who would actually use it: https://innercircleledger.com/go/
Use the bio-ready card
Pinned routeCapture: Use when a reader is likely on mobile and needs one route with the Page follow, feeds, source map, and proof-safe ask.
Proof: Count only visible follows, measured visits, public replies, accepted links, or referral URLs after the route is used.
Start here if the Ledger helped: follow the Page, save the feeds, or open the source map from one mobile card: https://innercircleledger.com/go/
RETURN LOOP
Follow HubGive useful readers one way back
After a reader opens a source route, ask for the smallest useful next step: follow the Page, save the feed, read why the Ledger is worth following, or send one route to a person who checks public records.
FOLLOW ASK KIT
Direct, RSS, referral, curator, replyUse the ask that fits the reader
Use these copy blocks only after the Ledger has already helped with a source route, answer page, tracker update, or citation. The ask should feel like a next useful step, not a cold blast.
Direct follow ask
Use after a useful readCapture: Use when someone already opened a Ledger source route and needs a simple next step.
Proof: Count only the visible Facebook follower number or Page insight receipt after the ask.
If this Ledger source route helped, follow Inner Circle Ledger so the next public-record update can find you: https://innercircleledger.com/fb/
RSS backup ask
Algorithm-freeCapture: Use for readers who will not follow on Facebook but may save a direct feed.
Proof: A saved feed is setup only; count later return visits, visible mentions, or accepted feed listings.
Prefer not to use Facebook? Save the Ledger news RSS feed and come back when the next sourced update posts: https://innercircleledger.com/news.xml
One-person referral ask
Manual onlyCapture: Use when a reader knows one person, writer, host, moderator, researcher, or curator who would use the source map.
Proof: Count only a visible referral URL, accepted link, reply, or measured referral visit.
If you know one person who tracks public records, send them the Ledger follow route instead of blasting a list: https://innercircleledger.com/go/
Curator or source-list ask
Permission-firstCapture: Use for newsletters, civic lists, resource pages, RSS directories, or show notes that accept source-map submissions.
Proof: Count an accepted listing, public citation, referral source, or Search Console/Analytics traffic later.
For a source list or newsletter: Inner Circle Ledger has a curator kit with the source map, RSS feeds, OPML bundle, and caveats in one place: https://innercircleledger.com/curator-kit/
Post-reply follow ask
Only after relevanceCapture: Use only after answering a real source question with the matching Ledger route.
Proof: Count only the visible reply/link placement and any measured visit or follow that follows.
Here is the clean source route I use for the released Epstein files. If it helps, follow the Ledger so future source updates are easier to find: https://innercircleledger.com/answers/where-are-the-epstein-files/
Link-in-bio ask
Use where one URL is allowedCapture: Use for profile bios, pinned Page posts, screenshots, printed notes, and short replies where one URL has to do the work.
Proof: A visible profile link or pinned route is not a follower. Count only later visible follows, replies, accepted links, or measured visits.
One link for the Ledger: follow the Page, save the feeds, or open the source map here: https://innercircleledger.com/go/
FOLLOW OPTIONS
Feeds, bookmarks, and statusCopy the route that fits the reader
News RSS
Live feedCapture: Use `https://innercircleledger.com/news.xml` for new briefs and current updates.
Proof: A reader can save the feed URL. Count only later returning users, referrals, or visible mentions.
Follow Ledger news RSS: https://innercircleledger.com/news.xml
Case RSS
Live feedCapture: Use `https://innercircleledger.com/feed.xml` for case-file updates and archive changes.
Proof: A feed follow is useful retention setup, not a measured view by itself.
Follow Ledger case updates RSS: https://innercircleledger.com/feed.xml
Answer RSS
Live feedCapture: Use `https://innercircleledger.com/answers.xml` for stable answer pages that handle source, caveat, and citation questions.
Proof: A saved answer feed is retention setup. Count only later returning visits, visible referrals, or measured traffic.
Follow Ledger answer pages RSS: https://innercircleledger.com/answers.xml
News JSON Feed
Live feedCapture: Use `https://innercircleledger.com/news.json` when a reader, app, or curator prefers JSON Feed.
Proof: A saved JSON Feed is retention setup. Count only later returning visits, public listings, or measured referrals.
Follow Ledger news in JSON Feed: https://innercircleledger.com/news.json
Case JSON Feed
Live feedCapture: Use `https://innercircleledger.com/feed.json` for case-file updates in JSON Feed format.
Proof: A feed copy is not traffic by itself; count later returning visits or accepted listings.
Follow Ledger case files in JSON Feed: https://innercircleledger.com/feed.json
Answer JSON Feed
Live feedCapture: Use `https://innercircleledger.com/answers.json` for source-safe answer pages in JSON Feed format.
Proof: A saved feed is setup only until a return visit, citation, listing, or measured referral appears.
Follow Ledger answer pages in JSON Feed: https://innercircleledger.com/answers.json
Feed bundle
OPML importCapture: Use `https://innercircleledger.com/feeds.opml` when a reader, RSS app, newsletter, or curator wants all public Ledger feeds at once.
Proof: An imported bundle is setup only. Count later return visits, accepted listings, public citations, or measured referrals.
Import all public Ledger feeds: https://innercircleledger.com/feeds.opml
Daily tracker bookmark
BookmarkCapture: Save the Trump tracker for current public-record movement and dated updates.
Proof: Use Traffic Pulse to count actual returning visits, not the act of copying the bookmark link.
Bookmark the Ledger tracker: https://innercircleledger.com/trump-tracker/
Epstein source map bookmark
BookmarkCapture: Save the Epstein-files map for official routes, caveats, answers, and document-entry points.
Proof: Count return visits or referral traffic only when analytics or a live source supports it.
Save the Epstein source map: https://innercircleledger.com/epstein-files/
Newsletter status
PausedCapture: Use the newsletter status page to explain that email is not active yet and RSS is the current follow path.
Proof: Do not collect emails or claim subscribers until the mailbox and unsubscribe flow are verified.
Email signup is paused; use RSS for now: https://innercircleledger.com/newsletter/
Reader referral route
Owner-runCapture: Use one exact route and one reason it helped. No contact import, bulk messages, or hidden relationship.
Proof: Count only a visible share, accepted link, referral URL, reply, or measured returning visit.
If this helped, send one exact Ledger route to one person who would use the source map: https://innercircleledger.com/reader-referral-kit/
Quick follow card
Mobile-firstCapture: Use `https://innercircleledger.com/go/` when a profile, screenshot, or one-line reply needs the Page follow, feeds, and best source routes together.
Proof: A copied profile link is setup only. Count later visible follows, referral traffic, accepted listings, or replies.
Follow, save, or start with the best Ledger source routes: https://innercircleledger.com/go/
RETURN RHYTHM
Useful return reasons onlyWhen to point people back
| Cadence | Move | Route | Use |
|---|---|---|---|
| Daily | Tracker check | https://innercircleledger.com/trump-tracker/ | Use when someone wants what changed today. |
| Twice weekly | Source-map return | https://innercircleledger.com/epstein-files/ | Use for official-file questions and document routes. |
| Weekly | Answer-page pass | https://innercircleledger.com/answers/ | Use the question pages that match actual reader confusion. |
| One-time | Feed bundle import | https://innercircleledger.com/feeds.opml | Use when a reader or curator wants all public feeds in one RSS app. |
| Weekly | RSS save prompt | https://innercircleledger.com/go/ | Ask readers to save the follow route, not to join a list that is not active. |
| After every referral | Traffic check | https://innercircleledger.com/traffic/#measurement | Record returning visits and referral sources without guessing. |
COUNTING RULES
Measure after the returnRetention setup is not traffic
- A copied RSS link, bookmark prompt, or referral ask is retention setup, not traffic.
- Email signup remains paused until sender identity, mailbox access, and unsubscribe handling are verified.
- Do not import contacts, scrape followers, send bulk DMs, or report private asks as public reach.
- Count a follow path only when Analytics, Search Console, platform insight, a live URL, or a referral record supports it.
- Repeat the follow prompt only when the reader has a clear next reason to come back: new brief, source map, tracker update, or answer page.
NEXT BEST ASK
Ask for one visible follow.
The cleanest growth move after a useful read is a return path: Page follow, RSS save, bookmark, or one qualified referral to someone who would actually use the source map.
Copy the follow line
If the Ledger helped, follow the Page or save the Follow Hub so the next source update can find you: https://innercircleledger.com/go/