Write a Clear About Page When You Are a One-Person Project

Quick scan

• Text type: About-page trust copy for a solo project.
• Risk: Sounding bigger than the project is, or underselling useful expertise.
• Tool path: Text Workbench -> Landing Page Lie Detector -> Markdown Preview.
• Human decision: Which owner details, affiliations, and claims can be published accurately.

An About page for a one-person project should not pretend to be a corporation, and it should not read like an apology for existing. The useful middle is precise: name the operator, explain what the site offers, state how it handles responsibility, and give readers a way to make corrections.

A vague first draft

We are a leading team building revolutionary tools trusted by creators everywhere. Our mission is to transform the way everyone works with content and AI through best-in-class experiences.

This copy hides the important answers:

• Who is responsible for the site?
• What does it actually contain?
• How can someone report a mistake or privacy concern?
• Which claims can be demonstrated?

Step 1: Clean the draft, but do not preserve its premise

Text Workbench is useful for pasted formatting and word counts. It cannot fix an inaccurate identity statement. If the project has one operator, do not merely polish we are a leading team; rewrite the premise.

Step 2: Run ambitious wording through a claims check

Paste the vague draft into Landing Page Lie Detector. Its rules are expected to flag terms including:

leading
revolutionary
trusted by
everyone
best

The flags do not prove dishonesty. They identify words that require evidence or narrower language.

A clearer About-page block

This sample follows a small independent site model:

## About Fieldnote

Fieldnote is an independent browser-tool project operated by Maya Lind in Gothenburg, Sweden. It publishes small writing utilities and practical notes for people editing product and support copy.

Tools process pasted text in the browser unless a page clearly states otherwise. Articles are written as examples and checklists, not proof of outcomes for every user.

For corrections, accessibility feedback, or privacy questions, contact Maya through the contact page.

Why this is stronger:

• operated by Maya Lind establishes responsibility.
• browser-tool project and small writing utilities explain scope.
• the processing sentence states a trust boundary.
• the article sentence avoids promising universal results.
• the contact sentence gives accountability a destination.

The name and location above are fictional sample content. Replace them only with information the real operator is comfortable publishing and able to maintain.

Step 3: Preview hierarchy before publication

Paste the final Markdown into Markdown Preview. Check that the owner statement appears near the start, trust wording is not hidden below a wall of mission copy, and the contact link is visible.

If an existing About page mixes we, I, and a named operator, pick a deliberate perspective and use it consistently. An independent project can use a site voice, but ownership should not remain ambiguous.

What not to claim without evidence

Avoid these unless the page can substantiate them:

• user counts, client logos, or broad trusted by statements
• professional qualifications not actually held
• security guarantees stronger than the site's implementation
• outcomes such as saving time or improving conversions

Specific scope is more credible than borrowed scale.

Related paths

• Edit a Draft workflow
• A Plain-English Pass for Privacy and Consent Copy
• Tiny tools that earn trust in 10 seconds

FAQ

Should a solo project say "I" everywhere?

Not necessarily. A site can use its brand name or a neutral editorial voice. It should still state clearly who operates it and handles contact or privacy requests.

Can a claims detector review an About page?

It can highlight broad promise language worth checking. It cannot establish identity, credentials, or legal compliance.

Is this legal or business disclosure advice?

No. It is an editorial example for clear trust copy. Required disclosures depend on the project and applicable rules.