**π Overview**
Two of the most common OTTO setup issues are **not being able to locate the installation script** and a **logo being detected as an H1 heading** on your site. Both problems can prevent OTTO from running diagnostics correctly and deploying optimisations. This guide walks you through resolving each one.
**βοΈ Step 1 β Find and Install the OTTO Script**
The OTTO script is the foundation of all automation. Without it installed on your site, diagnostics cannot run and no changes can be deployed.
- Log in to Search Atlas and navigate to **OTTO SEO** in the left sidebar, then open **SEO Automation**.
- Select the website project you want to work with.
- Look for the **OTTO Setup** or **Connect Site** prompt. If OTTO is not yet activated, you will see a button to begin setup β click it.
- On the setup screen, locate the **OTTO script snippet**. It is a short JavaScript tag that looks similar to: ****
- Copy the full script snippet.
- Paste the snippet into the **** section of every page on your website. If you use a CMS such as WordPress, you can add it via your theme's header file or a header/footer plugin.
- Save your changes and reload your website.
**Tip:** If you manage multiple sites, each site has its own unique script. Make sure you copy the script for the correct project.
**β
Step 2 β Verify the Script Is Detected**
After installation, confirm that Search Atlas can detect the script before attempting to run diagnostics.
- Return to **OTTO SEO** in the left sidebar and open **SEO Automation**.
- Open your website project and look for a **script status indicator** or **connection status** badge near the top of the page.
- If the status shows **Connected** or **Active**, the script is installed correctly and diagnostics can proceed.
- If the status shows **Not Detected**, double-check that the script was pasted inside the **** tag and that there are no caching layers serving an older version of your page. Clear your site cache and try the verification again.
**Common reason diagnostics fail:** A caching plugin or CDN (such as Cloudflare) serving a cached page without the new script. Always purge your cache after installation.
**πΌοΈ Step 3 β Resolve the Logo Detected as H1**
OTTO flags a logo as an H1 when your site's HTML wraps the header logo image inside an **
** tag. This is a structural SEO issue because every page should have exactly one H1 that describes the page content β not the site logo. To fix this issue, you need to change the HTML tag wrapping your logo from **** to a non-heading element such as a ** ** or ** **, or simply remove the heading tag entirely and keep the anchor link and image only. 1. Open your website's theme or template editor and locate the header file (commonly **header.php** in WordPress themes, or the equivalent in your CMS). 2. Find the code block that outputs the logo. It will look similar to: **Site Name** 3. Replace the outer **** and **** tags with a neutral element. For example: ** Site Name ** 4. Save the file and clear your site cache. 5. Return to OTTO and re-run diagnostics to confirm the H1 issue is resolved. **Important:** If your theme does not give you direct access to the header HTML, check your theme's **Customizer** or **Logo settings** β some page builders and themes have a toggle to control whether the logo is wrapped in a heading tag. Page builders such as Elementor, Divi, and Beaver Builder expose this as a simple dropdown option in the header widget settings. # **π Step 4 β Re-run OTTO Diagnostics** Once the script is verified and the logo H1 issue is corrected, run a fresh diagnostic scan to confirm everything is in order. 1. Go to **OTTO SEO** in the left sidebar and open **SEO Automation**. 2. Open your website project and click **Run Diagnostics** (or the equivalent scan button in the OTTO panel). 3. Wait for the scan to complete. This typically takes a few minutes depending on the size of your site. 4. Review the results. The logo H1 flag and any script-related warnings should no longer appear. # **π‘ Quick Troubleshooting Checklist** - **Script not detected?** Confirm it is in the ****, not the footer, and that your cache has been cleared. - **Logo H1 persists after editing?** A caching layer may still be serving the old HTML β purge all caches including your CDN. - **Using a page builder?** Check the header widget or section settings for a heading-level option and set it to none or paragraph. - **Changes not saving?** Ensure you have the correct file permissions and that you are editing the active theme, not a parent theme that gets overridden. # **π¬ Need More Help?** 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.