This site has a useful foundation, but important gaps still limit AI readability.
Key strengths include AI guidance file and sitemap, while plain-text page access and homepage access need attention.
Recommended next step
add content negotiation for Accept: text/markdown on the homepage and return a markdown representation with Content-Type: text/markdown.
Keep the HTML response for regular browser requests.
Turn this scan into weekly monitoring.
Create a free workspace first, then unlock weekly monitoring for AI visibility changes after site, pricing, docs, sitemap, or crawler-rule updates.
Overall score
// score breakdown
8 checks
Public link
llmscan.dev/scan/n3FAuHD1Y7TMP07BjeR43
Signals checked
8 AI visibility signals
Fix bundle
4 copy-ready files
Share badge
Needs Work · 63/100A compact badge for footer, press, or trust sections that links visitors to this public report.
<a href="https://www.llmscan.dev/scan/n3FAuHD1Y7TMP07BjeR43"
target="_blank"
rel="noopener"
>
<img
src="https://www.llmscan.dev/scan/n3FAuHD1Y7TMP07BjeR43/badge.png"
alt="LLM Scan AI visibility score badge"
width="460"
height="120"
style="width: 260px; max-width: 100%; height: auto;"
/>
</a>Share your score
Post the public report with: “We scored 63/100 for AI-readability.”
Download fixes
Grab generated files and implementation notes for the highest-impact gaps.
Rescan weekly
Save this domain to catch regressions after content, sitemap, or robots changes.
Monitor weekly// signal breakdown
The homepage is reachable, but the requested URL redirects before reaching the homepage.
Signal weight
Evidence
Recommendation
Next step: Serve a non-empty HTML homepage with a canonical link tag that points to the preferred public URL.The robots.txt file was found, but it contains formatting issues.
Signal weight
Evidence
Recommendation
Next step: Fix robots.txt syntax issues so each rule uses Field: value format, directives appear under a User-agent, and Sitemap entries use absolute URLs.The llms.txt file was found and includes the expected text, length, heading, and URL signals.
Signal weight
Evidence
The sitemap index is valid and the checked child sitemap contains URL entries.
Signal weight
Evidence
The homepage returned HTML when requested with Accept: text/markdown, so the server appears to ignore markdown content negotiation.
Signal weight
Evidence
Recommendation
Next step: Add content negotiation for Accept: text/markdown on the homepage and return a markdown representation with Content-Type: text/markdown. Keep the HTML response for regular browser requests.The homepage has some semantic HTML signals, but one or more title, metadata, heading, landmark, content, or link text checks need improvement.
Signal weight
Evidence
Recommendation
Next step: Add exactly one h1 element that describes the page topic. Add missing semantic elements: main, article, nav, footer. Add visible body copy after script and style removal so the page has at least 200 words.Valid JSON-LD structured data was found with core Organization or WebSite schema.org types.
Signal weight
Evidence
AI content usage signals detected via Content-Signal robots.txt directives.
Signal weight
Evidence
Recommendation
Next step: Consider adding Content-Signal HTTP header, AI-specific head meta tags, robots noai/noimageai directive so AI systems can consistently discover content usage preferences across robots.txt, HTTP headers, and HTML metadata.// generated fixes
Preview the generated files below. Enter your email to reveal the full fixes, download the bundle, or copy the agent-ready implementation prompt.
Done-for-you
Agency packageNot sure how to ship the technical fixes? Book a call and we can help turn this report into implemented updates.
Fix planning from your scan
Implementation guidance
AI visibility monitoring
# Go Publicly – Discover, Launch, and Upvote Indie Projects > Go Publicly is the platform to discover, launch, and upvote the best indie projects. Join our community of makers and innovators. This llms.txt file summarizes the public, canonical resources that AI assistants and crawlers should use to understand this site. ## Site Overview - Canonical URL: https://www.go-publicly.com/- Site type: organization# robots.txt additions# Copy these blocks into the existing robots.txt file. Keep current rules unless a note calls out a conflicting Disallow. # AI crawler access# Add explicit Allow rules for AI crawlers so public content permissions are clear.{ "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://www.go-publicly.com/#organization", "name": "Go Publicly – Discover, Launch, and Upvote Indie Projects", "description": "Go Publicly is the platform to discover, launch, and upvote the best indie projects. Join our community of makers and innovators.", "url": "https://www.go-publicly.com/",# Content-Signal recommendations Use these directives to make AI-use preferences explicit for compliant crawlers and AI systems. They are advisory signals, so keep them aligned with robots.txt, terms, and access controls. ## Recommended values - ai-train=no: AI model training, fine-tuning, and dataset creation.- search=yes: AI search indexing, snippets, and discovery.- ai-input=yes: AI answer grounding, retrieval, and generated-response context.