Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Google November 2026 Core Update Impact Report: Did It Hit Your Site?

    1

    Classifies every Search Console query and page after a Google core update and returns a FINAL or PROVISIONAL impact report using Google's own before/after method.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Google November 2026 Core Update Impact Report: Did It Hit Your Site?

    Google November 2026 Core Update Impact Report: Did It Hit Your Site?

    Example session with this skill installed

    Did the May 2026 core update hit my standing-desk review site? Here is my Search Console Queries export in Compare mode: 14–20 May 2026 vs 11–17 June 2026.

    • Read your context and instructions
    • Compiled the google november 2026

    Status: FINAL Verdict: LIKELY_CORE_UPDATE_IMPACT
    Rollout: 2026-05-21 → 2026-06-02 (Search Status Dashboard)
    Clicks: 1943 before, 821 after (-57.7%), 11 rows with ≥100 impressions

    Timing checks
    PASS Before window 2026-05-14..2026-05-20 ends before rollout start 2026-05-21
    PASS After window 2026-06-11..2026-06-17 starts ≥7 days after completion (earliest 2026-06-09)
    PASS Windows are the same length (7 vs 7 days)

    Where the clicks went
    LARGE_DROP 3 rows 72% of lost clicks → deep assessment
    SMALL_DROP 2 rows 10% → no drastic change
    CTR_ONLY 1 row 8% → review title/snippet, AI Overview
    LOST 1 row 5% → check indexing first
    DEMAND_DROP 1 row 5% → seasonality check

    Top LARGE_DROP
    best standing desk under 300 420 → 18 clicks position 3.2 → 24.6
    standing desk review 310 → 22 clicks position 4.1 → 27.9
    ergonomic chair comparison 190 → 15 clicks position 5.0 → 21.3

    What not to do: do not edit "standing desk height chart" (2.1 → 3.8, small drop).

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Did the Google November 2026 core update hit your site, or is it Black Friday seasonality, a lost AI Overview click, or a technical break? This skill answers that with Google's own documented method instead of guesswork.

    Google started the November 2026 core update on 10 November 2026 and said the rollout "may take up to 2 weeks". Most traffic-drop analyses go wrong in the same ways: they judge during the rollout, compare the wrong weeks, read site-wide average position, and rewrite pages that were never hurt.

    What it does

    • Timing gate: checks your comparison windows against Google's rules (rollout complete, one-week wait, same length, same weekday) and labels the report FINAL or PROVISIONAL. Exit code 0 or 3, so agents cannot fudge it.
    • Per-row classification of every query and page from your Search Console export: LARGE_DROP (Google's 4 → 29 case), SMALL_DROP (2 → 4), LOST (usually indexing), CTR_ONLY (SERP feature or AI Overview), DEMAND_DROP (seasonality), STABLE, GAIN, NEW.
    • Site verdict: LIKELY_CORE_UPDATE_IMPACT, CHECK_TECHNICAL_FIRST, DEMAND_OR_SEASONALITY, SERP_CTR_CHANGE, MIXED_SMALL_SHIFTS or NO_MATERIAL_IMPACT, with each class's share of lost clicks.
    • 12-point false-positive checklist (data anomalies, manual actions, security, migrations, spam updates, seasonality, search type, brand split) plus a Black Friday 2026 rule.
    • Deep assessment rubric for LARGE_DROP pages, built on Google's people-first content guidance.

    Deliverables: report.md (client-ready), findings.csv (every row with class and action), summary.json.

    Works with a single Search Console Compare-mode export (CSV or the .zip) or two plain exports. Python 3.8+ standard library only; no API keys, no Search Console login, no data leaves your machine. Facts checked against Google Search Central and the Search Status Dashboard on 14 November 2026, and dated inside the skill.

    It reads Search Console exports, so it is limited to the rows Search Console exports (up to 1,000 per table in the UI). It shows correlation with rollout dates, not proof of cause. It does not crawl your site, read Manual Actions or Security Issues, or fetch the Search Status Dashboard on its own; the checklist tells the agent where to look. Column detection expects English export headers. Until Google marks the November 2026 rollout complete and seven days pass, every report is PROVISIONAL by design. No recovery is promised.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Requires

    Python 3.8+
    Google Search Console export

    Permissions

    Allowed Hosts

    status.search.google.com (optional)
    developers.google.com (optional)

    File Scopes

    the
    Search
    Console
    export
    you
    pass
    in
    output
    folder
    (report.md
    findings.csv
    summary.json)

    The script makes no network requests. Optional web access is only for checking rollout status and Google documentation.

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Yes, for monitoring. The report is labelled PROVISIONAL and tells you the earliest date a FINAL report is possible (completion plus seven days for the after-window).

    Google's method, the November 2026 start date and earlier 2026 update dates were checked against Google Search Central and the Search Status Dashboard on 14 November 2026, and the skill tells the agent to re-check rollout status every run.

    It enforces Google's timing rules with an exit code, classifies each row with Google's own small-drop vs large-drop examples, and separates LOST, CTR_ONLY and DEMAND_DROP so you do not mistake indexing, AI Overviews or Black Friday demand for a ranking loss.

    Yes. Pass any update's start and completion dates. Reference dates for the March and May 2026 and December 2025 core updates are included.

    No. The script is standard-library Python that only reads your export and writes files locally.

    New in Business & Operations