Audit your app

Website Content Audit: Does Your Copy Do Its Job?

Run a website content audit on your own words with a read-aloud and mark-up pass, plus a swap-the-name test that catches generic copy.

A website content audit, for a small site, checks two things: whether a first-time visitor can tell what your product is from the headline alone, and whether the rest of your pages back that up. Read your copy out loud, mark what sounds vague, then swap another product's name into your lines. Any line that still works after the swap is generic.

Words are the cheapest thing on your site to fix, and the first thing a visitor has to go on. This guide gives you one method you can finish in a single sitting, with a pen and no special software.

What is a website content audit for a small site?

In marketing, a content audit usually means an inventory. Every page goes into a spreadsheet with its traffic numbers, and each one gets a verdict: keep, update, or delete. That's the right job for a blog with hundreds of posts, or for a site where search visits are the main goal.

This guide is the smaller job. You've got a handful of public pages, and you want to know whether the words are pulling their weight. If your site is big, do the inventory first, then come back and run this method on the pages that matter most.

What does Clarity and Promise ask of your words?

Our audit scores every public site on the same six areas, and the first one is about words. Clarity and Promise asks whether a first-time visitor could tell you what this is after reading your headline, and whether your other pages tell the same story. We put it first because everything else leans on it. A tidy mobile layout and a specific button don't do much if nobody can tell what you're selling.

In our sample report, an audit of ismyappslop.com dated 28 September 2026, Clarity and Promise scored 98. "What works" credits a headline and subheadline that say what the product does, who it's for, and the value, and "Slop tells" for that area reports none observed. Yes, the sample is our own site. Seemed only fair.

Outside sources back up the basic idea. The US government's plain-language guide calls writing for your audience its first rule (Digital.gov). Google's self-assessment questions for content ask whether a page leaves readers feeling they need to search again for better information (Google Search Central). That page is about search content, but the question travels well: would a visitor leave to go find a plainer answer?

How does the read-aloud and mark-up pass work?

When I started The Budget Fashionista, there were no online content guides to follow, so I wrote as if I were talking to my sister-in-law. Sometimes I really was talking to her. It's still a pretty good test for any copy, and reading out loud is how you run it. Your eyes skim right past empty phrases. Your mouth won't let you.

  1. Strip the design. Copy the words from one page into a plain document. Start with the homepage, then pricing, signup, and about.
  2. Read it out loud. Normal speaking pace, like you're explaining the product to a friend across the table. Don't fix anything yet.
  3. Mark as you go. Use 4 marks:
  • Underline any sentence where you stumble, run out of breath, or have to reread.
  • Circle any claim with nothing behind it, like "trusted," "fast," or "powerful" with no number, example, or name.
  • Box any word you'd never say to a friend, like "leverage," "seamless," or "next-generation."
  • Draw a wavy line under any sentence you could drop onto a different site, word for word.
  1. Count the marks on each page. The page with the most marks gets fixed first.
  2. Finish the sentence. Say your headline, then say "This is for" and finish it in one breath. If you need an "and also," the headline is carrying too many ideas.

What is the swap-the-name test?

The wavy line is a hunch. This test checks it. Take your headline, your subheadline, and your first 3 feature lines. Swap in another product's name, or swap your category word (receipts for invoices, recipes for workouts). If the line is still true and still reads naturally, it's generic.

Specific lines break when you swap them. They name your input, your outcome, or your person, and those don't transfer to anybody else's product. Our homepage FAQ lists the vague headline as one of its examples of slop, and this test is a quick way to find yours.

What does vague copy look like, and how do you fix it?

Say a small app turns photos of receipts into an expense report for freelancers. The left column is a first draft. The right column is a rewrite worth testing, which isn't the same thing as proof it'll do better.

Part of the pageVague draftPlainer rewrite to test
HeadlineSupercharge your workflow with next-generation toolsTurn a pile of receipts into a tidy expense report
Who it is forBuilt for modern teamsMade for freelancers who do their own books
ButtonGet startedScan my first receipt

The draft headline fails the swap test, because "supercharge your workflow" fits a calendar, a notes app, or a chat tool just as well. It also earns a box around "next-generation" and a wavy line under the whole sentence. The rewrite names the input (receipts), the outcome (an expense report), and the person (freelancers). Swap in another product and it stops being true.

Do your other pages agree with the headline?

Clarity and Promise has a second half: does the rest of the site agree? Read your pricing, signup, about, and footer text out loud with the same 4 marks, and hold each one up against your homepage headline. Watch for a page that talks to a different audience, a page that describes a different promise, and leftover template text or placeholder names nobody got around to replacing. Each one makes a visitor wonder whether they landed in the right place. Fix the page that's out of step, and keep the headline as your anchor.

What if an AI tool wrote the words?

Then run the swap-the-name test first, before the read-aloud. AI-drafted copy tends to read smoothly, so it can sail through a read-aloud without a single stumble and still fit a thousand other products. The swap test doesn't care who wrote the line.

For every line that survives the swap, add one detail only you have: your real input, your real price, or your real outcome. Then read it out loud again to make sure it still sounds like you, and not like your AI's idea of you.

Does the next step read clearly?

Read each button and link as if it were your only clue, and check that the label says what happens when you press it. Button wording, forms, and the full path to a purchase are all covered in our landing page audit guide.

Can an audit do this for you?

Part of it. Our report scores Clarity and Promise on its own line, lists what works and any slop tells, ranks the fixes, and puts a verdict at the top, so you get an outside read on your headline and on whether the rest of the site agrees with it. For friction in navigation, forms, and mobile use, see our website UX audit guide.

What no report can know is what you meant to say. That's why the read-aloud comes first. It gives you your own marks, and the report becomes a second opinion on them.

Which marked lines do you rewrite first?

For each mark that matters, write 3 short things: what a visitor reads, why it might confuse them, and what you'll change. Then work in this order:

  1. The headline and the one-sentence promise, since every other page leans on them.
  2. Pages that disagree with the headline.
  3. Button labels and next steps.
  4. Everything else, like tone and polish.

Words you wrote yesterday sound different today, so read the new version out loud one more time before you publish it.

What is a good first step today?

Give it 10 minutes. Take the headline, the subheadline, and the first 3 feature lines on your homepage. Read them out loud, make your 4 marks, and run the swap-the-name test. Then rewrite only the headline, and read it out loud again. If you get stuck on the rewrite, our guide on how to write website copy starts from the promise sentence. That's it for today.

You got this.

Sources, both read 5 October 2026: Digital.gov's plain-language principles (published 11 September 2025) and Google Search Central's guidance on creating helpful content (updated 5 October 2026).