High-Performance Serverless Indexing
For WooCommerce & Custom Catalogs
Index your high-volume product catalog using our dedicated serverless architecture. Designed for large databases to completely prevent hosting timeouts and rate-limiting blocks during bulk data migrations to Typesense.
* Note: This license key is valid for one successful catalog migration. Future syncs/re-indexing will require a new migration license.
Zero Timeout Limit
Offloads complex MySQL formatting and collection imports to high-speed serverless background functions.
WAF & Rate Safe
Throttled chunk-based processing prevents your server IP from getting rate-limited by hosting WAF firewalls.
Self-Healing Queue
Built-in worker recovery monitors processing status and auto-resumes indexing if any network drop occurs.
Reduced Server Load
Offloads heavy queue orchestration to Vercel, reducing your WordPress server's CPU and RAM footprint during indexing.
Run & Forget
No browser tab locking. Once initialized, the serverless queue runs completely in the cloud. You can close the tab or shutdown.
Live Logs & Control
Monitor detailed progress in real-time. Pause, resume, and inspect live request logs directly from your WordPress dashboard.
Firewall & Security Configurations
Configure your hosting environment and security layers to ensure the serverless sync runner can securely connect to your database.
01. REST API Accessibility
Since the synchronization runner is hosted on our serverless cloud, your WordPress REST API must be reachable by our service. Verify that your site endpoints (located at /wp-json/) are publicly accessible and not blocked by local networks, password gates, or intranet settings.
02. SSL / HTTPS Encryption
Your site must have a valid SSL certificate and run over secure https://. Unencrypted HTTP connections are blocked by serverless proxy layers due to security policies, and expose your secret credentials during database transmission.
03. Caching Exclusions
Ensure the endpoint prefix /wp-json/swift-search-migration/v1/ is completely excluded from all server-side page caching (such as Varnish, Nginx FastCGI cache, or WP Rocket caching). If the API is cached, the sync runner will receive duplicate product batches instead of moving through the queue.
04. Cloud Server Whitelist Parameters
To prevent automated security tools from blocking sync requests, configure your server or proxy rules to grant a bypass matching our service identifiers:
/wp-json/swift-search-migration/v1/
X-SwiftSearch-Cloud-Secret
Step-by-Step Security Setup
Follow these configurations inside your hosting environments and security platforms to authorize connection requests.
Configure custom rules in Cloudflare to bypass bot protection blocks.
- Navigate to Security > WAF in your Cloudflare dashboard.
- Create a new Custom Rule.
- Set Field to URI Path -> Operator to contains -> Value to
/wp-json/swift-search-migration/v1/. - Set Action to Bypass (specifically bypass Managed Rules and Bot Fight Mode).
Prevent ModSecurity from blocking sync requests as false positives.
- Open the ModSecurity tool under the Security section of your panel.
- Check your server error logs to find blocked request rule IDs.
- Disable the specific triggered Rule ID for your domain.
- Alternatively, whitelist the API path:
/wp-json/swift-search-migration/v1/.
Bypass rate-limiters (Fail2ban, limit_req) for high-frequency queries.
- Open your server configuration file (e.g.
nginx.confor.htaccess). - Exempt requests containing the header
X-SwiftSearch-Cloud-Secretfrom active rate-limiting zones. - Ensure ports 80 and 443 are open for inbound traffic.
Adjust plugins (Wordfence, Sucuri) to allow JSON database crawl.
- Open your security plugin configuration dashboard inside WordPress.
- Whitelist the exact REST API prefix:
/wp-json/swift-search-migration/v1/. - Temporarily enable Wordfence Learning Mode during migration runs.
Exempt serverless migration requests from proprietary hosting firewalls.
- Log in to your hosting portal (WP Engine User Portal / MyKinsta).
- Go to your environment's Web Application Firewall (WAF) settings.
- Whitelist or add an exception rule matching path:
/wp-json/swift-search-migration/v1/. - Or request hosting support to exclude this route from WAF rate-limiting.
Quickly test if your REST API is reachable by the serverless migration runner.
- In your browser, visit
yoursite.com/wp-json/swift-search-migration/v1/documents. - If the screen displays
rest_forbidden(HTTP 403), connection is successful. - If you see a 404, 502, or timeout, check if the plugin is active or if firewalls are blocking the path.