Grow search traffic with workflows you own
Open-source SEO software gives your team search checks whose code you can read, run and change. Tin's SEO workflows use the Apache 2.0 licence. Our experienced founders and engineers run them on your site, then write the pages and make the fixes the findings point to.
What is open-source SEO software?
Open-source SEO makes the code behind a search check available to the team using it. You can examine how the check reaches its finding and change how it works. In Tin, each workflow occupies a folder in the repository. That folder holds the steps it runs, the data it reads and the evaluations used to score it. Your team can see the method behind the audit in the same place it reads the code.
That makes it possible to trace an audit finding back to its logic. Tin connects natively to Google Search Console and keeps findings as plain files with git history. Its SEO workflows cover technical audits, keyword plans, content plans and page refreshes. Together, these give the work a record: what the site needs, what buyers search for and which pages deserve attention next.
Someone still needs to schedule the checks, tune them as the site changes, write pages and repair problems. A subscription SEO tool gives the team packaged checks and reports. Open-source scripts give an in-house team code to run and adapt. Tin's team runs its open-source workflows and does the writing and fixes they identify. Compare the options by whether you can understand each check and who will act on its findings.
- Read the check. The repository contains the steps and data behind the finding, so the method is available to inspect.
- Change the instructions. Editing a workflow file lets the team adapt the check as the site changes.
- Keep the findings. Plain files with git history preserve the research and reports for later work.
Unread SEO findings keep your pages out of Google
The team installs a search tool, then product work fills the week and the findings wait for someone to act.
- Old settings block discovery. One site's sitemap and canonical tags pointed to an old domain; no page appeared in Google.
- The logic becomes unfamiliar. When nobody understands a check, the team loses the knowledge it invested in it.
- Scripts need attention. Keeping in-house checks tuned takes time from the same people who maintain the product.
Having someone run the checks and repair the site turns those files into work that gets done.
We run the SEO workflows and make the fixes
We connect the repository and search data, then handle the audit, writing and repairs so findings have someone responsible for acting on them.
Connect the site
We set up Tin on the marketing repository and connect Search Console, so the search work starts from your own data.
Research the opportunities
We run audits and keyword research to find site problems, buyer searches and terms where competitors appear.
Repair search access
We fix indexing issues, canonical tags and sitemaps so the site points search engines to the intended pages.
Write useful pages
We produce buyer guides, comparisons and page refreshes, with a person checking the writing before it reaches readers.
Every site change arrives as a pull request you merge
The owner sees the proposed site changes in the marketing repository. Our team does the work, and the owner decides when to merge it.
First
Connect the marketing repository
We connect the outward-facing site first, along with Search Console, so the work starts with the pages buyers see.
Then
Record the findings
The technical audit and keyword plan leave their findings in files the team can open in the repository.
Next
Review the pull requests
After our review, fixes and articles go to the owner as pull requests ready for a merge decision.
Each week
Read the search response
We bring Search Console data to the weekly call and Slack to decide what to continue, change or stop.
Example: finding brand searches behind our clicks
Our own query data showed why we needed to examine where the clicks came from. Of 134 Search Console clicks, 130 came from the brand query. Four came from searches that did not name us. That finding pointed the next work toward the questions buyers search before they know the company to look for.
We keep every SEO check readable in your repo
Your team’s knowledge of a check matters when the site changes and someone has to adapt the code. Keeping its logic beside the findings means your team can return to the work and see why a page was written or a fix proposed.
- Preserve the reasoning. Readable checks let the team examine how a finding was reached before deciding what to change later.
- Follow the history. Research and drafts stay in files with git history, so earlier work remains available as the site develops.
- Own what we build. Each open-source workflow we set up, with your accounts and data, stays yours.
It fits founders who read code
Technical B2B founders
We run search work for pre-seed to Series A teams that understand their product code and have no marketing lead.
Coding-agent users
We work with teams already using Claude Code, Codex or Cursor, keeping the SEO work in familiar files and repositories.
Junior marketers with technical needs
We provide the engineering support to turn search findings into site fixes alongside the content a marketer handles.
Talk to Tin
Let's discuss which checks your site needs first and what the repository is ready for. We can run that SEO work with no long-term commitment.
FAQ
Is the code free to use?
Yes. Open source, Apache 2.0. The code is available in the Tin repository. The repository holds each check’s steps, inputs and evaluations. Your team can inspect those files to understand a finding and edit them to change how the check works.
Can we run the workflows ourselves?
Yes. One command adds Tin to a coding agent, and you can run it on your own machine with your own keys. Self-hosting is an option. Running them also means keeping them tuned and acting on the reports. We can take on that setup, research, writing and repair work.
Which coding agents does it work with?
Tin works with Claude Code, Codex and Cursor. The same projects are also available in the browser at app.tin.computer. When we run the service, your team can still read the research files and proposed changes in the repository.
Does it check AI search as well as Google?
Yes. The technical SEO and AI visibility audit covers both. We check the site’s support for search discovery and the company information available to AI answers. We use those findings to choose which pages to write and which site problems to repair.
Talk about the checks your site needs first
The founders and engineers who build and run these workflows can discuss your site's search work with you. We can look at what you want to understand about the checks and which findings would be useful to act on.