## 📌 What This Article Covers

The URL Indexer tool submits your pages to Google for faster indexing. To do this, it relies on the **Google Indexing API**, which requires a connected **Google Cloud Platform (GCP) project** with valid credentials. If a GCP project is missing, misconfigured, or has hit its daily quota, your submissions cannot be processed and you may see **zero URLs processing for indexation**. This guide explains why this happens and how to resolve it.

## **❓ Why URL Indexer Needs a GCP Project**

Google does not allow pages to be submitted for indexing anonymously. Every submission must be authenticated through the Google Indexing API using service account credentials from your own GCP project. Without a connected project, the URL Indexer has no way to authorize requests, so submitted URLs stay at zero and never enter the processing queue.

- **Authentication:** The GCP service account proves the request is authorized.
- **Quota:** Each GCP project has a daily submission limit set by Google. You can connect additional GCP projects to increase your total daily indexing quota.
- **Ownership:** The service account must be verified as an owner of your property in Google Search Console.

## **🕓 Why You See Zero URLs After the 96-Hour Window**

The 96-hour window describes how long Google may take to act on a valid submission. That timer only starts once URLs are **successfully accepted** by the Indexing API. If your submissions show zero processing, the URLs were most likely never accepted in the first place. Common causes include:

- No GCP project is connected to your account or campaign.
- The service account was not added as an **owner** in Google Search Console.
- The **Indexing API** is not enabled inside the GCP project.
- Your project's **daily quota** was already used, so new URLs were rejected.
- The uploaded credentials (JSON key) are invalid or expired.

In these cases the 96-hour clock never began, which is why nothing appears to be processing.  


## **⚙️ How to Connect Your GCP Project**

Follow these steps to set up and connect a GCP project so your URLs can be submitted:

1. Sign in to the **Google Cloud Console** and create a new project (or select an existing one).
2. Open the **APIs & Services** library and enable the **Web Search Indexing API**.
3. Create a **Service Account** and generate a **JSON key** file.
4. Copy the service account email address (it ends in **gserviceaccount.com**).
5. In **Google Search Console**, open your property settings and add that service account email as an **Owner**.
6. Return to the URL Indexer tool in the platform and upload the JSON key file to connect the project.

## **✅ How to Confirm It Is Working**

After connecting your project, verify the setup so future submissions process correctly:

- Check that the URL Indexer shows your GCP project as **connected**.
- Submit a small batch of URLs and confirm the count moves above zero.
- Review your **remaining daily quota** before submitting large batches.
- Allow up to **96 hours** for Google to act on accepted URLs.

## **🛠️ Troubleshooting Common Issues**

If URLs still show zero processing, work through these checks:

- **Re-check ownership:** Confirm the service account is listed as an Owner, not a restricted user, in Search Console.
- **Confirm the API is enabled:** The Indexing API must be active in the same project as your service account.
- **Verify your quota:** If the daily limit is reached, wait for it to reset, request a higher quota in GCP, or connect an additional GCP project to raise your total daily quota.
- **Re-upload credentials:** Replace the JSON key if it was deleted or regenerated in GCP.
- **Re-submit URLs:** After fixing the setup, submit the URLs again so they enter the queue with valid authentication.

Some causes are platform-side rather than configuration errors, and several have already been resolved:

- **Instant indexing on an existing GCP project:** Activating **instant indexing** for an existing GCP project that had no assigned indexing project could previously fail, sometimes with an HTTP 500 error. This has been fixed — try activating again.
- **HTTP 400 "Invalid project name or URLs":** Submissions that failed with this error despite valid URLs and available quota have been resolved. Re-submit your URLs.
- **Silent submission failures:** A bug that caused URL submissions to fail silently with a network error has been fixed; retry your submission.

If your setup is correct and URLs still show zero processing or indexing is not being triggered, this may match a known issue our product team is currently investigating. Contact support (below) so we can link your account to the open report..