Technical discovery
HTTP status, redirects, canonical, robots/noindex, sitemap and reachability.
Free public beta · live raw-HTML retrieval
SEO and GEO diagnostic tool
Enter a public website URL to retrieve its raw HTML, robots.txt, sitemap.xml and llms.txt. The tool checks whether search engines can extract the title, canonical, H1, schema, FAQ, language signals and citation-ready facts. It returns pass, warning and failure evidence instead of inventing an AI ranking score.
Public pages only; 10 checks per source in 10 minutes. Submitted targets are omitted from application logs. · Try the LyProxy example
What the tool does and does not measure
This is an engineering diagnostic, not an official score from Google, Baidu or an AI answer engine. It verifies evidence currently available to a public crawler. Ranking, indexing, AI citations and conversion require Search Console, real-user data, repeatable prompt tests and external references over time.
On-page evidence
Title, meta description, one H1, raw-HTML content, internal links and image alt text.
GEO readiness
Extractable schema, FAQ, brand-fact entry points, llms.txt and bounded claims.
International delivery
HTML language, mobile viewport and declared hreflang; semantic equivalence still needs editorial review.
Need target-country search and landing-page QA?
LyProxy provides static residential, rotating residential and SOCKS5 network options for compliant local SERP, ad landing-page and cross-border website QA. Countries, cities, carriers and availability are dynamic and must be confirmed in the live console.
FAQ
Is this result a Google ranking score?
No. The tool reports evidence-led passes, warnings and failures. Actual ranking must be evaluated with search-engine data and sufficient observation time.
Can it prove citation by ChatGPT, Gemini or Perplexity?
A page fetch cannot prove a citation. The tool checks citation readiness such as extractable answers, schema, FAQ, llms.txt and source structure. Actual citations require repeatable prompt monitoring and referral or crawler evidence.
Why does the tool only retrieve public pages?
It is a self-service webmaster check for public websites. Private, loopback and reserved addresses, nonstandard ports, large responses, excessive redirects and high request rates are blocked.
What should be fixed first?
Fix HTTP availability, noindex conflicts, canonical errors, blank rendering, mobile issues and sitemap discovery before refining titles, content, schema, FAQ, language equivalence and external evidence.
Are submitted targets stored?
The application log omits submitted target URLs. The web server retains only the normal API endpoint access record. Results are rendered in the browser and are not published as customer cases.
Method and official references
These sources support the diagnostic method. They do not endorse LyProxy or guarantee ranking, indexing or AI citation.