Search Atlas Help Center

OTTO Deployed but Changes Not Showing Live

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🧭 Overview

OTTO SEO marks a deployment as successful once it writes metadata changes to your project. However, if your site is built on a JavaScript framework such as React, Next.js, TanStack Router, or Lovable, the live page may still display old title tags and meta descriptions — even after clearing your browser cache and confirming there are no IP or DNS issues.

This is a framework-level rendering conflict, not a crawl-blocking issue and not a problem with OTTO itself. This article explains why it happens and how to resolve it.

⚠️ Why This Happens

Traditional websites serve HTML directly from the server, so OTTO's metadata changes appear immediately in the page source. Single-Page Applications (SPAs) work differently:

  • The browser downloads a JavaScript bundle and builds the page client-side.
  • Many SPA frameworks include their own metadata management libraries (for example, React Helmet, Next.js Head, TanStack Router loaders, or Lovable's built-in meta handling).
  • These libraries write their own title tags and meta descriptions after the page loads, which overwrites the values OTTO already deployed.
  • Because OTTO's changes exist in your project files but are overridden at runtime, the Search Atlas dashboard may correctly show the deployment as successful while visitors and search engines see the old metadata.

Clearing your cache does not resolve this because the conflict happens in the framework's runtime logic, not in cached files.

✅ How to Confirm This Is Your Issue

  1. In Search Atlas, confirm that OTTO shows the affected pages as successfully deployed.
  2. Open the live page in your browser and press Ctrl+U (or Cmd+Option+U on Mac) to view the raw page source.
  3. Search the source for your expected title tag or meta description text.
  4. If the source shows OTTO's updated values but the rendered page (viewed normally) shows old values, your framework's metadata manager is overriding OTTO at runtime.
  5. If the source itself still shows old values, OTTO's deployment may not have completed — contact support using the instructions at the bottom of this article.

🛠️ How to Fix the Conflict

The resolution requires telling your SPA framework to defer to OTTO's metadata rather than managing it independently. Follow the steps below based on your stack.

⚛️ React (Create React App or custom React)

  1. Locate any usage of React Helmet or React Helmet Async in your codebase.
  2. Remove or comment out the <Helmet> blocks that set title and meta description on