菜单
Algorithm update types, diagnosis workflows, recovery strategies, and proactive hardening for Google algorithm changes. Use when diagnosing traffic drops, responding to algorithm updates, or hardening sites against future updates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when a Remotion video needs creative direction: hook, visual sequence, scene purpose, motion restraint, and CTA direction before render.
Use when a Remotion video has timing, sync, transition, caption, pacing, or audio-fit risk and needs editing discipline before render.
Use when /remotion-video needs existing Synthex ElevenLabs, brand-config, Remotion, output storage, Claude, or Hermes integration without adding vendors.
/remotion-video one-shot Remotion command skill and ENTRY POINT for the Remotion Skills Package. Use for video, explainer, ad, promo, reel, intro, social cut, marketing, training, or launch videos. Reads the brief, classifies intent, enforces one single Synthex ElevenLabs voice, emits a production/wave plan, and dispatches the right sub-skills in topological order. Always invoked first.
Use when a Remotion video job needs production gates, render evidence, output discipline, and pass/fail validation before it can be called shippable.
Use when a Remotion video needs a professional marketing QA pass for brand fit, readability, pacing, typography, polish, and not-looking-generated.
| name | google-updates-sentinel |
| description | Algorithm update types, diagnosis workflows, recovery strategies, and proactive hardening for Google algorithm changes. Use when diagnosing traffic drops, responding to algorithm updates, or hardening sites against future updates. |
| metadata | {"author":"synthex","version":"1.0","engine":"synthex-ai-agency","type":"reference-skill","triggers":["algorithm update","google update","core update","spam update","helpful content","ranking drop","traffic drop","penalty","sentinel","algorithm recovery"],"requires":["google-search-console"]} |
| context | fork |
SYNTHEX runs a Sentinel system that monitors site health, tracks Google algorithm updates, and alerts when performance regressions correlate with known rollouts. This skill documents how to interpret Sentinel data, diagnose algorithm impacts, and execute recovery strategies.
| Layer | File | Exports / Purpose |
|---|---|---|
| Orchestrator | lib/sentinel/sentinel-agent.ts | runSentinelCheck(userId, orgId) — full check: seed updates, resolve site URL, check health, run alerts |
runSentinelCheckForAllUsers() — batch check for cron (limit 100 users) | ||
| Algorithm Feed | lib/sentinel/algorithm-feed.ts | KNOWN_ALGORITHM_UPDATES (12 known updates, 2024-2026), seedAlgorithmUpdates(), getRecentUpdates(days), getActiveRollouts(), getAllUpdates() |
| Health Checker | lib/sentinel/health-checker.ts | checkSiteHealth(siteUrl, userId, orgId) — score 0-100 from GSC + PSI data |
getSnapshotHistory(userId, siteUrl, days), getLatestSnapshot(userId, siteUrl) | ||
| Alert Engine | lib/sentinel/alert-engine.ts | runAlertEngine(current, previous, recentUpdates, thresholds) — compares snapshots, emits alerts |
| Types | lib/sentinel/types.ts | CoreWebVitals, SiteHealthReport, AlertThresholds, DEFAULT_THRESHOLDS, AlertType, AlertSeverity |
| Cron | app/api/cron/sentinel/route.ts | Runs runSentinelCheckForAllUsers() on schedule |
| Manual trigger | POST /api/sentinel/check | Triggers sentinel check for the authenticated user |
| Models | Prisma: AlgorithmUpdate, SiteHealthSnapshot, SentinelAlert | Persistent storage for updates, snapshots, and alerts |
From DEFAULT_THRESHOLDS in lib/sentinel/types.ts:
| Alert Type | Severity | Threshold | Description |
|---|---|---|---|
ranking-drop | warning | Position worsens by 20%+ | Average position declining |
ranking-drop | critical | Position worsens by 50%+ | Severe ranking regression |
traffic-drop | warning | Clicks drop by 30%+ | Traffic volume declining |
traffic-drop | critical | Clicks drop by 60%+ | Major traffic loss |
crawl-error-spike | warning | Coverage errors increase 50%+ | Crawl error surge detected |
cwv-regression | warning | LCP >3.0s | Largest Contentful Paint failed |
cwv-regression | warning | INP >300ms | Interaction to Next Paint failed |
cwv-regression | warning | CLS >0.25 | Cumulative Layout Shift failed |
algorithm-update | critical | Traffic drop during active high-impact rollout | Correlated algorithm impact |
algorithm-update | info | First snapshot recorded | Baseline established |
Sentinel alert triggered
|
+--> What alert type?
|
+--> algorithm-update (correlated with active rollout)
| |
| +--> Identify the update type from AlgorithmUpdate.updateType
| | core / spam / helpful-content / link-spam / other
| |
| +--> Follow type-specific recovery strategy (see above)
| |
| +--> Cross-reference: which pages lost the most?
| fetchAnalytics with dimensions: ['page']
| Compare 28 days before vs during rollout
|
+--> traffic-drop (no active rollout)
| |
| +--> Technical issue investigation:
| | 1. Check server errors in coverage (GSCSnapshot)
| | 2. Check robots.txt for accidental blocks
| | 3. Check for recent deploys that may have broken pages
| | 4. Check CWV regression (SiteHealthSnapshot.coreWebVitals)
| |
| +--> Competitive investigation:
| Invoke competitive-local-strategy skill
| Check if competitors published superior content
|
+--> ranking-drop
| |
| +--> Single page or site-wide?
| | Use fetchAnalytics dimensions: ['page'] to identify
| |
| +--> Single page: content or technical issue with that URL
| +--> Site-wide: algorithm impact or domain-level issue
|
+--> crawl-error-spike
| |
| +--> Check coverage report details
| +--> Server errors: check hosting, SSL, CDN
| +--> Redirect errors: audit redirect chains
| +--> Soft 404s: fix page content or return proper 404
|
+--> cwv-regression
|
+--> Which metric failed?
| LCP >3.0s: check image sizes, server response, render-blocking resources
| INP >300ms: check JavaScript execution, main thread blocking
| CLS >0.25: check layout shifts from ads, images without dimensions, dynamic content
|
+--> Run PageSpeed Insights for detailed recommendations
SiteHealthReport.coreWebVitals from health-checker.ts
Protect against future algorithm impacts:
Computed by computeHealthScore() in lib/sentinel/health-checker.ts:
| Component | Weight | Scoring |
|---|---|---|
| Average position | 30 points | Position 1 = 30pts, position 10 = 18pts, position 50+ = 0pts |
| Click volume | 20 points | 1,000+ clicks = 20pts, scales linearly down |
| Coverage errors | 20 points | 0 errors = 20pts, 50+ errors = 0pts |
| Core Web Vitals | 30 points | 10pts each for LCP, INP, CLS passing thresholds |
| Score | Status | Action |
|---|---|---|
| 80-100 | Healthy | Maintain current practices; monitor for changes |
| 60-79 | Attention needed | Investigate weakest component; address before it worsens |
| 40-59 | At risk | Multiple components degraded; prioritise fixes immediately |
| <40 | Critical | Significant issues across the board; emergency audit required |
| Frequency | Mechanism | Purpose |
|---|---|---|
| Daily (automated) | Sentinel cron (/api/cron/sentinel) | Full health check + alert generation for all users with websites |
| Real-time (event-driven) | SentinelAlert table | Persisted alerts with severity, type, and related update ID |
| On-demand | POST /api/sentinel/check | Manual trigger for immediate health check |
| Manual curation | KNOWN_ALGORITHM_UPDATES array | New updates added to lib/sentinel/algorithm-feed.ts as Google announces them |
When Google announces a new algorithm update:
KNOWN_ALGORITHM_UPDATES in lib/sentinel/algorithm-feed.tsname, updateType, announcedAt, rolloutStart, rolloutEnd (null if ongoing), impactLevel, description, sourceUrlseedAlgorithmUpdates() function will upsert it on next cron runrolloutEnd once Google confirms the rollout is completeReference skill: This is a read-only architecture guide — it documents existing systems and does not generate creative or code output. No capability uplift block is needed.