Site audit
Visibility & authority
Resources
Complete procedures, with the commands, the snippets to copy, and the traps you only meet in production.
featured in depth
A hotel was losing ten trust points over a return policy it cannot have. Here are the fifteen checks that can actually be verified, which of them apply to your business, and the four traps that corrupt the reading.
The NessFlow team · · 11 min read
in depth
Two pages on one query prove nothing. Across 49 published detection methods, not one separates an engine that is hesitating from an engine that has decided. Here is the protocol that does, by hand, and what our own thresholds are worth.
The NessFlow team · · 14 min read
With no server access, logs come through a control panel. Here is the checkbox that keeps them, and why some lines belong to other people’s sites.
The NessFlow team · · 2 min read
IIS writes a header-driven format whose columns are ticked one by one. Here are the ones that count, and the box that is almost always missing.
The NessFlow team · · 2 min read
Cloudflare answers for your server on a large share of traffic. Here is how to get its own logs, and what origin logs quietly leave out.
The NessFlow team · · 2 min read
The combined format field by field, where nginx and Apache write access.log, how to pull a specific period out, and what daily rotation quietly throws away.
The NessFlow team · · 2 min read
in depth
The most useful border in this subject runs between what you can count on a page and what you can only judge. Both serve the same decision, and blending them into a single rating destroys both.
The NessFlow team · · 6 min read
in depth
A total of inbound links decides nothing. The five questions to ask a profile, how to count referring domains without counting them twice, what a purchased risk score is actually worth, and the one competitive comparison that produces a finding.
The NessFlow team · · 5 min read
in depth
A ranking is not a property of your page: it is the result of a measurement, and a measurement only compares against another taken under the same conditions. The five settings to freeze, the three states of a reading, and the reference to judge a drop against.
The NessFlow team · · 6 min read
Three families of signal decide which address an engine keeps, and they contradict each other far more often than teams expect. The six most common contradictions, and the three checks that tell you where you stand.
The NessFlow team · · 4 min read
in depth
Why your React or Vue app looks empty to audit tools, how to check what an engine really sees, and the five defects that show up on nearly every project.
The NessFlow team · · 4 min read
in depth
Server logs are the only source that says what engines actually requested. How to get them, what they reveal, and how to analyse them without storing a single IP address.
The NessFlow team · · 4 min read
in depth
Allow search, refuse training, understand the tokens that match no crawler at all: the procedure, with snippets to copy and the four mistakes we find most often.
The NessFlow team · · 5 min read
Run an audit on your own site and read what the engine finds. If you would rather be walked through it, book a demo: we run it on your site, with your own URLs on screen.
Access opens in waves: we email you when yours is ready.