Auditing a landing page

An ad can be right and still lose the sale on the page it sends people to. A landing audit reads that page the way a visitor from an ad meets it, on a phone and on a desktop, and pins every problem it finds to the part of the page it is about, with what to change.

Asking for one

In a session, ask Nomi to audit a page, paste the address and ask what is wrong with it, or type /audit and the address. If the page is one of the product's landings, or the conversation already says which product, market and ad it is for, Nomi takes that into account. An audit takes one to three minutes.

Nomi opens the page as a new visitor twice, once as a phone and once as a desktop. It answers a cookie banner with the least it can agree to, in the banner's own language, takes the only answer a banner offers when there is no other, keeps any popup that opens on its own as evidence, and reads the page screen by screen, up to sixteen screens on each device.

The visit asks for English and comes from Ireland, so a site that picks its language from the visitor's browser or location shows its English version. The cookie banner is the law's, not the page's, so it is never a finding.

Reading the audit

When the audit is ready, a card in the conversation says what was audited and how many problems it found, by severity. Preview opens the audit beside the conversation, in Strategise as well as Generate, and pressing it again closes it. Each count opens it on that severity alone.

The page is shown whole, with a numbered marker on every element that has a problem. The colour is the severity: red is critical, amber is important, blue is minor. The numbers run from the worst down and stay the same on both devices.

Mobile and Desktop at the top switch between the two pages. A finding that applies to both keeps its number on each.

The score above the page starts at 100 and loses 10 for each critical finding, 4 for each important one and 1 for each minor one. It is counted from the findings, not estimated, so it is a way to compare two versions of a page rather than a prediction.

Taking it with you

The ⋯ menu opens the audit as a document saved in the Library, or downloads it straight away as a Markdown file. Opening the document replaces the audit beside your conversation. Drag the preview's left edge to make it wider, and use Document sections to jump between findings. Its ⋯ menu offers editing, copying as Markdown and downloading.

What it cannot do

A page that turns the visit away, one behind a password and some behind a bot wall, cannot be read; Nomi says so in the conversation and asks for screenshots instead. An audit reads what is on the page, so it does not know your conversion rate and does not predict one.

An audit is billed to your credits on what the reading used, like a conversation turn.