The playbook
Crawlability: Metrics and Measurement
Measure crawlability by defining important undiscoverable URLs precisely enough that two people can reproduce the result from the same records. Keep the reporting unit, date basis, and scope visible. Without those definitions, a change in the report may reflect a changed calculation rather than a changed customer outcome.
Put the task in context
Important detail pages should have ordinary linked paths from useful category or topic pages. A page accessible only after typing a query into an internal search box may be difficult to discover. Test the path to a sample of deep pages from the public site.
Create a metric definition
| Definition field | What it must explain |
|---|---|
| Measure | important undiscoverable URLs |
| Unit | What one page or query record or completed outcome represents |
| Included records | The scope identified by URL and discovery path |
| Date basis | The event date or period used to include a record |
| Exclusions | Tests, duplicates, or other records outside the agreed definition |
| Source owner | analytics owner |
Separate delivery checks from outcome measures
A delivery check asks whether the team completed a specific task, such as check navigation and contextual discovery paths. An outcome measure asks what happened for the user or business afterward. Keep both visible. Completing the task is useful evidence of execution, but it does not by itself prove that the broader outcome improved.
Worked arithmetic example
Suppose an illustrative review includes 80 eligible records, and 60 satisfy the explicitly defined completion condition. The completion share is 60 ÷ 80 × 100 = 75%. This is hypothetical arithmetic, not an industry benchmark or a predicted improvement. It describes only the population and condition you defined.
For crawlability, explain the condition before applying that calculation. If the question is whether the team can reduce unnecessary URL generation in filters and parameters, a record counts only when the evidence demonstrates that condition. Do not replace missing outcomes with successful ones just to complete a report.
Compare like with like
Keep the scope, date basis, and exclusions consistent between observations. If discovery path changes meaning between periods, note the change and rebuild a comparable view where possible. A rate can also move because the composition of the underlying group changed, even when individual performance did not.
Investigate an unexpected result
- Check whether the underlying URL records are complete.
- Look for this known failure: creating valuable pages reachable only through internal search.
- Verify that the process still includes: inspect blocked paths and server errors.
- Reconcile a sample with the original record before changing the operating plan.
Use the report to choose an action
If the evidence supports a correction, add crawlable links from relevant category or topic pages. Record when the change occurred and what should be checked next. Keep uncertainty visible when the sample is small or the observation period is incomplete. The purpose of measurement is a better decision about important undiscoverable URLs, not a favorable-looking number.
Search results and indexing decisions are not controlled by the publisher. Record what your team changed and what was observed afterward. Avoid turning a correlation between a release and a traffic change into a claim of proven causation.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now