Understand URL Inspection quotas and daily limits

Learn why inspection stops and why restarting does not restore quota.

Last checked 21 August 2026

Google limits URL Inspection API calls. TechDash adds a lower safety allowance so scheduled monitoring does not consume the full published per-site quota.

Google's published limits

Google currently publishes these URL Inspection API limits:

  • 2,000 requests per day for one Search Console site
  • 600 requests per minute for one site
  • Additional, much larger limits for the Google Cloud project

Google can enforce project or service limits independently of TechDash. Published limits can also change, so Google's usage-limits page is the authority for the external quota.

TechDash's safety allowance

TechDash currently allows at most 1,800 URL Inspection request attempts per saved website connection and property on one UTC date. A UTC date runs from 00:00 through 23:59 UTC, which may not match your local calendar date.

The allowance counts attempts, not successful results. Retries also use allowance, so a day with errors can produce fewer than 1,800 successful inspections. Google applies its own per-site and project accounting independently. Another tool using the same property can consume Google's quota even though those calls were not made by this TechDash connection.

TechDash also controls request rate and concurrency. These controls can spread work over time even when daily allowance remains.

Why restarting does not help

TechDash persists daily usage and exhaustion. Closing and reopening the app reads the same state. Reconnecting to Google does not restore either Google's quota or TechDash's allowance.

When TechDash's allowance is used up, that UTC date is exhausted for the saved website connection and property. No more URL Inspection attempts start under that allowance for the date. At 00:00 UTC, the next date receives a new allowance. Google controls its own reset timing, so Google may still return a quota response after TechDash moves to a new UTC date.

Google can also explicitly report daily quota exhaustion before TechDash reaches its safety limit. In that case, TechDash stops starting more inspection calls and waits before trying again. A rate limit is different from daily exhaustion: it can pause or slow work without proving that the whole UTC-date allowance has been consumed.

How pages are prioritized

For each connected website, TechDash considers enabled monitored URLs in this order:

  1. The homepage first
  2. Other paths in alphabetical order

It stops when allowance is unavailable. If the enabled set is larger than the available daily allowance, later alphabetical paths may receive fresh evidence less often.

Disabling unimportant monitored pages removes them from scheduled URL Inspection. Removing a page also removes it from the queue, but use those controls based on monitoring needs rather than solely to chase the quota.

What you see when quota is reached

TechDash does not currently show a remaining-allowance counter or a page-by-page quota balance. You cannot use the interface to see, for example, that a precise number of attempts remains.

When the local 1,800-attempt allowance is exhausted, TechDash reports Daily URL Inspection safety allowance exhausted. This resumes later. Google can separately cause Daily Search Console allowance reached. This resumes later. or Google rate limit reached. TechDash will retry automatically. These messages identify the condition but do not expose the remaining allowance.

For scheduled inspection, quota and rate-limit conditions stop or defer work without creating an SEO incident. Missing fresh evidence is not evidence that Google cannot crawl the page. Inspection checks evaluate successful stored Google evidence as pass or fail; a URL without a successful result is omitted rather than failed.

Use Queue Status to review Search Console URL inspection waiting and active jobs. A backlog shows that work remains, but it is not a quota meter. An empty queue does not prove that every enabled URL received a result.

Existing inspection evidence remains available after quota is reached. Check its request time and Google's last crawl time before acting. Old evidence may describe a problem that has already been fixed. Verify current behavior with Search Console's interactive URL Inspection tools, then allow a later successful TechDash inspection to store newer evidence.

What to do

  • If the UTC date is exhausted, wait for the next UTC date instead of restarting repeatedly.
  • Keep TechDash running and online so later hourly sweeps can resume.
  • Keep the website unpaused.
  • Enable monitoring only for pages that matter.
  • Investigate repeated authorization or property errors separately from quota.
  • If Google quota errors recur with a small monitored set, keep the exact message, note the UTC date and time, and contact support.

Sources

Related articles