DEV Community: D. Ceabron Williams

The CRAAP Test and Why AI Should Show Its Work

D. Ceabron Williams — Thu, 25 Jun 2026 05:14:46 +0000

Somewhere in a school library right now, a student is staring at a source their AI tool called "reliable" — with no explanation of why. They copy it. They move on. They learned nothing about evaluation.

I've been a librarian for over two decades. The CRAAP Test wasn't handed down from on high — it was built by librarians because we kept seeing students get burned by sources that looked fine on the surface. Currency, Relevance, Authority, Accuracy, Purpose. Five questions. No magic.

Most AI tools ignore all of it.

What the CRAAP Test Actually Is

The CRAAP Test is a framework — not a rubric, not a score. You evaluate a source against five criteria:

Criterion	What You're Checking
Currency	How recent is this? Has the information been superseded?
Relevance	Does it actually answer the question, or just vaguely orbit it?
Authority	Who wrote this? What's their expertise? What's their agenda?
Accuracy	Is this verifiable? Are there citations? Are there errors?
Purpose	Is this meant to inform, persuade, sell, or entertain?

Librarians love it because it teaches a process. A student can internalize those five questions and apply them to any source — a Wikipedia article, a government report, a TikTok video, a peer-reviewed journal. That's the whole point: evaluation as a skill, not a verdict.

The Problem With "Trust Me" AI

Here's what most AI research tools do:

You paste a URL or ask a question
The tool says something like "This source is credible" or "Use this"
No breakdown. No evidence. No reasoning.

That's not evaluation. That's a black box giving you a verdict.

Students don't learn anything from that. Worse — they can't tell when the tool is wrong. A source can have outdated information, an unknown author, and a clear bias, and the AI still says "looks good." The student has no framework to push back.

I started seeing this pattern years before generative AI was mainstream. Every year, more students arrived with learned helplessness around sources — they could find things, but they couldn't evaluate them. AI tools are making that worse, not better.

Sabia Librarian's Approach

When I built Sabia Librarian, I started with a question: what would a librarian's evaluation actually look like?

Not a score. Not a thumbs up or down.

A breakdown.

When you evaluate a source with Sabia, you get structured results for every CRAAP criterion — a pass or fail on each point, with evidence and flags. You can see why something scored the way it did. You can see exactly where the authority fell apart or why the currency was a problem.

That transparency is the point.

A student who sees "Authority: FAIL — no author listed, no institutional affiliation" can go find that information. They're learning evaluation in real time. The tool didn't just hand them an answer — it showed them the work.

Why Showing Your Work Matters More Than Being Right

Here's the thing about information literacy: the goal is not to find the right source. The goal is to be able to evaluate any source.

That's the difference between teaching and testing. A good test gives you a score. A good lesson teaches you to ask better questions.

Most AI tools are built like tests — they give you an output and move on. Sabia is built like a lesson. The breakdown is the product, not a side effect.

When I say "showing your work" — I mean it literally. Our methodology page explains exactly how we evaluate each CRAAP criterion. We publish the criteria. We publish the scoring logic. We don't hide it.

We Scored Ourselves 35 Out of 100

This is the part that makes most tech founders uncomfortable.

We ran Sabia Librarian through the same evaluator we built for sources. Our methodology is transparent, but our product is still young — we have known gaps in coverage, known limitations in certain source types, known areas where the model needs more training data.

Our overall score: 35 out of 100.

We published that. Read it yourself — it's on the site, along with every evaluation we've run. We want users to see what we got wrong so they can tell us where we're wrong.

That's not humility theater. It's the same standard I held my students to: show your reasoning, take accountability for your conclusions, stay teachable.

Try the Evaluator

If you're a school librarian, a teacher, or anyone who works with students on research, try the Sabia Librarian evaluator — it's free to start.

And if you want to see exactly how we evaluate, read the methodology. No hidden criteria. No unexplained verdicts.

AI tools should show their work. Libraries taught me that. Sabia is built to honor it.

D. Ceabron Williams, M.L.I.S.
Founder, Sabia Librarian
Former public and academic librarian

I Scored My Own AI Tool 35/100. Here's What I Fixed.

D. Ceabron Williams — Sun, 21 Jun 2026 05:06:18 +0000

The Score: 35 Out of 100

I ran sabialibrarian.com through our own evaluator — the same tool we give to school librarians evaluating AI-generated student work — and scored 35 out of 100.

That hurt.

Not because the score was low in absolute terms, but because I'd been telling people for months that our evaluator was credible, well-reasoned, and built on actual librarian methodology. And then I turned it on ourselves and watched it hand back a 35.

Here's the thing about self-evaluation: it's easy to skip. It's easier to ship and say "we'll audit later." I was about to do that. Then I read the criteria breakdown and realized some things were genuinely broken — not just mediocre, but broken in ways that would confuse or mislead the librarians using the tool.

This is what I found, and what I fixed.

Why Self-Evaluating Your Own Tool Is Not Optional

If you're building a credibility tool and you don't test it against your own website, you have a credibility problem.

We built the Sabia evaluator so librarians could apply the CRAAP framework (Currency, Relevance, Authority, Accuracy, Purpose) to AI-generated content and web sources. The whole premise is: use a structured, transparent methodology to surface what's wrong with a source.

If that tool scores sabialibrarian.com at 35/100, I have to ask: what are the librarians who use this tool seeing when they evaluate their own students' work? And the answer is — whatever we shipped. Unaudited.

A tool you don't test against yourself is a tool you're not in control of.

The 35/100 Score: What Failed

Running the evaluator against sabialibrarian.com returned the following failures across the CRAAP criteria:

Criterion	Status	Reason
Currency	PASS	Site live and maintained; current domain registration
Relevance	FAIL	Content not matched to evaluator; no clear statement of who the tool is for
Authority	FAIL	No author credentials visible on the site; /about page returned 404
Accuracy	FAIL	Evaluator returning errors on the homepage; results not displaying
Purpose	PASS	Clear intent to help librarians evaluate sources

Two of the five criteria failed outright. One — Accuracy — was broken at a code level. Purpose passed, but only because the intent was legible even when the execution wasn't.

What Was Actually Broken

1. The evaluator was crashing on sabialibrarian.com

The scoring logic had a bug in the hero section evaluation — the code was calling a function that didn't exist in the current deployment. When a user landed on the homepage and ran an evaluation, the tool would error out before returning a result. This wasn't a low score. It was a broken tool.

2. The criteria breakdown wasn't connected

Even when evaluations ran, the per-criterion pass/fail breakdown — the most important part for librarian users — wasn't displaying in the results. The score showed, but not the reasoning. That's like handing someone a report card without the grades.

3. The /about page returned a 404

This one is embarrassing to write, but: the /about page — the single most important page for establishing who we are and why a librarian should trust us — was not actually deployed. It returned a 404. We'd been talking about the "about the founder" page for weeks. It was never on the server.

4. No methodology page existed

The evaluator asks users to trust its reasoning. But if you can't explain how it evaluates sources, the output is just an AI making claims with no accountability. We had no public methodology page — nothing showing what the CRAAP framework means in the context of the tool, what counts as a pass or fail, or how the scoring works.

What I Shipped to Fix It

Evaluator crash fixed (May 27)

Replaced the broken function call in the hero evaluation module. Added a guard clause for pages with dynamic content. Evaluations now complete without throwing errors.

Criteria breakdown wired live (May 28)

The per-criterion pass/fail results now display correctly. Users see why the score is what it is — which criteria passed, which failed, and what evidence the tool found. This is the feature that should have existed at launch.

/about page deployed (May 28)

The /about page is now live at sabialibrarian.com/about. It includes my background as a public and academic librarian, my M.L.I.S. credentials, and the specific experience that grounds the evaluator's methodology. Librarians evaluating the tool should be able to evaluate us too.

