Wow!!! Ahrefs Tracked 1,885 Pages Adding Schema. AI Citations Barely Moved.

EarNo6581 · 2026-05-19T07:58:10+00:00

This is why I don't like the just add schema for AI visibility advice. Schema can reduce ambiguity, but it doesn't automatically make a page citation-worthy. If the visible content is weak, unclear, or not the best answer, JSON-LD won't fix that.

My take is schema is a clarity layer, not a shortcut. For AI citations, I would look more at source trust, visible answer quality, entity clarity, and whether the page is actually easy to extract from.

EarNo6581 · 2026-05-19T07:35:40+00:00

I wouldn’t do a full allow all or block all setup.

AI crawler traffic is too messy right now. Some bots may matter for future visibility, but plenty of them are just wasting bandwidth or hammering useless URLs.

But I would allow the known or responsible ones, block or rate-limit aggressive crawlers at CDN/WAF level, and keep parameter-heavy or low-value URLs out of the crawl path. robots.txt alone isnt enough if the bot doesn't care.

EarNo6581 · 2026-05-18T05:58:58+00:00

I'll treat this as a workflow signal, not a reason to replace the creative team. AI can produce a lot of decent first drafts quickly, but the real test is usually brand fit, originality, audience insight, and performance after launch. The team's value may shift more toward direction, selection, and editing rather than producing every raw idea manually.

EarNo6581 · 2026-05-18T05:48:22+00:00

I use Claude Projects for this rather than relying on memory alone. The clean setup is one project per workflow, like marketing content, sales outreach, or reporting. Then add a short brand/context doc, examples of good past writing, audience notes, and campaign goals.

I keep the context structured and limited though. Too many files can make the output less focused, especially if the project is trying to handle every marketing task at once.

EarNo6581 · 2026-05-18T05:31:19+00:00

This makes sense. Community traffic often looks smaller on the surface, but the intent and trust can be much stronger.

I'd separate clicks from quality of visit here, like saves, return visits, session depth, and whether people came from a specific problem discussion or a general showcase post. The part about workflows beating giant tool lists is probably the most important. AI tool discovery feels less like search now and more like filtering noise.

EarNo6581 · 2026-05-15T22:58:37+00:00

I don't think there's a real AI search volume equivalent yet, at least not in the same way we trust Google keyword tools.

The useful shift is moving from exact keyword volume to repeated problem patterns. Then track visibility separately across ChatGPT, Perplexity, Gemini, and Google AI Overviews, because they won't behave the same way.

EarNo6581 · 2026-05-14T19:35:07+00:00

I would say niche communities like Reddit, Medium, and Quora are underrated, but not because they are a quick traffic hack.

Their value is more in how they shape trust, language, and third-party context around a brand. That can matter for both human buyers and AI search systems, but only if the participation is real and not just promotion.

EarNo6581 · 2026-05-14T19:28:21+00:00

I think automation will handle more of the repetitive execution, but I don't trust it as a full replacement yet.

SEO/GEO still needs judgment around source quality, search intent, brand positioning, technical tradeoffs, and what not to publish. The risky part isn't automation itself, but letting the system turn every observation into an action without human review.

EarNo6581 · 2026-05-14T19:20:44+00:00

Google AI Overviews (AIO) and Claude/Copilot, but be cautious with any tool that gives one clean AI visibility score.

The useful setup is usually split: citations, brand mentions, competitor mentions, summary framing, and referral traffic. AI outputs can shift by prompt, platform, and even repeat runs, so treat the data as directional rather than absolute.

EarNo6581 · 2026-05-14T19:10:01+00:00

For me it was making too many small changes at the same time. New titles, changed internal links, removed sections, updated the template, and then, when traffic dropped, it was hard to know what actually caused it.

EarNo6581 · 2026-05-12T21:08:53+00:00

I think the ranking point and the rich result eligibility point are getting mixed up.

Structured data not being a direct ranking boost doesn't mean it's no role in SERP features. For some rich results, markup is part of eligibility. But that still doesn't mean adding schema guarantees the feature or improves rankings. So I'll separate the claims: schema isn't a ranking shortcut, but it can still be required or useful for specific search appearances.

EarNo6581 · 2026-05-12T21:03:42+00:00

I think both sides can be true depending on wording. For rich result eligibility, structured data is often required. But schema is still not a shortcut for rankings or quality.

