How do I turn a report into a task a developer can complete?
The PDF uses the existing audit result. Before handing it over, verify the URL, time and scope; add an owner, page purpose and completion criterion to each task.
What to do step by step
- Read the separate outcome counts in the summary.
- Open Items to review and start with critical issues before moving to lower priorities.
- Assign owners to review decisions.
- Preserve passing checks as reference, not extra work.
- Compare the same rule IDs after publication.
A practical example
A useful handover says — “Fix the H1 shown in section 01. Let us decide the variant canonical policy before implementing the review in section 02.”
A common mistake
A report may contain page text or code fragments with personal information. Review it before sharing and send it only to relevant recipients.
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 PDF do you need for the task?
The complete export separates an SEO audit into three PDFs. Items to review contains errors and reviews, Passed contains successful checks, and Repair plan provides working steps.
- Give the developer the plan together with evidence for the selected tasks.
- Use the passed document for regression checks; the scoring methodology explains what the points mean.
What to check before exporting a report
Export uses the existing audit data. Downloading a file does not start another crawl or supply a measurement missing from that result.
- Confirm the audited address, time and page scope.
- For an unavailable measurement, record how to obtain it; do not present it as a successful test.
How to hand a finding to your developer
The PDF supplies the rule and evidence. A person who knows the website must supply decisions about the offer, wording or preferred URL.
- Example task. Render the service name as an H1, preserve its appearance and test two other services.
- Name an approver for contextual decisions, such as the catalogue owner for product variants.
How to share the current report safely
A report is a portable copy of the findings. Check its evidence and recipients before sending; a public page can still contain personal information.
- For email delivery, check the main recipient and optional copied addresses.
- After deployment, run a fresh audit and compare the same rules; PDF page counts can change through layout changes alone.
How to verify the result
Download the complete report for a ZIP with three PDFs, or choose Send by email for the report and repair plan. No account is needed. Check the recipient and any copied addresses before sending.
Primary documentation developers.google.com ↗
Frequently asked questions
How do I turn a report into a task a developer can complete?
Choose a confirmed failure and include the URL, rule identifier, and concrete evidence. Add the expected outcome and retest method. Combine findings caused by a shared template into one task. Keep passing checks as reference rather than turning them into unnecessary work.
When the task is complete
The developer can reproduce the issue and identify a verifiable completion condition. A PDF preserves the original scan context; after deployment, run a new audit rather than rewriting history.
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.