# OnSite Analysis

> Audit a page on mobile and desktop, find the biggest improvements, and export a practical fix list.

Canonical: https://docs.georanker.com/docs/keywordds-denisty-tool

Find what is slowing a page down and which technical improvements to make first. **OnSite Analysis** opens the **On-page Audit** workspace, with Lighthouse results from Google PageSpeed Insights.

## Run a page audit

1. Select your project from the top-left project menu.
2. Open **OnSite Analysis** and click **New Audit**.
3. Enter the full **Page URL**, including `https://`. For example, `https://booking.com/`.
4. Under **Device Strategy**, choose **Mobile**, **Desktop**, or both.
5. Leave **Recurring Audit** off for a one-time check. Click **Run Audit**.
6. Return to **Audit History** and open the completed audit.

[Interactive example: On-Page SEO: audit setup](https://docs.georanker.com/docs/keywordds-denisty-tool). The example uses illustrative sample data.

Start with one important page, such as your homepage or a landing page losing traffic. An audit checks the URL you enter, so use [Broken Links](https://docs.georanker.com/docs/broken-links) when you want to crawl links across a site.

## Turn the results into a fix list

Open the **Audit** tab and choose **Mobile** or **Desktop** to view that device's results.

| Result | How to use it |
| --- | --- |
| Performance | Find loading and rendering problems. |
| Accessibility | Review automated checks that affect how people use the page. |
| Best Practices | Review technical recommendations. |
| SEO | Check the page's basic technical SEO signals. |
| Core Web Vitals panel | Inspect the reported timing and layout metrics alongside the scores. |

Under **Action Plan**, start with **Biggest Wins** for the largest opportunities or **Quick Wins** for a smaller first pass. Read the individual finding and its estimated saving before choosing a fix.

[Interactive example: On-Page SEO: audit results](https://docs.georanker.com/docs/keywordds-denisty-tool). The example uses illustrative sample data.

For example, the illustrated mobile audit highlights unused JavaScript and multiple redirects. That gives the developer a clear place to start. A high SEO score does not mean the page will rank first, and automated accessibility checks do not replace manual review.

After making changes to your website, use **Run Audit** again to check the result. Compare the same URL and device, and check the capture date before treating an older report as current.

## Export the findings

Open **Export** and choose:

- **Export PDF Summary** for a report to review with your team.
- **Export Opportunities (CSV)** for a working list of improvements.
- **Download JSON** for the underlying audit data.

## Content analysis

The **Content** tab is separate from the technical audit. If it shows **Content Analysis Not Active**, keyword density, heading analysis, and content suggestions are not included in that report yet. The tab offers **Enable Content Module**; a completed technical audit alone does not mean content analysis is enabled.

If a saved report says **No audit data available**, return to **Audit History** and open another completed audit, or run a fresh check of the correct URL.