🔍 Overview
If you have deployed title tags or meta descriptions through OTTO and they appear to revert without any action on your part, the most likely cause is that the affected pages are returning a 202 status code instead of a standard 200 OK response. A 202 status means the server has accepted the request but has not yet finished processing the page. OTTO cannot fully crawl or confirm fixes on pages in this state.
⚙️ What Is a 202 Status Code?
HTTP status codes tell crawlers how a server responded to a request:
- 200 OK — The page loaded successfully and is fully crawlable.
- 202 Accepted — The server received the request but the page is still being processed. The content is not yet in its final state.
When OTTO encounters a 202 response, the page is not considered crawlable or indexable. As a result, OTTO cannot verify that your deployed fixes are live, and the dashboard may show those pages as unresolved or appear to show the original, unfixed metadata.
🤖 What Is a Robot Challenge Screen?
A robot challenge screen is a security layer — commonly served by tools like Cloudflare — that presents an automated browser check before allowing access to a page. When OTTO's crawler encounters this challenge, it cannot read the page content and receives a non-200 response (such as a 202) instead of the finished HTML. This prevents OTTO from confirming or reading your deployed SEO changes.
🛠️ How to Diagnose the Problem
- Identify which pages appear to have reverted titles or meta descriptions after deployment.
- For each affected page, manually check the HTTP status code. You can do this by opening your browser's developer tools, going to the Network tab, and reloading the page — look for the status code shown next to the page URL. Alternatively, use a free online HTTP status checker by pasting in the page URL.
- If a page returns 202, the page is still processing or is behind a bot-challenge screen. OTTO will not be able to confirm fixes on that page until it returns a 200 OK.
- If a page returns 200 OK, OTTO should be correctly reading and displaying your deployed changes. If fixes still appear missing on 200-status pages, proceed to request a recrawl (see below).
✅ What You Can Do
- Wait for processing to complete. If your pages are genuinely still loading or being built server-side, wait and check the status code again after some time. Once the page returns 200 OK, OTTO will be able to crawl and confirm your fixes.
- Check your site's bot-protection settings. If your hosting provider or CDN (such as Cloudflare) has bot-fight or challenge modes enabled, these can block legitimate crawlers including OTTO. Review your security settings and, if safe to do so, configure exceptions to allow automated crawlers access to your pages.
- Trigger a recrawl in OTTO. Once affected pages are returning 200 OK responses, initiate a recrawl from within the OTTO section of the platform so that OTTO can re-read and confirm your deployed fixes.
- Do not redeploy unnecessarily. Redeploying fixes to pages still returning 202 responses will not resolve the underlying issue and may cause confusion. Wait until the pages are fully accessible before redeploying.
📊 Pages With 200 OK Status
For any pages that are already returning a 200 OK status code, OTTO should be correctly displaying your original deployed titles and meta descriptions. If you notice discrepancies on those pages specifically, this may be a separate caching or deployment issue rather than a crawl-access problem.
💡 Additional Context
This issue is most common on sites hosted on platforms with aggressive bot-protection enabled, or on pages that use server-side rendering with delayed processing. The root cause is always that OTTO cannot access the final, rendered version of the page — not that your SEO changes have been lost. Your deployed changes remain intact; OTTO simply cannot confirm them until the page is crawlable.
🆘 Still Need Help?
If you have verified that your pages are returning 200 OK responses and your fixes are still not being reflected, or if you are unsure how to adjust your bot-protection settings, If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.