Download the free website audit report template
Use this template when the audit is done but the evidence is still scattered across screenshots, notes, and exports. It gives you a place to write the summary, define the scope, document each finding, assign the work, and record the re-test.
Download the free PDF template
Prefer a file you can edit directly?
- Download the styled Excel audit workbook
- Download the Markdown report outline
- Download the CSV audit tracker
- See a completed website audit report example
There is no email wall. These are working templates with clearly marked fictional examples, not automated audits or certificates. They do not scan a website or certify SEO, security, accessibility, or legal compliance.
If you need findings rather than a place to write them, run a website audit. Roast My Web reviews one public page at a time and produces an editable web report with an optional PDF export.
What is inside the PDF
The downloadable website audit report template is 15 printable pages long. It leaves five full pages for detailed findings and separate pages for the baseline, shared patterns, and re-tests.
| Page | What it helps you do |
|---|---|
| Cover | Record the website, audit date, preparer, business goal, pages reviewed, and report version |
| How to use it | Follow the audit in order and apply consistent priority rules |
| Executive summary | State what should stay, the biggest supported risk, and the first action |
| Goal, scope, and limits | Document the decision, audience, pages, devices, markets, sources, exclusions, and unknowns |
| Baseline and evidence plan | Record metric definitions, sources, periods, baselines, targets, and missing evidence |
| Findings overview | Compare issues by priority, category, page, owner, and status |
| Five finding sheets | Give each problem a full page for the observation, evidence, impact, fix, trade-offs, owner, and re-test |
| Patterns and root causes | Group findings only when the evidence points to a shared cause or template |
| Work plan | Assign work across the next 7 days, 30 days, and later review |
| Re-test record | Compare the observed result with the baseline and target, then close, revise, revert, or collect more evidence |
| Evidence and handoff | Link claims to sources and check that the report is ready to share |
The format is plain on purpose. An audit report should make the next decision obvious, not win a design award.
How to use the website audit report template
1. Define the decision before you inspect the site
Start with the business goal, the pages in scope, and the person who will use the report. "Improve the website" is too broad. "Find the issues stopping qualified visitors from starting checkout on the pricing page" gives the audit something concrete to answer.
Write down what you did not review too. A one-page audit cannot support claims about an entire domain without crawl data, analytics, and evidence from other page templates.
2. Capture evidence before writing recommendations
Recommendations written from memory are hard to defend. For each finding, save enough detail for someone else to reproduce it:
- affected URL and device;
- screenshot or screen recording;
- metric, source, and date;
- test conditions;
- expected result and actual result;
- any uncertainty or missing data.
Do not write "this fix will increase conversions by 25%" unless you have evidence for that number. Explain why the change may help, then name the metric you will check after release.
3. Write one finding per distinct problem
Keep each finding to one problem. If two problems need different owners, fixes, or re-tests, split them. Use this structure:
| Field | Example |
|---|---|
| Observation | The mobile pricing CTA appears after the full comparison table |
| Evidence | Screenshot at 390 px width, captured 2026-08-23 |
| Why it matters | A ready buyer must scroll through every plan detail before seeing the next action |
| Recommendation | Add the primary CTA after the pricing summary and keep the full table below |
| Trade-off | The first screen becomes more commercial |
| Validation | Compare qualified checkout starts from the pricing page before and after release |
Keep observations separate from conclusions. "The CTA is below the comparison table" is something another person can verify. "This is losing 30% of buyers" needs data.
4. Prioritize with consistent rules
The template uses four levels:
| Priority | Use it when | Expected response |
|---|---|---|
| P0 | The issue blocks a critical task, creates material risk, or prevents crawling or conversion | Fix or contain now |
| P1 | The issue has high expected impact and solid evidence, but is not an emergency | Plan next |
| P2 | The issue has lower impact, lower confidence, or depends on other work | Add to the backlog |
| Monitor | The signal is incomplete or the expected benefit does not justify a change yet | Collect evidence |
Priority is not a nicer word for severity. It is a decision about what to do next. Weigh the expected impact against confidence, effort, dependencies, and the business goal.
5. Assign an owner and a re-test
An unowned recommendation is just a note. Give every accepted fix an owner, a due date, and a definition of done. Add the re-test result to the same report so it records what changed, not only what was wrong.
What to inspect in a website audit
Not every audit needs every category below. Pick the checks that can answer the decision you defined at the start.
Technical SEO
For a search-focused audit, verify that search engines can reach, understand, and index the intended page. Check the response status, robots directives, canonical, sitemap membership, internal links, structured data, redirects, and mobile HTML. Use the technical SEO audit guide when the problem extends beyond one page.
On-page SEO and content
Read the page as a visitor with a specific job to finish. Do the title, heading, introduction, sections, and internal links help with that job? Record stale claims, missing evidence, duplicated intent, and pages competing for the same query. The website audit checklist has a broader inspection list.
UX and conversion
Try to complete the primary task on both desktop and mobile. Look for a mismatch between the promise and the page, unclear actions, form friction, poor error recovery, missing trust information, and a confusing next step. Taste is not evidence of user behavior, so use analytics, recordings, interviews, or usability tests when you can.
Performance and accessibility
Test representative pages and devices, then record the tool, conditions, date, and page state. Automated checks catch useful problems, but they do not replace keyboard, screen-reader, zoom, contrast, and task testing. Use current measurements instead of copying generic benchmarks into the report.
How to write the executive summary
Write the summary after the rest of the report. Keep only what someone needs to make the next decision:
- What did you review?
- What is working?
- What is the biggest supported risk?
- What should happen first?
- Who owns that action?
- How will you know it worked?
Put the detailed evidence later in the report. If the findings cannot support a claim, it does not belong in the summary.
PDF template, editable template, or generated report?
Pick the version that fits how you plan to work.
| Option | Best for | What you get |
|---|---|---|
| Excel workbook | Managing a real audit through handoff and re-testing | Six styled sheets, filters, dropdowns, status colors, formulas, and worked examples |
| PDF template | Workshops, print review, and a fixed handoff structure | Fifteen blank, printable pages |
| Markdown outline | Writing in a text editor, Notion, or a repository | Editable headings and tables |
| CSV tracker | Importing findings into another tool | Portable issue register with detailed fields |
| Sample report | Seeing how evidence and recommendations fit together | A worked example |
| Roast My Web audit | Generating findings for one public page | Editable web report and optional PDF export |
Need the longer writing guide rather than the downloadable files? Use the website audit report template guide. The two pages have different jobs: this page owns the download intent, while the guide explains how to write and customize a report.
Limitations to state in the report
A report without limitations looks more certain than the evidence allows. Common limitations include:
- only one page or template was reviewed;
- analytics or Search Console access was unavailable;
- the crawl ran without authentication;
- tests used a simulated device or connection;
- accessibility checks were automated only;
- conversion impact is a hypothesis until measured;
- security checks were observational and not a penetration test;
- recommendations have not yet been tested in production.
Do not bury these notes in a footnote. Scope changes what every finding means.
Frequently asked questions
Is the website audit report template free?
Yes. You can download the Excel workbook, PDF, Markdown outline, and CSV tracker without giving us an email address. They are working templates, not completed audits.
Is this an SEO audit report template?
Yes. The structure works for technical SEO and on-page findings. It also has room for UX, conversion, performance, accessibility, content, and trust issues. Delete any category that falls outside your scope.
Can I add my own branding?
Yes. Copy the Markdown outline into your own document, or restyle the Excel workbook before you share it. Replace the title, brand, and contact details before exporting a client version.
Does the PDF automatically audit my website?
No. It gives you a structure for evidence collected with your own tools and review. To generate findings for one public page, run a website audit.
Can I use the template for a client report?
Yes. Replace the blank fields with evidence from the client's site, and keep the scope and limitations visible. For a worked version, see the sample website audit report.
Start with the download
Download the free website audit report PDF. Start with the scope and evidence. Write the executive summary after you have settled the priorities, owners, and re-test plan.



