Fix GSC Instant Indexing failures, meet Bing Indexing requirements, recover missing AI Premium credits, and use the Domain Knowledge Network (DKN) to close content gaps and grow your site's topical authority.

## 📡 GSC Instant Indexing Is Not Working

GSC Instant Indexing connects Search Atlas to Google Search Console so you can request faster crawling and indexing of your pages. There are two distinct failure modes — identify which one applies to you before taking action.

### 1. Connection or authentication issues (re-authenticate via OAuth)

Use this flow when Search Atlas shows your Google Search Console integration as disconnected, errored, or with an expired token.

1. Go to **Settings → Integrations** in Search Atlas. If you don't see Integrations, contact Support to confirm your plan includes GSC Instant Indexing.
2. Confirm your Google Search Console property shows a **Connected** status.
3. If the status shows an error or expired token, click **Reconnect** and complete the Google OAuth flow.

**Known display bug:** If the GSC Performance report shows an **Authorize Connection** screen only when you change the time-range filter (for example, switching from 1 Year to 1 Month or 2 Months), this was a previously documented display bug that is now resolved. Refresh the page first; if the screen persists, clear your browser cache before attempting to reconnect.

### 2. Connection is valid but indexing requests still fail

Use this flow when your GSC integration shows as **Connected** but URL submissions are not being processed, or when the **Generate Unique Address** button returns an error.

- **Generate Unique Address button returns an error:** Clear your browser cookies and cache, reload the page, and retry. If the error persists, contact Search Atlas Support — an agent can retrieve your service-account address directly from the backend (example format: `indexing-[customer]@indexed-[hash].iam.gserviceaccount.com`).
- **Submissions appear accepted but pages are not being indexed:** Check [status.searchatlas.com](https://status.searchatlas.com/) for any active incidents before contacting Support.

If an active incident is listed, no further action is needed — the team is already investigating. Subscribe to incident updates on that page, or open a support ticket to be notified when the issue is resolved.

## 🔗 Bing Indexing Requires Root Domain Access

Bing Indexing uses the Bing URL Submission API. This API requires **root domain ownership verified** in Bing Webmaster Tools — subdomain or subfolder-level access is not sufficient and will prevent submissions from being accepted.

### Requirements before connecting Bing Indexing

- **Root domain verification:** Verify ownership of the root domain (e.g., `example.com`) in Bing Webmaster Tools — not a subdomain (`blog.example.com`).
- **Bing Webmaster Tools API key:** Generate an API key under **Settings → API Access** in Bing Webmaster Tools.

### How to connect Bing Indexing in Search Atlas

1. Complete root domain verification in [Bing Webmaster Tools](https://www.bing.com/webmasters/).
2. Copy your API key from Bing Webmaster Tools.
3. In Search Atlas, go to **Settings → Integrations → Bing Indexing** and paste the API key.
4. Save and re-submit your URLs for indexing.

Once root-level access is confirmed and the API key is saved, Bing Indexing will show accepted submissions in the integration dashboard.

## ✍️ Error When Editing the "About the Author" Section

If you see an error while editing an article's **About the Author** section, this is a known intermittent issue caused by the Content AI processing pipeline. No article data is lost when this error occurs.

### What to do

- Wait a few minutes, reload the tab, and try the edit again.
- Check [status.searchatlas.com](https://status.searchatlas.com/) to see if a Content AI incident is currently active.
- If the error persists for more than 30 minutes, contact Search Atlas Support with your article URL and the full error message so the team can investigate.

The Search Atlas team actively monitors and mitigates this issue. Once the pipeline clears, the edit will complete normally.

## 💳 Missing AI Premium Credits — How Quotas Work and How to Restore Them

AI Premium credits come in two distinct types. Understanding the difference is essential when credits appear missing or cannot be restored.

### Recurring vs. non-recurring credits

- **Recurring credits** reset automatically each billing cycle. If these appear missing or incorrect, Support can restore them directly.
- **Non-recurring credits** are one-time top-ups. Once consumed, they cannot be restored — Support cannot reissue spent non-recurring credits.

### Steps if your AI Premium credits are missing

1. Contact Search Atlas Support and specify whether the missing credits were recurring or non-recurring.
2. After Support restores your recurring credits, **reload the tab** — the updated balance appears immediately on refresh.
3. Verify your credit balance under the **account menu (person icon, top-right) → Billing → Plans & Top-ups**.
4. If non-recurring credits were consumed unexpectedly, provide Support with the date and the feature where they were used so the team can review the usage logs.

After a Support-initiated restore, your recurring credit balance will reflect the correction on the next page reload.

## 🗺️ Domain Knowledge Network (DKN) — Best Practices for Content Strategy

The Domain Knowledge Network (DKN) maps the topical coverage of your domain and surfaces gaps where content is missing. Use it to make deliberate, cluster-driven editorial decisions rather than publishing on disconnected topics.

### How to read the DKN map

- **Gaps on the map** are topics your domain has not yet covered — each gap is a candidate for your next article.
- **Incomplete clusters** — topic groups where you have 1–2 articles but not full coverage — signal the highest-priority opportunities. A few targeted articles can close the cluster and send stronger topical authority signals to Google.

### DKN prioritization strategy

1. **Start with incomplete clusters.** Expanding a cluster you've already started is more efficient than opening a new one from scratch.
2. **Prioritize by authority potential.** Focus on clusters in your core niche before moving to adjacent topics.
3. **Follow the clusters, not random topics.** Use the DKN as your editorial calendar — each article should advance a specific cluster toward completion.
4. **Pair DKN with the Search Atlas Content Planner.** Once you identify which cluster gaps to fill, use the Content Planner to brief and create those articles.

### DKN resources

- Review the [DKN documentation](https://searchatlas.com/docs/domain-knowledge-network/) for a full feature walkthrough.
- Watch the Search Atlas DKN training sessions for guided walkthroughs using real-world examples.

When used consistently, the DKN shortens the path to topical authority by showing you exactly which articles to write next — and in what order.

**🎯 You now know how to verify and fix GSC and Bing Indexing connections, recover missing AI Premium credits, work around the intermittent Content AI editing error, and use the Domain Knowledge Network to build a cluster-driven content strategy. For real-time platform status on any issue, always check [status.searchatlas.com](https://status.searchatlas.com/) first.**