AEM Cloud Service Managed CDN (Fastly)
This configuration routes agentic traffic (requests from AI bots and LLM user agents) to the Edge Optimize backend service (live.edgeoptimize.net). Human visitors and SEO bots continue to be served from your origin as usual. To test the configuration, after the setup is complete, look for the header x-edgeoptimize-request-id in the response.
Prerequisites
To start routing agentic traffic to Edge Optimize:
-
In LLM Optimizer, open Customer configuration and select the CDN configuration tab.
-
Locate the Deploy optimizations to AI agents section. Tick the Enable optimization engine checkbox.
-
In the confirmation dialog, select Enable. The Adobe team will handle the routing configuration on your behalf.
Once the routing is configured and active, the status updates to Completed with a green checkmark confirming that routing is enabled. No further action is required on your end.
Additionally, if you require any help with the above steps, reach out to your Adobe account team or llmo-at-edge@adobe.com.
Self-service routing via Cloud Manager Pipeline
If you prefer to configure the routing yourself through the Cloud Manager Pipeline, follow the steps below. The routing configuration is done by using an originSelector CDN rule. The prerequisites are as follows:
- Decide the domain to be routed.
- Decide the paths to be routed.
- Decide the user agents to be routed (recommended regex).
In order to deploy the rule, you need to:
- Create a configuration pipeline.
- Commit the
cdn.yamlconfiguration file in your repository. - Run the configuration pipeline.
kind: "CDN"
version: "1"
data:
# Origin selectors to route to Edge Optimize backend
originSelectors:
rules:
- name: route-to-edge-optimize-backend
when:
allOf:
- reqHeader: x-edgeoptimize-request
exists: false # avoid loops when requests comes from Edge Optimize
- reqHeader: user-agent
matches: "(?i)(AdobeEdgeOptimize-AI|ChatGPT-User|GPTBot|OAI-SearchBot|PerplexityBot|Perplexity-User)" # routed user agents
- reqProperty: domain
equals: "example.com" # routed domain
- reqProperty: originalPath
matches: '(/[^./]+|\.html|/)
**Verify the setup**
After completing the setup, verify that bot traffic is being routed to Edge Optimize and that human traffic remains unaffected.
**1. Test bot traffic (should be optimized)**
Simulate an AI bot request using an agentic user-agent:
curl -svo /dev/null https://www.example.com/page.html
--header “user-agent: chatgpt-user”
A successful response includes the `x-edgeoptimize-request-id` header, confirming that the request was routed through Edge Optimize:
< HTTP/2 200
< x-edgeoptimize-request-id: 50fce12d-0519-4fc6-af78-d928785c1b85
**2. Test human traffic (should NOT be affected)**
Simulate a regular human browser request:
curl -svo /dev/null https://www.example.com/page.html
--header “user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36”
The response should **not** contain the `x-edgeoptimize-request-id` header. The page content and response time should remain identical to before enabling Optimize at Edge.
**3. How to differentiate between the two scenarios**
| Header | Bot traffic (optimized) | Human traffic (unaffected) |
|---|---|---|
| `x-edgeoptimize-request-id` | Present — contains a unique request ID | Absent |
| `x-edgeoptimize-fo` | Present only if failover occurred (value: `1`) | Absent |
**4. Check routing status in LLM Optimizer**
You can also confirm routing in the LLM Optimizer UI. Open **Customer configuration** and select the **CDN configuration** tab. When routing is active, the **Deploy optimizations to AI agents** section shows **Completed**.
To learn more about Optimize at Edge, including available opportunities, auto-optimization workflows, and FAQs, return to the [Optimize at Edge overview](/help/dashboards/optimize-at-edge/overview.md).
# routed extensions, with .html extension or without extension
- anyOf:
- { reqProperty: originalPath, in: [ "/page.html" ] } # routed pages, exact path matching
- { reqProperty: originalPath, like: "/dir/*" } # routed pages, wildcard path matching
action:
type: selectOrigin
originName: edge-optimize-backend
origins:
- name: edge-optimize-backend
domain: "live.edgeoptimize.net"
Verify the setup
After completing the setup, verify that bot traffic is being routed to Edge Optimize and that human traffic remains unaffected.
1. Test bot traffic (should be optimized)
Simulate an AI bot request using an agentic user-agent:
CODE_BLOCK_PLACEHOLDER_1
A successful response includes the x-edgeoptimize-request-id header, confirming that the request was routed through Edge Optimize:
CODE_BLOCK_PLACEHOLDER_2
2. Test human traffic (should NOT be affected)
Simulate a regular human browser request:
CODE_BLOCK_PLACEHOLDER_3
The response should not contain the x-edgeoptimize-request-id header. The page content and response time should remain identical to before enabling Optimize at Edge.
3. How to differentiate between the two scenarios
x-edgeoptimize-request-idx-edgeoptimize-fo1)4. Check routing status in LLM Optimizer
You can also confirm routing in the LLM Optimizer UI. Open Customer configuration and select the CDN configuration tab. When routing is active, the Deploy optimizations to AI agents section shows Completed.
To learn more about Optimize at Edge, including available opportunities, auto-optimization workflows, and FAQs, return to the Optimize at Edge overview.