Step 1
Collect the signals 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 are reviewed like code
SHIP reads what people search for and what AI answers cite, and picks the pages worth writing. You approve the list each week, and every page is reviewed and tested 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
Measure, brief, publish, then measure again
Step 2
Approve the week's picks
A prioritization mission ranks the opportunities and puts fixes to pages that already rank ahead of new ones. You approve the week's list by merging 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
Keep every number traceable to a source
Ground every number in a file your pipeline wrote
Agents read 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 writing new ones
Pages ranking in positions 3 to 20, or shown in results without clicks, get a refresh before anything new in their topic.
Shape each page for AI answers
Each page answers its question in its first 100 words, and ships with structured data and an llms.txt entry.
Judge content types by the signups they bring
Guides, comparisons and definitions run as separate experiments, and each is judged by the signups its pages bring in.
See what every page cost
Each page is a mission with its own recorded cost and duration, so you can weigh it against the traffic the page earns.
Evidence
Read the first pages from SHIP's own briefs
letsship.ai is building this loop on its own repository first. A weekly workflow there pulls Search Console data and flags the pages to fix first. The first pages were written from briefs reviewed in the repository, and they are the baseline the loop's own pages will be measured against.
FAQ
Frequently asked questions
Is the content factory available today?
Not yet: the weekly loop is in early access. Today you can hand SHIP a written brief with ship delegate plan, and the page comes back as a pull request that passed review and a test of the rendered page.
What is a content factory?
A content factory is a repeatable pipeline that turns search demand into published pages. SHIP's, in early access, 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 automates the research, ranking and review around each page, but a person approves each week's list, so you publish a few pages a week that each answer a real search question.
Which data does the content factory use?
The loop 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 any is written. Each page then arrives 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 and run the loop SHIP uses on its own site.
Join the early-access list
Answer 4 questions. SHIP emails you when it opens to you.