Azuqe
Go to Dashboard

SEO Optimization Suite

Auto-Indexing Engine

Submit newly published URLs to Google and Bing in real time using direct API handshakes, bypassing the days-long wait for search bots to discover your content organically.

Why Auto-Indexing Exists

When you publish a new article, Google typically discovers it through one of two mechanisms: a regular scheduled crawl (which can take days or weeks depending on your site's crawl budget) or a sitemap re-submission (which triggers a crawl, but not instantly).

The Auto-Indexing Engine bypasses both of these slow paths. It uses official search engine APIs to directly notify Google and Bing the exact moment your content goes live, leading to indexing in minutes instead of days.

This matters because: - Being indexed faster means appearing in search results before competitors can publish similar content - Time-sensitive content (news, product launches, seasonal offers) loses value if it takes a week to appear in search - For high-volume publishing teams, manual re-submission per article is impractical

How the Indexing Queue Works

The indexing engine uses a background Bull job queue called auto-index. Here is the exact technical flow:

  1. 1URL Submission: When you publish an article (or manually submit URLs), the platform creates a submission record per URL per provider (Google, IndexNow). Each record has a status: Pending, Submitted, Indexed, or Failed.
  1. 1Deduplication: The same URL won't be queued twice within a 10-minute window. This prevents accidental duplicate submissions from rapid-fire saves or multi-platform publishes.
  1. 1Queue Processing: The queue processor picks up the job and runs two parallel submission paths: the Bing/IndexNow path and the Google path.
  1. 1Retry Logic: All submissions use 3 retry attempts with exponential backoff. The first retry waits 5 seconds, subsequent retries wait progressively longer. Transient HTTP 500 and 429 errors trigger automatic retries; permanent errors (like 403 permission issues) are recorded as Failed with a descriptive message.
  1. 1Status Tracking: Every submission is recorded in your dashboard with the timestamp, response code, and provider. You can see at a glance which URLs were successfully submitted and which failed.

Google Search Console Setup

To enable Google indexing submissions:

  1. 1Go to Settings → Integrations → Google Search Console.
  2. 2Click Connect Google and sign in with the Google account that manages your site's Search Console property.
  3. 3The platform requests the webmasters scope, which allows it to re-submit your sitemap via the Search Console API.
  4. 4Once connected, the platform automatically identifies which GSC property matches your site's domain.

If you see "Insufficient permission" errors after connecting, disconnect and reconnect Google. Make sure to approve all requested permissions on the Google authorization screen, including the Search Console (webmasters) scope.

Bing & IndexNow Setup

Bing submission uses the IndexNow protocol, which also notifies Yahoo and Yandex:

Option A: Bing Webmaster API (Recommended): 1. Go to Settings → Integrations → Bing Webmaster. 2. Connect your Bing Webmaster Tools account via API key. 3. With this connected, submissions go through the Bing Webmaster API directly. No key file needs to be hosted on your domain. Bing trusts submissions from verified API accounts.

Option B: IndexNow Key File (Fallback): If you don't have a Bing Webmaster account, the platform generates an IndexNow key automatically and stores it in your site settings. You need to host a text file at https://yourdomain.com/{key}.txt containing just the key value. This proves domain ownership to the IndexNow protocol.

The platform always attempts the Bing Webmaster API path first, and falls back to IndexNow only if Bing is not connected.

Dripfeed & WebSub

Beyond single-URL submissions, the engine supports two advanced indexing patterns:

Dripfeed Indexing: Instead of submitting all URLs at once (which can look spammy to search engines), you can schedule a batch of URLs to be submitted gradually, for example 10 URLs every 60 minutes. This mimics natural publication pacing and is ideal for large content migrations or bulk publishing campaigns.

WebSub (PubSubHubbub): If your site publishes an RSS or Atom feed, the platform can ping Google's PubSubHubbub hub to notify it of feed updates. The platform auto-discovers your feed URL from the homepage's <link rel="alternate"> tags, then probes common feed locations (/rss/, /feed/, /feed.xml) if no declared feed is found. For sites without any RSS feed (catalog pages, landing sites), this feature is shown as "Not Applicable", not an error.

Frequently Asked Questions

Frequently Asked Questions

Was this page helpful?

Let us know how we can improve this documentation.