## **🗺️ Overview**

Two of the most common setup questions from new Search Atlas customers are: **should I start on staging or production?** and **how do I connect my Google Search Console (GSC) account?** This article answers both clearly so you can get up and running without delays.

## **🏗️ Staging vs Production: Which Should You Set Up First?**

The short answer is: **always set up Search Atlas on your production site first.** Here is why this matters and what each option means in practice.

- **Production** is your live, public-facing website. This is where real users visit, real traffic is measured, and real SEO signals are generated. Search Atlas tools — including OTTO SEO, rank tracking, and site audits — are designed to work against live data.
- **Staging** is a private copy of your site used for testing before changes go live. Because staging environments are typically blocked from search engines (via `noindex` tags or password protection), data collected there will not reflect your actual SEO performance.

Setting up on production first ensures that your GSC data, backlink profiles, keyword rankings, and site audit results are accurate and actionable from day one.

## **✅ When Staging Can Be Useful**

While production is always the primary setup target, staging has a limited role in your workflow. You may use a staging environment to:

- Preview and test OTTO SEO code changes before applying them to your live site.
- Validate structured data or schema markup implementations.
- Test site speed improvements before deploying to production.

**Important:** Never connect your GSC property to a staging URL. GSC only captures meaningful data for verified, publicly indexed properties. Connecting a staging URL will result in missing or misleading data.

## **🔗 How to Connect Your Google Search Console Account**

Connecting GSC to Search Atlas links your real organic search data — impressions, clicks, average position, and indexed pages — directly to your dashboard. Follow these steps:

1. Log in to your Search Atlas account and navigate to **Site Metrics → Site Explorer**.
2. Click **Open Google Search Console** to reach the **Manage Sites** page.
3. Click **Connect GSC Account** and sign in with the Google account that has access to your GSC property.
4. Select the correct **GSC property** from the dropdown. Make sure you select the production URL (e.g., **https://yourdomain.com**), not a staging or subdomain variant.
Once connected, Search Atlas will begin pulling your GSC data. It may take up to 24 hours for the full data set to populate in your dashboard.

## **⚠️ If GSC Says to Reach Out to Support**

In some cases, the GSC connection screen will display a message instructing you to contact support. This typically happens when:

- Your Google account does not have **Owner** or **Full User** permissions on the GSC property.
- The GSC property has not been verified in Google Search Console yet.
- There is a conflict with a previously connected Google account on your Search Atlas workspace.
- Your Search Atlas plan requires a manual authorization step for GSC integration.

Before reaching out, check the following in your Google Search Console account:

1. Go to **Google Search Console → Settings → Users and permissions**.
2. Confirm that the Google account you are using to connect has **Owner** or **Full User** access to the property.
3. Confirm that the property is verified and shows data (not a newly added, unverified property).
4. Return to Search Atlas and retry the connection using that verified Google account.

If the issue persists after following these steps, our team can resolve it for you quickly.

## **🛠️ Quick Troubleshooting Checklist**

- **Wrong property selected:** Make sure you pick the exact property format that is verified in GSC (e.g., domain property vs. URL-prefix property).
- **Multiple Google accounts:** If you manage several Google accounts, ensure your browser is logged in to the correct one before authorizing.
- **GSC data delay:** New connections can take up to 24 hours to reflect data. Check back the following day before troubleshooting further.
- **Staging URL connected by mistake:** Disconnect the staging property and reconnect using your production URL.

## **💬 Need Further 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.