TinTinWorkflows
GitHubSign in

An open-source SEO audit that also checks AI answers

Tin checks up to 100 public pages for technical SEO problems, then asks whether AI answers mention, cite or recommend your business. You get a report, findings you can act on, and the evidence behind each one.

Find it on GitHub
codex mcp add tin --url https://app.tin.computer/mcp

What the workflow does

A Tin workflow is a repeatable job: declared inputs, a bounded run and a defined output. The steps below are what this one does, every time.

  1. 01Crawls up to 100 public pages of the site you name and records technical findings.
  2. 02Checks whether AI answers mention, cite or recommend the business for its market.
  3. 03Saves a report, a list of actionable findings and the supporting evidence to project Files.
  4. 04Feeds later workflows: the content plan and the technical fix both start from an audit run.
ask your agent

Run Tin's organic audit on our site for the US market and walk me through the top findings.

workflow keyorganic.audit
required inputs
site_urlmarket
outputAudit report, findings and evidence in project Files
needsA public site. No GitHub connection required.
guardrailRead only. The audit changes nothing on your site.

What every workflow here comes 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 already knows which pages matter and which are legacy, so it can name the market precisely and tell a real finding from a page you meant to retire.

All workflows →

Using something else for this today?

What this workflow replaces in each product, and what it does not.

Questions

How many pages does the audit cover?

Up to 100 public pages per run. It is sized for a startup or product site, not for crawling a very large catalogue.

Does the audit change my site?

No. It only reads public pages. Fixes are separate workflows that open a pull request for you to review.

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

Run this once in your terminal. It connects Tin to your agent and opens the sign-in. Then ask your agent to grow your project.

Find it on GitHub
codex mcp add tin --url https://app.tin.computer/mcp