See the source.
Know the limit.

1. Choose a distinct reader task

We ask what a reader needs to finish and whether another guide already answers the same question. A search trend can indicate relative interest, but it does not reveal absolute monthly searches, advertising rates, or whether this site will rank.

2. Identify the evidence

A source-checked guide explains instructions from a provider, museum, library, or other primary source. A tested guide reports an action we performed and the result we inspected. Its badge and article text should make that difference clear. We do not claim an independent result from a provider's description alone.

3. Check the outcome where possible

The first PDF series used synthetic files with known page counts and visible labels. We recorded the service page, input, settings, date, and downloaded file, then checked the pages and text in the output. This test covers those files and steps. For a source-checked guide, the reader should inspect the current interface and their own result before relying on it.

4. Edit and challenge the draft

We check factual claims against the recorded material, remove repetitive or inflated language, and keep the limitations visible. A draft can remain unpublished when the source is weak or its reader task duplicates another guide.

5. Revisit when something changes

The checked date records when we reviewed the cited source or test. The published date, when shown, records the first public release of the approved guide. We change the modified date only when the article's content changes. If a service changes or a reader reports a problem, we recheck the affected step.