CiteRanger CiteRanger

Docs Beta

FAQ and troubleshooting

Answers to the questions that come up in the first week: pages that will not scan, claims that look wrong, and what CiteRanger does not do.

A page will not scan

  • The page requires a login. CiteRanger reads public URLs only. Publish a staging copy at a public, unlisted URL and scan that.
  • The page blocks automated access. Some sites block non-browser requests. Check whether the page loads with a plain HTTP request; if your own site blocks it, allow CiteRanger’s requests.
  • The URL redirects. CiteRanger follows redirects; if the final page is different from the one you meant, scan the final URL directly.

A claim was marked outdated but the page is right

Open the source shown in the report. If the source is wrong or does not apply to your context, keep your claim and note it; if the source is right, the page needs the update. Verdicts are only as good as the sources, which is why every verdict shows its source.

A claim is unverifiable

No current source confirmed or contradicted it. Original data, first-hand statements and very specific claims land here. Decide whether the claim needs a source added, a rewrite, or nothing. See Reading the report.

A confirmed claim looks wrong to me

Report it. Confirmations are cross-checked across providers, but a source can be wrong. If you have a better source, use it and tell us.

Does CiteRanger change my pages?

No. It reads published pages and produces reports. Every change is made by you in your CMS.

Does it store my content?

Scanned content is stored with the report so you can compare scans over time. See the privacy policy for details.

Is there an API?

It is in development. Join the early access list to be notified.