[nish3451]

Adds WebPage + FAQPage JSON-LD to the live anonymous one-page check (/check), with a matching visible FAQ section so every schema claim is readable on the page.

• checkJsonLd(origin) emits an @graph of WebPage (publisher/website refs, mainEntity pointing at the FAQ) and FAQPage covering: what the check measures, what is stored (nothing beyond hashed rate-limit counters), that it is not a full site audit, and the no-ranking boundary.
• The four questions render as a visible FAQ section mirroring the schema answers verbatim — truthful by construction, matching the page boundary copy (no stored report/URL, hashed counters, no ranking/traffic promises).
• </script>-safe escaping (\\u003c) matches pages.js.
• Tests: new public-check.test.mjs case parses the JSON-LD, verifies WebPage/FAQ structure, every answer visible on the page, and no overclaim; pages.test.mjs pins the visible FAQ section.

Verified: npm run check passes (18/18 suites + build).

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[greptile-apps]

nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

[coderabbitai]

Warning

Review limit reached

@nish3451, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 16 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4612b8c8-9643-45cc-bff2-3dfde9681e65

📥 Commits

Reviewing files that changed from the base of the PR and between e5c8dfe and 8cbc069.

📒 Files selected for processing (3)

• worker/routes/pages.test.mjs
• worker/routes/public-check.js
• worker/routes/public-check.test.mjs

---

_{Comment @coderabbitai help to get the list of available commands.}