| 开发者 |
sitealerts
zheynlab |
|---|---|
| 更新时间 | 2026年9月23日 18:16 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
Traffic — August 2, 2026 Traffic dropped 41% Your human traffic decreased sharply compared to recent activity. What this means: A decrease in human traffic means fewer real visitors reached your site compared to your normal activity. This does not always indicate a problem and can happen after website changes, availability issues, visibility changes, broken links, or changes in visitor behavior. Why this alert? The decrease exceeded your configured threshold of 30% by a significant margin, indicating an unusual deviation from your recent traffic pattern. Today: 445 · 7-day average: 754 · Change: -41% Pattern: This alert has appeared for the second consecutive day. Related activity: Detected together with: 404 Errors, Bot Activity. What you should check next: - Verify that your most important pages are available and responding correctly. - Review major recent changes, migrations, deployments, or settings updates that may have affected visitor access. - Check that your site is loading normally and important pages are accessible. - Review recent content updates, deleted posts, or changes to important pages.404 alerts include the top 3 broken URLs with fix suggestions. Bot alerts list the top 3 crawlers by name with visit counts and context. This is just the beginning. The free plugin will keep improving with new read‑only integrations and detection refinements, while more advanced anomaly types — like slow page detection and server error surge detection — are planned for the Pro version. Built for privacy and performance The plugin never phones home. All data is collected, summarized, and stored inside your own database. We use lightweight tables that hold only the last 7 days of aggregated metrics. No personal visitor data is ever saved. No cookies. No front‑end scripts. GDPR‑friendly by design. Zero‑configuration monitoring Install, activate, done. The plugin starts logging data from day one and begins anomaly detection after a 7-day baseline period. No API keys, no tracking codes, no setup wizard. Optional settings are available under Site Advisor → Settings if you want to customize alert thresholds or email notifications. Features
No. It's an advisor, not an autopilot. It tells you what's wrong and what to check, so you stay in full control.
The plugin hooks into WordPress to log page views and 404 errors. Data is aggregated daily and old raw logs are deleted – only the summarized metrics stay.
At the end of each day, via WordPress Cron. You don't need to click anything.
It compares yesterday's numbers to the average of the previous 7 days. A significant deviation triggers an alert. During the first 7 days after activation, the plugin only builds the baseline and does not generate alerts. Anomaly alerts can appear from day 8 onward.
The plugin needs 7 full days of data to understand your site's normal traffic, 404, and bot patterns. After that baseline is built, it starts comparing daily values and generating alerts only when thresholds are exceeded.
The three most-hit broken URLs from that day, with the number of hits and a plain‑English suggestion (e.g., "Set up a redirect from /old-page to /new-page").
The top three bot names (like Googlebot, AhrefsBot) with visit counts and context on whether their activity is unusual.
Absolutely. Upcoming free releases will add read‑only integrations with popular analytics plugins such as WP Statistics, Burst Statistics, MonsterInsights, and Site Kit by Google. Later free security signal integrations are planned for Wordfence and Solid Security. Advanced anomaly types like slow page detection and server error surge detection are planned for the Pro version.
The core plugin is and will remain free, licensed under GPL-2.0-or-later. A Pro version with advanced features is planned for the future, which will help support ongoing development.
No. The plugin has zero front‑end footprint. All processing happens in the background after page load, using efficient database queries. Your visitors won't notice it.
warning and critical alerts in email notifications.info, warning, and critical (previously only info).deflate in browser Accept-Encoding headers.alerts.php configuration file, adding shared alert strings and improving message consistency.stats_date <= %s) instead of excluding it, ensuring accurate 7‑day averages for anomaly detection.critical/warning) is now dynamically calculated based on user‑defined thresholds, making severity levels consistent with each site’s custom settings.top_404_json or top_bots_json values no longer result in malformed alert metadata – now properly handled as empty arrays.FOR UPDATE locking in markAsBot() is now wrapped in an explicit transaction, eliminating race conditions under concurrent requests.TrafficAnalyzer, Error404Analyzer, BotTrafficAnalyzer) – their logic is fully covered by the new Generator architecture.