Integration
ParSEO for coded sites on GitHub
Updated · 2 min read · By The ParSEO team
The short answer
For a website built in code, ParSEO puts each published post into the site's own code as a pull request, through ParSEO's GitHub App installed on just the repository that holds your site. The post goes live at once through ParSEO Edge, and once your developer merges and deploys the pull request, the site's own copy takes over. ParSEO never merges.
Key points
- One GitHub App on one repository, with Contents and Pull requests read and write.
- Posts arrive as Markdown or MDX files in your blog folder, matching your existing posts.
- ParSEO only adds files and opens pull requests. Your developer merges after the preview.
- Edge serves the post until your own copy is deployed, then steps aside.
At a glance
How it connects
A GitHub App and pull requests
What ParSEO can change
- New blog posts, as Markdown or MDX files with the same front matter your existing posts use
- Posts go into your blog folder, such as content/blog or src/content/posts, wherever your posts already live
- Titles, descriptions and other fixes reach the live site through ParSEO Edge
If you leave ParSEO
Every post your developer merged is a file in your own code and stays exactly where it is. Posts that were only served by ParSEO Edge stop when you leave; merge their open pull requests first to keep them.
Set up ParSEO on GitHub
Open Connectors
In ParSEO, open Settings, then Connectors, and find Posts in your website's code.
Create ParSEO's app
GitHub opens with ParSEO's app filled in. Press Create.
Install it on one repository
Install the app on the repository your site's code is in. GitHub lets you pick just that one.
Pick the repository in ParSEO
Back in ParSEO, pick that repository. From the next live post, a pull request opens for your developer.
How it works
- You approve a post in ParSEO, and it goes live at once through ParSEO Edge.
- ParSEO writes the same post as a file in your site's code, using the same Markdown and front matter your existing posts use, so your blog shows it like any other.
- It opens a pull request into your repository. Your developer checks the preview build and merges.
- Once the file is deployed, your site's own version takes over by itself, and Edge's copy stays only as a safety net.
What the app is allowed to do
ParSEO's GitHub App asks for two permissions: Contents (read and write) and Pull requests (read and write). It may only add files and open pull requests. It never merges: your developer does. Its tokens last one hour and are made fresh each time.
You can pause it from ParSEO: no new pull requests until you resume, and posts stay live.
If a pull request isn't merged
The post stays live through ParSEO Edge, and ParSEO shows that your developer hasn't added the copy yet.
What stays if you leave
Every merged post is a file in your own repository and stays. Posts served only by ParSEO Edge stop when you leave, so merge their pull requests first.
Questions people ask
Does ParSEO need access to all my repositories?
No. GitHub lets you install the app on one repository, and ParSEO only needs the one that holds your site.
Can ParSEO push to my main branch?
No. It adds files on its own branch and opens a pull request. Your developer reviews and merges.
Which frameworks does it work with?
Any site that keeps blog posts as Markdown or MDX files in its code, in folders like content/blog, content/posts, src/content/blog, posts or _posts.
Sources
Read next
See what Google and AI say about your business.
Add your website and get your Day 0 in minutes: where you rank, what AI answers say, and what to fix first.
Start your Day 0