{"id":70,"date":"2026-10-23T22:50:49","date_gmt":"2026-10-23T14:50:49","guid":{"rendered":"https:\/\/glossary.clawoxy.com\/?p=70"},"modified":"2026-10-23T22:51:25","modified_gmt":"2026-10-23T14:51:25","slug":"coverage","status":"publish","type":"post","link":"https:\/\/www.clawoxy.com\/glossary\/coverage\/","title":{"rendered":"Coverage"},"content":{"rendered":"\n

Coverage describes how much of the intended collection a crawler actually captured. It is not simply the number of rows in an export: a large result can still miss important sections, dates, or page types.<\/p>\n\n\n\n

Define the denominator<\/h2>\n\n\n\n

Before measuring coverage, state what counts as the target set. It might be URLs from a sitemap, products in a catalog, pages within a date range, or records returned by a defined query. Then count successful, valid results against that scope. If the total is unknown, report a proxy\u2014such as discovered URLs processed\u2014and label it clearly.<\/p>\n\n\n\n

Break results down by useful dimensions: section, page type, status code, or crawl date. This helps distinguish a parser failure from pages the crawler never discovered. Track missing required fields separately from pages that were never fetched; they represent different gaps.<\/p>\n\n\n\n

Coverage is a measurement, not a guarantee of completeness. Sites change, links may be inaccessible, and the target set may be ambiguous. Preserve the scope and exclusions with each run so future comparisons mean the same thing.<\/p>\n\n\n\n

Sources<\/h2>\n\n\n\n