---
title: "Google algorithm update checker | SEO Skill"
description: "Compare unusual Search Console traffic dates with confirmed Google ranking updates without treating a matching date as proof of what caused the change."
canonical: "https://seoskill.dev/docs/reports/update-correlation"
language: "en"
---

# Google algorithm update checker

Check whether a search change overlaps a confirmed Google ranking update window. Matching dates are useful context, but they do not prove the update caused the movement.

## Install and run the tool

Install the CLI once, then run `seo start` to connect your site and Google data. After setup you can run this tool yourself or ask your agent to run it.

Install the SEO CLI globally.

```
npm i -g seo
```

Run setup after installation.

```
seo start
```

Compare traffic movement with confirmed Google update windows.

```
seo update-correlate --project example
```

## What the tool gives you

Compare unusual Search Console traffic dates with confirmed Google ranking updates without treating a matching date as proof of what caused the change.

Best for

A traffic anomaly falls near dates listed on Google’s Search Status Dashboard.

Needs

Search Console traffic anomaly result

You get

Compare unusual Search Console traffic dates with confirmed Google ranking updates without treating a matching date as proof of what caused the change.

Use next

Review winners and losers around a Google update

Every report follows the same rules for missing data and outside estimates.[See how report data works](https://seoskill.dev/docs/reports#how-report-data-works).

## What you need before you run it

The report uses the information below. Optional sources are only used when you ask for them.

### Search Console traffic anomaly result

Provides the observed movement, baseline, recent window, and significance evidence.

### Official Google ranking update windows

Provides confirmed rollout dates from Google Search Status.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### You need winners, losers, page patterns, and known site changes around a confirmed update window.

Run the update postmortem. It anchors matched Search Console comparisons to the official window, inspects segment and page patterns, and keeps migrations, releases, tracking changes, and other confounders visible.

Google update postmortem

](https://seoskill.dev/docs/reports/update-postmortem)

### You need proof that a Google update caused a traffic change.

No automated report can prove that from timing overlap. Compare affected and unaffected segments, representative pages, known site changes, demand, seasonality, and later recovery evidence. Update correlation only establishes whether the dates overlap.

Needs more evidence

## Use the tool with an agent or in code

The command above is enough for most work. These options let an agent, script or application run the same tool with explicit input and structured output.

### CLI

Use the report catalog when an agent, script or CI job needs predictable JSON instead of the normal terminal output. Check the current input first, then run the tool with the validated parameters.

Check the current input before the agent or script runs the tool.

```
seo reports describe update-correlation --json
```

Once the input is valid, run the tool through the report catalog.

```
seo reports run update-correlation --params '{"site":"sc-domain:example.com","days":90,"recentDays":7,"paddingDays":2,"refresh":false}' --json
```

### MCP

An MCP agent follows the same two-step flow. It inspects the current schema, fills the required fields and only then runs the tool.

Ask the MCP server for the current tool input.

```
{
  "id": "update-correlation"
}
```

Run the tool after the agent has checked and filled the input.

```
{
  "id": "update-correlation",
  "params": {
    "site": "sc-domain:example.com",
    "days": 90,
    "recentDays": 7,
    "paddingDays": 2,
    "refresh": false
  }
}
```

### TypeScript

Install the package in a Node 22 project when your application needs to run the tool directly. The result includes the same evidence, warnings and limits returned through the CLI and MCP server.

Add the SEO package to your project.

```
npm install seo
```

Run the tool from your TypeScript application.

```
import { executeReport } from 'seo/mcp'

const result = await executeReport(
  'update-correlation',
  {
  "site": "sc-domain:example.com",
  "days": 90,
  "recentDays": 7,
  "paddingDays": 2,
  "refresh": false
},
)

console.log(result)
```

## What to do next

Use the matching update window as context for the investigation, not its conclusion. Inspect the pages and queries that moved, then run a postmortem after the comparison window has settled.

1.  01Use the update postmortem workflow to inspect winners, losers, and known confounders.
2.  02Audit representative pages before making template-wide changes.

## Related reports

[

Review Search Console winners and losers around a confirmed Google update window and keep timing evidence separate from a claim of cause in the final report.

Google update postmortem

](https://seoskill.dev/docs/reports/update-postmortem)[

Compare Search Console movement by page, query, country or device to find which segment explains a wider gain or loss across the selected dates.

SEO segment impact report

](https://seoskill.dev/docs/reports/segment-impact)[

Audit one URL for technical SEO, metadata, canonicals, schema, links and Search Console queries. See the live evidence before changing the page.

SEO page audit

](https://seoskill.dev/docs/reports/audit-page)

## Sources used by this tool

These primary sources define the provider data or search controls used by the result.

-   [Search Console Search Analytics API guidance](https://developers.google.com/webmaster-tools/v1/how-tos/search_analytics)
-   [Google Search Status Dashboard](https://status.search.google.com/products/rGHU1u87FJnkP6W2GwMi/history)