SoftReviewed Multi-Engine Indexing
Automated real-time search engine indexing for Google, Microsoft Bing, and Yandex. Pushes instant crawl requests via official APIs the moment WordPress content is published, updated, or removed.
Real-Time Search Engine Push Architecture
Most WordPress websites rely entirely on static XML sitemaps to communicate with search engines. While sitemaps are essential, search engine bots often take days or weeks to discover, crawl, and index updated pages through passive polling.
SoftReviewed Multi-Engine Indexing eliminates crawl latency by establishing direct, programmatic communication channels with major search engine indexing gateways. Whenever you publish, revise, or trash a post or page, the plugin immediately transmits an authenticated dispatch signal.
Why Direct API Indexing Matters
Search engines allocate limited crawl budgets to websites. Direct API notifications provide priority discovery signals directly to crawler queues, ensuring breaking editorial articles, product updates, and critical revisions are indexed rapidly without waiting for automated recrawls.
Core Capabilities & Features
Direct integration using Google Cloud Service Account keys. Dispatches real-time URL_UPDATED and URL_DELETED requests securely with zero external Google SDK libraries.
Native IndexNow protocol implementation. Automatically generates, stores, and hosts your domain verification key file (/<key>.txt) for instant participation.
Asynchronous submission pipeline powered by WordPress Cron (fmi_submit_event). The WordPress block editor never stalls or waits on third-party network requests.
Built-in operational log detailing exact HTTP response codes from API endpoints, alongside a bulk submission tool allowing up to 50 URLs to be queued simultaneously.
Architectural Comparison
| Feature / Criterion | SoftReviewed Multi-Engine | Standard XML Sitemaps | Bulky SEO Suites |
|---|---|---|---|
| Discovery Speed | ⚡ Instant (< 5 seconds) | Hours to Days (Passive) | Instant (via add-ons) |
| External Dependencies | Zero (Native OpenSSL) | None | Heavy (Composer/SDKs) |
| Codebase Size | < 750 lines (Single file) | Core feature | 10,000+ lines & DB tables |
| IndexNow Verification | Dynamic auto-serve (.txt) |
Not supported | Static file writes |
| Editor Experience | Non-blocking (WP Cron) | Non-blocking | Can lag during save |
Step-by-Step Configuration Guide
Upon plugin activation, a unique 32-character IndexNow API key is generated. The plugin automatically intercepts requests to https://yoursite.com/<key>.txt and serves the required key string. No manual file uploads or FTP edits are required.
Create a free Service Account in your Google Cloud Console, enable the Google Indexing API, grant the service account Owner access in Google Search Console, and paste your Service Account JSON credentials into the plugin settings screen. The plugin uses PHP’s native OpenSSL module to sign JWT assertions without third-party dependencies.
Whenever a post, page, or supported custom post type is published or modified, the plugin queues the URL for dispatch. For existing content or bulk updates, navigate to Settings > Fast Multi Indexer and paste up to 50 URLs into the Bulk Submitter tool for instant push notifications.
External Services & Regulatory Disclosures
Third-Party API Disclosures (WordPress.org Guideline 6)
To provide automated search engine indexing functionality, this plugin connects to external third-party endpoints as documented below:
- Google Indexing API & OAuth 2.0: Sends the modified page URL, action type (
URL_UPDATED/URL_DELETED), and an encrypted token tohttps://indexing.googleapis.com/andhttps://oauth2.googleapis.com/token. Review the Google APIs Terms of Service and the Google Privacy Policy. - IndexNow Protocol (Microsoft Bing & Yandex): Transmits your host domain, page URL, and verification key to
https://api.indexnow.org/indexnow. Review the IndexNow Protocol Specification, the Microsoft Privacy Statement, and the Yandex Privacy Policy.
No personally identifiable user data, visitor telemetry, analytics cookies, or tracking beacons are collected, stored, or transmitted by this plugin.
