ONE-PAGE SIGNAL CHECK / 2.3
Every website
leaves a signal.
Find yours.
What can a crawler actually read? What is missing? Get the evidence — and a useful next move.
Read your website.
Public pages only. No browser rendering. URL and result metadata may appear in logs or owner notifications. Baselines stay in this browser. Privacy
What it actually looks at
Seventeen checks in four groups. Core checks have equal weight; optional content and performance observations are separate. Every row shows its evidence, detection limits and a way to verify the next action.
GROUP 01
Can the page be read
Business metadata, a page title, semantic headings and text available before JavaScript runs. The report shows the fetched HTML; different crawlers may render scripts differently.
GROUP 02
Are business facts exposed
Contact routes, declared review signals, HTTPS and a canonical URL. Local businesses can include a service-area check. The scan checks this page; it does not verify outside profiles or require a private home address.
GROUP 03
Can facts be quoted
Currency amounts, declared availability and visible customer questions. These are clues to useful information, not verification that the prices are yours or that an assistant will quote them.
GROUP 04
Can crawlers reach it
Path-specific search-crawler rules, noindex directives, response headers and HTML payload. Training permissions are shown separately. These observations do not establish rankings or real-user speed.
WHY IT MATTERS
Counts, not a grade
Each row explains what was detected and what to do next. The total counts applicable checks on one page only. It does not grade the whole website, conversion, traffic or AI visibility.
NEXT STEP
Fix. Verify. Share.
The checklist can point to signals worth reviewing; it cannot show whether a page earns trust, leads or sales. The field guide separates measured evidence from claims about opaque platforms. To check the writing itself, try the text check.