---
name: verify-all-pages-written-in-first-person
description: "Help a personal site sound like its owner. Keep quotes and formal bios in their proper voice."
category: Website QA Audit
stage: —
definitive_article: /website-qa-audit
status: complete
---

# Verify all pages written in first person

Your personal site should sound like you. This guide helps you find copy that talks about you like a brochure. Start with the page’s purpose, so you do not rewrite a quote or formal bio by mistake.

**The path:** Page role → Exact wording → Source-backed voice → Checked copy.

**Use this when:** A personal-brand site’s editorial voice is being audited. A company site or a deliberately third-person executive bio needs its own stated voice decision.

## Inputs
- The scoped page inventory, site owner identity and agreed personal-brand voice.
- Actual interviews, approved first-person statements and facts needed to support a rewrite.
- A list of legitimate quoted, third-party, legal or executive-bio content and its owner-approved role.
- Supported edit scope and a report for exact sentences, decisions and source references.

## First-run prompt

> Review the supplied personal-site pages, intended roles and real source statements. Find exact voice mismatches, preserve quotes and formal exceptions, and make authorized source-backed revisions with grade-5 openings. Report remaining proof or voice decisions without inventing the owner’s experience.

## Steps
1. Classify the site and page roles before checking pronouns. A personal editorial page normally speaks as “I” or “my”; a company may truthfully use “we.” A designated formal executive bio can intentionally remain third person.
2. Read the home/about and every other page in scope silently. Search for the owner’s name and third-person constructions to find candidates, then read the surrounding passage. A pattern match is a lead, not a verdict.
3. Separate the owner’s narrative from exact testimonials, press quotes, captions and third-party bios. Do not change another speaker’s quote into “I” or manufacture the owner’s speech.
4. For a real voice mismatch, rewrite with the actual speaker’s facts and tone. Use a specific supported scene and useful lesson rather than a trophy-name resume paragraph. Changing “Alex has advised” to “I have advised” does not verify the claim.
5. Check relationship words and praise under the maintained credibility rules. Keep unsupported friend/client/partner claims and anonymous praise HOLD. Source limits follow the content into repurposing; a voice edit does not make stronger claims true.
6. Check the opening at grade 5 or below and explain the useful result in plain words. Keep internal confidence scores, production labels and repeated defensive caveats out of public copy, while preserving a necessary scoped compliance disclosure.
7. Apply authorized exact-source edits. Preserve deliberate third-person exceptions with their reason in the internal report. Do not read media aloud or play a speaker’s clip through the user’s speakers to complete a voice review.
8. Recheck the canonical page after saving. Record page-level results, exact changed sentences and remaining source/voice decisions; a search-engine query is not proof that every page has been read.

## Definition of done (QA checklist)

- [ ] The personal-brand or other intended voice is defined for each scoped page.
- [ ] Exact quotes and legitimate formal/third-party exceptions are preserved.
- [ ] First-person rewrites are source-supported and retain credibility/HOLD limits.
- [ ] Openings meet the grade-5 rule and public copy avoids internal review theater.
- [ ] Authorized changes are checked publicly with an exact scope and exception list.

## Example(s)

**Fictional teaching example — no copy was rewritten.** Alex’s personal about page says, “Alex helps riders take useful repair photos.” The supplied fictional interview contains the same point in Alex’s own words.

The teaching rewrite is “I help riders take clear photos so the shop can plan the next step.” A separate downloadable speaker bio remains “Alex teaches…” because its declared purpose is a formal third-person introduction. A customer’s exact quote stays in the customer’s voice.

The correct audit does not replace every occurrence of Alex’s name with “I.”

## Handoff and Content Factory context

The content owner receives exact voice changes and exceptions. [Verify achievement evidence](https://local-service-spotlight.github.io/task-library/?task=verify-achievements-are-evidenced-not-just-claimed#task-verify-achievements-are-evidenced-not-just-claimed) checks the truth of claims that a pronoun edit cannot prove.

This is a supporting quality check for the [Content Factory](https://blitzmetrics.com/content-factory/). Produce gathers real source material; Process makes useful assets; Post places and checks them; Promote distributes suitable work within its own scope. This check does not automatically execute all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

Run before publication and after material copy changes. The default does not convert company sites or locked executive bios into personal first-person pages.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** —
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 2, gating 3 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Canonical article: https://blitzmetrics.com/website-qa-audit
- Exact task: [Verify all pages written in first person](https://local-service-spotlight.github.io/task-library/?task=verify-all-pages-written-in-first-person#task-verify-all-pages-written-in-first-person)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Website QA Audit](https://blitzmetrics.com/website-qa-audit/)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- The actual approved voice, source statements and declared formal-bio exceptions require the project.