How do I use GitHub Copilot for SEO and to show up in ChatGPT?
Use GitHub Copilot in Agent mode as the hands, not the judge: put your page rules in an .instructions.md file or AGENTS.md, connect an MCP server in .vscode/mcp.json for live data and checks, and confirm each page on the published site before calling it done. Copilot writes pages well; it cannot see whether Google indexed them or ChatGPT read them.
Facts
- MCP servers in Copilot Chat for VS Code need VS Code 1.99 or later and the Agent mode in the chat box. (GitHub Docs: Extending GitHub Copilot Chat with MCP)
- For Copilot Business and Copilot Enterprise, the MCP servers in Copilot policy is disabled by default, and the organization or enterprise decides whether members can use MCP. (GitHub Docs: Extending GitHub Copilot Chat with MCP)
- VS Code reads a project's MCP servers from .vscode/mcp.json under a top-level servers object, as of 2026-10-13. (VS Code docs: Add and manage MCP servers)
- For an http server, VS Code tries HTTP Stream first, falls back to SSE, and opens a browser window to authorize OAuth on the first connection. (VS Code docs: MCP configuration reference)
- VS Code applies a *.instructions.md file in .github/instructions to the files that match its applyTo glob, as of 2026-10-13. (VS Code docs: Use custom instructions)
Can GitHub Copilot do SEO by itself?
No, Copilot has no SEO mode; in Agent mode it does SEO through the instructions you give it and the tools you connect. That is enough to write correct pages, but not to know whether they were indexed, read by AI crawlers or visited.
Where do I put SEO rules for Copilot?
Put them in an .instructions.md file in .github/instructions with an applyTo glob for your page files, so they load when Copilot works on pages. Use .github/copilot-instructions.md for project-wide guidance, or AGENTS.md if other coding agents share the repository:
--- name: 'SEO for content pages' description: 'Use when creating or editing content pages.' applyTo: 'app/**/page.tsx' --- - One H1 per page, phrased as the question the page answers - Unique <title> and meta description; self-referencing canonical - Content rendered on the server, not only after JavaScript runs - JSON-LD only for what the page visibly says - Add every new page to the sitemap - Never change the home page or pages that already work
How do I connect an MCP server to Copilot in VS Code?
Run MCP: Add Server from the Command Palette, or add the server to .vscode/mcp.json with type http and its url, then switch the chat to Agent mode. At work, check first that your organization enabled the MCP servers in Copilot policy:
// .vscode/mcp.json (this project)
{
"servers": {
"<name>": {
"type": "http",
"url": "<server-url>"
}
}
}What can Copilot not check by itself?
Copilot sees your code, not the live site. These checks need the published page or outside data:
| Question | Where the answer is |
|---|---|
| Does the page render with content without JavaScript? | Fetch the live URL, for example with curl |
| Are title, canonical and JSON-LD right? | The live HTML, not the source file |
| Did Google index it? | Search Console |
| Did AI crawlers read it, did ChatGPT send visits? | Server logs or an analytics tool that splits AI traffic |
Step by step
- Write the rules. Create an .instructions.md in .github/instructions with an applyTo glob for your pages.
- Connect the tools. Add the MCP server to .vscode/mcp.json and authorize it in the browser.
- Switch to Agent mode. Pick Agent in the Copilot Chat box so it can use the server's tools.
- Ask for one batch of pages. Ask for a few new pages, each answering one question, without touching existing pages.
- Check live. Deploy, open each published URL, check content, title and canonical, then watch indexing and AI visits.
Common mistakes
- Copying a config with mcpServers into .vscode/mcp.json, where VS Code expects servers.
- Expecting MCP tools outside Agent mode, or at work before the organization enables the policy.
- Accepting Copilot's summary that pages are live without opening the URLs.
- Letting it rewrite the home page or pages that already bring traffic.
How easyIndex solves it
easyIndex connects to Copilot as a remote MCP server, https://easyindex.app/api/mcp, and you authorize it in the browser. It is more than a server to call: the method comes inside it, with step-by-step instructions and the current rules, so there is nothing to install or keep updated. Copilot makes every change, and easyIndex never touches your site or repository.
Each page is audited when submitted and checked on the live site after publishing, and a step completes only on evidence easyIndex checks, not on Copilot's report. The dashboard then shows AI-assistant visitors per page, which pages AI crawlers read and Search Console data, for US$ 30 per website a month after a 7-day free trial.
Frequently asked questions
Is this the same as getting recommended by Microsoft Copilot?
No. GitHub Copilot is a coding agent that edits your site; whether Microsoft Copilot cites your site is a separate question with its own guide.
Can I use the same rules in Copilot and Claude Code?
Yes, through AGENTS.md at the repository root; VS Code reads it when the chat.useAgentsMdFile setting is on.
Why does Copilot not show my MCP server's tools?
Check that the chat is in Agent mode, that VS Code is 1.99 or later and, on Business or Enterprise, that the MCP policy is enabled.
Will Copilot get my site into ChatGPT?
No tool can promise that. Copilot can build clear, crawlable pages; whether ChatGPT cites them is decided by ChatGPT.
Continue reading
- How do I get my company recommended by Microsoft Copilot?
- What SEO rules should I put in AGENTS.md or CLAUDE.md?
- What should a GEO MCP server for my coding agent do?
- How do I use Cursor for SEO and to show up in ChatGPT?
- How does easyIndex work, what do I need, and how long until results?
- How much does easyIndex cost?
Last verified on .