TL;DR. Third-party platforms drive ~97% of LLM citations; your brand site is the other ~3%. Profile completeness and sameAs reciprocation are load-bearing for AI visibility.
The X Presence is the audit you reach for when you already suspect a problem in this dimension and need a fast, copy-paste-able fix list. It reuses the same chrome as every other jwatte.com tool — deep-links from the mega analyzers, AI-prompt export, CSV/PDF/HTML download — but the checks it runs are narrow and specific to the dimension described above.
Audits a public X / Twitter profile for bio completeness, pinned post, location, verification status, link presence, and follower-to-following ratio — plus the signals AI models use to link the handle to your entity.
Why this dimension matters
Third-party platforms (Reddit, YouTube, LinkedIn, Substack, TikTok, etc.) are where ~97% of LLM citations come from — the brand site accounts for only ~3%. Auditing your platform presence is as load-bearing for AI visibility as auditing your own site, and most SMBs have measurable gaps (stale bios, missing sameAs links in their site schema, no posting cadence, profile fields left blank) that cost them citations they would otherwise earn for free.
Common failure patterns
- Bio + profile fields left blank — most platforms score completeness as a ranking input. A profile with a blank "About" section, no pinned post, no custom URL, and no banner image will rank below a fully-filled peer even with the same follower count.
- No
sameAsback-reference from the website — if your site's Person / Organization schema doesn't list the profile insameAs, search engines treat the profile as a weak match for your identity. The fix is onesameAsentry per profile; add to the site-wide schema. - Handle inconsistency across platforms —
@jwatteon one,@joshwatteon another,jwatte-devon a third. LLMs disambiguate via handle proximity; fragmenting handles fragments the entity graph. - Posting gap over 90 days — most platforms de-rank dormant profiles. A profile that hasn't posted in 3 months is treated as inactive and surfaces less in discovery feeds. The audit flags the last-post timestamp so the gap is measurable.
How to fix it at the source
Fill every available profile field — the audit surfaces exactly which are empty. Unify handles where possible (register your canonical handle early on any platform you might ever use). Add sameAs for every profile to the site-wide Organization / Person schema. Set a minimal posting cadence you can sustain (one post per month beats a burst followed by silence) and track last-post timestamps so gaps are visible before they drag ranking.
When to run the audit
- After a major site change — redesign, CMS migration, DNS change, hosting platform swap.
- Quarterly as part of routine technical hygiene; the checks are cheap to run repeatedly.
- Before an investor / client review, a PCI scan, a SOC 2 audit, or an accessibility-compliance review.
- When a downstream metric drops (rankings, conversion, AI citations) and you need to rule out this dimension as the cause.
Reading the output
Every finding is severity-classified. The playbook is the same across tools:
- Critical / red — same-week fixes. These block the primary signal and cascade into downstream dimensions.
- Warning / amber — same-month fixes. Drag the score, usually don't block.
- Info / blue — context only. Often what a PR reviewer would flag but that doesn't block merge.
- Pass / green — confirmation. Keep the control in place.
Every audit also emits an "AI fix prompt" — paste into ChatGPT / Claude / Gemini for exact copy-paste code patches tied to your specific stack.
Related tools in this family
- E-E-A-T Audit — the Person / Organization schema + sameAs depth audit.
- Brand-SERP Audit — audits how the brand appears when queried by name.
- Knowledge Graph + Wikidata Entity Audit — Wikidata is the strongest anchor for entity disambiguation.
- Author Authority per Article — per-article author schema — surfaces missing bylines + weak Person entries.
- AI Visibility Prompt Pack — tests whether LLMs cite your brand across a matrix of representative prompts.
Fact-check notes and sources
- Schema.org: Person type, sameAs property
- Google: sameAs for entity disambiguation
- Moz: Entity SEO + brand authority (ongoing research)
This post is informational and not a substitute for professional consulting. Mentions of third-party platforms in the tool itself are nominative fair use. No affiliation is implied.