Check whether a crawl-budget audit fits the problem
Spend effort where crawl allocation could be limiting useful discovery or refresh.
Use this for: Sites considering advanced crawl-budget work.
Compare the size and publishing pace of your site with the actual symptom. Look for important new or changed pages whose fetching is repeatedly delayed, a rapidly expanding URL inventory, or host strain during crawling. A low number of requests alone is not a defect.
A stable 32-page site normally needs working links, a current sitemap and page-level indexing checks first. Targeted diagnostics can still help when a particular page fails. If you have no evidence of an inventory or capacity problem, mark the remaining advanced checks Not applicable and return to ordinary technical maintenance.
Hypothetical example: A service site has 32 linked pages and its updates are fetched promptly. It does not need a target of hundreds of Googlebot requests per day.
- Compare page count and publishing pace with the reported problem.
- Check a few affected pages and a few healthy pages.
- Continue only where a crawl-allocation or host-capacity question remains.
More help and optional notes
If it fails: Start with the affected page and determine which stage fails before proposing site-wide changes.
Retest: Revisit the decision if the inventory, publishing pace or observed crawl behavior changes.
Not applicable: This initial suitability decision applies to every crawl-budget audit.
Optional: the page or URL group, what you found and the next action. Keep confidential data out of shared exports.
Changing this result updates your checkmark and progress immediately. Notes are optional.

