Source Evaluation Criteria
Detailed criteria for assessing source reliability and authority.
The CRAAP Test (Modified for AI Research)
For each source, evaluate:
Currency
| Factor |
High Quality |
Low Quality |
| Publication date |
Within 1-2 years for tech; 5 years for stable topics |
Undated or >5 years old |
| Last updated |
Recently revised |
No revision history |
| Links |
Working, current |
Broken, outdated |
| Version specificity |
Matches current versions |
References deprecated APIs/features |
Red flags:
- No date anywhere on the page
- References to "new" features that are now standard
- Broken external links
- Deprecated syntax or APIs
Relevance
| Factor |
High Quality |
Low Quality |
| Depth |
Directly addresses the question |
Tangentially related |
| Audience |
Appropriate technical level |
Too basic or too advanced |
| Scope |
Focused on specific topic |
Overly broad coverage |
| Applicability |
Matches user's context |
Different domain/use case |
Authority
| Factor |
High Quality |
Low Quality |
| Author credentials |
Named expert with verifiable background |
Anonymous or unknown |
| Publisher |
Recognized organization, institution |
Unknown domain |
| Peer review |
Academic journal, official docs |
Self-published |
| Citations |
Well-cited by others |
No external citations |
Authority indicators by domain:
| Domain Type |
Authority Signals |
| .gov |
Government agency, high authority for regulations/data |
| .edu, .ac.* |
Academic institution, peer-reviewed research |
| .org |
Varies widely; check specific organization |
| Official docs |
Primary source for that product/service |
| GitHub |
Check stars, contributors, maintenance activity |
| Medium/blogs |
Highly variable; verify author credentials |
Accuracy
| Factor |
High Quality |
Low Quality |
| Citations |
Claims backed by references |
Unsourced assertions |
| Verifiability |
Can be checked against primary sources |
Unverifiable claims |
| Consistency |
Agrees with other authoritative sources |
Contradicts consensus |
| Methodology |
Clear, reproducible |
Vague or absent |
Verification techniques:
- Check if cited sources actually support the claims
- Cross-reference with official documentation
- Test code examples if possible
- Look for corroborating independent sources
Purpose
| Factor |
High Quality |
Low Quality |
| Objectivity |
Educational, informational |
Marketing, promotional |
| Transparency |
Disclosures, clear ownership |
Hidden affiliations |
| Tone |
Balanced, evidence-based |
Sensational, one-sided |
| Intent |
Help reader understand |
Sell product/service |
Bias indicators:
- Affiliate links without disclosure
- Only positive coverage of a product
- Attacks on competitors
- Sponsored content not clearly labeled
- Author works for company being discussed
Source Type Reliability Hierarchy
From most to least reliable (general guidelines, exceptions exist):
- Primary sources — Official documentation, original research, firsthand accounts
- Academic/peer-reviewed — Journal articles, conference papers, institutional research
- Authoritative secondary — Well-sourced news from reputable outlets, industry analyst reports
- Expert analysis — Known experts writing in their field, with citations
- Community consensus — High-vote Stack Overflow answers, widely-used GitHub repos
- General secondary — Wikipedia (follow its sources), established tech blogs
- Individual opinions — Personal blogs, forum posts, social media
- Unknown/anonymous — Unsourced claims, SEO content farms, AI-generated without verification
Red Flags That Lower Source Trust
Content Red Flags
Technical Red Flags
Structural Red Flags
Evaluating AI-Generated Content
AI content is increasingly common; evaluate carefully:
Warning signs of unverified AI content:
- Generic, surface-level coverage
- Confident claims without citations
- Plausible-sounding but incorrect technical details
- Inconsistencies within the same article
- Lack of specific examples or real-world context
Mitigation:
- Never trust AI summaries as primary sources
- Always trace claims back to original sources
- Verify technical claims against official docs
- Test code examples before accepting them
Source Evaluation Checklist
Before citing any source, verify:
- [ ] Author/organization identified and credible
- [ ] Publication date is acceptable for topic
- [ ] Claims are consistent with other sources
- [ ] Technical content is current and accurate
- [ ] No obvious commercial bias
- [ ] URL is functional and content is accessible
Recording Source Quality
When documenting research, include:
| Source | Type | Authority | Recency | Bias Risk | Notes |
|--------|------|-----------|---------|-----------|-------|
| [URL] | Official docs | High | Current | Low | Primary source |
| [URL] | Blog post | Medium | 2023 | Medium | Author works at competitor |
| [URL] | Research paper | High | 2022 | Low | Peer-reviewed, highly cited |
1---2name: 1254-source-evaluation-9bc285fb3description: Source Evaluation Criteria4---5# Source Evaluation Criteria67Detailed criteria for assessing source reliability and authority.89## The CRAAP Test (Modified for AI Research)1011For each source, evaluate:1213### Currency1415| Factor | High Quality | Low Quality |16|--------|--------------|-------------|17| Publication date | Within 1-2 years for tech; 5 years for stable topics | Undated or >5 years old |18| Last updated | Recently revised | No revision history |19| Links | Working, current | Broken, outdated |20| Version specificity | Matches current versions | References deprecated APIs/features |2122**Red flags:**23- No date anywhere on the page24- References to "new" features that are now standard25- Broken external links26- Deprecated syntax or APIs2728### Relevance2930| Factor | High Quality | Low Quality |31|--------|--------------|-------------|32| Depth | Directly addresses the question | Tangentially related |33| Audience | Appropriate technical level | Too basic or too advanced |34| Scope | Focused on specific topic | Overly broad coverage |35| Applicability | Matches user's context | Different domain/use case |3637### Authority3839| Factor | High Quality | Low Quality |40|--------|--------------|-------------|41| Author credentials | Named expert with verifiable background | Anonymous or unknown |42| Publisher | Recognized organization, institution | Unknown domain |43| Peer review | Academic journal, official docs | Self-published |44| Citations | Well-cited by others | No external citations |4546**Authority indicators by domain:**4748| Domain Type | Authority Signals |49|-------------|-------------------|50| .gov | Government agency, high authority for regulations/data |51| .edu, .ac.* | Academic institution, peer-reviewed research |52| .org | Varies widely; check specific organization |53| Official docs | Primary source for that product/service |54| GitHub | Check stars, contributors, maintenance activity |55| Medium/blogs | Highly variable; verify author credentials |5657### Accuracy5859| Factor | High Quality | Low Quality |60|--------|--------------|-------------|61| Citations | Claims backed by references | Unsourced assertions |62| Verifiability | Can be checked against primary sources | Unverifiable claims |63| Consistency | Agrees with other authoritative sources | Contradicts consensus |64| Methodology | Clear, reproducible | Vague or absent |6566**Verification techniques:**671. Check if cited sources actually support the claims682. Cross-reference with official documentation693. Test code examples if possible704. Look for corroborating independent sources7172### Purpose7374| Factor | High Quality | Low Quality |75|--------|--------------|-------------|76| Objectivity | Educational, informational | Marketing, promotional |77| Transparency | Disclosures, clear ownership | Hidden affiliations |78| Tone | Balanced, evidence-based | Sensational, one-sided |79| Intent | Help reader understand | Sell product/service |8081**Bias indicators:**82- Affiliate links without disclosure83- Only positive coverage of a product84- Attacks on competitors85- Sponsored content not clearly labeled86- Author works for company being discussed8788## Source Type Reliability Hierarchy8990From most to least reliable (general guidelines, exceptions exist):91921. **Primary sources** — Official documentation, original research, firsthand accounts932. **Academic/peer-reviewed** — Journal articles, conference papers, institutional research943. **Authoritative secondary** — Well-sourced news from reputable outlets, industry analyst reports954. **Expert analysis** — Known experts writing in their field, with citations965. **Community consensus** — High-vote Stack Overflow answers, widely-used GitHub repos976. **General secondary** — Wikipedia (follow its sources), established tech blogs987. **Individual opinions** — Personal blogs, forum posts, social media998. **Unknown/anonymous** — Unsourced claims, SEO content farms, AI-generated without verification100101## Red Flags That Lower Source Trust102103### Content Red Flags104105- [ ] No author attribution106- [ ] No publication or update date107- [ ] No citations or references108- [ ] Claims that can't be verified109- [ ] Sensational or clickbait headlines110- [ ] Grammatical errors or poor writing quality111- [ ] Contradicts well-established facts112- [ ] "According to experts" without naming them113114### Technical Red Flags115116- [ ] Deprecated or non-working code examples117- [ ] Incorrect technical terminology118- [ ] Advice that contradicts official docs119- [ ] Missing security considerations120- [ ] Platform/version mismatch with current reality121122### Structural Red Flags123124- [ ] Excessive ads or pop-ups125- [ ] Content hidden behind paywalls with no credentials126- [ ] Domain looks like a content farm127- [ ] No About page or organizational info128- [ ] Recently created domain with authoritative claims129130## Evaluating AI-Generated Content131132AI content is increasingly common; evaluate carefully:133134**Warning signs of unverified AI content:**135- Generic, surface-level coverage136- Confident claims without citations137- Plausible-sounding but incorrect technical details138- Inconsistencies within the same article139- Lack of specific examples or real-world context140141**Mitigation:**142- Never trust AI summaries as primary sources143- Always trace claims back to original sources144- Verify technical claims against official docs145- Test code examples before accepting them146147## Source Evaluation Checklist148149Before citing any source, verify:150151```markdown152- [ ] Author/organization identified and credible153- [ ] Publication date is acceptable for topic154- [ ] Claims are consistent with other sources155- [ ] Technical content is current and accurate156- [ ] No obvious commercial bias157- [ ] URL is functional and content is accessible158```159160## Recording Source Quality161162When documenting research, include:163164```markdown165| Source | Type | Authority | Recency | Bias Risk | Notes |166|--------|------|-----------|---------|-----------|-------|167| [URL] | Official docs | High | Current | Low | Primary source |168| [URL] | Blog post | Medium | 2023 | Medium | Author works at competitor |169| [URL] | Research paper | High | 2022 | Low | Peer-reviewed, highly cited |170```