| 开发者 | alexmorgandev |
|---|---|
| 更新时间 | 2026年11月4日 02:21 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/seo-sentry/.SEO Sentry is a WordPress SEO monitoring plugin that detects changes to important technical and on-page SEO elements. It can monitor noindex and robots directives, titles, meta descriptions, canonical URLs, schema markup, H1 headings, redirects, HTTP errors, robots.txt, XML sitemaps, and other SEO signals.
No. SEO Sentry monitors SEO output and records changes. It does not automatically rewrite titles, change canonicals, edit robots.txt, modify schema, or change indexing settings.
No. Your SEO plugin can continue managing titles, meta descriptions, canonicals, schema, sitemaps, and other SEO settings. SEO Sentry provides a separate monitoring layer that helps detect when those outputs change.
The first successful check creates the baseline for that page. There is nothing to compare during the first check. Findings appear when a later check detects a difference from the saved baseline. The SEO health check on the dashboard shows the result of the first check immediately. It shows problems that already exist, for example a noindex page or a missing sitemap.
Yes. You can select multiple pages from public WordPress post types or add multiple URLs at once. Monitoring can also be paused, resumed, or removed in bulk.
If the robots meta directives change and noindex appears, SEO Sentry records the change and grades it according to its severity. If your email alert threshold includes that severity, the finding can also be included in the email digest for that check run.
Yes. SEO Sentry can detect when a canonical tag changes, disappears, or begins pointing to another domain.
Yes. SEO Sentry monitors structured data found on the page. It can detect schema types being added or removed and JSON-LD that no longer parses correctly.
Yes. SEO Sentry monitors robots.txt for changes and can raise a critical finding if the file begins blocking crawling across the whole site. It also checks supported AI crawler directives.
Yes. SEO Sentry checks whether the XML sitemap is reachable and valid and can detect significant drops in the sitemap URL count.
Yes. SEO Sentry can record requests from supported AI crawler user agents such as GPTBot, ClaudeBot, PerplexityBot, and CCBot. It also checks robots.txt rules associated with supported AI crawlers and services. Crawler activity indicates that a crawler requested the site. It does not mean the content will necessarily be indexed or appear in AI-generated answers.
SEO Sentry schedules an automatic re-check approximately 90 seconds after a plugin, theme, or WordPress core update. This is designed to help identify SEO changes introduced by software updates.
You can choose hourly, twice daily, daily, or manual-only monitoring. Scheduled checks use WordPress scheduling functionality.
No. SEO Sentry groups qualifying findings from a check run into one email digest rather than sending a separate email for each finding. You can also choose the minimum severity required before an email is sent.
Scheduled page checks run separately through WordPress scheduling rather than as part of rendering normal visitor pages. AI crawler tracking only applies when a supported crawler user agent makes a request. As with any scheduled WordPress task, actual resource usage depends on the number of monitored pages, check frequency, hosting environment, and site configuration.
No. The free version does not require an SEO Sentry account, API key, or external monitoring service.
No. The free version does not send usage telemetry or monitoring data to the plugin developer. Monitoring information is stored in your WordPress database.
Yes. Monitoring can be paused and resumed for individual pages or multiple pages in bulk.
Yes. Each site maintains its own monitored pages, findings, history, and settings.
Deactivating the plugin keeps its stored data so monitoring can be resumed later. Deleting the plugin removes its plugin-specific tables, options, scheduled events, and cached values.