Bulk URL inspection in Search Console: the index status of forty pages in one table
Which pages are indexed and which are not? Bulk inspection returns index status, last crawl and canonical mismatches in one table. Quota and practical limits.
Team Tecrube
Automazione marketing
What an inspection tells you
A URL inspection tells you four things about a page: whether Google has indexed it, when it was last crawled, whether the canonical you declared matches the one Google selected, and whether the page carries mobile or structured data issues.
The problem is that the Search Console interface makes you do it one page at a time. Checking forty product pages means forty separate lookups. Because the Tecrube connector brings Search Console into Claude and ChatGPT, “put the index status of these forty URLs in a table” is a single command, and as a read it spends no credits.
When to run a bulk inspection
In three situations: after publishing a new series of category or campaign pages, after a site migration or URL structure change, and when you see an unexplained drop in organic traffic.
If a furniture store, for example, has published thirty product pages for the new season, a bulk inspection a week later shows which pages are still “discovered, not indexed”; you want to know that before spending ad budget on them.
Even without a major change, inspecting your priority pages once a quarter catches pages that quietly drop out of the index early.
Canonical mismatch, the biggest time sink
If the canonical you declare on the page differs from the one Google selected, ranking signals are flowing to another URL. Common causes: parameterised URLs serving the same content, both http and https versions being live, filter pages carrying the same text as the main category.
Seeing the “declared” and “selected” columns side by side in the bulk table exposes the issue in minutes. The fix is usually on the page side: correcting the canonical tag, adding a redirect or merging thin pages.
Quota and practical limits
Google applies a daily quota per property for URL inspection; inspecting thousands of pages in one go is not possible. Tecrube tells you in the preview how many URLs will be inspected and whether the quota suffices; for large sites, starting with priority pages is the right approach.
Bulk inspection does not speed up indexing; it only shows status. Keeping the sitemap current and adding internal links does the real work for pages you want indexed. Submitting a sitemap is the one write in Tecrube's Search Console tools; it is previewed and sent to Google on your approval.
What to do with the results
Split the table into three groups: indexed and clean, not indexed, and canonical mismatches. The second group needs content and internal links, the third needs a technical fix. A page returning “not found” is fine if you removed it; if it is still live, it points to a server or redirect error.
Do not forget the paid side: using a non-indexed page as a final URL in Google Ads lowers Quality Score. In the same chat you can say “list the ads using these URLs” and check both sides at once.
An example bulk inspection flow
In a Claude chat connected to Tecrube the flow goes like this. First you say “list the product pages in my sitemap published in the last two months”; the list arrives. Then you ask “put the index status, last crawl date, and declared and selected canonical of these URLs in a table”. The table is ready within minutes and spends no credits.
Next you have the table filtered: “show only the non-indexed pages and canonical mismatches, with a likely cause for each”. The assistant might report that five pages create duplicate content through a filter parameter while three have not been crawled yet. The technical fix goes to your team; a request to resubmit the sitemap for the uncrawled pages arrives as a preview.
Two weeks later, repeat the inspection on the same URL list and ask for a comparison of the two tables. Seeing which fix worked is the shortest route to not repeating the mistake on the next series of pages.
You can tie this flow to the ad side as well. If one of the non-indexed pages is a campaign's final URL, that campaign's landing page experience score may stay low until the page is indexed. In the same chat, “list the ads using non-indexed URLs and suggest an alternative landing page for each” brings both sides into one table; if a URL change is needed it is applied through a preview.