Add SEO meta titles and descriptions for docs pages

oshankkkk · oshankkkk · commit 248fee830221 · 2026-04-27T23:15:15.000+05:30
diff --git a/documentation/docs/components/amp-instrumentation.mdx b/documentation/docs/components/amp-instrumentation.mdx
@@ -1,3 +1,8 @@
+---
+title: WSO2 Agent Manager Instrumentation | OpenTelemetry for Python Agents
+description: Enable zero-code OpenTelemetry tracing for Python agents using amp-instrumentation in WSO2 Agent Manager. Capture LLM calls, MCP requests, and more.
+---
+
 # WSO2 Agent Manager Instrumentation
 
 Zero-code OpenTelemetry instrumentation for Python agents using the Traceloop SDK, with trace visibility in the WSO2 Agent Manager.
@@ -49,4 +54,4 @@ amp-instrument poetry run python script.py
 amp-instrument uv run python script.py
 ```
 
-That's it! Your application is now instrumented and sending traces to the WSO2 Agent Manager.
+That's it! Your application is now instrumented and sending traces to the WSO2 Agent Manager.
diff --git a/documentation/docs/concepts/evaluation.mdx b/documentation/docs/concepts/evaluation.mdx
@@ -1,5 +1,7 @@
 ---
 sidebar_position: 2
+title: AI Agent Evaluation in WSO2 Agent Manager
+description: Learn how WSO2 Agent Manager evaluates AI agent quality with trace-based scoring, built-in evaluators, and continuous monitoring.
 ---
 
 import Tabs from '@theme/Tabs';
@@ -380,4 +382,3 @@ To use LLM-as-Judge evaluators, you need to provide an API key for at least one
 | **Mistral AI** | `MISTRAL_API_KEY` |
 
 Credentials are stored securely with the monitor and used only when the evaluation job runs. You only need to add each provider once per monitor. All evaluators using that provider share the same credentials.
-
diff --git a/documentation/docs/concepts/observability.mdx b/documentation/docs/concepts/observability.mdx
@@ -1,5 +1,7 @@
 ---
 sidebar_position: 1
+title: Observability for AI Agents in WSO2 Agent Manager
+description: Understand how WSO2 Agent Manager captures traces, metrics, and logs for deployed and externally hosted AI agents.
 ---
 
 # Observability
@@ -80,4 +82,4 @@ No changes to your agent code are required. The same Traceloop-based auto-instru
 
 Once traces start flowing in, you can explore them in the AMP Console under your agent's sidebar:
 
-- **OBSERVABILITY → Traces** — search and inspect individual traces by time range or correlation ID; expand a trace to see LLM spans, tool spans, and agent reasoning steps
+- **OBSERVABILITY → Traces** — search and inspect individual traces by time range or correlation ID; expand a trace to see LLM spans, tool spans, and agent reasoning steps
diff --git a/documentation/docs/contributing/contributing.mdx b/documentation/docs/contributing/contributing.mdx
@@ -1,3 +1,8 @@
+---
+title: WSO2 Agent Manager Contributing Guidelines
+description: Guidelines for using GitHub Discussions and Issues to collaborate on WSO2 Agent Manager.
+---
+
 # Contributing Guidelines
 
 This document establishes guidelines for using GitHub Discussions and Issues for technical conversations about the Agent Manager.
@@ -84,4 +89,4 @@ Once a design proposal is approved:
 1. Create GitHub Issues for implementation tasks
 2. Link issues back to the design proposal discussion
 3. Assign issues to appropriate milestones
-4. Track progress through milestone completion
+4. Track progress through milestone completion
diff --git a/documentation/docs/getting-started/on-k3d.mdx b/documentation/docs/getting-started/on-k3d.mdx
@@ -1,5 +1,7 @@
 ---
 sidebar_position: 2
+title: Install the Agent Manager on a local Kubernetes cluster 
+description: Install WSO2 Agent Manager on a local single-node k3d Kubernetes cluster for development and exploration.
 ---
 
 import AmpInstallation from './_partials/_amp-installation.mdx';
diff --git a/documentation/docs/getting-started/on-your-environment.mdx b/documentation/docs/getting-started/on-your-environment.mdx
@@ -1,5 +1,7 @@
 ---
 sidebar_position: 3
+title: Install the Agent Manager on an existing Kubernetes cluster
+description: Install WSO2 Agent Manager on an existing Kubernetes cluster such as EKS, GKE, AKS, or any distribution with LoadBalancer support.
 ---
 
 import AmpInstallation from './_partials/_amp-installation.mdx';
diff --git a/documentation/docs/getting-started/quick-start.mdx b/documentation/docs/getting-started/quick-start.mdx
@@ -1,5 +1,7 @@
 ---
 sidebar_position: 1
+title: WSO2 Agent Manager Quick Start Guide
+description: Install WSO2 Agent Manager locally with a single command using the dev container quick start.
 ---
 # Quick Start Guide
 
diff --git a/documentation/docs/overview/what-is-amp.mdx b/documentation/docs/overview/what-is-amp.mdx
@@ -1,5 +1,7 @@
 ---
 sidebar_position: 1
+title: WSO2 Agent Manager
+description: WSO2 Agent Manager is an open control plane for deploying, managing, observing, and evaluating AI agents at scale.
 ---
 # WSO2 Agent Manager
 
diff --git a/documentation/docs/tutorials/configure-agent-llm-configuration.mdx b/documentation/docs/tutorials/configure-agent-llm-configuration.mdx
@@ -1,5 +1,7 @@
 ---
 sidebar_position: 6
+title: Configure LLM Providers for an Agent in WSO2 Agent Manager
+description: Attach organization-level LLM providers to platform-hosted or external agents and use the generated connection details in code.
 ---
 
 # Configure LLM Providers for an Agent
@@ -246,4 +248,4 @@ Multiple providers can be attached to a single agent, allowing the agent code to
 - For external agents, the Endpoint URL routes traffic through the AI Gateway, enabling centralized rate limiting, access control, and guardrails configured at the org level.
 - The external agent API Key shown after saving is a **one-time display** — it cannot be retrieved again. If lost, delete the LLM provider binding and re-add it to generate a new key.
 - The **Setup Agent** instrumentation step is for observability (traces) only and is independent of LLM configuration.
-- Guardrails added at the agent-LLM binding level are applied **in addition to** any guardrails configured on the provider itself.
+- Guardrails added at the agent-LLM binding level are applied **in addition to** any guardrails configured on the provider itself.
diff --git a/documentation/docs/tutorials/custom-evaluators.mdx b/documentation/docs/tutorials/custom-evaluators.mdx
@@ -1,5 +1,7 @@
 ---
 sidebar_position: 3
+title: Custom Evaluators in WSO2 Agent Manager 
+description: Create custom code-based and LLM-judge evaluators in the AMP Console for domain-specific quality checks.
 ---
 
 import Tabs from '@theme/Tabs';
diff --git a/documentation/docs/tutorials/evaluation-monitors.mdx b/documentation/docs/tutorials/evaluation-monitors.mdx
@@ -1,5 +1,7 @@
 ---
 sidebar_position: 2
+title: Evaluation Monitors in WSO2 Agent Manager
+description: Create, configure, and manage evaluation monitors in the AMP Console to score agent traces over time.
 ---
 
 # Evaluation Monitors
diff --git a/documentation/docs/tutorials/observe-first-agent.mdx b/documentation/docs/tutorials/observe-first-agent.mdx
@@ -1,5 +1,7 @@
 ---
 sidebar_position: 1
+title: Observe Your First Agent in WSO2 Agent Manager
+description: Register an externally hosted agent, enable zero-code instrumentation, and view traces in the AMP Console.
 ---
 
 import Tabs from '@theme/Tabs';
diff --git a/documentation/docs/tutorials/register-ai-gateway.mdx b/documentation/docs/tutorials/register-ai-gateway.mdx
@@ -1,5 +1,7 @@
 ---
 sidebar_position: 4
+title: Register an AI Gateway in WSO2 Agent Manager
+description: Register and configure a WSO2 AI Gateway in WSO2 Agent Manager to route LLM traffic through a controlled proxy.
 ---
 
 # Register an AI Gateway
@@ -132,4 +134,4 @@ Once running, the gateway appears in the **AI Gateways** list with status **Acti
 - A **Default AI Gateway** is pre-provisioned in new organizations.
 - Each gateway can serve multiple environments (e.g., `Default`, `Production`).
 - The registration token (generated via **Reconfigure**) is environment-specific and must be kept secret.
-- Marking a gateway as **Critical production gateway** helps signal its importance for operational monitoring.
+- Marking a gateway as **Critical production gateway** helps signal its importance for operational monitoring.
diff --git a/documentation/docs/tutorials/register-llm-service-provider.mdx b/documentation/docs/tutorials/register-llm-service-provider.mdx
@@ -1,5 +1,7 @@
 ---
 sidebar_position: 5
+title: Register an LLM Service Provider in WSO2 Agent Manager
+description: Register upstream LLM providers such as OpenAI, Anthropic, and Bedrock and expose them through an AI Gateway.
 ---
 
 # Register an LLM Service Provider