/methodology page added (May 29)

A methodology page explaining exactly how the evaluator applies the CRAAP framework — what each criterion measures, what counts as a pass or fail, and what the score means in practice. Transparent methodology is not optional for a tool that claims to evaluate credibility.

CRAAP reference sheet (May 29)

A print-ready CRAAP reference PDF is available on the /resources page. This gives librarians something to use with students even if they're not using the full tool.

Honest Limitations That Remain

The 35/100 score came from the evaluator — not from me. I can explain what it found, but I need to be straight about what it doesn't cover yet:

No real-time web crawling: The evaluator analyzes content signals and structural patterns but doesn't do live page verification. Citations and domain registration are checked at the time of the run, not against live records.
Multilingual evaluation is partial: The tool works in English, Spanish, and Portuguese — but not equally well across all content types.
No confidence calibration for edge cases: Sources that are borderline pass/fail still get scored without indicating uncertainty. A "38/100" score doesn't communicate that the evaluator was close to a different call on the Authority criterion.

These are not excuses. They're what the evaluator found, and they point to the next round of improvements.

Try It on Your Own Site

If you're a school librarian — or anyone building an AI literacy tool — run your own site through the evaluator at sabialibrarian.com.

If it scores low, that's useful information. Not all low scores mean "bad." Sometimes they mean "unfinished." I'd rather know which one I'm looking at than guess.

D. Ceabron Williams, M.L.I.S., is a retired public and academic librarian. The Sabia Librarian evaluator is built on the CRAAP framework and designed for school librarians evaluating AI-generated content and web sources. Try it at sabialibrarian.com.

5 Razones por las que tus estudiantes no saben evaluar fuentes en internet — y cómo solucionarlo

D. Ceabron Williams — Tue, 16 Jun 2026 05:48:08 +0000

¿Cuántas veces has visto a un alumno citar Wikipedia como fuente principal? Probablemente más de las que quisieras admitir.

El problema no es la pereza. Es que nadie les enseñó a distinguir entre una fuente confiable y ruido digital.

Como bibliotecarios escolares en América Latina, enfrentamos un desafío particular: no solo enseñamos a buscar información, sino a evaluarla críticamente en un ecosistema donde cualquier persona puede publicar cualquier cosa.

La brecha de evaluación de fuentes en bibliotecas escolares latinoamericanas

Estudios de UNESCO y la IFLA documentan que los estudiantes en la región frecuentemente:

No distinguen entre opinión y dato. Confunden un blog personal con una fuente académica.
Confían en el diseño visual. Páginas con colores profesionales = "es oficial".
Evitan verificar fuentes cruzadas. Un solo sitio parece suficiente.
Desconocen el sesgo de confirmación. Buscan solo lo que confirma lo que ya creen.

El resultado: investigaciones con fuentes mediocres, trabajos académicos comprometidos, y una generación sin herramientas para pensar críticamente.

¿Qué es el Método CRAAP y por qué funciona?

El CRAAP Test es un marco de evaluación de fuentes desarrollado por la bibliotecaria Carrie Lennon en la California State University, y es uno de los más utilizados en bibliotecas escolares de Estados Unidos y Canadá.

Las cinco preguntas:

Letra	Criterio	Pregunta clave
C	Currency (Moneda)	¿Cuándo se publicó? ¿Está actualizado?
R	Relevance (Relevancia)	¿Es útil para mi investigación?
A	Authority (Autoridad)	¿Quién escribió esto? ¿Tiene credenciales?
A	Accuracy (Exactitud)	¿Está respaldado por evidencia? ¿Tiene errores?
P	Purpose (Propósito)	¿Cuál es la intención del autor?

El problema: Aplicar CRAAP manualmente toma tiempo. Los estudiantes se frustran. Los bibliotecarios tienen grupos de 30+ alumnos.

5 Razones por las que tus estudiantes fallan en evaluar fuentes

1. Buscan rápido y creen en lo primero que aparece

Google entrega resultados por relevancia algorítmica, no por calidad. El estudiante hace una búsqueda, abre el primer link, y asume que encontró lo mejor.

Solución: Enseñar la diferencia entre buscar y evaluar. El primer paso no es abrir el resultado — es preguntarse "¿Es este recurso fiable antes de leer?"

2. No saben quién es el autor

Muchos sitios no muestran autor o muestran un nombre sin contexto. El estudiante asume que si existe online, alguien lo verificó.

Solución: Enseñar a buscar el nombre del autor + su rol profesional. No basta con el nombre — hay que buscar la credencial.

3. Confunden ".com" con ".org" con ".edu"

El dominio no garantiza calidad, pero los estudiantes frecuentemente asumen que .org es siempre institucional y .com es siempre comercial sin valor académico.

Solución: Explicar que los dominios no determinan la calidad. Un blog personal en .com puede tener mejor información que una página institucional.

4. No verifican la fecha de publicación

Un artículo de 2008 sigue apareciendo en resultados. Los estudiantes lo usan sin preguntar si la información sigue vigente.

Solución: Crear el hábito de buscar la fecha en el artículo antes de citar. En ciencias, salud y tecnología, la fecha lo es todo.

5. No evalúan el propósito

Contenido patrocinado, artículos virales, contenido ideológico — todo parece "información" a primera vista.

Solución: Enseñar a hacerse la pregunta: "¿Quién se beneficia de que yo crea esto?"

Herramientas que facilitan la evaluación en el aula

Para estudiantes

Sabia Librarian — Evaluador de fuentes con IA. Pega una URL o texto y recibe un desglose por criterios (moneda, autoridad, exactitud, propósito) en segundos. Soporta español, inglés y portugués.
Google Advanced Search — Para filtrar por dominio, fecha, tipo de archivo.
DOI.org — Para verificar artículos académicos.

Para bibliotecarios

CRAAP Test printable — Descarga nuestra guía de evaluación CRAAP en PDF para usar en el aula.
Google Scholar Alerts — Para monitorear nuevas publicaciones en tus áreas temáticas.
EdPuzzle / Google Forms — Para crear quizzes de evaluación de fuentes.

Cómo integrar la evaluación de fuentes en tu programa de alfabetización

No necesitas una unidad completa. Puedes empezar con estos micro-hábitos:

Antes de buscar: Pedir a los alumnos que escriban 3 preguntas antes de hacer una búsqueda — esto enfoca la evaluación posterior.
Después de encontrar: Hacer la pregunta "¿Cómo sé que esta fuente es fiable?" — no como juicio, sino como rutina.
Al final del proyecto: Un "check de fuentes" grupal donde los alumnos evalúan las referencias de un compañero con la lista CRAAP.
Uso de IA como aliado: Inteligencias artificiales como Sabia Librarian pueden acelerar la evaluación y dar feedback inmediato — pero siempre con supervisión del docente.

Conclusión

La evaluación de fuentes no es una habilidad natural. Es un hábito que se construye con práctica, estructura y herramientas adecuadas.

Los bibliotecarios escolares tenemos la oportunidad — y la responsabilidad — de enseñar este pensamiento crítico antes de que los estudiantes lleguen a la universidad o al mercado laboral.

Sabia Librarian está diseñado exactamente para esto: ayudar a bibliotecarios y estudiantes a evaluar cualquier fuente en segundos, con criterios claros.

👉 Pruébalo gratis en sabialibrarian.com

Why Your School Library Needs an AI Evaluation Policy

D. Ceabron Williams — Wed, 10 Jun 2026 05:14:40 +0000

Your students already use AI. Your school probably has a policy for that. But do you have a policy for evaluating what AI produces?

Most schools answered that second question with a shake of the head. Not anymore.

The Gap You Didn't Know Your School Had

