TRANSPARENT BY DESIGN
Audit methodology
A deterministic page inspection, not a ranking forecast. Every score comes from the ten checks below, using public HTML, response headers, and robots.txt.
What is checked
- HTTPSThe submitted address is a public HTTPS URL.
- HTTPThe page returns a successful HTML response.
- OAIrobots.txt does not block OAI-SearchBot for the audited path.
- GOOGLErobots.txt does not block Googlebot for the audited path.
- INDEXNo noindex directive is detected in supported page or response metadata.
- TITLEThe page has a useful title.
- DESCRIPTIONThe page has a useful meta description.
- CANONICALThe page declares a canonical URL.
- SCHEMAJSON-LD structured data is present.
- CLARITYA clear H1 and basic company, contact, or privacy signals are detectable.
Scoring
Each check is worth 10 points: Pass = 10, Review = 5, Fix first = 0. Scores of 80–100 indicate a strong technical foundation, 50–79 indicate room to improve, and 0–49 indicate important blockers. These bands are product heuristics, not search-engine grades.
Data handling
The submitted URL and fetched page content are processed only to return the audit and are not written to the app database. The database stores two totals only: completed audit events and report-interest events. They are event counts, not unique people.
Important limits
- No ranking, traffic, citation, lead, or revenue outcome is guaranteed.
- The audit does not query private search indexes or inspect how an AI system answered a specific prompt.
- JavaScript-only content may not be visible to the static inspection.
- Availability at audit time can affect the result.