SEO automation that ends in a pull request you review

Pick one missing title or missing description finding from an audit. Tin rechecks it against the live site and the repository, and proposes a verified pull request. When no safe repair exists, it explains why and opens nothing.

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.

01Rechecks the finding so you never fix something already fixed.
02Locates the page source. Exact static HTML and bounded Python-wheel HTML templates are supported.
03Proposes the change as a pull request and verifies it.
04Lists unsupported pages separately and saves a result receipt.

ask your agent

Take the first missing description finding from our Tin audit and propose the fix as a PR.

workflow keyorganic.technical_fix

required inputs

audit_run_idaudit_revisionfinding_idexpected_repositoryrepository_serves_site

optional inputs

context

outputUnmerged GitHub PR and reports/technical-fix/{run_id}/RESULT.md

needsAn audit run and the GitHub integration for the repository that serves the site.

guardrailNever merges or deploys. GitHub runs whatever PR checks you have configured.

source on githubgithub.com/tin-computer/tin →

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 can confirm the repository really serves the site and review the diff in context, which is the part generic SEO automation gets wrong.

All workflows →

Using something else for this today?

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

Tin as a Semrush alternativeSEO Tin as a Screaming Frog alternativeSEO

Workflows that run well with this one

SEO and AI visibility auditorganic.audit Site health fix as a PRsite.health_improve

Questions

Which findings can it fix today?

Missing title and missing meta description findings, on static HTML and on bounded Python-wheel HTML templates. Other pages are listed as unsupported.

Will it change my live site?

No. It opens a pull request. You merge and deploy on your own terms.

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.