> For the complete documentation index, see [llms.txt](https://docs.adalysis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adalysis.com/manage/landing-pages/analyze-your-landing-pages.md).

# Analyze your landing pages

Adalysis analyzes the landing pages used in your ads and keyword final URLs to assess their impact on your quality score. It provides a summary grouped by URL, showing how the range of keyword quality scores correlates with landing page performance.

As an advertiser, this helps you to spot low quality scores caused by poor landing page experience. You can then choose a new landing page or improve the existing page content.

To search for a specific URL, head to **Manage** > **Landing pages**.

{% hint style="info" %}
The landing page data covers the last 90 days.
{% endhint %}

### Analyzing landing page experience to improve quality scores

Adalysis analyzes Google’s landing page experience ratings for each keyword (above average, average, and below average). It then groups them based on the target URL in the Google Ads account.

The breakdown helps you quickly identify which pages are most in need of improvement.

<figure><img src="/files/jxTtCxKJsq4x3EomjnAY" alt=""><figcaption></figcaption></figure>

A [prebuilt alert ](/tools/audit/prebuilt-alert-list/landing-pages/landing-pages-that-need-improvement.md)and matching filter will flag landing pages when more than 50% of their traffic comes from keywords with a below-average score.

<figure><img src="/files/ClkN2huGOvQRCmh9VUG6" alt="" width="449"><figcaption></figcaption></figure>

### Non-converting landing pages

Adalysis also offers a [prebuilt alert](/tools/audit/prebuilt-alert-list/landing-pages/landing-pages-with-poor-conversions.md) and matching filter for landing pages that aren’t converting well. You can customize them in the alert settings (**Audit** > **Audit settings** > **Prebuilt** > **Landing pages)**.

<figure><img src="/files/f8kyyFTWpek4q9c9WAo0" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="/files/XCasE69Cqp6Ao827GWTL" alt="" width="449"><figcaption></figcaption></figure>

### PageSpeed Insights

The mobile and desktop icons in the **Page speed** column open a new window with the PageSpeed Insights test results for your URL. Use these insights to identify and resolve page speed issues that may impact user experience and landing page performance.

<figure><img src="/files/24OR1obYdz5OTArylu9i" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.adalysis.com/manage/landing-pages/analyze-your-landing-pages.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.