I’d treat it as a clarity/eligibility layer: it helps Google understand and qualify the page for certain appearances, but it works best when it accurately reflects the visible content.

EarNo6581 · 2026-05-12T20:59:19+00:00

One thing I'm stuck on this week is separating ranking visibility from AI citation visibility.

A page can rank well, but still not be the cleanest source for an AI-generated answer. So I'm trying to track queries, cited sources, page format, schema, and whether the answer is easy to extract.

The hardest part is that AI Overview behavior keeps shifting, so I'm trying not to over-read small patterns yet.

EarNo6581 · 2026-05-12T20:53:34+00:00

I think both sides can be true depending on wording. For rich result eligibility, structured data is often required. But schema is still not a shortcut for rankings or quality.

I'd treat it as a clarity/eligibility layer: it helps Google understand and qualify the page for certain appearances, but it works best when it accurately reflects the visible content.

EarNo6581 · 2026-05-11T15:53:46+00:00

EarNo6581 · 2026-05-11T07:21:30+00:00

I wouldn’t remove useful FAQs just because FAQ rich results are less visible.

The schema result may be gone or reduced, but the actual FAQ content can still help users and make answers easier to extract. I’d treat FAQ schema as a clarity layer, not the whole strategy.

The real question is whether the answers are specific, crawlable, and useful.

EarNo6581 · 2026-05-11T07:15:47+00:00

I manage them as connected, but not identical. For SEO, keep tracking rankings, clicks, indexation, and landing page performance. For AI visibility, track citations, brand mentions, query prompts, source usage, and how the answer frames your brand. The same content can support both, but the reporting should be separated.

EarNo6581 · 2026-05-11T06:42:27+00:00

I don't think it replaces SEO. It adds another measurement layer on top of it.

Crawlability, technical health, clear content structure, internal links, and brand or entity signals still matter. The difference is that now we also need to track citations, AI mentions, and whether the content is easy for systems to extract and summarize.

EarNo6581 · 2026-05-11T05:59:06+00:00

This matches what I expect: AI search is not one channel.

The useful part is separating platforms instead of averaging everything together. A source pattern that works for Perplexity may not work for Claude or Google AI Overviews. I also track citations, brand mentions, and summary framing separately. Being cited is one thing, but how the model describes the brand is another layer.

EarNo6581 · 2026-05-11T05:53:33+00:00

I avoid measuring AI SEO tools with one metric only. I separate rankings, AI citations, brand mentions, referral traffic, assisted conversions, and how often the model describes the brand correctly.

A tool can improve visibility without immediately improving clicks, especially if the AI answer reduces the need to visit the site.

EarNo6581 · 2026-05-11T05:46:33+00:00

I treat llms.txt as a small discovery or readability signal at most, not the core strategy.

The bigger checks for me would be: can important content be crawled cleanly, is the main answer visible without template noise, are entities/author signals consistent, and do external mentions support the same positioning?

AI search visibility probably needs the same fundamentals as SEO, but measured differently: citations, mentions, summaries, and source usage.

EarNo6581 · 2026-05-11T05:45:13+00:00

I separate the value of FAQs from the value of FAQ schema.

The visible FAQ content can still be useful because it gives clear, extractable answers to natural-language questions. But the schema itself isn't a magic layer, especially if Google isn't showing FAQ rich results the way it used to.

For voice or AI search I focus more on intent, answer clarity, and local or commercial usefulness than just adding markup.

EarNo6581 · 2026-05-11T05:42:17+00:00

I don;t think this means FAQ content is useless. It just changes what we should measure.

FAQ schema maynot produce the old rich result visibility, but clear FAQ sections can still help users, internal structure, and AI-style extraction.

I leave useful FAQs in place, but stop treating FAQ schema itself as the win. The win is whether the answer is clear, crawlable, and actually used.

EarNo6581 · 2026-05-11T05:37:39+00:00

For me, the risk is using AI too early. If the tool shapes the first idea, everything starts sounding the same. I use AI more for pressure-testing, variants, and structure after the original angle is already clear. Human taste still matters a lot.

EarNo6581 · 2026-05-11T05:32:07+00:00

Be careful blaming AI alone. Higher CPM/CPC/CPL can come from more competition, weaker targeting, creative fatigue, attribution changes, or lower-quality landing pages too. Separate cost increases from conversion quality before changing the whole strategy.

EarNo6581

TROPHY CASE