What should I check before sending a report to someone else?
Use public URLs you have a legitimate reason to inspect. Do not include credentials, secret preview links or personal data in the address. Review an export before sharing it.
Review the PDF reports before sharing. Evidence can quote a contact page or other visible page text. With JavaScript, also inspect what appears after loading. The methodology explains which input supports each finding.
What to do step by step
- Submit a public URL without secret parameters.
- Expect the destination server to receive a request.
- Review report evidence before forwarding it.
- Check email recipients and CC carefully.
- Read the privacy page for operator and processing information.
A practical example
A public product URL is preferable to a private preview link containing a token. Do not make confidential content public merely to run a scan.
A common mistake
Public availability does not mean the content contains no personal information. A PDF can capture contact text or code fragments.
Try the report before checking your site.
Explore the sample report, then enter your own URL to see findings, HTML evidence and a repair plan for your page.
Run your audit
Which URL can you submit for an audit?
An SEO audit needs a URL accessible without your login. An access token does not belong in the input; removing every parameter, however, can change the page being checked.
- Use the public product or service address instead of a private order-management link.
- Keep a functional variant parameter when it is the subject of the check and contains no access credentials.
What requests does the checked website receive?
Fukamo obtains content and technical evidence from the website being checked. The target server may therefore record these requests in its own operational logs.
- Check websites for which you have permission to carry out this inspection.
- For a sensitive service, agree on the permitted URL scope and timing beforehand.
What information can a report contain?
Evidence can include text or HTML from a public page, including names and work email addresses. A PDF is another copy of that information.
- Remove unrelated personal information and login secrets from a support request.
- Check the recipient and every copied address before sending a report by email.
How does optional audit history work?
The audit itself processes the submitted address and fetched content. Browser history and analytics have separate choices; declining them does not disable requests needed to perform the scan.
- Change your choices through Cookie settings in the footer.
- When handing an audit to a client, agree who may receive it and where its copy will be stored.
How to verify the result
The rule-based audit does not use a generative model for evaluation, but it still processes retrieved website data. Consult the applicable service information for processing details.
Primary documentation commission.europa.eu ↗
Frequently asked questions
What should I check before sending a report to someone else?
Read code and text excerpts as well as the summary. Public pages can contain personal contacts or information you do not intend to redistribute. Never submit access tokens or private links. For email delivery, verify both the main recipient and CC addresses.
When the task is complete
The shared document contains evidence needed for the task and the recipients are correct. Hosting and retention are separate operational facts; no generative AI does not mean no data processing.
Related SEO guides
Check a specific page.
Fukamo shows findings, evidence and the next step.
679 rules + SEO, AI readability, performance and accessibility measurements for free.