Use server-side credentials
Never expose the API key in JavaScript, HTML or visitor browsers; call the API from a trusted backend.
WORDPRESS URL INDEXING
Send new post and product URLs through server-side API calls, webhooks or a reviewed sitemap without exposing credentials.
A sound WordPress integration does not blindly submit every record. It checks publication state and technical eligibility first, keeps the API key on the server, uses an idempotent client reference for retries, and stores the resulting state in your own workflow.
Never expose the API key in JavaScript, HTML or visitor browsers; call the API from a trusted backend.
Do not automatically submit drafts, noindex pages or access-restricted URLs.
Use a client reference derived from the post ID and canonical URL to reduce double submissions.
Use WordPress, Make, n8n and Zapier examples with your own approval and error handling.
When your URLs are public and technically reachable, turn submission work into a repeatable operational process.
Paste individual URLs or import a public XML sitemap you are authorized to manage. Invalid and duplicate inputs are removed.
Standard Index is designed for regular work with a 3-hour to 7-day window; Instant Index targets time-sensitive work in 5-10 minutes.
The valid URL count, unit price and exact total are shown before the job is created. No subscription is required.
Follow queued, processing and completed states in the dashboard. Optionally query search visibility with URL Result Check.
No. Keep the key server-side and never send it to visitor browsers.
No. Check publication state, noindex, canonical and reachability before submission.
For backward compatibility, calls without the service field use Instant Index. Select Standard explicitly when needed.
No. It automates submission; search engines independently decide crawling and indexing.
Create your account for free and contact our team directly for trial or balance requests.