Technical visibility diagnostic
Can Google and AI see your website?
One public URL. Four separate facts. Exact evidence, impact, and the next safe action—without an invented visibility score.
What are you trying to solve?
Choose a task. It changes the scan action and the first result view.
Output preview
Find the first technical blocker
WebVisible will prioritize verified exclusions and risky unknowns before showing the full evidence set.
Public URLs only · bounded fetches · no persistent report · allowed does not mean indexed or cited
Quick Scan
Inspecting the public response
Starting scan…
- 1Validate targetPublic URL and redirect safety
- 2Fetch responseStatus, headers, redirects, bounded body
- 3Read directivesrobots, meta, headers, canonical
- 4Map policySearch, model-use, user-triggered
- 5Build actionsEvidence, impact, fix, verification
Request stopped
Check the URL and try again
Primary answer
Evidence ready
Next actions
Start here
Quick Scan verification
What changed after the fresh scan
Evidence → impact → fix → verify
Findings for this URL
Crawler policy matrix
Policy by product purpose
Search discovery, model-use controls, and user-triggered retrieval remain separate.
Initial response
What arrives before JavaScript runs
Status, directives, metadata, meaningful text, links, schema, and framework evidence.
Optional browser evidence
Does JavaScript materially change the page?
Run one bounded WebVisible browser attempt, then compare raw and rendered text, metadata, links, structured data, and accessibility structure. This is not an official crawler visit.
Waiting up to 15 seconds for network idle, then comparing bounded machine-readable representations…
Rendered comparison
Raw response vs browser result
Rendered verification
What changed after the browser re-check
Need the exact evidence model, crawler taxonomy, or security limits? Read the methodology.