Skip to content

How people find your site ledger

Keeps a ledger in your repo of every referrer, AI assistant, link preview platform and web mention that has ever sent someone to your site. Each run reports only what is new, and the agent looks up each new host and writes a one line note, so junk surfaces once and a real blog post or forum thread gets read.

MarketingWorks with Claude Code · CursorCommunity example
Build your promptSee requirements

What it does

  • Pulls referrers from analytics, CDN logs, backlink data and mention searches
  • Compares against the ledger and lists only new hosts, surges and new pages
  • Visits each new host and writes a one line note on what it is
  • Records junk hosts so they never show again
  • Keeps the ledger as two files in the repo you can read and edit

Your approval boundaries

Read only

Reads connected data. It does not send messages or change records.

You decide what happens next.

More about this workflow

This setup is for marketers and solo creators who need steady output without losing their voice. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it pulls referrers from analytics, CDN logs, backlink data and mention searches. Next, it compares against the ledger and lists only new hosts, surges and new pages. Then it visits each new host and writes a one line note on what it is. After that, it records junk hosts so they never show again. Finally, it keeps the ledger as two files in the repo you can read and edit. It works with your analytics, web fetch and web search, each on its own login with limited access.

You get the finished work, ready to read. It only reads, so nothing is sent, changed or paid for. You decide what to do with it.

“Each run reports only what is new since the last one.”
preziotte preziotte on GitHub · Oct 31, 2026
Before you startAnalytics · Web fetch accessRead-only permissionsClaude Code or Cursor
Explore required tools and model recommendations

Tools and access

  • Google Analytics

    Handles the analytics part of this job. Grant Viewer role.

    API required: Yes. Needs a Google Cloud project with the Analytics Data API and an OAuth app or service account.

    Sign up: Google Analytics

  • Web fetch

    Handles the web fetch part of this job. Grant public pages, no logged-in sessions.

    API required: No. Built into most agent harnesses. It reads public pages with no login.

    No sign-up needed

  • Web search

    Handles the web search part of this job. Grant public search results only.

    API required: Optional. Built into most agent harnesses. A standalone search API needs its own key.

    No sign-up needed

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Strong general writer at a mid price.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

GPT-6 Luna

Very low cost for first drafts and digests.

$0.10 per million input tokens, $0.50 per million output tokens, for prompts up to 272K tokens.

OpenAI docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

analytics, cdn logs, backlinks, mentions

default 7 days

default docs/foundby.md

2Your prompt

4 of 4 still empty
Fill these in before you run it: [SITE DOMAIN] [SOURCES WIRED: analytics, cdn logs, backlinks, mentions] [WINDOW: default 7 days] [LEDGER PATH: default docs/foundby.md] You are the How people find your site ledger agent. Keeps a ledger in your repo of every referrer, AI assistant, link preview platform and web mention that has ever sent someone to your site. Each run reports only what is new, and the agent looks up each new host and writes a one line note, so junk surfaces once and a real blog post or forum thread gets read. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Pulls referrers from analytics, CDN logs, backlink data and mention searches - Compares against the ledger and lists only new hosts, surges and new pages - Visits each new host and writes a one line note on what it is - Records junk hosts so they never show again - Keeps the ledger as two files in the repo you can read and edit What you must never do without a yes from a person: - Anything that writes, sends, or spends. This job only reads. Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Cursor

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Google Analytics with its own login, not yours. Grant Viewer role.
  2. 2Set up Web fetch. Keep it to public pages, no logged-in sessions.
  3. 3Set up Web search. Keep it to public search results only.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access30 / 30

Read only. It never writes, sends or spends.

Human approval30 / 30

Nothing to approve, it only reads.

Undo and logs20 / 20

No changes to undo. Reads can be logged.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

Nothing major to fix. One polish tip: show a short daily log of what it read, so you can spot it reaching for anything new.

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for How people find your site ledger](https://trustcase.dev/badge/how-people-find-your-site-ledger.svg)](https://trustcase.dev/use-cases/how-people-find-your-site-ledger)
HTML
<a href="https://trustcase.dev/use-cases/how-people-find-your-site-ledger"><img src="https://trustcase.dev/badge/how-people-find-your-site-ledger.svg" alt="Trustcase trust score for How people find your site ledger" height="20"></a>

More marketing workflows

Other workflows that use the same tools

  • Daily portfolio explainer

    Personal. Reads your stock tracker each day and explains in plain words what happened to each holding and why. It checks your own rules but never tells you to buy or sell.

  • Supplier review check

    Ecommerce and resale. Reads a supplier's reviews before you place an order and rates them green, yellow, red or unknown. Every red flag comes with a quote as proof.

  • Apartment listing scout

    Personal. Checks rental sites for new listings that fit what you want and sends you only the good matches. Helps you see places before everyone else applies.