chore(seo): retitle Python framework integration guides#568
Merged
Conversation
…keyword targeting Rewrites the H1 + frontmatter title + description on the five Python framework integration how-tos to lead with the category-search terms (budget control, cost enforcement, cost governance) instead of the brand-led "Integrating Cycles with X" pattern. Motivation: the Python adoption side is lagging TypeScript by a wide margin (PyPI flat for 6+ weeks; cycles-client-python at 157 unique cloners vs. cycles-client-typescript at 288). Diagnostic showed the biggest sub-gap is discovery — Cycles doesn't rank for natural Python search queries while named competitors (AgentBudget, AgentGuard, agent-cost-guardrails) do. The brand-led titles were a contributor. Changes: - LangChain: "Integrating Cycles with LangChain" → "LangChain Budget Control via Callback Handlers (Python)" - LangGraph: "Integrating Cycles with LangGraph" → "LangGraph Budget Control: Per-Node Cost Enforcement" - CrewAI: "Integrating Cycles with CrewAI" → "CrewAI Budget Control: Multi-Agent Cost Enforcement" - AutoGen: "Integrating Cycles with AutoGen" → "AutoGen Budget Control: Cost Governance for Microsoft AutoGen" - OpenAI Agents SDK: "Integrating Cycles with OpenAI Agents SDK" → "OpenAI Agents SDK Budget Control (Python)" Inbound anchor references both point at subheadings, not the H1, so no internal-link breakage. URL slugs (filenames) unchanged — existing external links and search-engine indexes preserved. Part of Phase 1 of the Python-gap closing plan. Phase 1 also includes PyPI metadata + GitHub topics updates on cycles-client-python (separate repo, separate PR proposed).
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.
Summary
Phase 1.4 of the Python-gap closing plan. Retitles the five Python framework integration how-tos to lead with category-search terms (budget control, cost enforcement, cost governance) instead of the brand-led "Integrating Cycles with X" pattern.
Why
The Python adoption side is lagging TypeScript materially (PyPI flat for ~6 weeks pre-source-change;
cycles-client-python157 unique cloners vs.cycles-client-typescript288). The diagnostic (traffic signal interpretation memory — internal) found the biggest sub-gap is discovery — Cycles doesn't rank for natural Python search queries while named competitors (AgentBudget, AgentGuard, agent-cost-guardrails) do. Brand-led titles were a contributor.Changes (frontmatter title + H1 + description on each)
integrating-cycles-with-langchain.mdintegrating-cycles-with-langgraph.mdintegrating-cycles-with-crewai.mdintegrating-cycles-with-autogen.mdintegrating-cycles-with-openai-agents.mdWhat this doesn't change
#the-callback-handler-approach,#prerequisites), not the H1 — verified safe.Phase 1 status (rest of the plan)
cycles-client-pythonhas a fullstreaming.pymodule; it's just missing from the README. Follow-up: add a "Streaming" section tocycles-client-pythonREADME.cycles-client-pythonrepo.Test plan
npm run dev, navigate to/how-to/, confirm sidebar labels reflect new titles./how-to/integrating-cycles-with-langchain#the-callback-handler-approach(referenced from langgraph guide) and/how-to/integrating-cycles-with-openai-agents#prerequisites(referenced from openai-agents-sdk-has-guardrails blog post).