RefMatch helps editors review whether verified references fit the manuscript topic, bibliography context, and journal questions before peer review. It is advisory only: no automatic editorial decisions.
Scores only confirmed metadata. Unresolved references stay visible and are never sent to Gemini.
A DOI can resolve, metadata can match, and the bibliography can still offer weak topical support. Editors need pre-review context before they spend scarce peer-review time.
Long reference lists can inflate apparent grounding while adding little support to the manuscript’s actual claims.
References may share a broad discipline but not the title, abstract, methods, or topic the paper claims to address.
Editors often see reference quality only after peer review starts. RefMatch surfaces a transparent advisory snapshot earlier.
RefMatch starts after CheckRef validation. It enriches confirmed references, scores the visible topic fit, and keeps every uncertainty explicit.
Compares each confirmed cited work with the manuscript title, abstract, keywords, and stated topic.
Summarizes whether the reference list appears concentrated, broad, under-covered, or uneven across visible concepts.
Labels each row High, Medium, Low, or Unresolved, with a neutral reason and engine provenance.
Analyses run in the background and generate email-ready report links without exposing reference content in email.
Run CheckRef first. RefMatch only scores references with confirmed metadata and a DOI.
OpenAlex metadata and concepts add topic context for each confirmed work.
Gemini semantic analysis runs with no search grounding and structured output.
Editors inspect an advisory report with bands, reasons, unresolved rows, and exports.
Scope fit is rolling out. Current reports focus on manuscript-topic relevance and transparent unresolved metadata.
Advisory language only. RefMatch helps editors ask better questions. It does not determine manuscript validity, acceptance, or rejection.
RefMatch does not judge your work. It shows whether the submitted bibliography visibly supports the manuscript topic from verified metadata, helping teams improve literature grounding before review.
RefMatch is a standalone subdomain product, while login, users, reports, and admin remain centralized in CheckRef.
Validate references and DOI metadata before publishing.
Audit published metadata quality and record health.
Assess bibliography relevance and manuscript-topic support.
Author visibility and journal outreach after publication.
No. RefMatch is advisory only. It provides relevance bands and neutral reasons to support editorial review, but it never makes acceptance, rejection, or validity decisions.
Only references that are confirmed by CheckRef, have a DOI, and can be enriched through OpenAlex are scored. Everything else is listed as Unresolved and never sent to Gemini.
Reference metadata comes from CheckRef validation, Crossref, and OpenAlex. RefMatch does not scrape or use Google Scholar data.
Gemini receives only verified metadata for scoreable references and the manuscript metadata needed for comparison. Search grounding is disabled; the model is instructed to judge only the provided metadata.
Journal scope fit is rolling out. Current production reports focus on reference-to-manuscript relevance, with scope-related language kept advisory and clearly marked when not enough scope data exists.
RefMatch uses the normal CheckRef login at checkref.org. Administrators grant access with the `allowed_apps.refmatch` flag; there is no separate RefMatch account.
Use RefMatch after CheckRef validation to see whether confirmed references visibly support the manuscript topic.