This article covers three connected issues that can occur during or after an OTTO site installation: the installation staying stuck in a Processing state, the OTTO script appearing as Not Found despite correct placement, and OTTO recommendations showing Length: 0 across crawled pages even after a fix is deployed. These issues are often caused by 301 redirect conflicts that interfere with OTTO's internal page-fetching process.
OTTO verifies its installation by fetching your pages internally. When a 301 redirect is present — for example, between a www and non-www version of your site, or between trailing-slash and non-trailing-slash URLs — that redirect can interfere with OTTO's ability to confirm the script is installed, and the installation loop continues indefinitely. This same redirect behaviour also prevents OTTO from reading page content, which causes recommendations to remain blank after deployment.
Additionally, OTTO may list both the 301 and 200 versions of a redirected URL in its crawl data, leading to duplicate entries and data gaps that further block recommendation generation.
Open your OTTO SEO dashboard and navigate to your connected site.
Locate the script snippet provided for your site.
Verify the snippet is placed inside the <head> tag on every page of your site, including your homepage.
If you are using a WordPress plugin, confirm the plugin is active and has not been deactivated by a recent update.
A 301 redirect between your site's www and non-www versions, or between trailing-slash and non-trailing-slash URLs, is the most common cause of a stuck installation. Follow these steps:
Determine the canonical version of your domain — for example, https://example.com (non-www) versus https://www.example.com (www).
In your OTTO SEO dashboard, confirm that the domain entered during setup exactly matches your canonical version, including the correct www or non-www prefix.
Check your server or WordPress settings (.htaccess, Nginx config, or redirect plugin) and ensure all traffic resolves to a single canonical URL without chained or conflicting redirects.
If you use a caching plugin or CDN, purge all caches after making redirect changes.
After resolving redirect conflicts and confirming your script is correctly installed, trigger a reprocess of your site within the OTTO SEO dashboard. This allows OTTO to re-crawl your pages and generate recommendations based on accurate page content.
If you have completed the steps above and OTTO remains stuck in Processing, the script still shows as Not Found, or recommendations continue to show Length: 0, the issue may require a backend investigation. When contacting support, please have the following ready: your site's domain name, the exact error or status shown in your dashboard, and the approximate date and time you first noticed the problem.
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.