π What a missing payload means
** When the dashboard shows fixes as deployed, the changes have been deployed in Search Atlas. This does not guarantee that every affected page immediately receives or displays them. OTTO must resolve the appropriate project and page, and the page must be able to load and apply the OTTO installation. Processing, caching, or request failures can also delay the visible result.
βοΈ Why affected URLs may return nothing
- ** The URL may not have been discovered or processed successfully: Check whether the affected page appears in the OTTO project and whether its relevant fixes have been generated and deployed. A crawl problem can prevent OTTO from discovering or generating page-specific optimizations.
- ** The requested URL may not resolve to the expected project or page: Compare the live URL, including its hostname, path, redirects, and any relevant parameters, with the URL in Search Atlas. The standard OTTO endpoint handles trailing-slash variants, so a trailing slash alone is not necessarily a mismatch.
- The OTTO installation is unavailable: The required OTTO code may be missing, blocked, modified, or not loading on the affected page template.
- Caching is serving an older version: Browser, hosting, CDN, or page-cache layers may still return a version from before deployment.
- The page is blocked or inaccessible: Login requirements, firewall rules, robots restrictions, server errors, or bot protection can prevent OTTO from reaching the URL.
- ** The deployment or page processing may still be underway, or a cached response may be delaying the result. Check the deployment status and recheck the affected pages after processing completes.
β What must happen before payloads are served
** For each affected URL, confirm that it is represented in the correct OTTO project, is not excluded, and has an applicable deployed optimization. Check that the live page loads the OTTO installation and that its optimization request succeeds. Processing and caches can delay updates, but clearing caches alone does not guarantee a payload.
π§ How to troubleshoot affected URLs
- Open each affected URL directly in a private browser window and confirm it loads successfully.
- Compare the live URL with the URL listed in Search Atlas. Check the protocol, hostname, path, trailing slash, redirects, and query parameters.
- Confirm that the OTTO installation is present and loading on the affected page, especially if the URLs use a different template or subdomain.
- Check whether a CDN, hosting provider, caching plugin, firewall, or security tool is blocking OTTO requests or serving cached HTML.
- ** After confirming that deployment and page processing have completed, clear relevant site or browser caches where appropriate and recheck the page. If the optimization response remains stale, contact support with the affected URLs and the checks performed.
- Recheck the URLs after the site is accessible and the deployment has finished processing. If only some pages remain affected, compare their templates and server responses with a working URL.
π Deployed versus served
** Deployed means the optimization has been deployed in Search Atlas; it does not by itself confirm that a visitorβs page received and applied the change. A page may still be affected by project or URL resolution, an excluded page, installation or request failures, processing, or cached responses.
π¬ When to contact support
** If the affected URLs load normally, are listed in the correct OTTO project, have applicable deployed optimizations, and load the OTTO installation, but the optimizations still do not appear after processing and cache checks, contact support. Share the exact URLs, the affected fixes, and the troubleshooting steps already completed.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.