How it Works

The Publishing Handshake

When you click Publish on an article in Azuqe, the platform triggers a multi-step handshake with every connected CMS. Here is exactly what happens, in order:

1. 1Content Preparation: The article body (HTML), title, slug, meta description, focus keyword, featured image URL, tags, and category are assembled into a structured payload.

1. 1CMS Delivery: The payload is sent simultaneously to each of your connected platforms using their native APIs. For WordPress, this goes to your site's /wp-json/aisuite/v1/submit endpoint via the installed plugin, authenticated using your integration key. For Ghost, it uses the Ghost Admin API. For Notion, it converts your HTML content into native Notion block structures.

1. 1Indexing Queue: Once publishing is confirmed, the article's live URL is added to the Auto-Indexing queue with a deduplication window. The same URL won't be submitted twice within 10 minutes to avoid spamming search engine APIs.

1. 1Search Engine Submission: The queue processor submits your URL to Google via the Search Console Webmasters API (your sitemap is re-pinged) and to Bing, Yahoo, and Yandex via the IndexNow protocol or the Bing Webmaster API if you have that connected.

1. 1Audit Scheduling: An SEO crawl of the newly published URL is queued to verify on-page health, checking for proper canonical tags, meta description presence, and header structure.

The SEO Audit Lifecycle

Every time you run an audit (manually or on schedule), it goes through a controlled lifecycle:

• PENDING: The audit job has been created and is waiting in the processing queue.
• RUNNING: The crawler is actively fetching your pages, checking DOM structure, validating canonical tags, meta descriptions, header hierarchies, and image alt attributes. Pages are crawled with up to 15 concurrent requests with a 5-second per-page timeout and a 15-second total wall-clock budget per crawl session.
• COMPLETED: All pages have been processed. Issues are classified by severity (Critical, Warning, or Info), with the specific HTML element, rule code, actual value vs. expected value, and whether an auto-fix is available.
• FAILED: A transient error (network timeout, server error) occurred. The queue automatically retries up to 3 times with exponential backoff before marking the audit as failed.

Each completed audit generates an SEO Health Score (0–100) and a Competitive Edge Score, both stored in your site's score history so you can track improvement over time.

The Indexing Queue

The indexing system is a background Bull queue (auto-index) that processes URL submissions asynchronously. This is what makes it fast and reliable:

• Submission records are created per URL per provider (Google, IndexNow). Duplicate submissions within a 10-minute window are automatically skipped.
• Bing path (preferred): If you have connected Bing via OAuth or API key, the platform submits via the Bing Webmaster API. No key file needs to be hosted on your domain.
• IndexNow fallback: If Bing is not connected, the platform uses the open IndexNow protocol (notifies Bing, Yandex, and others). This requires placing a verification key file at your domain root, which the platform can generate automatically.
• Google path: The platform re-submits your sitemap.xml to Google's Search Console Webmasters API using your connected Google OAuth credentials.
• Retry logic: All submissions use 3 retries with exponential backoff (starting at 5 seconds) for transient failures like HTTP 500 or 429 rate limits.

Content States Explained

Your content moves through clear, predictable states:

• Draft: Active editing. Writers and editors collaborate here. SEO checklist scores update in real time.
• Review: Content is flagged for manager approval. Comments and revision requests can be added.
• Scheduled: The article is locked with a publication date. The queue dispatcher handles automatic publishing at the target time.
• Published: Live on all connected platforms. Indexing queue has been triggered. Audit scheduled.

Frequently Asked Questions