AI Visibility Scorecard
codekodo.tistory.com · Technology
Somewhat visible. AI bots can read codekodo.tistory.com, but it is missing the structured signals that push citation rate above competitors.
AI engines read this profile 16 times
Claude · Meta AI · ChatGPT · Apple Intelligence
#194,659 of 2,705,291 in Technology for AI visibility
29
5
AEO Visibility
iBorderline · 5.2/10
5
Muse Index Score
iAI agent readiness
Basic · 5/100
0
AI Adoption
iNone detected · 0/100
from our crawl and measurement
codekodo.tistory.com describes itself simply: "전체 글 💻 개발/iOS [iOS / SwiftUI].mask를 활용하여 Custom ProgressView를 구현해보자2023.04.27 지금 진행하고 있는 프로젝트에서 디자인 시스템을 도입하고 있다." Its AI visibility score is 5.2 out of 10: the engines can find it, but they do not have much to hold on to.
Our crawl found structured data on the page (WebSite), a sitemap and a readable heading structure. It is missing an llms.txt file.
AI crawlers have visited 4 times in our tracking, including ClaudeBot (Anthropic) and GPTBot (ChatGPT).
Strong · Good · Fair · Weak
Structured Data
Weak
Organization / LocalBusiness JSON-LD that AI can read.
Content Structure
Strong
Clear headings and answer-style content.
Entity Clarity
Fair
How clearly your brand identity reads to AI.
E-E-A-T Signals
Experience, Expertise, Authority, Trust
Weak
Experience, Expertise, Authority, Trust markers.
Technical AEO
Good
robots.txt, llms.txt, and AI-bot crawl access.
AI Discoverability
Fair
Sitemaps and entity links AI can follow.
How the web signals your brand to AI
Backlinks
Strong
Inbound links from other sites.
Domain Authority
Good
Established authority for your domain.
Reference Presence
Strong
Recognized in AI knowledge graphs.
News & Press
Weak
No press coverage found yet.
Community
Weak
No community discussion yet.
Social Mentions
Strong
Social discussion and mentions.
Your AEO score measures whether AI search engines - ChatGPT, Claude, Perplexity, Gemini - can actually read your site and cite it in answers. Roughly two-thirds of sites are invisible to them. At 5.2/10, codekodo.tistory.com has a working base to build on - fixable, and the signals above are where to start.
[iOS / SwiftUI] OnAppear, OnDisappear는 언제 호출될까?
2022.12.01 SwiftUI로 개발을 진행하다가 View 내부에서 직접적으로 프로퍼티에 접근할 때 onAppear를 한 번쯤은 사용한 경험이 있을 것이다. 가령, print(프로퍼티)처럼 View 내부에서 접근하면 이런 에러가 뜬다. View를 반환해달라는 에러다. 이런 에러와 마주치지 않기 위해 View 내부에서 직접적으로 접근하지 않고, onAppear 클로저 내부에서 접근하는 방식을 택한다. 아무튼 이럴 때 자주 사용하는 onAppear는 SwiftUI View Life Cycle에 속하고, 오늘은 Life Cycle에 대해 알아보려고 한다. SwiftUI에선 3개의 Life Cycle이 있고, 각각의 Appear, Update, Disappear 이다. 1. onAppear onAppear은 View가 보여지기..
Is this your brand?
The exact fixes for codekodo.tistory.com
Which AI engines already crawl you
Free AI bot monitoring: see every AI crawler that visits you
Already have an account? Sign in
The search landscape has fundamentally shifted. While Google still dominates, millions of users now ask questions to ChatGPT, Gemini, and Claude instead of typing into a search bar.
Continue reading in your free Engagemii portalFree signup unlocks the full article plus your personalized AEO fix list for codekodo.tistory.com.
Scored by Engagemii on August 1, 2026. Methodology: engagemii.com/aeo/methodology
Source URL: https://engagemii.com/aeo/brands/codekodo-tistory
Cite this score: Engagemii (2026). "AEO Score for codekodo.tistory.com." Retrieved from https://engagemii.com/aeo/brands/codekodo-tistory
Licensed under CC BY 4.0. You may reuse this data with attribution: a visible link to engagemii.com.
Powered by Engagemii - The Answer Engine Optimization (AEO) Platform