Skip to content

docs(seo): lead titles and H1s with "<product> MCP server" and CLI keywords in EN, RU and ES - #675

Merged
leemour merged 3 commits into
mainfrom
docs/seo-titles
Nov 17, 2026
Merged

leemour merged 3 commits into
mainfrom
docs/seo-titles

Conversation

@leemour

@leemour leemour commented Nov 17, 2026

Copy link
Copy Markdown
Member

Search engines and AI answer engines read a page's <title>, H1 and description first. Ours hid the phrase people type: tool pages said "Connect Bitrix24 CRM to your AI agent" instead of "Bitrix24 MCP server", subpages put a generic word first with a long dash ("The MCP server — Telegram", "Install — Notion"), and the Notion landing was just "Notion". This PR puts the product and "MCP server" or "CLI" first in EN, RU and ES.

Approach

  • Tool landings (toolTitles in lib/seo-copy.json): the keyword set from the docs-marketing plan for all 11 tools, Notion added. tg, max, wa, zm and mail keep the titles docs(overviews): benefit-first overview pages for tg, max, wa, zm and mail in EN/RU/ES #672 merged.
  • Tool subpages: new pageTitles templates per locale, with per-tool overrides, used by documentationTitle in lib/seo.ts for both the H1 and <title>. For example "Install the Notion CLI and MCP server", "Telegram MCP server setup for Claude Code, Codex and Cursor", "Download and export Telegram chat history". Pages without a template read "Telegram: People", with no long dash.
  • Descriptions: new pageDescriptions (140 to 160 characters, keyword once) for the memo, b24, pbx and gcal overviews and every MCP page. They are checked before the synced frontmatter.
  • Site pages: keyword titles such as "Connect your AI agent to your chats, mail and documents" (was "Start here"). The old short name stays as sidebarTitle, so the menu does not change. The 9 pages that docs:opening now re-checks got their "On this page" lists and wording fixes.
  • Markdown copies (/llms.mdx/...) carry the same title as the HTML page.
  • All 805 page titles stay unique per language. Browser specs follow the new H1s.

Query choices were checked against Google autocomplete in each language: "telegram mcp server", "mcp telegram claude code", "export telegram chat history", "google drive mcp", "notion mcp", "bitrix24 mcp" / "битрикс24 mcp", "obsidian mcp", "exportar chat de telegram".

Examples

Page Before After
en tg/mcp The MCP server — Telegram Telegram MCP server setup for Claude Code, Codex and Cursor
en notion/installation Install — Notion Install the Notion CLI and MCP server
ru b24 Подключите CRM Bitrix24 к ИИ-агенту Битрикс24 MCP-сервер и CLI для CRM
ru tg/search Поиск — Telegram Поиск сообщений и переписки в Telegram
es notion Notion Servidor MCP y CLI de Notion con búsqueda sin conexión
es drive/installation Instalar y conectar — Google Drive Instala la CLI y el servidor MCP de Google Drive

Left out

Page EN RU ES
markdown (#668) Obsidian and Markdown notes MCP server for AI agents MCP-сервер для заметок Obsidian и Markdown Servidor MCP para notas de Obsidian y Markdown
ydisk (#668) Yandex Disk MCP server: search your files with AI MCP-сервер Яндекс Диска: поиск по файлам для ИИ-агента Servidor MCP de Yandex Disk para tu agente de IA
people People in your Telegram and MAX chats Люди в ваших чатах Telegram и MAX Personas en tus chats de Telegram y MAX
tasks Tasks and promises from your chats Задачи и обещания из ваших чатов Tareas y promesas de tus chats
first-tasks First tasks to ask your AI agent Первые задачи для ИИ-агента Primeras tareas para tu agente de IA

people, tasks and first-tasks were left as they are because a retitle makes docs:opening check the whole page, and these need a contents list and wording fixes first.

Checks

Local: pnpm lint, pnpm typecheck, pnpm exec vitest run scripts lib (520 passed), pnpm docs:check, pnpm check:links --source. next build was not run locally (memory limit on this machine). The browser specs did not run locally because the dev server would not start, so CI runs them.

🤖 Generated with Claude Code

leemour and others added 2 commits November 17, 2026 18:08
…n EN, RU and ES

Search and answer engines read the <title>, H1 and description first. Tool titles hid the
main query ("Telegram MCP server"), subpages put a generic word first with a long dash
("The MCP server — Telegram"), and the Notion landing was just "Notion".

- toolTitles: the keyword set from the docs-marketing plan for all 11 tools, Notion added
  (tg, max, wa, zm and mail match the open overviews PR).
- New pageTitles templates in seo-copy.json: product-first titles for install, MCP,
  commands, settings, search, export, browser use and the other shared pages, per locale,
  with per-tool overrides. Remaining subpages read "Telegram: People", no long dash.
- New pageDescriptions: keyword descriptions for the memo, b24, pbx and gcal overviews and
  every MCP page.
- Site pages: keyword titles with the old short name kept as sidebarTitle, so menus do
  not change. Pages docs:opening now checks got their contents lists and wording fixes.
- The Markdown copy for agents carries the same title as the HTML page.
- Browser specs follow the new H1s.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…new H1

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…breadcrumbs, llms.txt titles

- Shorten the memo and pbx landing titles and the MCP template (EN max/mcp drops
  "messenger"), and test that every keyword title plus " · WireCat" stays within 70
  characters, so search results do not cut it.
- Subpage titles without a template name the product on its own (`labels`): RU and ES
  get «Почта: …» and «Correo: …», not "Mail: …". The Memo email guide gets its own title.
- RU Google Calendar titles use one name, "Google Calendar".
- Breadcrumbs and BreadcrumbList show the page's short menu name, not the keyword H1.
- llms.txt lists each page under the same title as the page and its Markdown copy.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour
leemour merged commit 80de933 into main Nov 17, 2026
8 checks passed
@leemour
leemour deleted the docs/seo-titles branch November 17, 2026 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant