The AI visibility checklist I used on my own agency site

May 20, 2026 · 11:30 AM UTC ·7 min read · 0 reactions · 0 comments · 25 views

TL;DR · WeSearch summary

The article discusses an AI visibility checklist created by Dmitry Kargaev for his agency website. It emphasizes the importance of entity clarity and machine-readable context for AI systems to effectively understand and recommend services. Kargaev outlines specific changes made to his site to improve its visibility and ensure accurate representation by AI models.

Key facts

▪Kargaev found that many recommended AI visibility consultants lacked clear, machine-readable information about their services.
▪He emphasizes that SEO is essential but not sufficient; AI models require clear entity definitions to provide accurate answers.
▪The checklist includes steps such as defining the entity in a single sentence and making services and pricing unambiguous.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/deeflect/the-ai-visibility-checklist-i-used-on-my-own-agency-site-2247
Publication time	Wed, 20 May 2026 11:30:09 +0000
Retrieval time	2026-05-20T11:35:02.440Z
Last seen	2026-05-20T11:35:02.440Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	dYLaDqQconWp
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3820775) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Dmitry (Dee) Kargaev Posted on May 20 • Originally published at blog.deeflect.com The AI visibility checklist I used on my own agency site #w21 #geo #checklist #anchor A few weeks ago I asked an answer engine to recommend an AI-visibility consultant. The first five results were a wall of slop. Three were SEO agencies that had rewritten their homepage with the word "GEO" stapled to it. One was a Medium post by someone who clearly had not shipped anything. One was a course.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments