| 开发者 |
xealbrax
banfronix |
|---|---|
| 更新时间 | 2026年10月29日 15:45 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
xealbrax-auto-indexer directory to your /wp-content/plugins/ directory, or install directly through the WordPress plugins screen.iam.gserviceaccount.com).
4. Click on the Service Account, go to the Keys tab, and click Add Key > Create new key (JSON format). Download this .json file to your computer.
Step 3: Google Search Console Setup
Google will block the API if the service account does not have permission to manage your site.
1. Go to Google Search Console and select your website.
2. Go to Settings > Users and permissions.
3. Click Add User, paste the iam.gserviceaccount.com email address, and set the permission to Owner (Full or Restricted will not work).
Step 4: Finalize in WordPress
.json file you downloaded from Google Cloud.XML Sitemaps are passive. They simply leave a list of URLs on your server hoping Google comes to read them eventually. The Indexing API is active—it pushes a notification directly to Google's servers demanding an immediate crawl. You should use both: your SEO plugin (like Yoast/Rank Math) for sitemaps, and this plugin for instant indexing.
Google imposes a strict 200 URL/day quota on the Indexing API. The plugin pings Google instantly, which may trigger a 429 Error if you bulk import hundreds of posts at once. Please be mindful of Google's daily quotas when publishing or importing in bulk.
If you receive a cURL error or server timeout, your web host is likely blocking outgoing HTTP requests to googleapis.com. Contact your hosting provider to ensure your server firewall allows outgoing cURL requests.
This means you forgot to click the blue "Enable" button for the Web Search Indexing API inside your Google Cloud Console project.