Published is not indexed — close the gap

• Baidu push: after an article publishes, its URL enters the Baidu submission channel — configure site credentials once and it keeps working.
• Bing IndexNow: search engines supporting the IndexNow protocol receive direct notifications for new, updated or removed URLs.
• Per-site configuration: search credentials are managed per site, and submission history is recorded independently for each.

The platform draws a deliberate line between two things:

• Publish status: whether the article is live on your site (success / failure / retrying).
• Submission status: whether the URL has been submitted to Baidu or Bing (submitted / failed / pending retry).

Each retries on its own: a successful publish with a failed submission means retrying only the submission — never re-running the publish. Both export separately for reconciliation, keeping the story straight for clients.

To be explicit: submission is not indexing, and indexing is not ranking.

• Submission only notifies the search engine; crawl and index timing remain the engine's decision.
• Rankings depend on content quality, site authority, competition and search strategy — the platform promises no rankings.
• Google's Indexing API applies only to JobPosting and live-stream structured data, with no general fast-indexing endpoint for ordinary articles — so the platform does not package it that way.

• Do I need search credentials per site? Yes — Baidu and Bing credentials are configured per site, and the platform warns when they expire.
• Are failed submissions retried automatically? Failed submissions keep their status and reason and can be retried manually; publish and submission retries are independent.
• Is Google Search Console supported? The current version focuses on Baidu and Bing IndexNow; the Google data loop is on the product roadmap.