By July 2026, Ohio school districts must have a formal AI policy. Michigan released guidance for districts in May. Maryland and Idaho have mandated AI literacy standards and local evaluation policies. Virginia is piloting AI evaluation programs. Oklahoma's deadline is 2027–28. At the federal level, the Department of Education has made AI literacy a grantmaking priority — and the 2029 PISA will assess media and AI literacy internationally for the first time.

Here's what almost every one of those policies addresses: how students use AI.

Here's what almost none of them address: how students evaluate what AI produces.

That's not a minor gap. It's a different problem requiring a different solution.

An AI use policy tells students what they can and cannot do with AI tools. An AI evaluation policy teaches them how to think critically about the outputs those tools generate.

One is about compliance. The other is about literacy.

Without an AI evaluation policy, you're relying on the hope that students will independently develop the skill to distrust a confidently-written, structurally sound, completely inaccurate response from an AI tool. That hope is not a strategy.

What a Real AI Evaluation Policy Looks Like

A useful AI evaluation policy has five components. Most current policies have one — the prohibition of AI for cheating. Here's what's missing:

1. Verification triggers

Define exactly when students must verify AI-generated content. "Always" is not a policy. "Any AI-generated statistic, date, or named study must be cross-referenced before use" is.

2. Evaluation framework

Pick one. The CRAAP test (Currency, Relevance, Authority, Accuracy, Purpose) works. So does the LATR method (Look up, Ask who, Tool check, Re-read). Consistency matters more than which framework you choose.

3. Documentation of AI use

Require students to note when they've used AI in the research process. Not as a confession — as a transparency layer. "AI used to generate initial list of sources, then verified via lateral reading" shows thinking, not cheating.

4. Grade-level expectations

K–5: Identify that content can come from AI or humans; flag anything that sounds "made up."
6–8: Apply lateral reading to AI-generated claims; identify obvious hallucinations.
9–12: Evaluate AI output for bias, logical fallacies, and missing context; understand the tool's limitations.

5. Approved tools

When your school adopts Sabia Librarian, that belongs in the policy. Not as a resource — as an instruction. "Students may use Sabia Librarian to evaluate sources and AI-generated content during the research process." This normalizes AI-assisted evaluation rather than treating it as a workaround.

A 5-Point Starter Policy (Copy This)

SCHOOL LIBRARY AI EVALUATION POLICY
Draft template for immediate adoption — adapt to your district requirements

