## **🔍 What causes the timeout?**

\*\* A WordPress OTTO authentication timeout means the connection process did not complete in time. Possible causes include an expired session, blocked requests, plugin conflicts, or a slow server response.

## **✅ Check the WordPress connection**

1. Confirm that you are using an administrator WordPress account.
2. Log in to your WordPress site in a separate browser tab and confirm the site loads normally.
3. Temporarily disable browser extensions that may block scripts or pop-ups, then retry authentication.
4. Check whether a firewall, security plugin, hosting protection, or CDN is blocking requests from Search Atlas.
5. Confirm that WordPress REST API requests are enabled and that your site is not blocking authenticated requests.
6. \*\* Retry the connection using the flow you started. For the Search Atlas WordPress plugin, go to Search Atlas → Settings in WordPress and select Connect to Search Atlas. If you started automatic installation in Search Atlas, follow the instructions shown there. (`customer-frontend/src/modules/otto/shared/install-flow/\_\_tests\_\_/methods.test.tsx:71–78`)

## **🔄 Retry authentication safely**

Start a new authentication attempt rather than refreshing a timed-out screen. Keep the WordPress login tab open, complete every authorization step, and wait for the confirmation message before closing the window. If the process fails again, try a private browser window or another supported browser.

## **🧩 Check plugins and server settings**

Security, caching, maintenance, and login-protection plugins can interrupt authentication. Review recent security logs for blocked requests and allow the Search Atlas or OTTO connection requests when appropriate. Also ask your hosting provider to check for server-side timeouts, blocked REST API traffic, or rate limits. Re-enable any temporarily disabled protection after testing.

## **🆔 Restore a missing Pixel UUID**

\*\* The OTTO Pixel UUID is read-only and is populated automatically when Search Atlas provides a valid UUID through the connection or synchronization process. Do not edit or guess this value manually. If it remains blank, confirm that you are connecting the intended WordPress site and OTTO project, then retry the connection. Contact support if it remains blank. (`metasync/includes/class-metasync-settings-registration.php:751–761`, `:3523–3530`; `metasync/includes/class-metasync-admin-navigation.php:1382–1389`)

## **💬 When to contact support**

If the timeout continues or the read-only OTTO Pixel UUID remains blank, include the Search Atlas project name, WordPress site URL, approximate time of the failed attempt, and any visible error message. Support can review the connection details and determine whether the UUID needs to be linked or assigned manually.

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.