Skip to main content
Open Optimize > Site Diagnostics to analyze public pages associated with the monitored brand. Unlike the answer-monitoring pipeline, Site Diagnostics fetches pages. Only submit URLs that Qwairy is permitted to access.

​
Add pages

Use the available sitemap synchronization or URL controls to create the page set. Review the discovered URLs and remove paths that should not be audited. Pages behind authentication, bot protection, or network restrictions may not be accessible. A failed fetch should be investigated separately from a failed page check.

​
Run an audit

An audit can examine technical access, metadata, content structure, and other signals shown in the interface. Open a page to see its current checks, affected elements, and suggested remediation. Each completed page audit or re-audit costs 5 credits. A multi-page run is billed per completed page. See Providers & Credits for the operation table and calculation examples. Scores summarize the checks implemented by this feature. They are not search rankings and do not guarantee inclusion in an AI answer.

​
Work through findings

  1. Separate fetch errors from page findings.
  2. Confirm the current page content in a browser.
  3. Group repeated findings by template or component.
  4. Prioritize according to business scope and implementation risk.
  5. Re-run the relevant pages after deployment.
Use audit history to compare results only when the page set and check configuration are comparable.