Repository navigation
docs(seo): lead titles and H1s with "<product> MCP server" and CLI keywords in EN, RU and ES - #675
Merged
Merged
Conversation
…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>
leemour
force-pushed
the
docs/seo-titles
branch
from
November 17, 2026 17:08
fe3ad75 to
b61d355
Compare
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
toolTitlesinlib/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.pageTitlestemplates per locale, with per-tool overrides, used bydocumentationTitleinlib/seo.tsfor 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.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.sidebarTitle, so the menu does not change. The 9 pages thatdocs:openingnow re-checks got their "On this page" lists and wording fixes./llms.mdx/...) carry the same title as the HTML page.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
tg/mcpnotion/installationb24tg/searchnotiondrive/installationLeft out
homeTitle): unchanged. Proposal: lead with "Local MCP servers for your AI agent" and drop the long dash.markdown(#668)ydisk(#668)peopletasksfirst-taskspeople, tasks and first-tasks were left as they are because a retitle makes
docs:openingcheck 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 buildwas 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