How to monitor and manage indexing?

İzleme indexing means answering five questions, and the console has a report for each: when the robot came and what happened, which pages are in search and which were excluded and why, how each section performs, the status of a specific page, and the status of the pages you have marked as important.

The reports and what each is for

• Crawl statistics (Indexing → Crawl statistics) — the history chart plus a table of response codes the robot received. This is the record of events: what the server actually answered, and when.
• Page check (Indexing → Check page) — the status of one URL, desktop or mobile, with the detail behind it.
• Searchable pages — what is in search, what was excluded, and the stated reason for each exclusion.
• Site structure — the same picture per section, which is where a failing template becomes visible.
• Important page monitoring — per-URL surveillance with notifications.

The two controls

Alongside the reports, the console lets you set the crawl rate and check that robots.txt is configured as intended. Those are the only two direct levers; everything else is observation.

How to work the set

Read them in order of specificity. Site-level counts tell you whether something changed. Section-level figures localise it. Response codes in crawl statistics say what the server did. Page check confirms the diagnosis on a single URL. Starting at the specific end — checking individual pages before knowing whether the problem is site-wide — is how audits consume days and produce anecdotes.

The habit worth building

A short weekly pass: My sites for anything that moved, then the section view for whichever site moved, then crawl statistics filtered to the date. Ten minutes, and it catches template failures in the week they ship rather than the month they show up in revenue.