Technical audits & site health
Find technical and content barriers, prioritize repairs, and check what changed after a fix.
Product guide2 min read
Understand what blocks discovery
Technical Audit organizes website findings into a clearer health picture. Review crawl access, indexability, metadata, links, performance, mobile readiness, and answer-readiness findings where available. A crawl describes what the scanner could reach at that time.
Turn findings into a repair plan
- 1
Confirm the scope
Check the project domain and the pages included in the crawl. Review crawl status before relying on an incomplete result.
- 2
Inspect affected pages
Open the issue context and review the relevant pages. Distinguish an intended configuration from a genuine blocker.
- 3
Fix, then verify
Prioritize access and indexing problems before smaller refinements. Apply approved changes through your website workflow, then run the relevant check again.
Interpret health scores carefully
- A healthy crawl does not mean a search engine has indexed every page or will cite it.
- Authentication, robots rules, rate limits, and temporary failures can limit scan coverage.
- Do not remove intentional noindex rules, redirects, or access controls simply to increase a score.
- Where repository investigation or fixes are available, review the proposed change and its permissions before approval. A recommendation is not a completed deployment.