> 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/on-page-seo-checker.md).

# On Page Seo Checker

Check your landing pages for on-page SEO factors that affect Google Ads Quality Score. Analyze page titles, meta descriptions, content relevance, load speed, and mobile-friendliness.

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

## Where to find it

* **Web app** — [app.marketingtool.pro/tools/on-page-seo-checker](https://app.marketingtool.pro/tools/on-page-seo-checker)
* **iOS / Android app** — open the **Tools** tab and search “On Page Seo Checker”

## Inputs

| Input           | Type     | Required |
| --------------- | -------- | -------- |
| Page URL        | textarea | ✅        |
| Primary URL     | text     | ✅        |
| Target Keywords | text     | optional |

## Result workspace

Your result page is organized into tabs: **Overview**, **Analysis**, **Scoring**, **Fixes**.

## Tips for best results

* **Match Keywords in H1** — Your main headline should include the target keyword naturally.
* **Check Mobile Score** — Google prioritizes mobile experience for Quality Score.
* **Speed Matters** — Aim for < 2.5 second Largest Contentful Paint (LCP).

## How to run it

1. Open **On Page Seo Checker** (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/on-page-seo-checker.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.