Purpose: This policy governs not only the use of artificial intelligence tools but the evaluation of AI-generated content in student research. It supplements, and does not replace, existing academic integrity policies.
When Verification Is Required: Any AI-generated fact — including statistics, dates, author names, study citations, and event descriptions — must be verified using at least one authoritative external source before use in an assignment.
Evaluation Framework: All students will apply the CRAAP test (or school-approved equivalent) to any AI-generated source before citing it. The checklist includes: Currency (Is this current?), Authority (Who said this and what are their credentials?), Accuracy (Can this be confirmed elsewhere?), Purpose (Is the AI tool's output complete, or has it omitted key context?).
Documentation: Students must include a brief note of AI tools used in the research process in their assignment bibliography or process journal. Format: AI tool name — purpose in research process — date.
Tool Access: Sabia Librarian (sabialibrarian.com) is an approved evaluation tool for all grade levels and is available to students and staff at no cost for initial evaluation work.

Review annually. Coordinate with district AI use policy. Align with state information literacy standards.

How Sabia Librarian Supports Your Policy

Once your policy is in place, you need a tool that makes evaluation behavior teachable, repeatable, and documentable.

Sabia Librarian evaluates any source or AI-generated text against information literacy criteria — in English, Spanish, or Portuguese. Students get structured credibility feedback they can act on, not a thumbs-up/thumbs-down verdict.

For your policy implementation, Sabia provides:

A practical reference tool students can use independently to verify AI outputs
Structured evaluation output that demonstrates verification work has occurred
Grade-level appropriate analysis that connects directly to the evaluation framework your school adopts

You don't need to retrofit your library program around the tool. The tool supports the evaluation habits your policy is designed to build.

The Window Is This Summer

Ohio schools have until July 2026 to have AI policies on file. Every state will follow. The question isn't whether your district will need a policy — it's whether your policy will include evaluation or only compliance.

The schools that build evaluation into their policies this summer will be better positioned when PISA 2029 results land, when state audits happen, and when a principal asks: "How do we know students are actually learning to evaluate what AI produces?"

This policy template gives you a starting point. Adapt it. Pass it to your administration. Put it in front of your school board before August.

The work of information literacy doesn't end at "don't cheat with AI." It ends when students can independently interrogate what AI produces and decide for themselves whether to trust it.

Your library is where that work starts.

Sabia Librarian supports school and district evaluation standards. Individual educators: start free at sabialibrarian.com. School library and district pricing available at sabialibrarian.com/pricing.

Cómo Evaluar Fuentes en la Era de la IA — Guía para Bibliotecarios

D. Ceabron Williams — Tue, 26 May 2026 05:25:42 +0000

Las herramientas de inteligencia artificial están transformando la manera en que los estudiantes investigan, buscan y verifican información. Un estudiante puede pedirle a un chatbot que le resuma un artículo, que le explique un concepto o que le sugiera fuentes para un trabajo. En segundos, tiene una respuesta aparentemente completa, con un tono académico y referencias que suenan convincentes.

El problema es que las referencias suenan convincentes, pero no siempre lo son.

Como bibliotecarios, sabemos que la evaluación de fuentes es un skill, no un checkbox. Pero en esta nueva era, los marcos que enseñamos enfrentan un desafío que no existía hace tres años: la información generada por IA se presenta con la misma apariencia de autoridad que una fuente académica real, y muchas veces sin los errores tipográficos o las señales obvias que antes delataban el contenido falso.

No es que los estudiantes quieran engañar. Es que nadie les enseñó a preguntar: ¿Esto fue escrito por una persona o por una máquina? ¿Y cuándo?

El vacío en español

La mayoría de los recursos sobre alfabetización informacional e inteligencia artificial que existen hoy están en inglés. Guías de evaluación de fuentes, marcos como el CRAAP adaptado para IA, artículos sobre cómo verificar contenido generado por máquinas — casi todo está escrito para un público angloparlante.

Esto crea una brecha real. En Estados Unidos, el 13% de los estudiantes de escuelas públicas son Aprendices de Inglés como Segundo Idioma (ELL), según el NCES 2023, y muchos de esos estudiantes tienen bibliotecarios que también sirven comunidades bilingües. En América Latina, donde millones de estudiantes dependen de recursos digitales para investigar, el vacío es aún más grave: no hay materiales adaptados al contexto iberoamericano, con ejemplos relevantes para sus realidades educativas.

Los bibliotecarios hispanohablantes necesitamos herramientas, vocabulario y marcos que funcionen en nuestro idioma y en nuestros contextos. No podemos pedirle a nuestros estudiantes que evalúen fuentes si nosotros mismos no tenemos recursos adaptados para hacerlo.

Cinco estrategias prácticas para evaluar fuentes en la era de la IA

Estas estrategias están pensadas para integrarse en lo que ya haces — no como un reemplazo de tu programa de alfabetización, sino como una actualización necesaria.

1. Busca el origen humano

Antes de leer el contenido, investiga quién lo escribió. No basta con saber que una fuente es un "artículo académico" — necesitas confirmar que fue escrito y revisado por personas reales.

Qué hacer en clase: Pide a los estudiantes que busquen el nombre del autor, su afiliación institucional y cualquier historial de publicación. Si no pueden encontrar a la persona fuera del sitio donde se publica, es una señal de alerta.

Pregunta clave: ¿Puedo verificar la existencia de este autor en otra plataforma además del sitio donde encontré este contenido?

2. Verifica la fecha — especialmente en contextos de IA

La información de hace cinco años puede estar completamente desactualizada en un campo relacionado con inteligencia artificial. Las herramientas que existían en 2022 cambiaron radicalmente en 2025.

Qué hacer: Antes de presentar una fuente como válida, confirma que la fecha de publicación sea reciente. En temas de IA, anything de más de 18 meses puede estar obsoleto. Esto es especialmente importante en español, donde muchos recursos traducidos pierden contexto y fecha de actualización.

Pregunta clave: ¿Cuándo fue escrita esta información y ha cambiado algo importante en el tema desde entonces?

3. Usa la verificación lateral

El concepto de "lateral reading" — verificar una fuente consultando fuentes externas antes de leer el contenido en profundidad — es la estrategia más efectiva para detectar contenido generado por IA o fuentes de baja calidad.

En la práctica: En lugar de pedir a los estudiantes que crean lo que lean en un sitio web, enséñales a salir inmediatamente a buscar el mismo tema en medios reconocidos. Si una "noticia" no aparece en ningún medio verificable, no es una fuente confiable, independientemente de cómo esté redactada.

Para contextos hispanohablantes: Usa fuentes como SNDE (Ecuador), Comfact (Colombia), Animal Político (México) o cualquier medio de verificación local. La idea es siempre la misma: salir del sitio original para confirmar.

4. Examina las fuentes citadas dentro del contenido

Esto es especialmente importante con contenido generado por IA, que frecuentemente "inventa" citas. Los estudiantes tienden a aceptar una referencia con formato académico sin verificar que la fuente exista realmente.

Qué hacer: Pide a los estudiantes que busquen al menos dos de las fuentes citadas en cualquier trabajo que encuentren en línea. Si no existen, el documento pierde credibilidad inmediatamente.

Pregunta clave: ¿Las fuentes citadas en este documento son reales, accesibles y relevantes?

5. Identifica el registro y el tono

El contenido generado por IA suele tener patrones reconocibles: tono uniforme sin altibajos, uso excesivo de muletillas académicas ("es importante destacar que", "en este sentido"), ausencia de perspectivas personales o errores contextuales sutiles.

Ejercicio práctico: Pide a los estudiantes que comparen dos textos sobre el mismo tema — uno generado por IA y uno escrito por una persona. Que identifiquen las diferencias en estructura, tono y profundidad. Este ejercicio desarrolla un sentido crítico que trasciende cualquier herramienta específica.

Donde la tecnología ayuda

Hay herramientas diseñadas específicamente para ayudar a los bibliotecarios a enseñar estos skills a escala. Sabia Librarian, por ejemplo, integra evaluadores que trabajan en español, inglés y portugués, con marcos adaptados al contexto latinoamericano. El selector de idioma por defecto está en español, lo que significa que estudiantes y educadores pueden usarlo en su idioma nativo sin configuración adicional.

No se trata de reemplazar el juicio crítico del bibliotecario — se trata de darle herramientas que multipliquen su alcance en contextos donde el tiempo y los recursos son limitados.

El llamado a los bibliotecarios hispanohablantes

No podemos esperar a que las soluciones en inglés lleguen traducidas. El vacío de contenido en español sobre alfabetización informacional en la era de la IA es una oportunidad: la de construir recursos adaptados a nuestras realidades, con ejemplos que resuenen en nuestras aulas, con el vocabulario de nuestros contextos educativos.

La evaluación de fuentes no es una skill técnica. Es un acto de responsabilidad intelectual — y en un mundo donde la información falsa se produce a escala industrial, es también un acto político.

Empieza hoy: toma un tema que tus estudiantes buscan constantemente en línea, prepáralo con cinco fuentes verificadas en español y conviértelo en tu primer módulo de alfabetización informacional con IA. No necesita ser perfecto. Necesita existir.

D. Ceabron Williams, M.L., es director de biblioteca retirado y escribe sobre alfabetización informacional, herramientas de IA y el futuro de las habilidades de investigación. Sigue la serie en Dev.to.

How to Teach Source Evaluation When Your Students Use ChatGPT

D. Ceabron Williams — Thu, 21 May 2026 13:33:52 +0000

The classroom has changed. Students don't come to research sessions empty-handed anymore. They arrive with answers — polished, confident, plausible-sounding answers that ChatGPT or Copilot or Gemini produced in under ten seconds.

Your job used to be teaching them how to find information. Now it's teaching them what to do with information they've already found — and why that second step is harder than it looks.

The good news: source evaluation has never been more urgent, more teachable, or more relevant to students' actual lives. The challenge is redesigning instruction for learners who've already outsourced the first step of research to a machine.

Here's what's working.

The "Don't Use AI" Policy Doesn't Work. Here's What Does.

Let's skip past the policy debate. Students are using AI tools whether your school has a ban or not. The question isn't whether they'll encounter AI-generated content — it's whether they'll know how to interrogate it.

The librarians and educators getting traction right now aren't fighting the tools. They're turning them into teaching material.

5 Strategies That Actually Work in the Classroom

1. The AI Audit Assignment

Ask students to submit two versions of a research summary: one generated by an AI tool (ChatGPT, Copilot, Gemini — their choice), and one they wrote themselves after conducting their own source investigation.

Then ask them to annotate the differences.

Where did the AI get it right? Where did it oversimplify, hallucinate, or omit critical context? What sources did the AI cite — and do those sources actually say what it claims?

This assignment does several things at once: it validates that students can use AI (no performative bans needed), it builds metacognitive awareness about AI limitations, and it forces direct comparison between machine output and human-verified research. Students who do this exercise once tend to permanently recalibrate their trust in AI-generated content.

2. Lateral Reading Exercises — With AI Claims

Lateral reading is the practice fact-checkers use: instead of reading a source deeply and trying to evaluate it from the inside, you open multiple tabs and find out what other credible sources say about it.

Apply this directly to AI output. Give students a specific claim from a ChatGPT response and a 10-minute timer. Their task: verify or refute that claim using at least three independent sources. No AI assistance during the exercise.

The results are often striking. Students find outdated statistics, misattributed quotes, and confident-sounding claims that don't survive five minutes of lateral reading. It's not about gotcha moments — it's about building the reflex to check before trusting.

3. Source Comparison: AI Summary vs. Primary Source

Pick a topic your students are already studying. Run a ChatGPT query on it and print the response. Then pull the peer-reviewed article, government report, or primary source document that AI should have been drawing from.

Put both in front of students. Ask them to identify: What did the AI include? What did it leave out? Did it introduce claims not supported by the original? Did it accurately represent the author's conclusions?

This exercise is particularly effective because students can see the compression and distortion that happens when a large language model summarizes complex material. The primary source becomes legible in a new way — not as intimidating academic text, but as the thing the AI was approximating.

4. The "Prove It" Protocol

Simple, portable, and works at any grade level.

Every AI-sourced claim in a student's work requires a primary source citation before it can stay. No primary source? The claim comes out.

Students using this protocol quickly discover two things: (1) AI often can't tell them where it got something, and (2) when it does cite sources, those sources don't always say what AI claimed. The protocol isn't punitive — it's a habit-forming discipline. Researchers who ask "prove it" of every unverified claim are more rigorous, full stop.

5. An Evaluation Rubric That Accounts for AI

Most source evaluation rubrics — including the venerable CRAAP Test — were designed before generative AI existed as a research tool. They need updating.

When adapting your rubric for AI-era research, add explicit checks:

Traceability: Can every specific claim be traced to a named, verifiable source?
Currency of underlying sources: When was the AI's training data current? (Most models have a knowledge cutoff that may be 1–2 years behind.)
Consistency across tools: Does a different AI tool, or a direct source search, return the same information?
Synthesis transparency: Has the student verified the sources an AI cites, rather than trusting the citation?

A rubric that rewards this kind of verification teaches evaluation as a process, not a checkbox.

Where Sabia Librarian Fits In

Part of the challenge with AI literacy instruction is that it can feel abstract until students try it with real tools. Sabia Librarian is designed to function as a demonstration of AI that's built for verification — it surfaces primary sources, flags claims that need corroboration, and models the kind of cite-before-you-trust behavior we're trying to teach.

Several educators are using it as a classroom example: "Here's an AI tool. Here's how it approaches a research question differently than a general-purpose chatbot. What do you notice?"

It's not the only tool that fits this kind of lesson. But it's one that was designed with information literacy built in, not bolted on.

The Bigger Picture

Teaching source evaluation in 2026 isn't about convincing students that AI is bad. It's about giving them the judgment to use it well — and the skills to catch it when it's wrong.

The strategies above aren't new pedagogy. Lateral reading, primary source comparison, and citation verification are foundational information literacy practices. What's new is the urgency. Students without these skills aren't just writing weaker papers. They're navigating a world where machine-generated misinformation is indistinguishable from credentialed expertise at first glance.

That's the librarian's problem now. Which means it was always ours to solve.

Looking for a tool built around these principles? Visit sabialibrarian.com.

How to Teach Source Evaluation When Your Students Use ChatGPT

D. Ceabron Williams — Thu, 21 May 2026 12:53:27 +0000

Your job used to be teaching them how to find information. Now it's teaching them what to do with information they've already found — and why that second step is harder than it looks.

Here's what's working.

The "Don't Use AI" Policy Doesn't Work. Here's What Does.

The librarians and educators getting traction right now aren't fighting the tools. They're turning them into teaching material.

5 Strategies That Actually Work in the Classroom

1. The AI Audit Assignment

Then ask them to annotate the differences.

Where did the AI get it right? Where did it oversimplify, hallucinate, or omit critical context? What sources did the AI cite — and do those sources actually say what it claims?

2. Lateral Reading Exercises — With AI Claims

3. Source Comparison: AI Summary vs. Primary Source

4. The "Prove It" Protocol

Simple, portable, and works at any grade level.

Every AI-sourced claim in a student's work requires a primary source citation before it can stay. No primary source? The claim comes out.

5. An Evaluation Rubric That Accounts for AI

Most source evaluation rubrics — including the venerable CRAAP Test — were designed before generative AI existed as a research tool. They need updating.

When adapting your rubric for AI-era research, add explicit checks:

Traceability: Can every specific claim be traced to a named, verifiable source?
Currency of underlying sources: When was the AI's training data current? (Most models have a knowledge cutoff that may be 1-2 years behind.)
Consistency across tools: Does a different AI tool, or a direct source search, return the same information?
Synthesis transparency: Has the student verified the sources an AI cites, rather than trusting the citation?

A rubric that rewards this kind of verification teaches evaluation as a process, not a checkbox.

Where Sabia Librarian Fits In

Several educators are using it as a classroom example: "Here's an AI tool. Here's how it approaches a research question differently than a general-purpose chatbot. What do you notice?"

It's not the only tool that fits this kind of lesson. But it's one that was designed with information literacy built in, not bolted on.

The Bigger Picture

Teaching source evaluation in 2026 isn't about convincing students that AI is bad. It's about giving them the judgment to use it well — and the skills to catch it when it's wrong.

That's the librarian's problem now. Which means it was always ours to solve.

Looking for a tool built around these principles? Visit sabialibrarian.com.

How to Teach Source Evaluation When Your Students Use ChatGPT

D. Ceabron Williams — Thu, 21 May 2026 11:09:13 +0000

Your job used to be teaching them how to find information. Now it's teaching them what to do with information they've already found — and why that second step is harder than it looks.

Here's what's working.

The "Don't Use AI" Policy Doesn't Work. Here's What Does.

The librarians and educators getting traction right now aren't fighting the tools. They're turning them into teaching material.

5 Strategies That Actually Work in the Classroom

1. The AI Audit Assignment

Then ask them to annotate the differences.

Where did the AI get it right? Where did it oversimplify, hallucinate, or omit critical context? What sources did the AI cite — and do those sources actually say what it claims?

2. Lateral Reading Exercises — With AI Claims

3. Source Comparison: AI Summary vs. Primary Source

4. The "Prove It" Protocol

Simple, portable, and works at any grade level.

Every AI-sourced claim in a student's work requires a primary source citation before it can stay. No primary source? The claim comes out.

5. An Evaluation Rubric That Accounts for AI

Most source evaluation rubrics — including the venerable CRAAP Test — were designed before generative AI existed as a research tool. They need updating.

When adapting your rubric for AI-era research, add explicit checks:

Traceability: Can every specific claim be traced to a named, verifiable source?
Currency of underlying sources: When was the AI's training data current? (Most models have a knowledge cutoff that may be 1–2 years behind.)
Consistency across tools: Does a different AI tool, or a direct source search, return the same information?
Synthesis transparency: Has the student verified the sources an AI cites, rather than trusting the citation?

A rubric that rewards this kind of verification teaches evaluation as a process, not a checkbox.

Where Sabia Librarian Fits In

Several educators are using it as a classroom example: "Here's an AI tool. Here's how it approaches a research question differently than a general-purpose chatbot. What do you notice?"

It's not the only tool that fits this kind of lesson. But it's one that was designed with information literacy built in, not bolted on.

The Bigger Picture

Teaching source evaluation in 2026 isn't about convincing students that AI is bad. It's about giving them the judgment to use it well — and the skills to catch it when it's wrong.

That's the librarian's problem now. Which means it was always ours to solve.

Looking for a tool built around these principles? Visit sabialibrarian.com.

The CRAAP Test in the Age of AI — A Librarian's Updated Checklist

D. Ceabron Williams — Sun, 17 May 2026 19:34:52 +0000

The CRAAP Test in the Age of AI — A Librarian's Updated Checklist

The CRAAP test has been a librarian's best friend since 2004, when Sarah Blakeslee first published it in the CSU Chico library's quarterly. Currency, Relevance, Authority, Accuracy, Purpose. Five questions. No jargon. It worked beautifully for journal articles, news stories, and government reports — sources with authors, institutions, and publication dates you could actually look up.

Then came AI.

In 2025, ECPI University's library documented something striking: AI chatbots fail three of the five CRAAP criteria outright, and are weak in the remaining two. Not because they're malicious — but because the test was designed for sources with institutional accountability, and AI outputs simply don't have that.

If you're teaching or using the CRAAP test today, it needs an update. Here's what that looks like.

Currency: When Was This Actually Written?

Traditional currency check: When was this published? Is it recent enough for my topic?

AI-era addition: What is this AI model's knowledge cutoff?

Large language models don't know what they don't know. GPT-4o knows nothing about events after its training cutoff. Claude 3.5 Sonnet has a knowledge date. Gemini Ultra has its own. When you ask an AI about a recent law, technology, or policy, the answer may be confidently wrong — not because the AI is lying, but because it has no data on events that happened after it was trained.

Updated check: For any AI-sourced claim about laws, standards, technologies, or policies — search for the most recent source on that specific topic. If a 2026 article contradicts an AI output that may have been trained on 2024 data, trust the article.

Relevance: Could a Human Have Written This?

Traditional relevance check: Does this match my research question?

AI-era addition: Does this feel generic? Would a subject-matter expert with lived experience say it this way?

One of the clearest signs of AI-generated content is what I call the "confident vagueness" problem. The text is fluent, structured, and technically correct — but it never says anything a person who actually did the work would say. It has no rough edges, no specific failures, no real-world complications. It describes things as they should be in a textbook, not as they are in practice.

Updated check: Ask whether the source reflects the kind of nuance, specificity, or honest uncertainty that only comes from direct experience. If the content is smooth and generic with no texture, be suspicious.

Authority: Who Said This, Actually?

Traditional authority check: Who is the author? What are their credentials?

AI-era addition: Is this author's existence verifiable outside the source itself?

This is where AI content gets genuinely dangerous. AI tools cite Reddit and Wikipedia more than any other source category (Semrush, 2025). When an AI generates a claim and attributes it to a study, an expert, or a news article — you cannot assume that citation actually exists.

A 2024 study found that 30% of AI-generated citations led to papers that do not exist. Not misquoted — fabricated. The AI predicted what a citation would look like and generated one that sounded plausible.

Updated check: Every citation from an AI tool must be verified. Search for the author, the article title, the journal name. Check whether it appears in a reputable academic index (Google Scholar, JSTOR, PubMed, Web of Science). If you can't find it, the AI invented it.

When verifying an author's authority, look beyond the byline. Does the person exist in professional databases? Does their institutional affiliation check out? AI-generated bios — complete with plausible credentials and publication histories — are becoming common enough that the old "read the About page" check is no longer sufficient.

Accuracy: Is This Actually True?

Traditional accuracy check: Can I cross-reference this with other sources?

AI-era addition: Can I find the primary source, or am I only finding secondary AI summaries?

This is the hardest part. AI outputs are fluent enough that they feel verified. A well-structured paragraph with a statistic and a citation looks like a polished source — even when neither the statistic nor the citation is real.

The solution is not more fact-checking within the AI. It's leaving the AI entirely.

Updated check: Use the lateral reading method (which I covered in detail in a previous article). Leave the AI output. Open a new tab. Search for the specific claim in academic databases, news archives, or government publications. Apply the Rule of Three: find at least three independent, credible sources confirming the same fact before trusting it.

When an AI cites a study, find the actual study. When it cites a case law, pull the actual case. When it attributes a statistic, find the original data source. Do not trust summaries of sources — trust the sources themselves.

Purpose: What Is This Trying to Do?

Traditional purpose check: Is this informing, persuading, or selling?

AI-era addition: Is this output optimized for engagement or agreement, not accuracy?

Here is something the original CRAAP test didn't anticipate: AI outputs are optimized for being satisfying, not for being correct. A language model's training objective is to continue text in a way that sounds plausible to a human reader. Plausibility and accuracy are different things.

A polished, confident, well-structured AI response can be completely wrong and feel completely right. The fluency is not evidence of quality — it is evidence of statistical pattern-matching.

Updated check: Ask what the AI is optimized for. If you're using it to generate a first draft, to summarize existing material, or to brainstorm — that's appropriate use. If you're using it as a primary source of factual claims with no independent verification — that's a problem.

Quick Reference: Updated CRAAP Checklist for AI Content

CURRENCY
☐ Note the AI model's knowledge cutoff date
☐ Verify claims against sources published after that cutoff
☐ Check whether the topic has changed since the model's training date

RELEVANCE
☐ Does the content reflect domain-specific nuance?
☐ Could a practitioner with lived experience have written this?
☐ Does it include real-world complications, failures, or contradictions?

AUTHORITY
☐ Verify every citation independently — do not trust AI-generated references
☐ Check author credentials outside the source itself
☐ Cross-reference claims against domain experts and established institutions

ACCURACY
☐ Leave the AI output — don't fact-check inside the chat
☐ Find the primary source for every claim, not summaries
☐ Apply the Rule of Three: 3+ independent credible sources = confirmed

PURPOSE
☐ Is this content informing or just sounding informative?
☐ Is the AI tool being used as a search engine or a primary source?
☐ Would I trust this claim if it appeared without any citation?

How This Fits Into Practice

These checks aren't meant to make you distrust AI — they're meant to make you use it correctly. AI tools are powerful for drafting, brainstorming, explaining concepts, and synthesizing information. They fail when treated as authoritative sources of verified fact.

The updated CRAAP test gives you a vocabulary for that distinction. Currency becomes a data cutoff question. Relevance becomes a human-experience question. Authority becomes a citation verification question. Accuracy becomes a "get to the primary source" question. Purpose becomes an optimization question.

A Tool Built for This

When I evaluate sources through Sabia's evaluator, it applies these structural checks as part of the process — flagging when citations lack verification, when claims appear without corroboration, and when content has the characteristics of AI-generated text rather than documented research. If you want a systematic way to apply this checklist to the sources you encounter, sabialibrarian.com is built for exactly that.

The CRAAP test was good enough for twenty years of information literacy instruction. With a few AI-specific additions, it's good enough for twenty more.

How to Verify AI-Generated Content (A Librarian's Framework)

D. Ceabron Williams — Thu, 14 May 2026 10:44:40 +0000

In January 2025, a university professor submitted a sworn declaration to a federal court. He was an expert on AI misinformation. The filing was about the dangers of AI-generated content.

It contained three hallucinated citations — generated by the very ChatGPT he was warning the court about.

Judge Laura M. Provinzino called it "the irony." Professor Hancock — credentialed, published, credible on the stand — had been fooled by his own tool. The citations attributed articles to authors who had never written them, on topics slightly adjacent to his actual expertise.

This is not an edge case. It's the defining verification challenge of our moment.

Why Traditional Fact-Checking Breaks Down

Before we get into the framework, let's be clear about what's different.

Traditional fact-checking works when there's a traceable source. A newspaper article has a publication date, an author, an outlet with editorial standards. A research paper has a journal, peer review, a DOI. A government report has an agency, a contact, a PDF.

You can look up the author. You can check the publication. You can verify the outlet exists and has standards.

AI content has none of this.

When a language model generates a confident claim — "The FDA approved this drug in 2023" or "Case law establishes that X" — there is no author, no publication date, no institutional accountability. There is only text that sounds like it could have come from a credible source.

The tool does not know it is lying. It has no ground truth. It generates the most statistically likely continuation of the prompt, regardless of whether that continuation is true.

This is what we call hallucination. And it is structurally different from the typos, biases, or oversights you find in human-authored content.

The Librarian's Verification Framework

Here's what to do instead. I've organized this around five moves — each one borrowed from how professional fact-checkers and research librarians evaluate sources they've never seen before.

1. Lateral Reading — Leave the Page

The most effective fact-checking technique professional fact-checkers use is called lateral reading. The core insight: instead of analyzing the source in front of you, you leave it and check what independent, trusted sources say about it.

With AI content, this means asking a different question than you would with a traditional source.

Traditional source: Who created this?
AI output: Who else is saying this?

When you encounter a claim from an AI tool, fractionate it — break the output into individual assertions — and open a new tab. Search for each claim by its key terms. Look for corroboration from news organizations, academic databases, government sites, or established fact-checking organizations (Duke Reporters Lab, PolitiFact, Africa Check, Full Fact).

A useful rule of thumb: the Rule of Three. Find at least three independent, credible sources that confirm the same fact. If you can't find any, treat the claim as suspect.

2. Verify Citations Before You Trust Them

Hallucinated citations are the single clearest signal that you're dealing with AI-generated content that may be unreliable.

This is not just a theoretical concern. The Damien Charlotin AI Hallucination Cases database has logged over 160 documented cases since 2023. The Johnson v. Dunn case (N.D. Ala., July 2025) resulted in sanctions against a large law firm for submitting a brief containing hallucinated case citations — generated by the same AI the firm had explicitly warned its attorneys not to use.

When an AI tool gives you a case citation, a journal article, a statistic attributed to a study — verify it. Search for the case name, the article title, the author. Check whether the work actually exists. If the citation doesn't appear in a reputable legal database, academic index, or news archive, the AI invented it.

This step is non-negotiable in any professional or academic context.

3. Check the Date — and Look for What's Newer

AI training has a cutoff date. When you ask about recent developments, the model's answer is often based on training data that predates the event you're asking about.

Before accepting any AI claim about a law, a standard, a technology, or a policy — ask: is this current? Search for the most recent update on this topic. If your search finds a 2025 or 2026 source that contradicts an AI output that may have been trained on 2023 data, trust the newer source.

This is especially important for technical content. The AI may confidently recommend a library version that was deprecated two years ago, cite a specification that was superseded, or describe a regulatory framework that has since changed.

4. Assess the Source — or the Absence of One

Every credible source has a chain of accountability. An author, an institution, a publication, a date, a contact. You can look these up. You can evaluate whether they have expertise, what their incentives are, whether their track record is solid.

When AI generates content, that chain is often missing. There is no author, no institution, no editorial process. Just text.

Source triangulation replaces the traditional authority check. If the AI makes a claim about medical evidence, find the actual medical journal. If it cites a legal standard, find the actual statute or case. If it describes a technical specification, go to the standards body or the primary source.

Look for: Who else is saying this? If the claim appears nowhere in the domain's credible literature — not in a journal, not in an official publication, not in an established reference — treat it as suspect.

5. Look for Provenance Signals (When Applicable)

For images, audio, and video, C2PA (Coalition for Content Provenance and Authenticity) Content Credentials are beginning to provide cryptographic provenance metadata — a tamper-evident record of whether a file was created by a camera, edited in software, or generated by an AI model.

This only works for content that implements C2PA at the source. OpenAI, Adobe, Google, and Meta now embed these manifests in AI-generated content. If an image carries a Content Credentials badge, you can verify its origin by visiting contentcredentials.org/verify.

For text content, this step doesn't apply — but the preceding four steps do, and they're more than sufficient.

A Practical Workflow

Here's how this plays out in practice:

Get the AI output. Note the specific claims, not the overall impression.
Leave the chat. Open new tabs. Don't analyze — search.
Search each claim by key terms. Apply the Rule of Three.
Check the date. Look for 2025–2026 sources. Trust newer over older.
Verify citations. Pull the actual case, article, or study.
Triangulate. Find the credible domain literature. If it's not there, the claim is suspect.
Apply CRAAP (Currency, Relevance, Authority, Accuracy, Purpose) to everything you find.

How Sabia Fits Into This

This framework — lateral reading, citation verification, source triangulation, CRAAP — is exactly what I use when evaluating a source through Sabia's evaluator. The tool doesn't just check whether content sounds credible; it applies these structural checks and flags when claims lack corroboration or when citations may be fabricated.

If you want a structured way to apply this framework to the AI outputs you encounter, sabialibrarian.com is built for exactly that.

5 Red Flags That a Source Is Unreliable (and How to Check in 60 Seconds)

D. Ceabron Williams — Fri, 08 May 2026 07:01:08 +0000

You've all been there. You find an article that sounds authoritative. The writing is confident. The claims are specific. But something feels off. And by the time you've verified it, you've already shared it with two people.

The problem is real: 78% of students globally can't reliably distinguish credible sources from fabrications. Worse, AI is making this problem exponentially harder. ChatGPT hallucinations that sound like expert analysis. "Expert" blogs written entirely by language models. Wikipedia pages edited by people with axes to grind.

🔍 Want to skip the manual work? Sabia gives you an instant credibility analysis — author verification, citation count, language analysis, and a credibility score — all in under 60 seconds.

👉 Try Sabia Free at sabialibrarian.com →

The good news? You don't need a librarian to spot the fakes. You need to know what to look for.

Here are five red flags that should make you pause before trusting a source — and a 60-second check that takes the guesswork out.

Red Flag #1: No Author Byline or Credentials

The problem: Anonymous content has no accountability. If something is wrong, who are you holding responsible?

What to look for:

No author name listed at all
Author name with zero professional history (no LinkedIn, no previous publications, no "About" page)
Credentials that sound impressive but are vague ("Digital Strategist," "Content Creator," "AI Expert")

Real example: A viral article claiming a new AI breakthrough that cited zero sources and had no author byline. When someone dug into it, the domain was registered two weeks prior under a privacy proxy. It was marketing hype masquerading as news.

The fix: Hover over the author name. Does a real profile exist? Has this person published elsewhere? Are they a domain expert or just someone with a compelling opinion?

Red Flag #2: No Publication Date (or Very Old)

The problem: Outdated information is everywhere. AI tools, regulations, and research change monthly. A "guide to social media marketing" from 2019 is functionally useless.

What to look for:

No visible publication or update date
A date from 5+ years ago (without a recent update notice)
A date that contradicts the content ("We're excited to announce this new technology" from 2015)

Real example: A guide claiming the "best practices" for API authentication was published in 2009. It recommended approaches that are now security vulnerabilities. Hundreds of developers had bookmarked and shared it because it ranked well on Google.

The fix: Scroll to the bottom of the page. Most legitimate publications timestamp their content. If it's not there, it's a red flag. If it's old, check the date on related sources — are they consistently dated, or did this one slip through without updates?

Red Flag #3: Emotional or Sensationalist Language

The problem: Emotions bypass critical thinking. Headlines like "THIS ONE WEIRD TRICK" or "SHOCKING TRUTH" are designed to bypass your skepticism, not to inform you.

What to look for:

ALL CAPS phrases
Excessive exclamation marks (more than one per paragraph)
Words like "shocking," "exposed," "they don't want you to know," "finally revealed"
Loaded language instead of neutral description ("devastating impact" vs. "15% decrease")

Real example: An article claiming a supplement "destroys cancer cells" (emotional, implies guarantee) vs. a peer-reviewed study that "shows compound X inhibited tumor growth in laboratory conditions" (specific, provisional, honest about the limitations). Same research. Totally different credibility.

The fix: Rewrite the claim in neutral language. If you can't do it without losing the point, the source is probably trying to manipulate you.

Red Flag #4: No Citations or References

The problem: Good sources cite their sources. Bad sources hope you don't notice they're making it up.

What to look for:

Claims with zero supporting links or citations
"Studies show..." without naming the study or linking to it
Quotes without attribution
Statistics without a source ("90% of people agree...")

Real example: A blog post claimed that "recent research proves remote work reduces productivity by 40%." No citation. Turned out the author had invented the number. The post got 100K shares because it confirmed what people already believed.

The fix: Google a specific claim or statistic from the article. If you can't find the source the author references, it probably doesn't exist.

Red Flag #5: Unfamiliar Domain with No "About" Page

The problem: Legitimate organizations (news outlets, research institutions, publications) have established domains and clear organizational information. Spammy sites hide who they are.

What to look for:

A domain name that looks like a major publication but isn't quite right ("nytimes-news.com" instead of "nytimes.com")
New domains (registered within the last year)
No "About" page explaining the publication's mission or team
No contact information or editorial guidelines

Real example: A site called "Medical Science Daily" (sounds official, right?) published articles claiming unproven treatments for serious diseases. The domain was registered to a company that sells supplements. No "About" page, no editorial team listed. Just articles designed to drive traffic to sales pages.

The fix: Check the domain registration date (use WHOIS lookup) and the site's "About" page. Legitimate publications have clear organizational identity.

The 60-Second Check

All of this takes time — time you probably don't have. Which is why I built Sabia.

Paste a URL into Sabia and get an instant credibility analysis: author verification, publication date, citation count, language analysis, and a credibility score — all in under a minute.

It's like having a librarian in your browser.

🚀 Try Sabia Free → sabialibrarian.com

Final Thought

You're going to encounter thousands of sources in your lifetime. You can't verify each one manually. But you can train yourself to spot the patterns that separate credible sources from noise.

And when you need to verify fast? That's what Sabia is for →

Share this with someone who needs it. Information literacy is a team sport.

By **D. Ceabron Williams, M.L.* — Librarian, information literacy researcher, and builder of source credibility tools*

A librarian's guide to evaluating sources in the age of AI

D. Ceabron Williams — Wed, 06 May 2026 19:51:02 +0000

The problem isn't AI. It's us.

Every day, developers ask ChatGPT, Claude, and Perplexity for code samples, architecture patterns, and technical explanations. We copy the answer. We ship it. We move on.

But here's what we don't ask: Where did that come from?

AI generates answers that sound authoritative—fluent, confident, well-structured. It does not tell you where the information originated. And when you ask for citations, it confidently generates ones that don't exist.

This isn't a bug in AI. It's a feature of how language models work. They predict the next most likely word based on patterns in training data. When they don't have a fact, they guess. And they guess so convincingly that MIT research in 2025 found they're 34% more confident when lying than when telling the truth.

The stakes are real.

In 2025, Deloitte submitted a $440,000 report to the Australian government—complete with fabricated academic sources. In November 2025, a $1.6 million health plan for Newfoundland & Labrador was discovered to contain at least four citations to non-existent research papers. In September 2025, a lawyer in San Francisco was sanctioned by a federal judge for submitting AI-hallucinated case citations to the court.

Over 700 legal cases in 2025 alone involved AI-generated hallucinated content. In academic publishing, NeurIPS 2025 accepted 4,841 papers—and GPTZero identified at least 100+ hallucinated citations across 53 papers, despite rigorous peer review.

For developers: A hallucination in your architecture recommendation doesn't get you sued. But it does get copied into production, into tutorials, into the next person's codebase. The technical debt compounds.

You already know how to solve this. You just don't know it.

Librarians have been evaluating sources for centuries. Long before Google, before citation indexes, before the internet itself, they built frameworks to determine: Is this source trustworthy? Where did this come from? Who benefits if I believe it?

These frameworks are still the gold standard for information evaluation. And they work perfectly for AI-generated content.

The Librarian's Framework: CRAAP

The most widely taught evaluation method in libraries is CRAAP:

Currency — When was this published or last updated? Is it current for my use?
Relevance — Does it actually address my question?
Authority — Who created this? What are their credentials?
Accuracy — Can I verify the claims? Are there citations? Can I cross-check them?
Purpose — Why does this exist? Who benefits from me believing it?

When you ask AI for a code sample, you're asking it to be a source. Apply CRAAP:

Currency? AI training data has a knowledge cutoff. If you ask ChatGPT about a library update from last month, you're asking it to guess.

Relevance? AI often answers the question you asked, not the question you need answered. It optimizes for plausibility, not precision.

Authority? An AI has no credentials, no affiliation, no reputation on the line. It's predicting words. When authority matters—cryptographic best practices, HIPAA compliance, security-critical algorithms—you need a source that can be wrong and suffer consequences.

Accuracy? A Columbia Journalism Review analysis found ChatGPT hallucinated citations 67% of the time. Grok-3 hallucinated 94% of the time when asked to identify the original source of news excerpts.

Purpose? AI has no purpose beyond the next token. It's not trying to help you or mislead you. It's generating statistically likely text. That neutrality doesn't make it reliable.

Three Real Hallucinations (and What They Cost)

Example 1: The Fabricated Legal Citation

In September 2025, attorney Katherine Cervantes submitted a brief to U.S. District Court citing a case that was completely invented. The judge sanctioned her—and later sanctioned her supervising partner for insufficient oversight of AI use.

For developers: If AI recommends a library, verify it exists on npm. Run npm view <library>. Check GitHub. Look at the commit history. A hallucinated library recommendation won't get you sued, but it will get copy-pasted.

Example 2: The Government Report with Fake Sources

Deloitte's 2025 report to the Australian government included several invented academic references. A $440,000 contract now under review—and scrutiny on every other AI-generated deliverable.

For developers: If you use AI to write documentation, architecture decisions, or threat models—verify every external claim. Don't assume the AI knows the difference between "standard practice" and "thing I hallucinated."

Example 3: The Predatory Journal Flooded with AI Hallucinations

In 2025–2026, lower-tier academic journals published hundreds of papers with AI-generated citations and fabricated data summaries. Many passed peer review. Why? Reviewers didn't have tools to detect hallucinations at scale.

For developers: Your code reviews catch logic errors. You need a different check for AI-generated components: Does every external claim have a verifiable source?

How to Evaluate AI Sources: The Practical Workflow

Step 1: Assume it's wrong until proven right.

When AI gives you an answer, don't ask "Does this look right?" Ask "Can I verify this independently?" Hallucinations look right. They're fluent, confident, well-structured. Your job is to override that instinct.

Step 2: Check the citation (the ACCURACY check).

If AI provides a source, verify it exists:

Copy the exact claim into Google Scholar
Search for the exact paper title
If it doesn't exist, it's hallucinated
If it exists but says something different, it's misattributed

A study tested eight AI assistants on identifying original news sources:

Perplexity: 37% hallucination rate
ChatGPT: 67% hallucination rate
Grok-3: 94% hallucination rate

None expressed uncertainty despite being wrong most of the time.

Step 3: Use lateral reading (the AUTHORITY check).

Open a new browser tab and search for the topic independently. Cross-reference multiple sources. When you read three independent sources, disagreement screams.

Step 4: Check the purpose (the PURPOSE check).

Ask: Who might have trained the model on this information? What assumptions are baked into the training data? If the AI recommends a popular framework, check if that's because it's genuinely better—or because it's more common in training data.

Step 5: Verify currency (the CURRENCY check).

Always ask the AI: What's your knowledge cutoff date? Then assume knowledge from the last 3–6 months is unreliable.

Where AI Actually Fails (and When to Trust It More)

It fails on:

Recent events or updates (knowledge cutoff)
Citations and attribution (fabrication by design)
Niche or specialized domains (sparse training data)
Things that only exist in paywalled sources

You can trust it more on:

Writing and editing (LLMs are good at language)
Brainstorming and ideation (generating options, not facts)
Summarization of content you provide
Refactoring and code style
Explaining concepts you already partially understand

The difference: Generative tasks are safer than retrieval tasks. Generate code from your spec. Don't retrieve "best practices" without verification.

The Tool That Does This Automatically

A librarian evaluates a source by looking at who created it, when, where, and for what purpose. They spot inconsistencies. They verify citations. They integrate multiple signals into a judgment call.

That's what Sabia does.

Sabia evaluates any URL in 30–60 seconds using librarian-grade criteria:

Authorship: Who wrote this? What are their credentials?
Publication: Where did this come from? Is it peer-reviewed, editorial, self-published?
Currency: When was it published?
Accuracy: Are claims supported by citations?
Objectivity: Does the source have a clear bias or agenda?

Feed Sabia a URL that an AI recommended—a tutorial, a research paper, a documentation page—and it tells you: Is this trustworthy? Who should trust this? What's the catch? Can I cite this?

It's what a librarian would do in real time. Except Sabia works while you code.

Why This Matters Beyond Not Getting Sued

A hallucinated architecture recommendation gets copied into production. The next developer inherits it. They don't know it came from an AI, so they treat it as established practice. Months later, when performance degrades or security issues arise, the investigation starts with "This is how we've always done it."

You wouldn't ship code without code review. Don't ship AI-generated information without information review.

The Framework You Already Have

You know how to do this. You do it every day in code review:

Authority: Does this PR come from someone who understands the system?
Accuracy: Are the changes correct?
Currency: Is this solution current, or are we using an outdated pattern?
Relevance: Does this solve the actual problem?
Purpose: What's the intent here? Is there a hidden cost?

These are the exact questions a librarian asks about sources. Apply that same rigor to AI-generated sources. It's not a new skill—it's a skill you already have, applied to a new problem.

Start Here

Next time you ask AI a question: Screenshot the answer and the source.
Verify one claim: Use Google Scholar. Does the cited paper exist?
Cross-check laterally: Search for the topic independently.
Keep a scorecard: How often does AI get this right?
Use Sabia for high-stakes sources: Try it at sabialibrarian.com.

Information literacy in the age of AI isn't about distrusting AI. It's about trusting yourself to be the filter AI can't be.