Fix GitHub Site SEO from Claude
Claude SEO on your real Search Console data, with fixes you approve in the same chat.
Fix GitHub Site SEO from Gemini
Gemini reads your real Google Search Console data through SEOmatic, finds what is holding your GitHub HTML pages and Markdown posts back, stages the fix, and tells you whether it worked. In Approval mode nothing goes live on GitHub until you approve it.
- Your real Search Console data
- Fixes staged in GitHub, with your approval
- Each change measured afterwards
Gemini
Last Updated
November 2026
Connect Gemini
A custom app in the Gemini web app, or one command in Gemini CLI for Gemini Code Assist and API-key users.
Cost
Free to connect and to read your Search Console. Staged fixes are part of paid plans, with a 14-Day Trial for $1, credited to your first payment. See pricing.
How to Fix GitHub SEO from Gemini
Why Gemini Needs SEOmatic on GitHub
Gemini cannot reach your GitHub admin on its own. With SEOmatic connected, it answers from your real Search Console data, names the HTML pages and Markdown posts that are losing clicks, and stages the fix. You approve it in the conversation or in SEOmatic, and SEOmatic writes it to GitHub through pull requests on your repository.
What It Looks Like
You: Why does /blog/drain-cleaning-cost get impressions but so few clicks?
Gemini: From Sep 13 to Oct 10 (28 days), /blog/drain-cleaning-cost had 2,640 impressions and 21 clicks at position 8.7 for "drain cleaning cost". That is a low click rate for page one, so the title is the first thing to test: it reads "Drain Cleaning". I staged a new title, "Drain Cleaning Cost: What You Will Pay", to be written to the title in the post's front matter, opened as a pull request. Approve it and SEOmatic opens the pull request; it goes live when you merge.
An example on a demo site; your numbers come from your own Search Console.
Step 1: Connect GitHub to SEOmatic
In SEOmatic, go to Connections, select GitHub, and click Continue with GitHub. On GitHub, install the app on the one repository your site lives in. GitHub sends you back to SEOmatic. The full walkthrough, with every screen, is on the GitHub integration page.
Step 2: Connect SEOmatic to Gemini
At gemini.google.com, open Settings, then Connected Apps, choose Add a custom app and paste this URL, then sign in to SEOmatic. Using Gemini CLI with Gemini Code Assist or a Gemini API key? Run gemini extensions install https://github.com/Minh42/seomatic-mcp in your shell instead.
Connect Gemini
https://app.seomatic.ai/api/mcpOther ways to connect are on the Gemini page.
Step 3: Ask Gemini, Then Approve
Paste any of these into Gemini. It answers from your data and stages the fix; you approve it before it reaches GitHub.
- “Which pages built from my repository lose the most clicks?”
- “Find pages Google has not indexed and tell me why.”
- “Audit my live site and point me to the files behind each issue.”
More that work well in Gemini:
- “Which pages has Google not indexed?”
- “Audit my homepage”
- “Do AI answers mention my brand?”
Did It Work?
After you approve, SEOmatic writes the change through pull requests on your repository and checks that it is live. Then it measures the result against the page's own baseline and your site's trend: 14 days after a title change, 28 after a content refresh, 90 after a new page. Each change is marked verified, ineffective or regressed, and a low-risk change that loses traffic is rolled back on its own. Ask Gemini "Did my GitHub title changes work?" and it answers from those verdicts.
What Gemini Can Change on GitHub
HTML Pages, Fully
On plain HTML files, agents set the title, meta description, canonical tag and structured data, and rewrite content inside your page's existing main element. Structured data sits in a clearly marked block, so your own markup is never touched.
Markdown and MDX Front Matter
On Markdown and MDX files, agents update the title and description in the front matter. The body is left alone, because converting it through HTML and back breaks its formatting and can break an MDX build, and a lossy edit is worse than none.
New Blog Posts in Batches
On a Markdown blog, programmatic pages arrive as one pull request per batch, all in a single commit with a manifest. The next batch is queued only once you merge the last one, and undoing a batch is reverting one commit.
A repository has no fields and no API for SEO, only files. So the agent has to earn the right to edit one: it maps each live URL to the file that produces it, checks that the file's title matches the page, and opens a pull request only when the match holds up (a page with no title to compare is matched on its path alone). When it is not, you get a note instead of a guess.
Every field, limit and safeguard is on the GitHub integration page.
Requirements
GitHub
A site whose pages live in a GitHub repository as HTML or Markdown files, and permission to install a GitHub App on that repository. The app asks for access to contents and pull requests on the one repository you choose.
Gemini
Gemini web app: a personal Google account, age 18 or over, in the US, in English, with Keep Activity on. Gemini CLI: a Gemini Code Assist license, a Gemini API key or Vertex AI. Google stopped Gemini CLI for personal Google sign-ins (free, Google AI Pro and Ultra) on June 18, 2026; those accounts use Antigravity. Plus a free SEOmatic account.
Use Gemini on Another Platform
Gemini works the same way on WordPress, Webflow, Shopify, Ghost, Blogger, Wix, Squarespace, Framer, Drupal, BigCommerce, HubSpot CMS, Contentful, Strapi, Sanity, Next.js, Lovable, Craft CMS.
Frequently Asked Questions
Can Gemini fix SEO on my GitHub site?
Yes, through SEOmatic. Gemini reads your Search Console data, finds the HTML pages and Markdown posts losing clicks and stages the fix, which SEOmatic writes to GitHub once you approve. The three setup steps are on this page.
What can Gemini change on GitHub?
SEOmatic works on your HTML pages and Markdown posts through pull requests on your repository: titles, descriptions and content first, and more where GitHub allows it. Every field and limit is listed on the GitHub integration page.
How do I know if a GitHub fix worked?
SEOmatic measures every change it ships against the page's own baseline and your site's trend, 14 days after a title change, 28 after a content refresh and 90 after a new page, and marks it verified, ineffective or regressed. Gemini can read those verdicts for you.
What do I need on the Gemini side?
Gemini web app: a personal Google account, age 18 or over, in the US, in English, with Keep Activity on. Gemini CLI: a Gemini Code Assist license, a Gemini API key or Vertex AI. Google stopped Gemini CLI for personal Google sign-ins (free, Google AI Pro and Ultra) on June 18, 2026; those accounts use Antigravity. Plus a free SEOmatic account.
Will Gemini publish to GitHub without asking?
No. By default every change SEOmatic proposes waits for your approval before it touches your site, and your assistant is told never to approve on its own. Approved changes are stored with the page's previous state, so any edit to an existing page can be rolled back. If you later want low-risk fixes to go ahead on their own, you can turn that on in your autonomy settings; changes to your URLs or indexing, and new content, still wait for you.
Is it free?
Connecting is free with no card. Search Console reports, page checks and 30-page site audits are free, as often as you like; live market data uses free questions, 5 a month plus a one-time 10 when you connect Search Console. Staging and publishing fixes is part of paid plans, which start with a 14-Day Trial for $1, credited to your first payment.
Fix GitHub Site SEO From Another Agent
The same SEOmatic server and approval rules, from the agent you prefer.
Fix GitHub Site SEO from Claude Code
One command connects your Search Console to the terminal, so Claude Code fixes SEO in the code.
Fix GitHub Site SEO from Claude Cowork
Hand Claude Cowork the SEO grunt work: it pulls your real numbers, writes the report into your files, and stages fixes you approve.
Fix GitHub Site SEO from ChatGPT
ChatGPT SEO on your real Search Console data, with fixes you approve in the same chat.
Fix GitHub Site SEO from Codex
Two commands give Codex your Search Console data, so it fixes SEO where the bug lives: in your code.
Fix GitHub Site SEO from Grok Bot
An always-on SEO teammate: routines that read your Search Console and speak up when something changes.