| 开发者 |
lukeaxiomflow
freemius |
|---|---|
| 更新时间 | 2026年8月28日 07:36 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
noindex. Your canonical quietly starts pointing somewhere else. Your sitemap begins returning errors. The site looks fine. The dashboard says nothing. Google notices — sometimes weeks before you do, and Google Search Console reports what its crawler decided, days later, without ever telling you what on your site changed or what changed it.
BuildsByLuke SEO Flight Recorder is the black box for your site's SEO. It records the SEO-critical output of the pages you care about, re-checks them on a schedule and immediately after anything on the site changes, and writes every difference to a flight log — with the site events that immediately preceded it, so the culprit has a name.
What it records, per monitored page
noindex appearing where it shouldn'tProduct or FAQPage type is a critical findingblog_public) — the classic staging-to-production catastrophe, caught even when page checks can't runnoindex appearing — stays critical even then.)
Alerts that respect your dashboard
Changes above your chosen severity arrive by email, once per check, with plain-language descriptions. When a critical finding stops being detected, it is marked resolved and you can get the all-clear. No site-wide nags, no dashboard takeovers — one dashboard widget with the headline, and everything else lives in the plugin's own pages.
Everything here is in the free plugin, uncapped
There is no page limit, no check-frequency tier, no history limit and no feature switched off pending payment.
wp seo-flight-recorder check / status, including --format=jsonGET /wp-json/sfrec/v1/status for scripts and dashboards, with the same manage_options permission the admin screens useSearch Console tells you what Google's crawler eventually decided, on its own schedule — often days or weeks later — and it doesn't watch social tags or canonical values, doesn't run the moment an update finishes, and never names the plugin that caused it. This plugin tells you what your HTML said, within your chosen check window (or ~90 seconds after an update), with the likely cause attached. They complement each other; only one of them is on your side of the fence.
As many as you want, as often as hourly. Neither is limited, and neither depends on paying for anything.
No. Checks run in the background via WP-Cron, fetch your pages with a strict time budget per batch, and store compact snapshots. Nothing runs on your visitors' page loads, and nothing is added to your front end.
No, and that's deliberate. It is strictly read-only: it records, diffs, and alerts. You (or your SEO plugin) stay in charge of what your pages say. A recorder you can trust must never be a hand on the controls.
A snapshot you take deliberately, rather than on a schedule. Before running a batch of updates, click "Arm baseline" — every monitored page is captured as it is right now. Run your updates, then click "Compare against armed baseline" and anything that moved is written to the flight log. It is the same recorder, pointed at a moment you chose.
noindex appearing on a monitored page, the site being switched to "Discourage search engines", a canonical moving to a different domain or disappearing, a schema type vanishing, a monitored page starting to return errors or redirect off-site, robots.txt blocking all crawlers, a broken or invalid sitemap, and an emptied title. Warnings cover meaningful-but-possibly-intended changes (title/description edits, Open Graph changes, H1 changes, sitemap shrinkage). Changes you made yourself by editing the page are logged as informational.
It keeps a short log of site events — plugin/theme/core updates, activations, deactivations, theme switches, SEO-relevant setting changes, and edits to monitored pages. When a check finds a difference, the events since the previous clean check are attached to the log entry. It is honest about uncertainty: entries say "site events immediately before this change", and when nothing happened in the window, it says so.
Yes — with all of them, and with none of them. It monitors the rendered output of your pages regardless of what generates it. It is not an SEO plugin and does not compete with yours; it verifies that whatever your SEO stack promised is actually what your pages serve.
Everything the plugin created: its three tables (pages, snapshots, changes), its options, transients, and scheduled tasks. Deactivating (without uninstalling) keeps your flight log.
sfrec/v1/status REST endpoint is now part of the free plugin, alongside the existing WP-CLI commands.