| 开发者 | dimapugash |
|---|---|
| 更新时间 | 2026年9月13日 18:05 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
indexsignal-seo-index-monitor-for-google directory to /wp-content/plugins/, then activate the plugin.
IndexSignal supports WordPress multisite through separate activation and connection on each subsite. Network Activate is not supported.Open IndexSignal, choose the page, and run Check index status. The saved result appears in the overview, the Pages and Indexing screen, and supported WordPress content screens. Google Search Console remains the authoritative source when it is connected; other available checks are shown as detected evidence, not a guarantee.
Common causes include a noindex directive, a canonical URL pointing elsewhere, robots restrictions, redirects or errors, missing discovery signals, duplicate content, or content Google does not choose to retain. IndexSignal reports observable technical signals and separates pages that should be fixed before any indexing workflow is considered.
No. On-page SEO plugins manage titles, descriptions, schema, sitemaps, and related settings. IndexSignal focuses on URL discovery, technical indexability, index-status checks, eligible indexing workflows, and saved monitoring history. They can be used together.
No. IndexSignal never starts a paid check or indexing workflow just because a post is published. You choose the URLs, see the exact cost, and confirm before anything starts.
No. Google Search Console is optional. Available checks and workflows can be used without storing Google credentials in WordPress.
No. Optional Google authorization and tokens stay in the hosted service infrastructure. WordPress stores only a revocable installation token for the connected site.
Yes. The local inventory includes public WooCommerce products and product categories. Out-of-stock status is informational; private, catalog-hidden, noindex, or non-canonical states may block or warn.
No. Google makes every indexing decision. IndexSignal checks technical eligibility, starts only the workflow you confirm, monitors saved evidence, and applies Credit-Back or Money-Back terms only where they are explicitly shown before confirmation.
The installation token is revoked on the hosted service and removed from WordPress. The local site scan is preserved unless you choose to remove local plugin data. Account billing records and remote reports remain subject to the account controls and retention policy.