Choose the page job
Select Home, Blog Post, Store Home, Product, Service, Landing, Intent, Comparison, Documentation, About, Collection, or Local Business.
One Page Scan checks a single public URL against rules chosen for its page type, then keeps optional AI clarity observations separate from the measured readiness score.
The workspace tool is being prepared for this deployment. You can create an account now and use it after activation.
Select Home, Blog Post, Store Home, Product, Service, Landing, Intent, Comparison, Documentation, About, Collection, or Local Business.
The rule engine checks safe access, metadata, headings, links, schema, trust evidence, and requirements specific to the declared type.
A small OpenRouter model can review compact extracted evidence. It cannot rewrite rule results or increase the readiness score.
The URL form, report, re-scan controls, AI retry, saved history, and Pro comparison all stay attached to the signed-in account. The public page never fetches a URL or creates a report.
3 page scans per day across 1 site, saved reports for 90 days, and 1 successful bounded AI analysis per day.
Up to 30 scans per 2-hour safety window across 3 sites, bounded AI analysis, retained history, and previous-scan comparison.
A homepage should make the organization, offer, audience, and main paths understandable. A blog post should answer its central question early, expose a usable heading structure, identify the author or publisher, show dates when appropriate, and support important claims. Store and collection pages need navigable categories, product paths, policies, and trust signals. Product pages need visible product identity, price or availability context when applicable, and consistent Product or Offer structured data.
Service, landing, and intent pages are evaluated against the decision they should help a visitor make. Documentation pages need task-focused headings, prerequisites, steps, code or examples when relevant, and routes to related documentation. Comparison pages need named alternatives, explicit criteria, balanced limitations, and evidence that lets a reader understand why the options differ. One Page Scan keeps these rule profiles separate so a missing product price is not treated as a problem on an About page.
The report separates verified observations, warnings, failures, and unavailable evidence. A network failure or inaccessible page does not become a zero score or a passing result. Each measured issue includes the observed evidence, why it matters for the declared page job, a smallest safe fix, and a way to verify the change. Optional AI-readable affordances remain outside the core score.
The AI section is intentionally bounded. A compact excerpt of extracted evidence is sent through the configured OpenRouter model, and the response must match a strict JSON contract. It can describe the purpose it understood, identify clarity gaps, and suggest a draft quick answer, but it cannot invent analytics or claim that the page is indexed, ranking, recommended, or cited. If the provider times out or returns malformed output, the deterministic report remains available.
The scanner accepts HTTP or HTTPS pages that pass URL, DNS, IP, redirect, and blocklist protections. It does not sign in to websites, inspect private dashboards, bypass access controls, or crawl a whole domain. The user confirms that the submitted page is public. Extracted evidence is bounded and the stored report does not include raw page HTML.
Free and Pro scans run only after authentication. Reports are linked to the account and ownership is checked again for reads, AI retries, and deletion. Free reports expire after 90 days under the current retention contract. Pro adds a larger safety window, more sites, and a comparison against the previous saved scan for the same final URL. See the pricing comparison for the current plan limits, or review the broader AI readiness checker when the question concerns an entire website rather than one page.
No. The public page explains the tool, but fetching a URL, creating a report, and using AI analysis require a signed-in Free, Pro, or admin account.
No. Page Readiness is based on visible technical and content evidence from one URL. It does not measure rankings, indexing, traffic, crawler visits, mentions, or citations.
Different pages have different jobs. A product page needs product and offer evidence, while an article needs a clear answer, authorship, dates, and useful supporting sources.
No. OpenRouter reviews a compact evidence summary for clarity observations. It cannot change check statuses, measured evidence, or the Page Readiness score.