Indexing

Statistics for all site pages

Bu sayfayı yapay zekâya sor

2 min read

The console’s on-screen reports are capped: 50,000 page changes under Indexing, and the first 3,000 queries over three months under Search queries. Extended statistics is the way around those caps — a downloadable archive with no such limits.

The condition

The archive is generated only if a Sitemap file is hosted on the site and has been downloaded by the indexing bot. This is the detail that catches people: a sitemap submitted through the interface but not reachable at a URL does not qualify. The archive covers pages listed in the sitemap, plus pages whose source carries a rel="canonical" pointing at a page in the sitemap.

Page status archive

Fields per URL:

  • url, httpCode, lastAccess — what the robot found and when.
  • status — the page’s status in search.
  • fromSitemap — whether the URL was in the sitemap.
  • redirTarget — redirect destination.
  • relCanonical — the declared canonical.
  • title and metaDescription — as the robot read them.

Those last two turn the archive into something the interface cannot offer: a site-wide audit of titles and descriptions as Yandex sees them, rather than as the CMS believes it published them. Finding every duplicate title on a fifty-thousand-page catalogue becomes a spreadsheet sort.

Query archive

Queries for which each page appeared over the last seven days, across all devices and regions, with clicks, impressions and average position by impressions. The seven-day window is short, so this is a sampling tool rather than a trend tool — but it is complete within that window, where the on-screen report is not.

How we use it

  1. Download the page status archive.
  2. Pivot by status to size each exclusion category.
  3. Sort by title to find duplicates and truncation.
  4. Filter relCanonical where it does not equal url, which surfaces canonical tags nobody intended.
  5. Cross-check fromSitemap against status to find pages that are submitted and never included.

None of those five questions can be answered from the interface on a large site, and all five are answered in an afternoon with the archive.

Alien Road

Biz bunu nasıl uyguluyoruz

For any site above a few thousand pages we work from this archive rather than the screen, and the first pivot is always relCanonical against url. Plugin-generated canonical tags pointing at the wrong page are the most common serious defect we find on large catalogues, and they are invisible until the whole set is in one table. The sitemap prerequisite is worth checking early — clients often have a sitemap in the console and nothing at the actual URL.

İlgili hizmetler

Share

© Copyright 2026 Alien Road. All rights reserved.