SEO & Git Publishing
It Opens a Pull Request. You Merge It.
MarkOS researches a keyword, writes the article, and opens a real pull request on your own website repository — add-only, on its own branch. You review it exactly like a PR from a colleague, and it goes live when you merge.
Spark and up — no separate upsellYou run a business, not an SEO agency.
No need to become an SEO specialist.
MarkOS picks the keyword, writes the article and opens a pull request on your own repository — target keyword, SEO score, meta description, cover image and up to three internal links already in it. You read it the way you would read a PR from a colleague.
What you actually do
- 1
Connect your repo and confirm what MarkOS found in it.
- 2
Read the pull request.
- 3
Merge it. Your usual deploy publishes it.
Search Console, then your repo
It finds the keyword. You merge the article.
MarkOS reads your Search Console data, sorts your keywords into the ones worth acting on, and turns the best of them into finished articles — each one delivered as a pull request on your own repository.
Three safeguards on every pull request
“It writes to my website” deserves a careful answer. Here is exactly what protects your repository.
Always a free filename
If a slug is taken, MarkOS finds an available variant, so your existing posts stay exactly as they are.
A new branch, then it stops
Each article gets its own branch. There is no update-in-place and no force-push anywhere in the code.
The commit only adds
New files are layered onto your existing tree. There is no delete operation in the publishing path at all — not disabled, never written.
Your repository is also never cloned. MarkOS works entirely through GitHub’s Git Database API — blob, tree, commit, branch, pull request — so your code stays where it is.
Setup reads your repo once, then asks you
You should not have to describe your own site’s conventions in a settings form. MarkOS looks at your repository and works them out.
- 1
Detect the framework
Next.js, Astro, Hugo, Jekyll, Gatsby or plain HTML.
- 2
Learn your conventions
Where your posts live, how filenames are formatted, and — by reading an existing post — your exact frontmatter schema.
- 3
Show you what it found
The whole detected profile, in plain language, before anything is written.
- 4
You confirm
Publishing unlocks once you approve the profile. Not before.
If your repo uses an unusual layout, MarkOS proposes a sensible default and tells you what it assumed, so you can adjust it.
What lands in the pull request
A finished article, and the notes to check it against
The description carries the target keyword, an SEO score out of 100, the meta description and a word count. The commit carries the article and a cover image — committed to your repo or referenced from a CDN, whichever your site expects.
- ✓Up to three suggested internal links to your existing posts, so the article isn't an orphan.
- ✓A short review checklist: frontmatter matches, right directory, cover renders.
Once you merge, your usual deploy publishes it. MarkOS tracks the PR and updates its own status to merged or closed to match.
Growing the publishing targets
On the way
- →GitLab repositories alongside GitHub.
- →Direct publishing to hosted CMS platforms.
See it working on your own business
Connect a repo, let MarkOS read it once, and confirm what it found. Nothing publishes before you do.
Start your 30-day trial →