Filter
Exclude
Time range
-
Near
Added JSON-LD via src/lib/seo/ JsonLd.astro. Layout.astro injects Organization WebSite globally; pages pass extra nodes through a jsonLd prop. /pricing → SoftwareApplication Offer (from Polar JSON) /docs/* → BreadcrumbList TechArticle /integrations → ItemList /integrations/{id} → SoftwareApplication on-page FAQ for visitors
1
13
Your brand can rank on Google and still be invisible to AI. That is the uncomfortable gap between traditional SEO and Generative Engine Optimization. SEO helps you get found. GEO helps your content get understood, extracted, attributed, and cited by AI systems. The fix is not "publish more." The fix is structure: - clear definitions - direct answers - strong entity signals - FAQ-ready extraction points - server-rendered JSON-LD that is visible in raw HTML That last detail matters. If schema only appears after JavaScript runs, some AI crawlers may never see the signal you thought you had. This is why I treat GEO as a data architecture problem, not a marketing trick. The same discipline that makes a page AI-citable is the discipline that makes a business system scalable: clean data, clear relationships, and structured flows. Question worth auditing: Can a machine understand what your brand is the authority on? #GEO #AIStrategy #ContentArchitecture #StructuredData #JSONLD #BrandVisibility
3
2
142
Will you keep using FAQPage schema after Google killed the rich results? #SEO #JSONLD
100% Yes
0% No
0% For some pages only
1 votes • Final results
4
3
118
ok so here it is - Seems like a lot of broken URLs and some blogs also contain broken URLs -- Google bot will penalize these and not index it - you can fix those immediately. A lot of pages URL is in English but keyword tags are missing and title is in Arabic - so it is being flagged as poorly formatted URL . Also none of the pages have JsonLD - that is a critical gap for AI discoverability in 2026. All these are the low hanging fixes you can do in a few hours with claude - give this report as input for basic fixes , and for the broken URLs , you can either use ubersuggest or reach out on DM, I can share the CSVs - tryansly.com/report/c7576f50…
1
2
46
#LongAnimationFrames #CBORLD #WebPerformance #SemanticWeb #LinkedData #JSONLD #CoreWebVitals #INP #FrontendPerformance Two Major W3C Advances in Web Performance and Semantic Data: Long Animation Frames API and CBOR-LD 1.0 #W3C#WebStandards seow3c.blogspot.com/2026/04/…

2
14
AI is quietly making human experts invisible. Someone built a tool to stop it. Every time you ask an AI to write code, something disappears. Not the code. The trail. The GitHub discussion. The Stack Overflow answer. The RFC your team wrote six months ago. The AI consumed all of it. The humans who produced it got nothing. Daniel Nwaneri built proof-of-contribution to fix this — and at its core is a Knowledge Graph schema that keeps the human knowledge chain intact inside AI-assisted codebases. When the skill is active, Claude automatically appends a Provenance Block to every generated output. When Claude generates code, it also generates a graph schema for Neo4j, Postgres, or JSON-LD.  Nodes for code artifacts, human sources, individual experts, AI sessions, and knowledge claims.  Edges that let you ask: "who are the humans behind this module?" or "what did username contribute to this codebase?" The result is a queryable, enforceable record that lives next to the code — not a comment nobody reads. The part that matters most is the Knowledge Gaps section. That's where AI admits what it synthesized without a traceable human source. No other tool produces this.  It turns "the AI wrote it" from a shrug into an auditable fact. AI should be a pointer to human expertise. Not a replacement. A pointer. By Daniel Nwaneri. dev.to/dannwaneri/ai-is-quie… #SoftwareEngineering #ClaudeCode #GraphSchema #Neo4j #JSONLD #ProvenanceTracking #GenAI -- Connected Data London 2026 has been announced! 11-12 November, Leonardo Royal Hotel London Tower Bridge 📝 connected-data.london/post/c… Join us for all things #KnowledgeGraph #Graph #analytics #datascience #AI #graphDB #SemTech #Ontology 🎟 Ticket sales are open. Benefit from early bird prices with discounts up to 30%. 2026.connected-data.london?u… 📺 Sponsorship opportunities are available. Maximize your exposure with early onboarding. Contact us at info@connected-data.london for more.
1
8
357
Apr 10
Setting up metadata and jsonLD for SEO is still a annoying problem that you have to go through everytime you setup a new project. I'm building something to fix this drama from ground up with sime simple and easily configurable functions. This is the start of something big.
5
68
Replying to @ItsDave_ADA
BOOM! Single tx, multi vote, multi asset with ofish vote jsonld embedded in the asset on-chain. Previously what I shared was a working process but not an official vote. I was showing what could be done. Now it's done, an ofish vote or votes. All current locations to view the jsonld of drep votes aren't set up to look at assets. Could easily be done though. Anyway, auto pulls in connected wallet drepID, few clicks, comment if you want, add multiple actions, submit, sign, done.
1
2
29
Replying to @ItsDave_ADA
I created a vote submission form to on-chain asset with the vote jsonld on-chain in the asset. I can update the form to handle multiple actions at once. Gonna work on that today. I plan to streamline the whole process for DReps. I used the app to create my DRep registration as well.
1
2
26
AI modellerini masrafa sokmadan, ai botlarının siteni bulması, okuması ve anlaması. LLMs.txt, inception page, semantic context sayfaları, semantic keywords, tl,dr özetleri, jsonld… ai botları, arama motorları gibi html okursa çok masraflı, bu yüzde temiz çıktıları okumak istiyor
5
376
18 Dec 2025
So! The FAQs from NameScore now have jsonLd data. Let's see how this affects SEO and whether Google and co. can do anything with it. Does anyone have any experience with this?
2
3
95
CIP-100 makes it totally possible to post rationales and other governance commentary on-chain without casting a vote, for what it's worth! Separate from our disagreement on this, that's something I've wanted to see people start utilizing more, so lets get behind that and push a bit. The main thing needed for this is: - Someone sit down and write down a markdown document describing the format of their commentary; for example, it defines two fields, "inReferenceTo" and "commentary", and explains that such a document should be considered an official statement from the submitter, and displayed alongside the "inReferenceTo" governance action. - Include the URL to this document in the `@context` field of a jsonld document, and post a transaction on chain with their commentary - Get governance tooling like gov tools to index and display such commentary, perhaps sorted by CC member vs dRep, etc. In particular, it's quite a bit more lightweight than going through the CIP process, and isn't gatekept by needing "approval"... you can just *do* things, invent your own standard, and then if it's popular and useful, tools have a self-describing documentation for how to interpret it and integrate it into the tooling. This would have been perfect for a scenario like this if we already had it in place :)
5
223
We’re working for AI visibility day by day. Deep dive tip- focus on JSONLD Schemas. For the most accurate actionable audit, and implement in 3 steps. go to Aeo.vc #buildinpublic #aivisibility #startup #b2bsaas #vibecide
1
3
58
8 Oct 2025
Good morning!😊 今日はJSON-LD と構造化データ の勉強。ブログやポートフォリオに実装しWebdiary のように SEO を意識した設計を試します。 おすすめ 👉 Googleの構造化データテストツールで自分のサイトをチェック✅ #Web制作 #SEO #JSONLD #構造化データ
4
87