Lock the questions
Questions represent category, comparison, trust, and hiring decisions connected to revenue.
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.
A technically strong website can still be absent. A mention can appear once and disappear on the next run. We report both measurements separately.
| Check | Points | Pass condition |
|---|---|---|
| Homepage access | 12 | The public homepage returns a successful, readable HTML response. |
| Search title | 6 | A clear, descriptive title is present and within the published length range. |
| Page description | 6 | A useful summary is present and aligned with the visible page. |
| Primary heading | 6 | One clear H1 explains the page or business outcome. |
| Readable page depth | 6 | The page contains enough visible text to explain the business without filler. |
| Structured data | 10 | JSON-LD structured data is present. |
| Business entity definition | 8 | The organization or service is explicitly defined in structured data. |
| Crawler instructions | 5 | robots.txt is available without an obvious site-wide block. |
| Named assistant crawler policy | 5 | The site states an intentional policy for relevant named crawlers. |
| XML sitemap | 6 | A readable sitemap is available at the standard location. |
| Canonical page signal | 5 | The homepage declares its canonical URL. |
| Optional llms.txt guide | 0 | Informational only. Google says this file does not affect its visibility or rankings. |
| Target service clarity | 7 | The homepage plainly reflects the service and market in the submitted buyer question. |
| Visible credibility evidence | 10 | The page contains specific proof, results, reviews, credentials, or case-study signals. |
| Action path | 8 | A direct contact, consultation, quote, or booking path is visible. |
| Total | 100 | Website foundation only—not a third-party ranking. |
Answers vary by wording, engine, date, and run. The baseline controls those variables and preserves the raw observations.
Questions represent category, comparison, trust, and hiring decisions connected to revenue.
Mentions, rank order, citations, accuracy, competitors, and null results all remain in the dataset.
Runs are distributed across measurement windows to reduce the chance that one moment looks like a durable result.
After implementation, the same protocol produces another 1,440 observations for a matched comparison.
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.