Pages
Every page Numative tracks, when it went live, how it is performing now, and the 404s and site searches your visitors hit along the way.
The Pages section is your site as an inventory rather than a traffic total: one row per page, with the date it went live beside how it is doing now. That pairing is what makes "this post never took off" and "this post used to work" answerable instead of guesses.
Four lenses share the section, switched with the buttons at the top left: All pages, New pages, Not found and Site search.
All pages
The full inventory, sortable on every column and searchable by path.
| Column | What it shows |
|---|---|
| Page | The path, with the page's title where a crawl has read one. |
| Launched | When the page first appeared, from the sitemap, a crawl, a publish ping or its first pageview, whichever came first. |
| Status | Live, or removed once the page has left the sitemap and stopped responding. Removed pages stay listed with their history. |
| Visitors and Pageviews | Traffic over the selected date range, from whichever source the dashboard is reading. |
| Trend | A sparkline of visitors across the range. Hover a point for the exact figure. |
| Scroll and Time | How far down a visit typically got, and how long the page was actually on screen. Both are measured by the Numative tracker, so a Google Analytics view has no values for them and the columns are left out rather than shown as zero. |
Where a site tracks bots, a Humans/Bots toggle flips the table to crawler traffic, which answers "what are the AI crawlers actually reading" page by page. Very large sites load the most-visited and most-recent pages first; search reaches any other page.
New pages
The same inventory narrowed to pages that went live inside the window, opening on a 90-day view because launches are sparse. It answers the question a top-pages list cannot: did the things I published recently work? Each page is shown with the visitors it drew in its own first days, so a post published last week is compared against other posts' first weeks rather than against a two-year-old page that has had time to accumulate.
Not found
Pages that answered 404, in two cards: the broken URLs people requested, and where they came from.
The second card is the one to act on. A 404 with no referrer is usually a stale bookmark or a scanner. A 404 arriving from one of your own pages is a broken internal link. A 404 arriving from somebody else's site is a backlink pointing at something you moved, and the most valuable redirect you can write today.
http_status property with the pageview. See Enhanced measurements.Site search
What people typed into your site's own search box, in two cards: every term, and the terms that returned nothing.
The empty-result list is the useful half. A term someone searched for and did not find is an unambiguous request for a page you have not written yet. It needs the same page context as the 404 lens: the WordPress plugin sends it, or send search_query and search_results properties with your results pageviews.
One page in detail
Clicking any row opens that page's own view, which is where "why did this move?" gets answered:
- Headline tiles for the window: visitors against the previous period, pageviews, scroll depth, time on page, and visitors in the page's first days live.
- Traffic, this page's own shape over the window.
- What moved it: the sources, countries and devices behind the change, so a drop that is really one referrer disappearing says so.
- Search queries this page ranks for, when Search Console is connected, and whether position, impressions or click-through is what actually changed.
- Speed and errors for this page specifically, including the elements and scripts holding its vitals down.
- Change history and snapshots: every edit detected on the page, with the word-level before and after.
For the site-wide version of the same question, ranked by impact, see Anomalies.