docs(cursor): rename the Cursor pages from Cursor IDE to Cursor AI - #4085
docs(cursor): rename the Cursor pages from Cursor IDE to Cursor AI#4085gkarthi-signoz wants to merge 1 commit into
Conversation
Search demand sits on the AI variant, not the IDE one. Google autocomplete suggests 'cursor ai monitoring' and 'cursor ai telemetry' but not 'cursor ide monitoring' or 'cursor ide observability', and every 'cursor ide' completion is consumer intent (download, pricing, themes, vs vscode). 'Cursor Agent' scored better still on intent but is Cursor's own name for the CLI, which these pages cannot serve, so it would draw traffic that can never convert. Body headings keep 'Cursor IDE', which stays accurate about scope and covers the IDE variant alongside the AI variant in the title.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Claude finished @gkarthi-signoz's task in 1m 2s —— View job Docs PR Review
This is a tightly scoped, well-reasoned SEO rename. The five surfaces (two doc frontmatters, sidebar, two listicles) are updated consistently, the slug/URL is unchanged so no redirect is needed, and a repo-wide search confirms the only remaining FindingsP3 — Title/body brand split reads slightly inconsistent (intentional, non-blocking) Personas & fitTeam leads / platform engineers instrumenting Cursor agent usage. Fit is unchanged — this is metadata only, no content or flow changes. JTBD coverageNo mandatory JTBD checks are affected. Title (~55 chars, keyword-first) and description (~143 chars) both stay within range after the rename. Happy path, steps, validation, and next steps are untouched. Checklist coverage
Open questions / assumptions
Onboarding label: skippedAll five files are |
|
✅ CMS Sync Successful Content has been synced to Strapi CMS with deployment status: 📊 Summary
🔗 RelationsThe following relations were automatically resolved:
📄 Processed DocumentsView 2 document(s)
📋 Listicle Sync
View 2 listicle(s)
|
1 participant
Pull Request
📄 Summary
Renames the two Cursor docs pages from Cursor IDE to Cursor AI in their titles, meta titles, descriptions, and nav labels. Follow-up to #4073, which is merged.
The pages were named "Cursor IDE" to fence the scope, since the Cursor CLI cannot feed this setup. That is accurate but it is not what people search. Checked against Google autocomplete, which orders completions by popularity:
cursor ai monitoringcursor ide monitoringcursor agent monitoringcursor ide observabilitycursor agent observabilitycursor ai telemetry(ranks abovecursor ide telemetry)cursor aiis also the top completion of barecursor. Everycursor idecompletion is consumer intent instead: download, pricing, themes, vs vscode."Cursor Agent" was considered and rejected. It scores best on intent, but it is Cursor's own product name for the CLI (their launch post is titled "Cursor Agent CLI", binary
cursor-agent). These pages cannot serve CLI users, so that title would attract traffic that can never convert.The qualifier does not cost us the bare term.
codex-monitoringcarries "OpenAI" in its title and still ranks far better without it: 16,251 impressions on queries without "openai" against 573 with it, over the last 12 months. So "Cursor AI" still catchescursor monitoringandcursor observability.Body headings deliberately keep "Cursor IDE". That stays accurate about scope, and it covers the IDE variant alongside the AI variant in the title.
Screenshots / Screen Recordings (if applicable)
n/a, frontmatter and nav labels only.
Issues closed by this PR
None.
✅ Change Type
Select all that apply
🧪 Testing Strategy
yarn check:docs-metadata,yarn check:doc-redirects, andyarn check:stale-urlsall pass. All three JSON files re-parse cleanly after the edit.cursor-observabilityslug is unchanged and stays valid, including the hardcoded guide link in feat(cursor): add Cursor IDE dashboard template dashboards#408.clickNamevalues change with the labels, so click events for these two cards split across the old and new names. Four days of data on pages that are barely indexed, so the loss is negligible.