diff --git a/public/__redirects b/public/__redirects index 879c686cd5cd9e5..77b17e58a662aec 100644 --- a/public/__redirects +++ b/public/__redirects @@ -653,8 +653,8 @@ /fundamentals/reference/the-internet/ /fundamentals/concepts/the-internet/ 301 /fundamentals/reference/http-request-headers/ /fundamentals/reference/http-headers/ 301 /fundamentals/security/browser-integrity-check/ /waf/tools/browser-integrity-check/ 301 -/fundamentals/signed-exchanges/ /speed/optimization/other/signed-exchanges/ 301 -/fundamentals/signed-exchanges/amp-real-ulr/reference/ /speed/optimization/other/amp-real-url/reference/ 301 +/fundamentals/signed-exchanges/ /speed/optimization/ 301 +/fundamentals/signed-exchanges/amp-real-ulr/reference/ /speed/optimization/ 301 /fundamentals/speed/aim/ /speed/aim/ 301 /fundamentals/speed/optimization/ /speed/optimization/ 301 /fundamentals/speed/prefetch-urls/ /speed/optimization/content/prefetch-urls/ 301 @@ -1341,19 +1341,19 @@ /fundamentals/network/0-rtt-connection-resumption/ /speed/optimization/protocol/0-rtt-connection-resumption/ 301 /support/speed/essentials/will-cloudflares-image-optimization-features-help-if-im-already-optimizing-images/ /speed/optimization/images/troubleshooting/multiple-optimizations/ 301 /support/speed/optimization-delivery/configuring-cloudflare-mirage/ /speed/optimization/images/mirage/ 301 -/support/speed/optimization-mobile/understanding-cloudflare-mobile-redirect/ /speed/optimization/other/mobile-redirect/ 301 +/support/speed/optimization-mobile/understanding-cloudflare-mobile-redirect/ /rules/url-forwarding/examples/perform-mobile-redirects/ 301 /support/speed/optimization-file-size/using-cloudflare-auto-minify/ /speed/optimization/content/ 301 /support/speed/optimization-file-size/what-will-cloudflare-compress/ /speed/optimization/content/compression/ 301 /speed/optimization/content/brotli/ /speed/optimization/content/compression/ 301 /speed/optimization/content/brotli/enable/ /speed/optimization/content/compression/ 301 /speed/optimization/content/brotli/content-compression/ /speed/optimization/content/compression/ 301 /support/speed/optimization-file-size/why-isnt-auto-minify-working/ /speed/optimization/content/troubleshooting/ 301 -/support/speed/optimization-mobile/why-is-the-mobile-redirect-i-set-up-through-cloudflare-redirecting-my-static-assets/ /speed/optimization/other/troubleshooting/mobile-redirect-affect-static-assets/ 301 -/speed/optimization/other/amp-real-ulr/ /speed/optimization/other/amp-real-url/ 301 -/speed/optimization/other/amp-real-ulr/reference/ /speed/optimization/other/amp-real-url/reference/ 301 +/support/speed/optimization-mobile/why-is-the-mobile-redirect-i-set-up-through-cloudflare-redirecting-my-static-assets/ /rules/url-forwarding/examples/perform-mobile-redirects/ 301 +/speed/optimization/other/amp-real-ulr/ /speed/optimization/ 301 +/speed/optimization/other/amp-real-ulr/reference/ /speed/optimization/ 301 /speed/optimization/other/mobile-redirect/ /rules/url-forwarding/examples/perform-mobile-redirects/ 301 -/speed/optimization/other/troubleshooting/mobile-redirect-affect-static-assets/ /speed/optimization/other/ 301 -/speed/optimization/other/troubleshooting/ /speed/optimization/other/ 301 +/speed/optimization/other/troubleshooting/mobile-redirect-affect-static-assets/ /speed/optimization/ 301 +/speed/optimization/other/troubleshooting/ /speed/optimization/ 301 /speed/optimization/content/auto-minify/ /speed/optimization/content/ 301 /speed/optimization/content/troubleshooting/auto-minify-not-working/ /speed/optimization/content/troubleshooting/ 301 /speed/optimization/content/speculation/ /speed/optimization/content/speed-brain/ 301 @@ -2323,9 +2323,9 @@ /fundamentals/get-started/setup/troubleshooting/* /fundamentals/setup/account-setup/add-site/ 301 /fundamentals/get-started/basic-tasks/account-security/* /fundamentals/account-and-billing/account-security/:splat 301 /fundamentals/get-started/setup/account-setup/* /fundamentals/account-and-billing/account-setup/:splat 301 -/fundamentals/speed/amp-real-ulr/* /speed/optimization/other/amp-real-ulr/:splat 301 +/fundamentals/speed/amp-real-ulr/* /speed/optimization/:splat 301 /fundamentals/speed/rocket-loader/* /speed/optimization/content/rocket-loader/:splat 301 -/fundamentals/speed/signed-exchanges/* /speed/optimization/other/signed-exchanges/:splat 301 +/fundamentals/speed/signed-exchanges/* /speed/optimization/:splat 301 /fundamentals/speed/speed-test/* /speed/observatory/:splat 301 /speed/speed-test/* /speed/observatory/:splat 301 /http-applications/* /version-management/:splat 301 @@ -2345,6 +2345,7 @@ /fundamentals/setup/manage-members/* /fundamentals/manage-members/:splat 301 /logs/get-started/enable-destinations/* /logs/logpush/logpush-job/enable-destinations/:splat 301 /logs/reference/log-fields/* /logs/logpush/logpush-job/datasets/:splat 301 +/speed/optimization/other/* /speed/optimization/ 301 # AI Crawl Control /ai-audit/* /ai-crawl-control/:splat 301 diff --git a/src/content/docs/fundamentals/api/get-started/account-owned-tokens.mdx b/src/content/docs/fundamentals/api/get-started/account-owned-tokens.mdx index 90f0ca2f9ae01d9..e717f8b306bf986 100644 --- a/src/content/docs/fundamentals/api/get-started/account-owned-tokens.mdx +++ b/src/content/docs/fundamentals/api/get-started/account-owned-tokens.mdx @@ -36,7 +36,6 @@ Account API tokens are generally available for all accounts. Some services may n | Account Analytics | ✅ | | Account Management | ✅ | | AI Gateway | ✅ | -| AMP | ✅ | | API Shield | ✅ | | Argo | ✅ | | Billing | ✅ | diff --git a/src/content/docs/fundamentals/performance/improve-seo.mdx b/src/content/docs/fundamentals/performance/improve-seo.mdx index 30c8e4dae0cd8ba..342f2bea76dd8b6 100644 --- a/src/content/docs/fundamentals/performance/improve-seo.mdx +++ b/src/content/docs/fundamentals/performance/improve-seo.mdx @@ -39,12 +39,6 @@ To make sure your domain is accessible over HTTPS: With [Crawler Hints](/cache/advanced-configuration/crawler-hints/), search engines and other bot-powered experiences have the freshest version of your content, translating into happier users and ultimately influencing search rankings. -### Enable Automatic Signed Exchanges (SXGs) - -Automatic Signed Exchanges (SXGs) is an open web platform specification developed by Google to verify a cached version of a website. - -When you enable [signed exchanges](/speed/optimization/other/signed-exchanges/), your site will load faster when linked to from a site supporting SXG. Since many search engines use page load times to determine search result ranking, SXGs can provide an SEO boost. - ## Troubleshooting Depending on your domain's security settings, you might accidentally block search engine crawlers. diff --git a/src/content/docs/rules/configuration-rules/settings.mdx b/src/content/docs/rules/configuration-rules/settings.mdx index b2fa611430796de..1dda905af487084 100644 --- a/src/content/docs/rules/configuration-rules/settings.mdx +++ b/src/content/docs/rules/configuration-rules/settings.mdx @@ -295,28 +295,4 @@ API values: `"off"`, `"flexible"`, `"full"`, `"strict"`, `"origin_pull"`. - - -## SXG - -[Signed Exchanges (SXG)](/speed/optimization/other/signed-exchanges/) is an open standard that makes it possible to cryptographically authenticate the origin of a resource independently of how it is delivered. - -Use this setting to turn on or off signed exchanges for matching requests. - -
- -API configuration property name: `"sxg"` (boolean). - -```json title="API configuration example" -"action_parameters": { - "sxg": false -} -``` - - - -
- -:::caution[Deprecation notice] -Signed exchanges is being deprecated and will be removed on October 20, 2025. -::: + \ No newline at end of file diff --git a/src/content/docs/speed/optimization/other/amp-real-url/enable-amp-real-url.mdx b/src/content/docs/speed/optimization/other/amp-real-url/enable-amp-real-url.mdx deleted file mode 100644 index 08d5f9df2597f3d..000000000000000 --- a/src/content/docs/speed/optimization/other/amp-real-url/enable-amp-real-url.mdx +++ /dev/null @@ -1,32 +0,0 @@ ---- -pcx_content_type: how-to -title: Enable AMP Real URL -description: Learn how to enable AMP Real URL in Cloudflare. -sidebar: - order: 1 - ---- - -import { DashButton } from "~/components" - -## Requirements - -AMP Real URL is available for all plans. However, refer to the following requirements before enabling this feature: - -* AMP Real URL relies on signed exchanges so all [requirements for signed exchanges must be met](/speed/optimization/other/signed-exchanges/enable-signed-exchange/). -* The origin server [must support AMP responses](https://amp.dev/about/how-amp-works/). - -## Enable AMP Real URL - -If your account satisfies the requirements to enable AMP Real URL: - -1. In the Cloudflare dashboard, go to the **Speed** > **Settings** page. - - - -2. Go to **Other**. -3. Scroll to **AMP Real URL** and toggle the button to enable it. - -## Limitations - -Since AMP Real URL responses are packaged in a signed exchange (SXG), the [limitations for SXGs apply](/speed/optimization/other/signed-exchanges/signed-exchanges-caveats/). diff --git a/src/content/docs/speed/optimization/other/amp-real-url/index.mdx b/src/content/docs/speed/optimization/other/amp-real-url/index.mdx deleted file mode 100644 index 681a8b371d017ae..000000000000000 --- a/src/content/docs/speed/optimization/other/amp-real-url/index.mdx +++ /dev/null @@ -1,30 +0,0 @@ ---- -pcx_content_type: reference -title: AMP Real URL -sidebar: - order: 3 - ---- - -import { FeatureTable } from "~/components" - -:::caution[Deprecation notice] -AMP Real URL is being deprecated and will be removed on October 20, 2025. -::: - -Cloudflare AMP Real URL leverages signed exchanges to authenticate content when served from Google’s AMP cache. When a supported crawler is detected, AMP Real URL will create a signed exchange for content that is requested from your domain. When using a supported Chromium browser, the page is validated using a signed exchange and is displayed on the user’s device with the original URL of your site. - -## Difference between AMP Real URL and AMP - -Without AMP Real URL, clicking on a search result for an AMP page takes visitors to a cached page served from `google.com/amp/`. AMP Real URL allows mobile browsers to show the actual URL of your website while still serving the content from Google’s AMP cache. This is accomplished through signed exchanges. AMP Real URL only works on pages that are compatible with the AMP specification, and only applies to visitors coming from Chrome on Android at this time. - -Showing the actual URL to your website's visitors offers several advantages: - -* **Brand fidelity**: Visitors to your site see your brand, not Google’s, at the top of all your pages. -* **More accurate analytics**: Keeping AMP and non-AMP content in the same domain facilitates more accurate analytics attribution. -* **Reduced bounce rates**: Showing your actual URL may encourage users to remain on your site, instead of returning to the search results page. -* **Security**: AMP Real URL uses signed exchanges to sign your AMP pages with a publicly verifiable certificate, ensuring no one can add, remove, or modify your content. - -## Availability - - diff --git a/src/content/docs/speed/optimization/other/amp-real-url/reference.mdx b/src/content/docs/speed/optimization/other/amp-real-url/reference.mdx deleted file mode 100644 index 933d2fc29e85e91..000000000000000 --- a/src/content/docs/speed/optimization/other/amp-real-url/reference.mdx +++ /dev/null @@ -1,18 +0,0 @@ ---- -pcx_content_type: reference -title: Reference -sidebar: - order: 2 -head: - - tag: title - content: Reference - Speed optimizations - ---- - -## Verify that AMP Real URL is working - -After the feature is enabled, it takes Google AMP Cache about a week to detect and serve the new URL. After this period of time, visit your AMP pages from Google search results on Chrome for Android, and you should be able to see your actual URL. You can also go to `https:///cdn-fpw/sxg/cert.pem.msg` to verify that the feature is working. If the page does not return a `404` error and instead prompts you to download a certificate, AMP Real URL is working. - -## Search Console errors - -Even when the Search Console (AMP Pages) is returning a `The dates for the signed exchange are invalid` error message, Google can still parse the signed exchange and treat it like regular HTML. In the case of an AMP page, Google should fall back to treat it like it would treat a regular AMP page. This should not be a problem. diff --git a/src/content/docs/speed/optimization/other/index.mdx b/src/content/docs/speed/optimization/other/index.mdx deleted file mode 100644 index 97f6c87047968a4..000000000000000 --- a/src/content/docs/speed/optimization/other/index.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -pcx_content_type: navigation -title: Other optimizations -sidebar: - order: 5 - group: - hideIndex: true - ---- - -import { DirectoryListing } from "~/components" - - diff --git a/src/content/docs/speed/optimization/other/signed-exchanges/enable-signed-exchange.mdx b/src/content/docs/speed/optimization/other/signed-exchanges/enable-signed-exchange.mdx deleted file mode 100644 index b3ceb98e77ad1e1..000000000000000 --- a/src/content/docs/speed/optimization/other/signed-exchanges/enable-signed-exchange.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -pcx_content_type: reference -title: Enable SXGs -sidebar: - order: 2 -head: - - tag: title - content: Enable Automatic Signed Exchange -description: Learn how to enable Cloudflare Automatic Signed Exchange (SXG) for improved content delivery. - ---- - -import { Render, DashButton } from "~/components" - -## Requirements - -Before enabling Cloudflare Automatic Signed Exchange, refer to the following requirements: - -* Read the [SXGs caveats](/speed/optimization/other/signed-exchanges/signed-exchanges-caveats/) to check requirements regarding request and response headers. -* SXGs are available for zones with a Pro or higher plan. SXGs are also available for zones on a Free plan with an APO subscription. -* SXGs only work with zones that have their nameservers managed by Cloudflare. Refer to [Change your nameservers](/dns/zone-setups/full-setup/setup/) to learn how to change your domain nameservers to Cloudflare. You will also have to confirm that Cloudflare is [proxying your traffic](/dns/proxy-status/). -* Zone certificates need to be managed by Cloudflare. - -:::note - -For SXGs to be enabled, a CAA record (Certification Authority Authorization) is required to allowlist the CA (Certificate Authority) permitted to issue Certificates for signing the Signed Exchange. Cloudflare will automatically add the corresponding CAA records in DNS on behalf of users after they enable SXGs. This is to ensure that SSL certificate issuance is not blocked. If you would like to obtain SSL certificates that are issued by other CAs, make sure that you manually add the required CAA records after enabling SXGs. -::: - -* Content needs to be cached for 120 seconds or longer, as Google checks this setting to generate an SXG. To ensure that content is cached for 120 seconds or more, go to the [Cloudflare dashboard](https://dash.cloudflare.com/) > select your account and domain > **Caching** > **Configuration** > **Browser Cache TTL** and check the period of time Cloudflare instructs a browser to cache files. - -## Enable SXGs - -If your account satisfies all the requirements, follow the steps below to enable SXGs. Be aware that, currently, signed exchanges are only used on Chromium browsers on Android and desktop. - -1. In the Cloudflare dashboard, go to the **Speed** > **Settings** page. - - - -2. Go to **Other**. -3. Scroll to **Automatic Signed Exchanges (SXGs)** and enable it. - - diff --git a/src/content/docs/speed/optimization/other/signed-exchanges/index.mdx b/src/content/docs/speed/optimization/other/signed-exchanges/index.mdx deleted file mode 100644 index 500111fe405a98d..000000000000000 --- a/src/content/docs/speed/optimization/other/signed-exchanges/index.mdx +++ /dev/null @@ -1,26 +0,0 @@ ---- -pcx_content_type: reference -title: Signed exchanges -sidebar: - order: 2 -head: - - tag: title - content: Signed exchanges (SXGs) - ---- - -import { FeatureTable } from "~/components" - -:::caution[Deprecation notice] -Signed exchanges is being deprecated and will be removed on October 20, 2025. -::: - -Signed exchanges (SXG) is an open standard that makes it possible to cryptographically authenticate the origin of a resource independently of how it is delivered. This authentication allows for a variety of use cases. For example, with SXGs, a search engine can download signed exchanges while users are navigating their search pages. Thus, when a user selects a link to a website, the search engine can serve a cached version of that webpage instead of fetching content from the origin server, improving performance. - -This performance improvement also has consequences for SEO. SXGs improve [Core Web Vitals](/web-analytics/data-metrics/core-web-vitals/), such as the Largest Contentful Paint (LCP). Cloudflare found that SXGs improve LCP for 85% of the sites tested and time to first byte (TTFB) for 98% of websites. - -For more information about signed exchanges, [refer to our blog post](https://blog.cloudflare.com/automatic-signed-exchanges/). - -## Availability - - diff --git a/src/content/docs/speed/optimization/other/signed-exchanges/reference.mdx b/src/content/docs/speed/optimization/other/signed-exchanges/reference.mdx deleted file mode 100644 index de8be02af6df538..000000000000000 --- a/src/content/docs/speed/optimization/other/signed-exchanges/reference.mdx +++ /dev/null @@ -1,35 +0,0 @@ ---- -pcx_content_type: reference -title: Reference -sidebar: - order: 4 -head: - - tag: title - content: Reference - Signed exchanges ---- - -## Verify that signed exchanges are working - -Make a request with the signed exchange request header: - -1. Open a terminal and run the following command, replacing `https://example.com` with your domain: - -```sh -curl -svo /dev/null https://example.com -H "Accept: application/signed-exchange;v=b3" -``` - -2. Verify that the `Content-Type` in the response headers is `application/signed-exchange;v=b3` rather than `text/html`. - -## Certificate authority used with SXGs - -Cloudflare uses [Google for SXGs' certificate issuance](https://web.dev/signed-exchanges/#certificates). Once SXGs is enabled, Cloudflare automatically adds the Certification Authority Authorization records on behalf of the zones. Refer to the following example below: - -```bash -dig example.com caa -``` - -```bash output -;; ANSWER SECTION: -example.com. 3600 IN CAA 0 issue "pki.goog; cansignhttpexchanges=yes" -example.com. 3600 IN CAA 0 issuewild "pki.goog; cansignhttpexchanges=yes" -``` diff --git a/src/content/docs/speed/optimization/other/signed-exchanges/signed-exchanges-caveats.mdx b/src/content/docs/speed/optimization/other/signed-exchanges/signed-exchanges-caveats.mdx deleted file mode 100644 index 50166fdacc92994..000000000000000 --- a/src/content/docs/speed/optimization/other/signed-exchanges/signed-exchanges-caveats.mdx +++ /dev/null @@ -1,74 +0,0 @@ ---- -pcx_content_type: reference -title: SXGs caveats -sidebar: - order: 3 -head: - - tag: title - content: Signed exchanges caveats - ---- - -## Allowed request headers - -Signed exchanges remove cookies and headers from HTTP requests, which can create problems with dynamic or personalized content. This is intentional since signed exchanges can be distributed to multiple browsers. Therefore, packaging any personalized or dynamic content into a signed exchange could be a security risk. The only request headers that are not removed are the following: - -* `AMP-Cache-Transform` -* `Accept` -* `From` -* `User-Agent` -* `Accept` -* `Via` -* `CF-Connecting-IP` -* `True-Client-IP` -* `X-Forwarded-For` -* `CF-RAY` -* `CF-IPCountry` -* `CF-Visitor` -* `CF-Loop` -* `CF-Worker` -* `CF-Threat-Score` -* `X-Bot-Score` -* `X-Static-Bot` -* `X-Threat-Score` -* `X-Tlsclientauth` -* `X-Verified-Bot` - -## Response headers - -Since Cloudflare cannot be sure whether a signed exchange includes private information or not, a signed exchange will not be generated in the presence of the following [response headers](https://wicg.github.io/webpackage/draft-yasskin-httpbis-origin-signed-exchanges-impl.html#name-stateful-header-fields): - -* `Authentication-Control` -* `Authentication-Info` -* `Clear-Site-Data` -* `Optional-WWW-Authenticate` -* `Proxy-Authenticate` -* `Proxy-Authentication-Info` -* `Public-Key-Pins` -* `Sec-WebSocket-Accept` -* `Set-Cookie` -* `Set-Cookie2` -* `SetProfile` -* `Strict-Transport-Security` -* `WWW-Authenticate` - -Signed exchanges will not be created if the response headers contain a `cache-control` header with one of the following values: - -* `private` -* `no-store` -* `no-cache` -* `max-age=0 ` - -For example, `cache-control=private` would mean that a signed exchange is not created. - -:::note - -The `cache-control` response header can have one of the following names: - -* `cache-control` -* `cdn-cache-control` -* `cloudflare-cdn-cache-control` -* `surrogate-control` - -For example, `cdn-cache-control=no-cache` would mean that a signed exchange is not created. -::: diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx index ed52517a786a758..b19640e53972d6e 100644 --- a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx +++ b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx @@ -49,10 +49,6 @@ To disable Universal SSL with the Cloudflare API, send a [`PATCH`](/api/resource -:::note -Even with Universal SSL disabled, some features such as [AMP Real URL](/speed/optimization/other/amp-real-url/) and [Signed Exchanges](/speed/optimization/other/signed-exchanges/) will still provision certificates for your domain. -::: - ## Re-enable Universal SSL diff --git a/src/content/docs/web-analytics/faq.mdx b/src/content/docs/web-analytics/faq.mdx index 353e79ee5e3d9b1..ba6f4fab0f2f876 100644 --- a/src/content/docs/web-analytics/faq.mdx +++ b/src/content/docs/web-analytics/faq.mdx @@ -106,10 +106,6 @@ Web Analytics only displays client-side analytics. All Cloudflare customers who Currently, users on Pro, Business, and Enterprise plans get advanced HTTP traffic analytics, which is the only way to see features like a breakdown of traffic by URL based on server-side analytics. -### Can I use Web Analytics with AMP? - -Not yet, but we plan to support AMP soon. - ### What is the period of time I can access data in Web Analytics? Currently, you can access data for the previous six months. diff --git a/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx b/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx index 9e400c75a7667fb..4c7417136d6c778 100644 --- a/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx +++ b/src/content/partials/cloudflare-one/access/self-hosted-app/product-compatibility.mdx @@ -6,8 +6,7 @@ When using Access self-hosted applications, the majority of Cloudflare products However, the following products are not supported: -* [Automatic Signed Exchanges](/speed/optimization/other/signed-exchanges/) * [Automatic Platform Optimization](/automatic-platform-optimization) * [Zaraz](/zaraz) -You can disable Automatic Signed Exchanges and Zaraz for a specific application - instead of across your entire zone - using a [Configuration Rule](/rules/configuration-rules/) scoped to the application domain. +You can disable Zaraz for a specific application - instead of across your entire zone - using a [Configuration Rule](/rules/configuration-rules/) scoped to the application domain. diff --git a/src/content/partials/ssl/caa-records-added-by-cf.mdx b/src/content/partials/ssl/caa-records-added-by-cf.mdx index a5adcba9cc59766..5e305d34f5779dc 100644 --- a/src/content/partials/ssl/caa-records-added-by-cf.mdx +++ b/src/content/partials/ssl/caa-records-added-by-cf.mdx @@ -3,14 +3,10 @@ --- -Cloudflare adds CAA records automatically in two situations: +Cloudflare adds CAA records automatically in the following situations: -* When you have [Universal SSL](/ssl/edge-certificates/universal-ssl/) or [advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/) and add any CAA records to your zone. -* When you have [Universal SSL](/ssl/edge-certificates/universal-ssl/) enabled and enable [AMP Real URL](/speed/optimization/other/amp-real-url/) or [Signed exchanges (SXG)](/speed/optimization/other/signed-exchanges/). - -:::caution[Deprecation notice] -AMP Real URL and Signed exchanges (SXG) are being deprecated and will be removed on October 20, 2025. -::: +- When you have [Universal SSL](/ssl/edge-certificates/universal-ssl/) and add any CAA records to your zone. +- When you have [advanced certificates](/ssl/edge-certificates/advanced-certificate-manager/) and add any CAA records to your zone. These records make sure Cloudflare can still issue Universal certificates on your behalf. diff --git a/src/content/plans/index.json b/src/content/plans/index.json index 371530ea2c8406a..1474f378b691650 100644 --- a/src/content/plans/index.json +++ b/src/content/plans/index.json @@ -2321,20 +2321,6 @@ }, "speed": { "title": "Speed", - "amp": { - "title": "AMP Real URL", - "link": "/speed/optimization/other/amp-real-url/", - "properties": { - "availability": { - "title": "Availability", - "summary": "Available on all plans", - "free": "Yes", - "pro": "Yes", - "biz": "Yes", - "ent": "Yes" - } - } - }, "automatic_platform_optimization": { "title": "Automatic Platform Optimization", "link": "/automatic-platform-optimization/", @@ -2349,20 +2335,6 @@ } } }, - "automatic_signed_exchanges": { - "title": "Automatic Signed Exchanges (SXGs)", - "link": "/speed/optimization/other/signed-exchanges/", - "properties": { - "availability": { - "title": "Availability", - "summary": "Included with Pro and above or [Automatic Platform Optimization](/automatic-platform-optimization/)", - "free": "No", - "pro": "Yes", - "biz": "Yes", - "ent": "Yes" - } - } - }, "brotli": { "title": "Brotli compression", "link": "/speed/optimization/content/compression/",