Crawl health & compliance

Both pages depend on server-side records. The page script cannot supply a status code. Where the records come from is in Server events & log import; the bot list is in Bots & AI crawlers.

ConsoleMonitoringCrawl healthConsoleMonitoringCrawler compliance

What the report shows

Crawl health cards are total fetches, success rate, distinct pages, 404s, and 5xx. Success is a status code below 400. A script record with no status code also counts as success. The trend is split by engine. Open a row for the pages that crawler fetched most.

If a sitemap URL is set, the page compares those URLs with what was fetched, and shows how long new pages from the last 30 days waited between first appearing and each engine’s first fetch. Crawler 404s are not the visitor 404s on Pages.

Crawler compliance fetches your rules file and compares it with real fetches. There are three violation types: fetched while blocked globally, fetched a path marked disallowed, and fetched sooner than the declared delay. You can refetch and rescan. A generator can draft rules for “block training crawlers”, “block answer engines”, or “allow major search engines only”, for you to publish on the site. The file itself cannot stop a fetch. This page is the evidence.

How to use it

Start with the engine table and the 404 list on crawl health. Fix paths that also appear as visitor 404s first. On compliance, open a violating row to copy a block snippet, or add that crawler to the site exclusion rules. To be alerted when one engine’s fetches in 24 hours fall below 30% of its 7-day daily average, turn on Crawl anomaly in notifications.

Limits

With only script collection you do not see status codes or response time, and you do not see crawlers that skip JavaScript. The page shows how many records came from the script and how many from the server. If the rules file is missing or empty, there are no violations.

FAQ

Why is the success rate almost 100%? Script records have no status code, so they count as success. After a log import, 4xx and 5xx split out.

Does adding a crawler to exclusion rules block it? No. Exclusion only stops TapCub from counting it. To refuse it on the server, use the block snippet the page gives you.

SEO & content decay

ConsoleMonitoringSearch performanceConsoleMonitoringContent decay

What the report shows

After an account is connected, search performance shows clicks, impressions, click-through rate, and average position, split by page, query, and country. The trend is clicks and impressions. Rank buckets group queries by average position, weighted by impressions. On the scatter plot each point is a page and the size is impressions. A page in the top 10 positions whose click-through rate is below the median is marked as the set where changing the title and description pays off first. Search data is usually 1 to 3 days late. The page states the date it is current through.

Content decay always looks at 13 weeks of visitors, one number per week, and compares the mean of the peak four weeks with the mean of the latest four weeks. The default channel is organic search. You can switch to all channels or AI sources. Statuses are growing, stable, decaying, severely decaying, and not enough data:

• Severely decaying: the latest four-week mean is under 40% of the peak mean.
• Decaying: under 70%, and the whole series slopes down.
• Growing: the latest four weeks slope up and the gain is over 30%.
• Not enough data: the peak week is under the threshold you set. These pages are left out of the monitored count.

Results refresh once an hour.

How to use it

If search performance is not connected, follow the steps on the page to connect Google Search Console or Bing Webmaster. Baidu does not offer an API for clicks and impressions. After you bind it, TapCub can only push new sitemap URLs. Baidu’s fetch frequency is still on Crawl health & compliance.

On content decay, open a row to compare sources in the first four weeks of the decline with the latest four weeks, and see whether only search dropped.

Limits

With no search account connected, search performance has no clicks or impressions. That is not zero traffic. Search terms recovered from the referrer on Sources are sparse; full queries come from the connected accounts here. See Sources & channels. Content decay does not use search rank. It uses visitors stored in TapCub. Change the threshold or the channel and the list changes.

FAQ

Is a decaying page the same as the change column on Pages? No. The pages column follows the dates you picked. Decay always uses two four-week windows inside 13 weeks, and by default only organic search.

Smaller rank is better. How do I read the chart? The axis starts at position 1 and gets worse to the right. The position is the average synced from the search product, not a rank TapCub computes itself.