SEO by platform
SEO for git-built sites
Articles commit as markdown files into the repository and path you choose, and your deploy turns each commit into a page. Built for Next.js, Astro, Hugo, Jekyll and any headless setup where a committed file becomes a page on the next build.
Writing opens to customers in October.
Publishing to GitHub
Each published article is a commit: a markdown file with front matter, title, description, date and slug, landing at the path template you configure, so common static-site generators pick it up without glue code. A retry publishes to the same path and overwrites rather than duplicates. Verification treats git differently on purpose: a repository file URL always resolves even when your site's page does not, so git publishes are never marked live off the repo URL, and the final page is your build's responsibility.
- 1
Create a fine-grained token
In GitHub, create a fine-grained personal access token that explicitly lists the target repository, with contents read and write. A token without that repo reads as not-found rather than forbidden.
- 2
Point the connection at the repo
In the project's Publishing tab, choose GitHub, paste the token, set the repository as owner/repo, the live site URL, and the file path template, for example content/blog/{slug}.mdx. Leave the live branch blank to have drafts arrive as PR branches.
- 3
Test and watch the build
Send a test publish, confirm the file appears in the repo, then let your site build and open the page it produced.
Markdown with front matter, at your path
Articles carry front matter with title, description, date and slug, and land where the connection's path setting points, for example content/blog. Generators differ on paths and front-matter keys, so the path is yours to set.
Docs: GitHubA token scoped to one repository
A fine-grained token with contents read and write on just the target repository is the right shape. Scoping it to one repo limits the blast radius of a leak.
Docs: GitHubGit publishes are never falsely marked live
A repository file URL resolving proves nothing about your site, so git-hosted publishes are not URL-verified. Reachability of the final page belongs to your build pipeline, and the states say so instead of pretending.
Docs: Publish verificationArticles come off a planned calendar
Plan items on the content calendar and write them two ways: click Write on a card, or let Auto-write pick each one up at midnight on its calendar date. Both run the same researched pipeline, which drafts the article and then revises it against the content score across sweeps.
Docs: Content calendarEvery article is scored before you ship it
The content score runs 36 fixed checks in 6 categories, with no randomness anywhere: the same page always produces the same score. Each check comes back as a pass, a warn or a fail, and each failure names its specific fix.
Docs: Content score
What it won’t do on GitHub
Better to know before your first publish.
The connection cannot see your build. A commit that lands while the deploy fails, or a file the generator ignores over a path or front-matter mismatch, produces no page, and the deploy log for the commit is where that shows.
Renaming or moving published files later is yours to manage in git.
- Docs: GitHub
What SearchBlueprint does for a GitHub site
A planning tool, not an editor: it doesn't change your GitHub settings. It crawls your site and tells you which searches to go after and which page should win each one.
Try each one below, on SearchBlueprint’s own plan for its own site
1Starting from a blank list
Your keyword list, started from your own site.
Most keyword tools hand you thousands of phrases. Your plan starts from your own GitHub site instead: the searches you already show up for, and the ones a site like yours could rank for.
- Your current position for each search you rank for
- Searches a site like yours could rank for, marked not ranking yet
- Monthly searches and cost per click for each keyword
- #71
free website traffic rankings
170 searches a month · $6.33 a click
- #71
web traffic statistics free
110 searches a month · $10.71 a click
- #50
spy seo
30 searches a month · $20.47 a click
- #80
what is my hosting
30 searches a month · $3.45 a click
2Which page gets which search
Give each search its own page.
You've watched two of your own pages chase the same search and neither win. Every keyword you confirm goes to one page. Where two pages compete, you're told which ones, and where nothing fits, the plan suggests a page to create.
- One main keyword per page, across the site
- A warning when two of your pages compete
- Pages to create, where no page answers a search
40 pages mapped · 2 to build
Primary keyword
seo automation
1,900 searches a month · KD 14
Page
- /
3What people ask ChatGPT
Questions to answer for ChatGPT and AI Mode.
People ask ChatGPT full questions, not two-word searches. From the keywords you pick, your plan drafts the questions a buyer might ask and ties each one to a page. You keep the ones that sound like your customers.
- Questions for ChatGPT, Perplexity, Gemini and AI Mode
- Each question tied to a page
- Remove any that don't sound like your customers
5 of 5 kept
4On a paid plan
A title and description for every page.
Confirm your keywords once and every page gets a title and a meta description in one list, ready to paste into GitHub's title and description fields. Your GitHub site only changes when you paste them in.
- A row for every page, not just the homepage
- Based on the keywords you confirmed for each page
- New pages to consider, listed with your current ones
- Keyword
- seo tool for agencies
- Secondary: client seo reporting, seo software for agencies
- Meta title
- SEO Tool for Agencies: Every Client Site | SearchBlueprint
- Meta description
- Run SEO and AI search plans for every client site, with branded reports and share links your clients open without a login.
- Recommended H1
- SEO for every client site, in one workspace
Questions people ask
The commit exists but no page appeared. Why?
Your site did not rebuild, or the generator ignored the file over a wrong path or a front-matter mismatch. Check the deploy log for the commit.
Is there a way to set this up without creating a token?
Yes, where it is switched on: the one-click GitHub and Next.js setup card connects through a GitHub App install with nothing typed in. It appears on the Publishing grid on servers where the App is configured.
What happens on a delivery retry?
The same article publishes to the same path, so a retry overwrites rather than duplicates. Two different slugs for one article means the slug changed between attempts, delete the stray file.
See the plan for your own GitHub site
Your first plan is free and needs no card. It shows your rivals, the searches people type to find sites like yours, and which page should answer each one.
- Free first plan
- No credit card
- Keep your plan