---
title: "GSC Pulse features — GSC Pulse"
description: "See how the extension turns property-level Search Console data into portfolio priority, evidence, and action."
canonical: "https://gscpulse.behlul.com/features/"
language: "en"
updated: "2026-08-06"
robots: "noindex, follow"
---

[Home](/)›GSC Pulse features

# GSC Pulse features

See how the extension turns property-level Search Console data into portfolio priority, evidence, and action.

## Ten-second decision brief

The first screen identifies the highest-priority property and summarizes the likely cause, scope, estimated loss, concentration, confidence, recent pulse, and the next evidence to open.

### Priority

Which property deserves attention before the others?

### Cause

Does the movement point toward rankings, CTR, demand, device, country, or a small set of pages?

### Scope

Is the change isolated to one property or moving across the portfolio?

### Action

Open the exact page, query, segment, sitemap, or native GSC report.

## Portfolio views

Use a decision view for priorities or a metrics view for clicks, impressions, CTR, position, trend, query movement, and sitemap health. Sort columns, filter properties, save favorites, and use 25, 50, or 100-row pagination.

## Performance evidence

- 7, 28, and 90-day equal-period comparisons
- Estimated click loss
- Contributing pages and queries
- Device and country concentration
- Position buckets for 1–3, 4–10, 11–20, 21–50, and 51–100
- Growing, declining, new, lost, and shared queries
- Optional partial hourly pulse
- [Search Appearance](/glossary/search-appearance/) categories when the API returns them

## Opportunity radar

Directional opportunity candidates include low CTR, page-one proximity, growing queries, declining pages, new visibility, and multiple URLs appearing for the same query.

## Sitemap diagnostics

Each technical card separates what the API confirms from likely checks and repair steps. The exact native detail remains one click away.

## Context notes

Add local notes for migrations, template releases, title changes, campaigns, or editorial events and compare them with the affected period.

## Language and privacy

The interface follows the Search Console language by default and supports manual English or Turkish selection. Search Console access is read-only; working data stays in Chrome local storage.