CodeCrafters URL Indexing for Google and IndexNow

No. Use either or both. IndexNow covers Bing and other partners with almost no setup. Google requires a Google Cloud project, Search Console ownership, and has a daily quota. Many sites start with IndexNow and add Google later.

Only if you enable the Google Indexing API. IndexNow works independently with the key generated by the plugin and does not require a Google account.

1. Open Google Cloud Console and create (or select) a project.
2. Go to APIs & Services → Library, search for Web Search Indexing API, and click Enable.
3. Go to IAM & Admin → Service Accounts → Create service account. Give it a clear name; no extra Cloud roles are needed.
4. Open the service account, go to Keys → Add key → Create new key → JSON, and download the file. Copy the service account email (it looks like name@project-id.iam.gserviceaccount.com).
5. Open Google Search Console, select the property for your site, go to Settings → Users and permissions, and add the service account email with Owner permission.
6. In WordPress, go to URL Indexing → Settings, enable Google Indexing API, paste the entire JSON file into Service account JSON, save, and click Test Google Connection.

In URL Indexing → Settings → Service account JSON. Paste the full contents of the downloaded .json file. Do not upload the file to your media library or leave it in a public folder. On later saves, leave the field blank to keep the stored key unchanged.

The key is stored in the WordPress options table, never as a publicly accessible file, and is not autoloaded on every page. Still treat it like a password: limit who has administrator access, use HTTPS, and never commit the key to version control or show it in screenshots.

Google authenticates with a service account (OAuth 2.0 signed with the private key in the JSON file) and requires that account to own the site in Search Console. IndexNow proves ownership differently: search engines fetch a key file from your domain. The plugin creates that key and serves the file automatically.

On activation the plugin generates a random 32-character key and serves it at https://yoursite.com/{key}.txt through a WordPress rewrite rule. No physical file is written to your server. Search engines fetch that URL to confirm you control the site.

IndexNow is a free, open protocol. Google's Indexing API is generally free within its documented quota (commonly 200 requests per day per Google Cloud project). Check Google's current quotas and billing policies for your project.

Google typically allows about 200 Indexing API requests per day per Cloud project. The plugin lets you set a lower cap (180 by default, up to 200) and stops sending Google requests once it is reached; those attempts are logged as "Quota exceeded". The counter resets at midnight UTC, and current usage is shown on the Settings and Tools screens.

IndexNow does not publish a small daily cap like Google's. Still, only notify real changes and avoid repeated resubmissions of the same URL.

No plugin can guarantee that. Notifications ask search engines to crawl your URL sooner, but Google, Bing, and others still decide whether and when to index it based on quality, crawl budget, and their own systems.

No. Saving a post never waits on a remote API. Pings are scheduled through WP-Cron and run in the background after the request finishes. Nothing is loaded on the front end of your site, and the admin screens use lightweight vanilla JavaScript with no jQuery dependency.

When a published post is moved to draft, pending, private, scheduled, or trash, or is permanently deleted, the plugin sends a URL_DELETED notification to Google and notifies IndexNow of the change, so engines can drop or recrawl the stale URL faster.

Yes. Open any published post or page in the editor and use Submit to Google or Submit to IndexNow in the CodeCrafters URL Indexing panel in the sidebar. The panel also shows the last submission result for each engine. Results appear in the Submission Logs.

Posts and pages are monitored by default. In Settings you can select any public post type with front-end URLs, such as WooCommerce products. Developers can adjust the list with the ccurlidx_post_types filter.

1. The Web Search Indexing API is enabled in the same Cloud project as the key.
2. You pasted the entire JSON, including private_key and client_email.
3. The service account email is an Owner of the correct Search Console property.
4. Your WordPress site URL matches the Search Console property (www vs. non-www, http vs. https).
5. The OpenSSL PHP extension is available on your server (required to sign the request).

1. IndexNow is enabled and settings are saved.
2. Open the Key file URL in a private browser window. It should show only the key text.
3. If that URL returns a 404, go to Settings → Permalinks and click Save Changes once to refresh rewrite rules.
4. Make sure a security plugin or firewall is not blocking the .txt URL.
5. If you just regenerated the key, wait a few minutes and test again.

Only if the key may have been exposed or you need to rotate it. Regenerating creates a new key and verification URL, and the old key stops working; search engines will re-verify the new key file.

No. Search Console ownership is required only for the Google Indexing API. Verifying your site in Bing Webmaster Tools is optional but lets you see IndexNow submissions there.

No. Keep your sitemap (WordPress core sitemaps or your SEO plugin). This plugin adds instant push notifications on top of normal crawler discovery.

30 days by default. You can change the retention period (7 to 365 days) in Settings, and old entries are pruned automatically by a daily scheduled task. You can also export logs to CSV or clear them from the Submission Logs screen.

The plugin sends page URLs (and for IndexNow, your host and API key) to search engines. It does not send personal data such as names, emails, or visitor identifiers, and it adds no tracking to your site. Credentials are stored in your WordPress database. Review Google's and Microsoft's privacy policies linked in the External Services section, and mention these transfers in your own privacy policy if required.

Deleting the plugin from the Plugins screen removes its settings, stored credentials, quota counters, scheduled events, and the submission log table.