Most Search Console users interact with coverage reports reactively — checking after a manual action or when traffic drops. Nexora Pulse is built for systematic indexing analysis: it pulls GSC data on a regular cadence, segments it by URL pattern, property, and device, and surfaces anomalies that the native Search Console interface doesn’t prioritise.
What Pulse tracks
Pulse connects to the GSC API and imports coverage, performance, and sitemap data into a structured index. From there it segments URLs into status groups — Valid, Valid with warnings, Excluded, Error — and tracks changes to those groups over time. This gives you a rolling view of indexing health rather than a single snapshot.
The key metrics Pulse monitors include:
- Coverage status changes per URL and URL group
- Submitted vs indexed ratio across sitemaps
- Crawl anomalies (discovered not indexed, crawled not indexed, soft 404)
- Click, impression, CTR, and position data per query and URL
- Opportunity scoring — pages with impressions but low CTR or ranking positions 5–20
Opportunity scoring
Pulse calculates an opportunity score for each URL based on impression volume, current position, and CTR relative to average for that position range. A page ranking at position 8 with 2,000 monthly impressions and a 2% CTR scores higher than a page at position 3 with 50 impressions — because the volume-weighted improvement potential is greater.
This prioritisation surfaces the URLs where a title tag refinement, content update, or internal link change is most likely to produce a measurable traffic lift. The lab articles on this site document specific experiments we’ve run against these recommendations.
Crawl anomaly detection
The ‘Crawled — currently not indexed’ and ‘Discovered — currently not indexed’ statuses are common in large WordPress installs but hard to act on from the native GSC interface. Pulse groups these URLs by URL pattern (taxonomy pages, paginated archives, parameter-heavy URLs) and surfaces them with their crawl frequency and last seen dates. You can identify whether the pattern is structural (e.g., all paginated /page/N/ URLs are excluded) or content-specific (individual posts are not being indexed).
GSC export views
For experiment workflows, Pulse supports date-ranged exports of performance data segmented by dimension — device, country, query type, page. These exports are designed to support A/B test evaluation: you can compare performance for URLs you modified against a control group during the same window, filtered to remove seasonal noise.
To see Pulse in action on your GSC property, submit a demo request with your domain and a brief description of your indexing goals. The walkthrough will be configured to your property data.