---
name: rankizz-write-tool-listicle
description: Research and write a best-tools, top-tools, software roundup, or niche buyer's-guide listicle with explicit inclusion criteria, consistent evidence, use-case recommendations, current pricing, meaningful drawbacks, disclosures, and enough detail for the list to stand on its own. Use when a user asks for "best X tools," "top X software," a ranked product list, a shortlist for a niche, or an editorial tools roundup. Rankizz keyword and SERP data is optional; current product and pricing research is required.
---

# Write a tool listicle

Help a specific reader build a shortlist. Do not manufacture a ranking from copied feature lists, affiliate payouts, brand fame, or a requested number of entries.

Read [references/listicle-evidence.md](references/listicle-evidence.md) before choosing or ranking tools.

## Define the list

Resolve:

- niche, reader, company size, skill level, and region
- job the reader needs to complete
- non-negotiable capabilities and disqualifiers
- budget model, currency, and billing preference
- whether the publisher tested any products
- publisher relationships, affiliate links, sponsorships, or ownership
- requested number of tools and whether enough qualified options exist
- research cutoff date

If only seven products qualify for a requested `top 10`, publish seven. Do not add weak entries to satisfy a number in the headline.

## Design the methodology first

Choose criteria before selecting winners. Keep the criteria specific to the niche. A useful rubric may include:

- task success and output quality
- required workflow coverage
- usability for the stated audience
- integration and data portability
- reliability, support, privacy, or security where relevant
- total cost at the reader's likely usage
- important limitations and switching costs

Set weights only when the evidence supports scoring. Avoid false precision such as `8.7/10` from subjective impressions. A transparent `meets`, `partly meets`, `does not meet`, or `not verified` scale is often more honest.

State:

- what was hands-on tested
- what was verified from official sources
- what came from named independent sources
- when facts and prices were checked
- how affiliate or ownership relationships affect the page

## Build an evidence matrix

Research every candidate with the same core questions. Prefer current official product pages, documentation, pricing, limits, security material, changelogs, and terms. Use independent sources for experience or reliability claims that official pages cannot prove.

| Tool | Best-fit reader | Required capability | Price basis/date | Direct test | Main limit | Sources |
| --- | --- | --- | --- | --- | --- | --- |

Do not infer a missing feature from silence. Mark it `not verified`. Do not call a free trial a free plan or compare one product's annual per-user price with another product's monthly team price.

Rankizz is optional. If a project is already connected, keyword metrics and live SERPs can help confirm intent and identify formats readers expect. They do not decide which tool is best. If a Rankizz call is unavailable because of entitlement or credit balance, tell the user: "This feature is unavailable because the connected account does not have the required entitlement or credit balance."

## Choose and order the tools

Include a product only when it passes the minimum criteria and offers a distinct reason to choose it. Assign category labels after evidence review, such as:

- best overall for the defined audience
- best for a specific workflow
- best for a constrained budget
- best for advanced control
- best open-source option

Every `best` label needs a `because` supported by evidence. Avoid giving every product a flattering superlative. It is acceptable to describe a qualified option without declaring it best at anything.

If the publisher owns one of the products, disclose that near the first recommendation and in the methodology. Do not automatically rank it first. Apply the same criteria and give competitors credit where they win.

## Write the page

### Opening

Answer who the list is for, what changed the selection, and how the products were evaluated. Avoid broad statements about a fast-moving industry.

### Quick comparison

Use a scannable table with fields that genuinely affect the decision. Do not fill it with generic checkmarks.

Useful columns:

- best for
- starting or typical price with billing basis
- tested status
- decisive strength
- decisive limitation

### Product sections

Give each tool enough useful content for the list to stand alone:

1. one-sentence verdict and best-fit user
2. evidence for the placement
3. workflow-specific strengths
4. concrete limitations or tradeoffs
5. current pricing basis and relevant limits
6. who should choose it and who should skip it
7. source or test date

Do not repeat the same feature list in prose, bullets, and a table.

### Decision support

End with a chooser based on real constraints. A short decision tree is more useful than declaring one universal winner.

## Do and do not

