Reachability gate
HTTPS/HTTP, redirect paths, DNS/TLS clues, robots.txt, sitemap.xml, llms.txt and source-vs-AI retrieval problems. Do not call an AI safety refusal a site-side HTTP failure.
Is your site reachable, understandable and genuinely helpful? Start with HTTPS, redirects and discovery files, then inspect content quality, optional search/AI visibility and proportionate improvements.
HTTPS/HTTP, redirect paths, DNS/TLS clues, robots.txt, sitemap.xml, llms.txt and source-vs-AI retrieval problems. Do not call an AI safety refusal a site-side HTTP failure.
Crawlability, titles, canonicals, readable answers, accessibility, source links, useful internal navigation and disclosure. Competitor/advertorial review is optional.
Google Trends, Bing Keyword Research, owner-authorised Search Console/Bing reports and AI citations when actually accessible. Figures retain source, place, period and metric definitions.
Enter your site's public address. This page creates a reusable instruction for your chosen AI. It does not scan the site itself or connect to Google/Bing accounts.
After the technical audit, review page clarity, evidence and AI-answer readability. Suggestions only, not automatic edits. Read the existing Aletheia Skill.
For a real audit, give a capable AI the linked Markdown and your domain. Capability gaps must be disclosed rather than simulated.
<hostname>-results.md evidence receipt; suggested actions are not marked as completed changes.No automatic advertising spend, account access, subscription, tracking installation, publication or guessed search volumes.
A few stars that lead you home.
Curated navigation links, not paid adverts.