Step 1
Pull the data in your own pipeline
A weekly job in your repository pulls Search Console, analytics, AI-answer citations and AI crawler visits into a data file, with your own credentials.
Content factory
Early accessTurn search demand into pages that SHIP reviews and tests like code
SHIP reads what people search for and what AI answers cite, then picks the pages to write. You approve the list each week, and SHIP reviews and tests every page before it merges.
- For
- Founders who need search and AI-answer traffic without a content team.
- Instead of
- An SEO agency, or a batch of AI pages nobody checked.
Runs today: Hand SHIP a written page brief with ship delegate plan, and get the page back in your site's repository as a reviewed, tested pull request.
Answer 4 questions. SHIP emails you when it opens to you.
How it works
Run the loop once a week
Step 2
Approve the week's list
A prioritization mission ranks the opportunities and puts fixes to pages that already rank ahead of new pages. To approve the week's list, you merge one pull request.
Step 3
Merge pages that passed review and test
A mission writes each page and its brief, with structured data and internal links. The Reviewer checks every number against its source, and the Tester checks the rendered page.
Capabilities
Know where every number comes from
Take numbers only from your pipeline's data file
Agents read the measured data and never write it. A check fails any pull request that edits the data file, and the Reviewer checks each number on a page against its source.
Fix pages that already rank before you write new ones
Pages in positions 3 to 20, or pages that show in results without clicks, get a refresh before anything new in their topic.
Write each page for AI answers
Each page answers its question in the first 100 words and comes with structured data and an llms.txt entry.
Judge each content type by its signups
Guides, comparisons and definitions run as separate experiments. You judge each type by the number of signups from its pages.
See what every page cost
Each page is a mission with its own recorded cost and duration, so you can compare it with the traffic the page gets.
Evidence
Read the first pages from SHIP's own briefs
SHIP builds this loop on its own repository, letsship.ai, first. A weekly workflow there pulls Search Console data and flags the pages to fix first. The first pages came from briefs that people reviewed in the repository. SHIP will measure the loop's own pages against them.
FAQ
Frequently asked questions
Is the content factory available today?
Not yet, because the weekly loop is in early access. Today you can hand SHIP a written brief with ship delegate plan. The page comes back in a pull request that passed review and a test of the rendered page.
What is a content factory?
A content factory is a repeatable process that turns search demand into published pages. SHIP's version is in early access. It measures demand in your own pipeline, writes each page as a pull request, and reviews and tests it before it merges.
Is this programmatic SEO?
Partly. SHIP does the research, ranks the pages and reviews each one, but a person approves each week's list. You publish a few pages a week, and each one answers a real search question.
Which data does the content factory use?
It reads Google Search Console, your product analytics, AI answers that cite their sources, and AI crawler visits from your own edge logs. Your pipeline pulls each one with your own credentials, so SHIP holds none of them.
Does a person approve what gets published?
Yes. You approve each week's list of pages before SHIP writes any of them. Each page then comes as a pull request, and it merges only when you merge it or turn on auto-merge.
Start your content loop with one brief
Join early access to run the same loop that SHIP builds for its own site.
Join the early-access list
Answer 4 questions. SHIP emails you when it opens to you.