| Do | Do not |
| --- | --- |
| Define the audience and criteria before researching | Search for products and invent criteria around the favorites |
| Evaluate every tool on the same core evidence | Give the sponsor a detailed section and rivals thin summaries |
| Say exactly what was tested | Write "we tested" after reading marketing pages |
| Normalize price, plan, billing period, seats, and limits | Compare incompatible price figures |
| Give every recommended tool a real drawback | Use token cons such as "may be pricey for some" |
| Explain why a winner fits one use case | Claim a universal best product |
| Include only qualified products | Pad the list to match the requested number |
| Add original analysis, testing, or decision logic | Rewrite merchant descriptions with synonyms |
| Put affiliate disclosures near recommendations | Hide the relationship in a footer |
| Mark paid links `sponsored` where implemented | Assume affiliate content is exempt from disclosure |

## Examples

### Weak recommendation

> Acme is our best overall choice because it offers powerful features, seamless integrations, and an intuitive interface for teams of all sizes.

The claim could describe almost any tool and provides no evidence or boundary.

### Better recommendation

> Acme is the strongest fit for agencies that need clients to approve work without buying full seats. Guest reviewers can comment on a proof from the email link, while two other finalists require a paid collaborator. Skip it if you need an on-premise deployment; Acme offers cloud hosting only. Pricing checked 16 August 2026.

This states the audience, decisive evidence, competitor difference, limitation, and date.

### Honest testing label

Good:

> Hands-on: created a three-step approval workflow and exported the audit log. Pricing and SSO limits were verified in official documentation.

Bad:

> Extensively tested by our experts.

### Useful score

Good:

> Meets requirement: exports all records as CSV. Partly meets: API export requires the business plan.

Bad:

> Data portability: 9.2/10.

## Add the SEO and publication package

Provide one descriptive H1, a concise title and page-specific description, a stable slug, descriptive internal links, a representative social image, and Article metadata when visible fields support it. Use `ItemList` or review markup only when it accurately represents visible content and follows current search-feature rules.

Do not create dozens of near-identical lists for small keyword variations. One strong page can address related wording when the audience and decision are the same.

## Limitations

- Official documentation cannot prove usability, reliability, or support quality.
- A free account may not expose enterprise limits, negotiated pricing, or regional availability.
- Prices, plans, ownership, and features change. Date every snapshot and identify facts that require rechecking.
- Do not invent hands-on testing, private customer feedback, or benchmark results.
- A ranked list does not guarantee search visibility, affiliate revenue, or reader agreement.
- High-stakes tools require qualified security, legal, medical, or financial review.

## Output template

```markdown
# [Number] best [tool category] for [specific audience or job]

[Direct answer: who this is for, how many qualified, and the main selection insight.]

Disclosure: [ownership, sponsorship, free products, or affiliate relationship in plain language]

## How we evaluated these tools
- Audience and task:
- Required criteria:
- Disqualifiers:
- Hands-on work completed:
- Source and pricing cutoff:
- Scoring or label method:

## Quick comparison
| Tool | Best for | Price basis | Evidence | Main limitation |
| --- | --- | --- | --- | --- |

## 1. [Tool]: best for [use case]
[One-sentence verdict]

### Why it earned this position
[Specific evidence and comparison]

### What it does well
- [Evidence-backed strength]

### Where it falls short
- [Concrete limitation and affected user]

### Pricing
[Plan, billing period, seats/usage, currency, date, and source]

### Choose it if
[Fit]

### Skip it if
[Non-fit]

[Repeat the same evidence structure for each qualified tool]

## Which tool should you choose?
- If [constraint], choose [tool] because [evidence].
- If [constraint], choose [tool] because [evidence].

## Research notes
- Last checked:
- Unverified claims omitted:
- Facts to refresh:

## Editorial QA
- [ ] Entry count matches qualified products
- [ ] Every `best` claim has evidence and a boundary
- [ ] Pricing comparisons use equivalent units
- [ ] Each entry contains a meaningful drawback
- [ ] Testing and commercial relationships are disclosed
- [ ] No copied merchant descriptions or invented experience
```