Start with the question
A crawl is a configured observation, not a complete description of a site. Record the starting URLs, include and exclude rules, rendering settings and limits. Without those, a missing page may reflect crawl configuration rather than a site defect.
A workflow you can check
Use the following steps as a small acceptance test. Keep the underlying observations with your notes so someone else can review the conclusion.
- Confirm the connector and setup through the crawler provider’s documentation.
- Use a small permitted site section as the acceptance test.
- Inspect status codes, canonicals, indexability and inlinks in raw results.
- Repeat the test after a known change and check that the evidence updates.
Interpret the evidence
MARqentic is not an SEO Spider controller. Keep externally collected crawl evidence labeled when combining it with search research. Prioritize shared template problems with verified examples rather than turning every crawler warning into a required engineering task.
A prompt to adapt
Replace the inputs with your own approved examples. Ask the assistant to explain its scope before starting research.
Review this crawl export and configuration. Group findings by likely root cause, identify evidence gaps and suggest a small set of URLs to inspect before changing templates.