TinTinWorkflows
GitHubSign in

Refresh the page searchers see but skip

Tin reads your latest audit and Search Console evidence, picks the one page with the most impressions at stake, and proposes new copy for the lines that keep it from earning clicks. After you approve, it changes exactly those lines in your site's source.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp
Page refresh
content.refresh
outputcontent/refreshes/{run_folder}.md, then the approved change in your repository
guardrailHuman review. Only the approved lines change; when a text is not in the source verbatim or appears in several places, delivery stops and says why instead of guessing.
needsA finished organic audit with Search Console evidence. GitHub, with the site's repository selected, to deliver the change.
required inputsnone
optional inputsdirection

What the workflow does.The same steps, every run.

A Tin workflow is a repeatable job: declared inputs, a bounded run and a defined output.

  1. 01Picks one page from the latest audit: seen near the top but rarely clicked, or ranking just below the top results.
  2. 02Proposes a new title and meta description, plus the H1 and opening answer when they miss the search, in your positioning and voice.
  3. 03Shows each change as now, proposed and why, for you to approve in Decisions.
  4. 04Changes exactly the approved text in the source and follows your delivery setting: a pull request or a commit to main.
  5. 05Waits six weeks after a refresh goes live, then reports the page's clicks before and after.
ask your agent

Refresh the page in our latest Tin audit with the most search impressions at stake, and show me the old and new text.

What every workflowcomes with.

Battle tested on real products

These are the workflows we run for real companies. Claw Messenger went from about $45 to $2,105 in monthly revenue in 124 days on them. Each one has declared inputs, bounded execution and tests, and anything public waits for your review.

See the case study →

Open source: read it, fork it, self-host it

Apache 2.0. Every workflow is a folder in the repository: the steps it runs, the data it reads and what it is allowed to do. Change it, or run the whole system on your own machine.

Open the repo →

Runs on the agent that already knows your product

Your agent knows how the site builds its titles, so it can tell you up front when a title comes from a template the refresh cannot touch.

All workflows →

Using something else for this?What it replaces, and what it does not.

Questions.

Does it rewrite the whole page?

No. It changes the title and meta description, and the H1 and opening answer only when they miss the search. Body paragraphs change only when the audit flagged decay or weak answer structure.

How do I know it worked?

Later runs compare the 28 days before and after the change went live: clicks, impressions, click-through rate and average position for that page.

Is Tin really open source?

Yes. Tin is licensed under Apache 2.0 and the source is at github.com/tin-computer/tin. You can read every workflow, change it, and self-host the whole system.

Which coding agents can run Tin workflows?

Any agent that speaks MCP, including Claude Code, Codex and Cursor. There is also an API, and the same projects run in the browser at app.tin.computer.

Why run marketing from a coding agent?

Because it already knows your product. It has the repository open, so it fills workflow inputs accurately, reviews output against what the product really does, and can act on the results in the same session.

Add Tin to your coding agent.It takes one command.

Try in browser →
codex mcp add tin --url https://app.tin.computer/mcp