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

Select Sync Sitemap to import pages from your sitemap, or add up to 5 sitemap URLs manually. The sync reports the pages found, added, updated, and removed. Review the imported 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

Select Run audit on a page, or Refresh all to queue every eligible page. An audit scores each page on four dimensions:
  • Technical: meta tags, structure, and speed;
  • Content: quality and AEO readiness;
  • AEO: optimization for AI answers;
  • PageSpeed: the page speed score.
The summary cards show the number of pages tracked and the average of each score. Open a page to see its checks, affected elements, and suggested remediation. Each completed page audit or re-audit costs 5 credits. Refresh all shows the maximum cost before you confirm; credits are reserved when an audit starts and finalized when its results are saved. See Providers and credits. Sitemap sync and audits are reserved for Owners and Managers. Members and Viewers can read the results. See Roles and permissions. Scores summarize the checks implemented by this feature. They are not search rankings and do not guarantee inclusion in an AI answer.

Filter pages

Search pages and filter by status (Pending, Auditing, or Audited), score band (Excellent 80+, Good 60 to 79, Fair 40 to 59, Poor 20 to 39, or Critical under 20), issues, or page type.

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.