SEO tools

Search Console rankings, backlinks with Domain Rating, Core Web Vitals, content decay and Google algorithm update markers.

Every site gets SEO tools alongside its analytics: Search Console rankings, backlink monitoring, and Core Web Vitals. Backlink and vitals changes write to the same change timeline as change detection, so lost links and vitals regressions appear as markers on the traffic chart next to your own edits.

Rankings

The Rankings section is powered by Google Search Console: it shows the queries and pages you rank for, your average position, clicks, impressions and CTR, and how each moved against the previous period. Search Console data updates daily and costs nothing to pull, so it captures the day a ranking moved without a per-keyword tracking fee.

Why a page moved. When organic traffic to a page changes, Numative reads the cause from Search Console: whether your position slipped (a ranking loss), whether impressions fell while position held (the queries are searched less), or whether click-through dropped at a steady position (often a SERP feature taking the clicks). The same decomposition drives the per-page root-cause panel.

A daily scan tracks links pointing at your site and raises new, lost, and regained events (a link that reappears within 7 days of being marked lost is treated as crawl jitter, not a regain). Daily new and lost counts are always exact; the number of individual links itemized per day is capped by plan size, highest-authority first — from 100 rows per day on the smallest plan up to 10,000 on the largest (per category, new and lost).

  • Your site's own Domain Rating is recorded daily and shown on the Backlinks section with its trend, so the number every link is meant to move is beside the links themselves.
  • Link authority is shown as Ahrefs Domain Rating (0 to 100). Wherever DR appears, the required "Domain Rating by Ahrefs" attribution is shown; that attribution is a condition of the data license.
  • New or lost links from domains with DR 60 or higher count as notable and can trigger email alerts.
  • On first scan, sites with up to 1,000 backlinks get a full baseline snapshot (larger profiles are tracked delta-only), and 12 months of daily new/lost counts are backfilled for the chart.
  • Backlink activity appears as sky-blue markers on the traffic chart.

Core Web Vitals

Numative measures your Core Web Vitals twice over, and the two answer different questions.

  • Your own visitors. The tracking snippet reads each page load's real timings in the visitor's browser, so LCP, INP, CLS, FCP and TTFB are available per page, per country and per device the day a deploy lands. This is the headline, and it lives in the Speed section.
  • The Chrome UX Report. Google's own field data, pulled daily: LCP, INP and CLS, separately for phone and desktop. It covers Chrome only and is a rolling 28-day average, so it moves slowly, but it is what search ranking actually reads. It sits below the real-user report as the secondary reference.

The rest of this section describes the Chrome UX Report half.

  • The Overview shows the current value for each metric, its grade, and a trend drawn against the good, needs-improvement and poor thresholds. Roughly six months of history is pulled from Chrome when a site is first scanned, so the trend is populated immediately.
  • When a metric's grade changes in either direction, a marker is added to the traffic chart. Vitals markers have their own toggle, separate from other site changes.
  • The vitals alert under Alerts sends an email or webhook when a metric drops a grade. Improvements do not trigger alerts.

Each score is the 75th percentile: 3 of every 4 page loads were at least this good. Google recalculates it daily from the last 28 days of visits, so consecutive days share 27 days of the same data. The trend therefore moves slowly, and a single day's change is not meaningful. Comparisons are made against a full 28 days earlier, where the two periods share no visits.

Page-level vitals

Site-level vitals are an origin figure: one score across every page load on the domain, weighted by traffic. It identifies that something regressed, not which page. Numative also collects vitals for individual pages, shown on each page's detail view.

  • Chrome reports a URL only once it has enough traffic of its own, which is a higher threshold than the site as a whole. Numative checks the busiest pages first, and records which pages Chrome has no data for so it does not query them again until their traffic grows.
  • Pages tracked per site scale with plan size: from 15 on the smallest plan up to 480 on the largest.
  • Page-level vitals require per-page traffic data, so they run on sites using the Numative tracker. GA4-connected sites receive origin-level vitals.
  • None of this limits the Speed section, which measures every page from your own visitors and has no per-page cap.
Google limits the Chrome UX Report to 150 queries per minute per project and does not sell additional capacity. Numative queues this work rather than competing for the limit, so requests wait rather than fail. Origin-level vitals for every site are fetched before any page-level vitals, so one large account cannot delay another account's headline metrics.
CrUX only reports origins with enough real Chrome traffic. Sites without field data say so on the card; there is nothing to configure.

Plan limits at a glance

Plans are sized by monthly pageview volume on the pricing slider, and these limits scale with the size you pick. The range across the slider:

LimitSmallest planLargest plan
Backlink rows itemized per day10010,000
Stored backlinks per site1,000100,000
Crawl budget (pages per 6-hour cycle)50020,000
Pages with their own vitals15480

The exact numbers for every size are on the pricing page. The 14-day trial runs backlinks at the smallest plan's depth. Backlink scans query an external data provider, so they run against a metered monthly budget; if it is exhausted, scans pause until the next month.