Scholar Forensics

Sample report  ·  format only

What a findings report looks like.

A report answers one question: why did coverage drop, and how sure are we. Every statement points to numbered evidence, and what we could not establish is written down.

1. Verdict

Citation metadata on the new platform no longer matches the PDFs, and Google Scholar dropped articles after the move. Redirects were correct and are not the cause. Confidence: High for the metadata mismatch, Medium for it being the only cause.

2. Evidence

IDObservationSourceTime (UTC)
E1Search Console shows indexed pages unchanged after the move; Scholar coverage of 40 sampled titles fell from 38 to 9.GSC export; dated Scholar baseline2026-01-12 / 2026-02-09
E2All 40 sampled old URLs return one 301 to the matching new URL.Redirect crawl2026-02-10 09:14
E3On 31 of 40 sampled articles, citation_title in the page differs from the title printed in the PDF.Page tags vs PDF text2026-02-10 11:02
E4citation_pdf_url returns an HTML viewer page, not a PDF, on 22 of 40.Direct fetch2026-02-10 11:40
E5The platform template changed on the move date; the old template emitted both tags correctly.Client changelog2026-01-08

3. Confidence, defined

4. Not established

5. Remediation, in order of risk

  1. Restore citation_pdf_url to a direct PDF address (E4). Staging first; no DOI target changes.
  2. Regenerate citation_title from the same source as the PDF (E3). Test on 10 articles, then all.
  3. Re-submit the sitemap; leave the redirects in place for at least a year.

6. Watch plan

Repeat the 40-title Scholar baseline at 2, 6 and 12 weeks after the fix. Report the movement against the first baseline, not against the last check.

Want this for your journal?

Start with the free check, or describe the problem.

Run the free check   Request a diagnosis