## **📍 Where to Find It**

**UI path:** Settings → Integrations

## **🔌 Why a Search Console Connection Fails**

When you add a new client, the connection to Google Search Console often fails for a few common reasons. Check these first:

- **Wrong Google account:** The Google account you sign in with must have access to the client's Search Console property.
- **Insufficient permissions:** The account needs at least Full user access in Search Console. View-only access is not enough for a full connection.
- **Property mismatch:** The website address in Search Console must match the client's domain. A URL-prefix property (for example, https://www.example.com) and a Domain property (example.com) are treated differently.
- **Property not yet verified:** Search Console must show the site as verified before it can be connected.

## **✅ Steps to Fix the Connection**

1. Sign in to Google Search Console and confirm that the site appears in the property list.
2. Check that your account has Owner or Full user permission for that property.
3. Confirm the property's address matches the domain you entered for the client in Search Atlas.
4. Return to Search Atlas, remove the existing Search Console connection for that project, and reconnect it using the account you verified in steps 1 to 3.
5. Allow a short time for data to appear. New properties can take several days to show full historical data.

## **🧭 Refining Your OTTO Prompt When Search Console Is Unavailable**

If you cannot connect Search Console for a client, you can still get useful results from OTTO. The key is to tell OTTO which data sources to use and what to do if one is missing. Vague prompts can lead OTTO to assume data is available, which produces unreliable recommendations.

Use these guidelines when you write your prompt:

- **State the data situation:** Say clearly that Search Console is not connected for this client.
- **Name the fallback sources:** Tell OTTO which other data it can rely on, such as analytics or crawl data.
- **Ask OTTO to flag gaps:** Request that OTTO label any recommendation that depends on missing data.
- **Limit the scope:** Focus the task on what you can measure, such as on-page improvements, content gaps, or technical issues.
- **Specify the output format:** Ask for a prioritised list, a summary, or a step-by-step plan so the result is easy to review.

## **💬 Example Prompt**

Use the following as a starting point and adjust it to the client's goals:

Create an SEO performance summary for this client's website. Google Search Console is not connected for this project, so do not estimate or infer search query or impression data. Base your analysis on the available crawl data and on-page content. Identify the five highest-priority technical or on-page issues, and for each one explain the expected benefit and the effort required. Mark any recommendation that would normally rely on Search Console data as Needs verification once the connection is restored. Present the results as a numbered list with a short summary at the top.

## **📊 Tips for Client Reports**

- Add a note in the report explaining which data sources were used and which were unavailable.
- Once the Search Console connection is working, run the same prompt again to compare results and update flagged items.
- Keep a checklist of connection steps so the same issue can be resolved quickly for future clients.

## **🛟 Getting Further Help**

If the connection still fails after you have checked the steps above, or if OTTO's output does not match what you expected, please reach out for help. 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.