Technical audit evidence for your own client reports
Review technical findings, export the CSV, and prepare your agency presentation in your preferred reporting tool. Branded PDF generation and client portals are not currently available in CrawlRaven.
Understand the reporting boundary
An agency report combines evidence, interpretation, and a presentation for a particular client. CrawlRaven supplies technical findings and search context for that process. Your reporting tool supplies the document layout, branding, and delivery. Decide which part you need before comparing plans or expecting a finished client document from the app.
White-label reporting usually means controlling the logo, colors, report domain, or client portal that the recipient sees. Those are separate capabilities from collecting findings. CrawlRaven does not currently provide them. Treat the CSV export as source material that you review and explain, rather than as a branded deliverable ready to send.
- Use the app to inspect findings and their supporting evidence before deciding which issues belong in the client discussion.
- Use your own document or reporting tool for the cover, visual layout, agency branding, and delivery to the client.
Choose the evidence for the client question
Start with the question the client needs answered. A technical review might ask which affected pages need investigation after a deployment. A content review might ask which existing pages deserve attention. These are different decisions. CrawlRaven keeps ranked content opportunities and technical audit findings in separate views, so keep that distinction in the presentation.
For technical work, review severity, category, affected URLs, and the finding details. When Search Console traffic is available, it can help you identify findings on pages that receive search clicks. That context supports prioritization; it does not calculate the ranking improvement a fix will produce or establish that the finding caused a traffic change.
- Include the website, audit date, reporting period, and the specific affected URLs so another person can trace the evidence.
- Keep observed search performance separate from estimates, suggested explanations, and the actions you recommend investigating with the client.
Review access and coverage before exporting
Technical SEO audits are available on eligible paid or trial websites with full workspace access, within a monthly page allowance. Review the completed run and its coverage before treating it as a complete inventory. A crawl that stops early or cannot fetch a page cannot establish that the missing page is healthy.
Keep coverage limitations in the client document. A failed fetch, a page outside the audited set, or unavailable search traffic should remain unknown. Avoid turning a missing value into zero or treating an incomplete run as an all-clear. Record which run supplied the export so later questions can be checked against the same evidence.
- Check the run status and coverage information before selecting findings for the client report or preparing a summary of technical health.
- Retain caveats about incomplete coverage, unavailable traffic, or pages that could not be checked when copying findings into another tool.
Prepare a useful findings presentation
Export the technical findings as CSV and select the rows relevant to the agreed scope. The export includes severity, rule, category, affected URL, detail, effort, available search clicks and impressions, and comparison status. A spreadsheet is useful for reviewing those fields before arranging a shorter presentation around the decisions the client needs to make.
Explain the observation, its practical relevance, the proposed next step, and who will own the investigation. A useful report distinguishes an observed condition from a confirmed defect. For example, a canonical or indexing instruction may be intentional. Check the intended behavior and page purpose before asking a developer to remove or change it.
- Keep a working evidence sheet with the source run, selected rows, and notes supporting each recommendation in the presentation.
- Prepare a concise client summary in your own reporting tool, with links or references back to the supporting findings and affected URLs.
Keep content priorities and outcomes clear
Content opportunities use search evidence and saved priorities to help you decide what to investigate next. Qualified linked GA4 evidence can provide additional context where available. Present those content decisions separately from technical findings. Combining them in a client presentation is your editorial choice; the app does not provide a single ranking queue combining both workflows.
Use the correct level of attribution. Search Console query metrics describe search performance, while linked GA4 outcomes describe landing pages and visits. Page-level outcomes do not establish conversions for a particular query. Keep the periods, source, and any missing evidence visible when explaining why a page deserves attention or how its performance changed.
- Label each chart or figure with its source and reporting period so search and analytics measurements can be interpreted correctly.
- Separate observations, proposed explanations, and planned actions instead of presenting a correlation as proof that one change caused an outcome.
Review later audits without overstating progress
After work is implemented, compare a later audit with the earlier run. The comparison can help distinguish new, unchanged, fixed, and not-rechecked findings. Review the coverage of both runs before reporting progress. A finding that was absent because its page was not checked again should not be presented as a verified fix.
A task marked complete in a workflow is a record of intent or reported work, not independent proof that the website changed. Ask the person responsible to confirm the actual edit and its date. Review subsequent search performance over an appropriate period, allowing for other site changes and external events that may also affect the observed trend.
- Distinguish verified fixes from findings whose affected pages were not rechecked, and explain any change in audit coverage between runs.
- Record what was actually implemented and when, then describe later performance as an observation rather than a guaranteed result of the work.
Select branding and delivery separately
If branded PDFs or a client portal are essential to the engagement, choose a reporting tool that explicitly supports them. Check the precise plan, recipient permissions, delivery options, and branding controls. The presence of an export button or an audit dashboard does not establish that a product can host a report on your agency domain.
For sensitive client work, also decide who may access the presentation and where the exported evidence will be stored. If you connect an AI client through MCP, approve only the permissions needed for the workflow. Returned data is processed by that client and its model provider under their policies, so review those arrangements before sharing client information.
- Confirm branding, client access, scheduled delivery, and data-source coverage with the reporting provider before committing to a client deliverable.
- Use the Technical SEO guide for audit behavior and the MCP reference for the current permissions and tool boundaries.
Read the current reporting guides
See the Technical SEO guide, MCP reference, and current plans. The white-label SEO definition explains the branding terminology; the free single-page SEO report generator produces a PDF audit of one URL, without branding controls.
Frequently asked questions
Investigate the evidence behind your SEO work
Start a 7-day free trial. Plans from $29/month.