> For the complete documentation index, see [llms.txt](https://docs.marketingtool.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.marketingtool.pro/free-ppc-audit-report.md).

# Free PPC Audit Report

Get a free, instant PPC audit report. Analyze account structure, wasted spend, keyword conflicts, and quality score issues without any cost or commitment.

**Category:** [Google Ads & PPC](/google-ads-and-ppc.md) · **Badge:** Audit

## Where to find it

* **Web app** — [app.marketingtool.pro/tools/free-ppc-tools](https://app.marketingtool.pro/tools/free-ppc-tools)
* **iOS / Android app** — open the **Tools** tab and search “Free PPC Audit Report”

## Inputs

| Input               | Type                                     | Required |
| ------------------- | ---------------------------------------- | -------- |
| Account Description | textarea                                 | ✅        |
| Industry            | text                                     | ✅        |
| Platform            | select — Google Ads, Microsoft Ads, Both | optional |
| Known Issues        | text                                     | optional |

## Result workspace

Your result page is organized into tabs: **Overview**, **Scan**, **Results**, **Fix**.

## Tips for best results

* **Share Campaign Names** — List your top 3-5 campaigns for a focused audit.
* **Include Spend Data** — Mention approximate monthly spend for realistic recommendations.
* **Note Pain Points** — Tell us what's not working so we can prioritize.

## How to run it

1. Open **Free PPC Audit Report** (links above).
2. Fill in the inputs and press **Generate**.
3. Review your full result page — it's saved to your History automatically. On desktop, use **Download All** to save every asset.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.marketingtool.pro/free-ppc-audit-report.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.