This site has a useful foundation, but important gaps still limit AI readability.
Key strengths include crawler policy and AI guidance file, while sitemap and content signals need attention.
Recommended next step
publish a valid XML sitemap at /sitemap.xml and reference it from the crawler policy file so crawlers and AI systems can discover important URLs.
Why monitor after one scan?
AI visibility changes when teams ship new pages, edit pricing or docs, update sitemaps, or change crawler rules. Weekly monitoring catches those silent regressions before answer engines and agents start reading stale or broken signals.
Monitor weeklyOverall score
// score breakdown
8 checks
Public link
llmscan.dev/scan/YT5gPag98Gq_B0r0062na
Signals checked
8 AI visibility signals
Fix bundle
4 copy-ready files
Share badge
Needs Work · 69/100A compact badge for footer, press, or trust sections that links visitors to this public report.
<a href="https://www.llmscan.dev/scan/YT5gPag98Gq_B0r0062na"
target="_blank"
rel="noopener"
>
<img
src="https://www.llmscan.dev/scan/YT5gPag98Gq_B0r0062na/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 69/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.robots.txt allows crawler access and includes Sitemap references.
Signal weight
Evidence
The llms.txt file was found and includes the expected text, length, heading, and URL signals.
Signal weight
Evidence
No accessible XML sitemap was found for this site.
Signal weight
Evidence
Recommendation
Next step: Publish a valid XML sitemap at /sitemap.xml and reference it from robots.txt so crawlers and AI systems can discover important URLs.The homepage returns markdown content when requested with Accept: text/markdown, giving AI systems a cleaner text representation with less navigation chrome to parse.
Signal weight
Evidence
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 missing semantic elements: article, footer.Structured data was found, but it is missing core Organization or WebSite schema, contains invalid JSON-LD, or only uses non-JSON-LD formats.
Signal weight
Evidence
Recommendation
Next step: Prefer valid JSON-LD and include Organization or WebSite schema.org types in valid JSON-LD for clearer AI interpretation.Content-Signal directive not detected in headers, HTML metadata, or robots.txt.
Signal weight
Evidence
Recommendation
Next step: Add the standard directive 'Content-Signal: ai-train=no, search=yes, ai-input=yes' to robots.txt, HTML metadata, or HTTP headers so AI systems can discover content usage preferences.// 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
# Erkin - Software Engineer > Personal website of Murat Erkin Cicek, a Full Stack Senior Software Engineer specializing in React, Node.js, and cloud technologies. 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.erkinn.com/- Site type: person# 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.User-agent: GPTBotAllow: / User-agent: ChatGPT-UserAllow: /{ "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://www.erkinn.com/#organization", "name": "Erkin - Software Engineer", "description": "Personal website of Murat Erkin Cicek, a Full Stack Senior Software Engineer specializing in React, Node.js, and cloud technologies.", "url": "https://www.erkinn.com/", "logo": "https://www.erkinn.com/apple-touch-icon.png",# 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.