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 instead when you need to investigate an entire site or repeated template-level issues.
Start a page audit
Open the workspace and choose Audit. Existing full-platform accounts choose Audit → Page Content Auditor inside the client.
Enter the complete public page URL.
Enter the target keyword you want the page to satisfy.
Add a location when the query depends on a specific market.
Let Rankability detect intent or choose Informational, Commercial, Transactional, or Navigational.
Review the displayed cost, 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.
After starting, a current-plan content audit returns to Projects, where one compound item tracks the audit and linked optimization. An existing full-platform Page Content Audit returns to All audits. Its 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.
Credits and the three gates
On current Rankability plans, the compound content-audit workflow consumes one optimization allowance only after both the audit and linked optimization artifact are usable. Existing full-platform Page Content Audits reserve 150 credits when the audit starts and finalize the charge only after the complete report succeeds.
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 and releases the reserved outcome or credits. Vendor timeouts and audit errors also release the reservation. A PageSpeed Insights failure is different: the rest of the audit can still complete without a performance score, and a usable successful audit still consumes its applicable usage.
Run a free audit without an account
Rankability also offers a free page audit that anyone can run without signing in. Enter an email address and complete the security check, then supply the same URL, target keyword, optional location, and intent as the signed-in tool. It runs the same analysis and produces the same report sections, and it does not use an allowance or credits.
Rankability emails a private link to the finished report, and sends a message if the audit could not complete. That link stays valid for 30 days. Treat it as private: anyone holding it can open the report, and Share copies that same link.
Free audits are limited per day. When you reach the limit, Rankability says so and you can run the audit again the next day or from a signed-in account.
Read the seven report sections
The completed report can contain:
Crawling & Indexing — fetchability, indexability, canonical and related technical evidence.
Content — keyword use, topic and entity coverage, search-intent alignment, competitor coverage, and content differentiation.
On-Page Structure — titles, descriptions, headings, links, freshness signals, broken links, schema, and semantic components.
UX & Performance — available PageSpeed and Core Web Vitals evidence, mobile and page-weight signals, readability, intrusive interstitials, and advertising patterns.
Trust & Authority — trust evidence relevant to the selected intent and page purpose.
Page Quality Score — a consolidated quality rubric for the analyzed page.
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.
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 or contact support with the URL, keyword, intent, audit time, and visible error.
Related articles
Last updated
Was this helpful?