Method · version 1.1

The score, the protocol, and the limits.

BuildLogics uses two separate measurements. The free scan evaluates public website foundations. The paid benchmark observes whether a company actually appears in repeated buyer-question research.

The ruleWebsite readiness is not answer visibility.

A technically strong website can still be absent. A mention can appear once and disappear on the next run. We report both measurements separately.

CheckPointsPass condition
Homepage access12The public homepage returns a successful, readable HTML response.
Search title6A clear, descriptive title is present and within the published length range.
Page description6A useful summary is present and aligned with the visible page.
Primary heading6One clear H1 explains the page or business outcome.
Readable page depth6The page contains enough visible text to explain the business without filler.
Structured data10JSON-LD structured data is present.
Business entity definition8The organization or service is explicitly defined in structured data.
Crawler instructions5robots.txt is available without an obvious site-wide block.
Named assistant crawler policy5The site states an intentional policy for relevant named crawlers.
XML sitemap6A readable sitemap is available at the standard location.
Canonical page signal5The homepage declares its canonical URL.
Optional llms.txt guide0Informational only. Google says this file does not affect its visibility or rankings.
Target service clarity7The homepage plainly reflects the service and market in the submitted buyer question.
Visible credibility evidence10The page contains specific proof, results, reviews, credentials, or case-study signals.
Action path8A direct contact, consultation, quote, or booking path is visible.
Total100Website foundation only—not a third-party ranking.
Paid Visibility Benchmark

One screenshot is not a measurement.

Answers vary by wording, engine, date, and run. The baseline controls those variables and preserves the raw observations.

15buyer questions
×
4controlled phrasings
×
8runs per phrasing
×
3research engines
=
1,440baseline observations
01

Lock the questions

Questions represent category, comparison, trust, and hiring decisions connected to revenue.

02

Record every outcome

Mentions, rank order, citations, accuracy, competitors, and null results all remain in the dataset.

03

Separate the days

Runs are distributed across measurement windows to reduce the chance that one moment looks like a durable result.

04

Retest the same way

After implementation, the same protocol produces another 1,440 observations for a matched comparison.

What we do not claim

Process guarantees. No placement guarantees.

We do not guarantee a recommendation, citation, ranking, traffic increase, or revenue outcome inside a third-party product.

We do not treat `llms.txt`, special Markdown, content chunking, or schema as a shortcut to visibility. Google explicitly says its search systems do not use `llms.txt` for visibility or ranking.

We do not hide misses. A zero-result answer is part of the baseline and stays in the report.

We do not treat a change observed after implementation as proof that one edit caused it. We report association, conditions, and limits honestly.

Primary references
ChangelogVersion 1.1 · August 14, 2026 — made llms.txt informational and reallocated its four points to service clarity and visible proof.
Start with the public foundation.

See what the scanner can prove right now.

Run the free scan