How to Read the Brand Already on Your Public Site

A working product page already makes visual and verbal choices. Buttons have colors. Headings have a typeface. The first screen has a tone. Before you ask an agent for an ad, a social card, or a demo, write down what a stranger can see on the public site. That sheet is the brief for the next asset.

A static read, including the free scan explained on the landing page analyzer, looks at the public page. It does not open design files, a hosting account, or a private dashboard. Anything behind a login stays unknown until you can point to it in the open.

What to copy off the live page

Open the homepage in an ordinary browser window and use the computed styles, not your memory of the last redesign.

**Color.** Inspect the main button, a text link, the page background, and the body text. Record the hex value and the job: button fill, link, text, or background. If the stylesheet exposes custom properties, copy the variable name beside the value. When two greens both appear, keep both and name the element that uses each one.

**Type.** Inspect one heading and one paragraph. Record the computed font-family and font-weight. If a fallback face is what actually paints, write that the intended file is not visible. Note whether the family arrives from a public stylesheet request you can see in the network panel. Seeing a family name does not tell you the license terms.

**Voice.** Copy three to five sentences a visitor can read without an account. Label them in ordinary words: short or long, formal or casual, concrete or abstract. Add the words the page repeats. Keep the samples as they appear on the page.

**Positioning.** Copy the hero promise as published. Then write one paraphrase: who it is for, what they can do next, and what the page says is different. If the page never names an audience, set the audience field to “not stated.”

**Pictures.** Note the hero: product screenshot, illustration, or empty. Check whether a share image is declared in the page metadata. The Open Graph image examples show how a declared share image can present a product. They are a reference, not artwork to drop onto your URL.

Riley Brown’s February 2025 post is a first-person walkthrough of trying a landing-page design. Use it as a dated example of how little ceremony a design trial can take. It is not evidence that a visual change produced customers.

Hypothetical: Fieldnote’s two greens

Fieldnote is a made-up public page for a voice-notes tool used on site visits. The primary button computes to #1F4D3A. A text link on the same screen computes to #246B4F. Headings compute to Source Serif 4 at weight 600. Body text computes to IBM Plex Sans at weight 400. The hero says, “Record a site visit, get a note you can search later.” There is no customer quote. The share-image tag is absent.

The brief locks #1F4D3A as the button color, keeps #246B4F as the link color, names both families and weights, pastes the hero sentence, and lists testimonials and the share image under “not on the page.” It does not add a quote to make the sheet feel finished. Landing page best practices are easier to apply after those observed choices are written down.

Build the brief

1. Save screenshots of the homepage and one inner page, such as pricing, at a desktop width and at a narrow phone width.
2. Fill five rows: color, type, voice, positioning, and missing.
3. Mark every cell observed or uncertain. Uncertain covers a font you meant to ship but cannot see, a color that exists only in a design file, and any customer claim.
4. Resolve only a clash a visitor can already meet. If the homepage button and the pricing button differ, choose the color on the URL you will actually share, and note the other as drift.
5. Pass that sheet to the next asset. New copy uses the sampled sentences. Empty proof stays empty.

Prompt

Read only these public URLs: [homepage], [one inner page]. Do not log in and do not infer private brand files. Return five sections: color, type, voice, positioning, missing. For every color and font, name the element and the computed value. Quote 3 to 5 sentences that appear on the page. Copy the hero promise verbatim, then add a one-line paraphrase labeled as a paraphrase. List testimonials, logos, and a share image only when the HTML shows them. Mark every field observed or uncertain. Invent no customers, counts, or hex values.

Finish rule

You are done when someone else can set a button color and a heading face from the brief alone, and every unsupported field is marked uncertain. After that, paste the same URL into the free scan and compare the top gap it names with your “missing” row. The scan scores the public page. It does not measure demand, and it leaves your site where it is.