> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/audit/page-content-auditor-guide.md).

# Using Page Content Auditor

Audit one page for a target keyword and intent, track background progress, interpret the report, understand usage and gate failures, and rerun safely.

Use Page Content Auditor to evaluate one public page against a specific target keyword and search intent. The report combines crawl and indexing checks with content, structure, performance, trust, quality, and AI-crawler evidence.

Use [Site Auditor](/audit/site-auditor-guide.md) instead when you need to investigate an entire site or repeated template-level issues.

## Start a page audit

1. Select the client and choose **Audit → Page Content Auditor**.
2. Enter the complete public page URL.
3. Enter the target keyword you want the page to satisfy.
4. Add a location when the query depends on a specific market.
5. Let Rankability detect intent or choose **Informational**, **Commercial**, **Transactional**, or **Navigational**.
6. Review the displayed usage impact, then start the audit.

Choose intent based on what a searcher expects from the result, not merely the page type you already have. A mismatch between intent and the page can affect competitor selection and several recommendations.

To audit several pages at once, choose **Have multiple pages? Run batch audits**. Give each row the page URL and the exact keyword to measure it against — up to ten rows, typed in or pasted as keyword-and-URL pairs, one pair per line separated by a tab or comma. Each page becomes its own audit with its own report, and Rankability starts them a few at a time; if some rows cannot start, it says which.

After starting, Rankability returns to **All audits**. The row moves through **Queued**, **Reading page**, **Researching results**, and **Scoring audit** while the list refreshes automatically. You can leave the page; the work continues on the server.

If the analysis request fails to start or remains pending without starting, the saved row displays **Needs attention** and **Retry**. Use that control instead of creating a duplicate audit.

## Usage and the three gates

Page Content Audits are included in full-platform pooled usage. A failed audit does not record completed work.

Before the full analysis, the page must pass three gates:

* **Crawlable** — Rankability can fetch the URL.
* **Indexable** — the page does not expose a blocking indexing condition.
* **Retrievable** — Rankability can extract enough usable page content for analysis.

If the page fails a gate, Rankability produces the available gate report. A PageSpeed Insights failure is different: the rest of the audit can still complete without a performance score.

## Read the seven report sections

The completed report can contain:

1. **Crawling & Indexing** — fetchability, indexability, canonical and related technical evidence.
2. **Content** — keyword use, topic and entity coverage, search-intent alignment, competitor coverage, and content differentiation.
3. **On-Page Structure** — titles, descriptions, headings, links, freshness signals, broken links, schema, and semantic components.
4. **UX & Performance** — available PageSpeed and Core Web Vitals evidence, mobile and page-weight signals, readability, intrusive interstitials, and advertising patterns.
5. **Trust & Authority** — trust evidence relevant to the selected intent and page purpose.
6. **Page Quality Score** — a consolidated quality rubric for the analyzed page.
7. **AI Crawler & Corpus Readiness** — whether major AI and search crawlers appear able to access and interpret the page.

Expand a failed or warning check to inspect its reason, current value, recommendation, and available page or competitor evidence. Treat the evidence as the basis for a decision—not the color of the badge alone.

Each failed or warning check also carries **How to fix**, which opens a recommended next step written for that checkpoint and your target keyword. The guidance is deliberately platform-neutral, so apply it in whichever content management system the page lives in, then rerun the audit to confirm the change.

**Ask Serena** in the same panel opens a Serena conversation about that specific check. Serena reloads the audit rather than trusting anything carried in the link, so the answer is grounded in the saved result for that page and keyword.

## Understand the score

The overall score runs from 0 to 100. Rankability weights the applicable sections and renormalizes the result when a section cannot be evaluated. Therefore, a missing or not-applicable section is not automatically scored as zero, and two audits with different available evidence are not always directly comparable.

The score is diagnostic. It does not guarantee a ranking improvement, and a lower-scoring recommendation can still be irrelevant to the page’s actual purpose. Verify major changes against the page, query, competitors, brand requirements, and conversion goal.

## Compare history and rerun

Rankability retains completed audits and can show score history for the same URL and target keyword. Keep the inputs consistent when you want a meaningful before-and-after comparison.

Use **Re-audit** after publishing material changes or when an older report lacks newly released checks. Rankability creates a new version while keeping the latest completed report available. The row shows the new version's background progress; if that version fails, the prior completed report remains readable and the row identifies the failed re-audit.

A re-audit is a new metered outcome when it completes successfully. Do not start another version merely because the list is still showing an active stage.

## Share the report

Use **Share** on a completed audit to create a public, read-only report link for a client or stakeholder. Anyone with the link can view the supported report content, so review it before sending and treat the URL as shareable information.

## Troubleshooting incomplete evidence

* Confirm that the URL is absolute, public, and returns the intended page without login or geographic blocking.
* Check robots directives, canonicals, noindex conditions, bot protection, and JavaScript-only content when a gate fails.
* A missing PageSpeed result usually means that performance data was unavailable, not that performance passed.
* Third-party competitor and performance data is best effort and can change between runs.

For repeated access failures, see [Whitelisting the Rankability crawler](/troubleshooting/whitelisting-rankability-crawler.md) or contact support with the URL, keyword, intent, audit time, and visible error.

## Related articles

* [Audit overview](/audit/audit-overview.md)
* [Using Site Auditor](/audit/site-auditor-guide.md)
* [Understanding your content score](/copywriter/understanding-your-content-score.md)
* [Usage limits reference](/account-and-settings/credit-costs-reference.md)