DEV Community: Joleford Arrojo

Mapping a Personal Knowledge Graph: How I Structured My Digital & Academic Footprint

Joleford Arrojo — Sun, 09 Aug 2026 01:11:28 +0000

In the modern web, your online presence is no longer just a collection of profiles. Search engines, academic databases, and knowledge graphs treat people as entities. If those entities are fragmented, your work becomes harder to discover, attribute, and verify.

This post documents how I approached building a coherent digital and academic footprint as an independent creator and digital publisher from the Philippines. It is both a personal case study and a practical reference for anyone interested in persistent identifiers, open access, and semantic web practices.

Why This Matters

When your work spans GitHub, academic repositories, publishing platforms, and social channels, name disambiguation becomes a real problem. Persistent identifiers (ORCID, DOIs, Wikidata items, Knowledge Graph nodes) solve part of that. The rest is consistency and intentional linking.

The goal was simple: make every major platform point back to the same entity so that search engines and research tools can connect the dots.

Core Knowledge Graph and Semantic Anchors

These serve as the primary identity nodes:

Google Knowledge Graph: /g/11npsdtn86
Wikidata: Q140690702
Google Trends entity: tracked here
Crunchbase: Joleford Arrojo

Having a Wikidata item and a Knowledge Graph node creates a stable reference that other systems can link to.

Academic and Research Identifiers

Persistent researcher IDs help with disambiguation across platforms:

ORCID: 0009-0005-5138-9727
Web of Science ResearcherID: QUT-7607-2026
Google Scholar: LOK9LOIAAAAJ
The Lens: jolefordarrojo/scholar
Europe PMC, DataCite Commons, OpenAIRE, and SciProfiles are also linked through the same ORCID.

These identifiers make it possible for research tools to aggregate work under one person rather than treating similar names as separate authors.

Permanent Identifiers and Open Repositories

Open archival platforms and DOIs provide long-term access:

Zenodo DOI: 10.5281/zenodo.21801432
Internet Archive collections related to National Fraternity Day PH documentation
Scribd publisher page and related documents

DOIs and archival deposits are particularly useful when the work involves regional historical or cultural documentation that may not fit traditional journal pipelines.

Publishing and Literary Registries

Independent publishing presence is recorded in:

Amazon Author Central: jolefordarrojo
Goodreads: jolefordarrojo
Open Library: jolefordarrojo

Developer and Technical Infrastructure

Technical work and project sites live here:

GitHub: joleforda
DEV Community: joleford_arrojo
GitHub Pages sites for personal portal, Bos TV, and related community hubs
Supporting WordPress sites for longer-form documentation

Media and Communication Channels

Additional verified distribution channels include FilmFreeway profiles, Substack, LinkedIn, Reddit, YouTube, TikTok, and Facebook pages connected to Bos TV and related initiatives.

Practical Takeaways

Start with persistent identifiers — ORCID and Wikidata are high-leverage starting points.
Be consistent with naming — Use the same form of your name across platforms whenever possible.
Link everything back — SameAs relationships (in schema.org or Wikidata) help machines understand that different URLs refer to the same person.
Prefer open and archival platforms — DOIs and Internet Archive deposits age better than social media posts.
Treat it as infrastructure, not marketing — The goal is discoverability and attribution, not just visibility.

This kind of structured presence takes time to build and maintain, but it creates a durable public record that search engines and research systems can actually use.

If you’re working on your own digital identity, knowledge graph presence, or open documentation practice, feel free to share what approaches have worked for you.

The Architecture of an Entity Node

Joleford Arrojo — Sun, 26 Jul 2026 01:27:02 +0000

When structured data is correctly deployed, search engine algorithms build an interconnected semantic map. By establishing a structured web of relationships, crawlers no longer need to infer context — the connections are explicitly declared inside a knowledge graph database.

Core Entity Node

The central subject is defined under a unique profile (in this example, a Person entity).

Properties & Attributes

Directed edges connect the entity to verified data points such as familyName, sexOrGender, and other biological or identity traits.

Explicit Relationships

The system maps the entity to its professional role (occupation), place of origin (placeOfBirth), and national identity (countryOfCitizenship).

From Schema Markup to a Persistent KGMID and Knowledge Panel

Moving from a regular webpage to a recognized entity depends on resolving data consistently across independent sources. When high-authority platforms (such as GitHub and DEV.to) publish identical, non-conflicting information, search algorithms gain enough confidence to assign a permanent identifier.

This consistency is what allowed the entity to be resolved and assigned a stable Knowledge Graph ID:

Verified KGMID: /g/11npsdtn86

Once an entity receives a KGMID and Google has high confidence in its attributes, it becomes eligible to appear in the Google Knowledge Panel — the information box displayed on the right side of search results. The Knowledge Panel is the visible result of successful entity resolution.

The most important takeaway for modern SEO and entity-based optimization is consistency. Maintaining zero conflicting data across primary digital anchors allows algorithms to map relationships, assign a KGMID, and surface a Knowledge Panel without ambiguity.

Originally published at joleforda.github.io.

How I Verified a Google Entity (Entrepreneur Label) Using Clean Schema Markup

Joleford Arrojo — Fri, 24 Jul 2026 18:24:00 +0000

Hello DEV Community!

I want to share a practical SEO experiment that recently yielded solid results. Lately, I’ve been analyzing semantic web technologies to see how effectively search algorithms transition from simple keyword matching to understanding real-world Entities (people, places, and brands).

As a digital publisher running local media initiatives like Bos TV in the Philippines, establishing an unambiguous digital identity across various high-authority databases is crucial. To test how Google's Knowledge Graph processes structural connections, I deployed a unified entity strategy across my primary platforms.

The Result of the Experiment

The strategy successfully triggered Google’s Entity Recognition. The algorithm completely resolved my digital identity and generated a verified entity summary header labeling me as an "Entrepreneur", complete with an associated profile image, a direct knowledge bio, and mapped authority links.

Below is the actual search engine result showing the successfully generated entity summary:

Caption: Google Search Graph identifying the core entity parameters, educational background, and organizational role.

Google has officially assigned a persistent Machine ID to my entity, cementing this structural data within the permanent Knowledge Graph database:

Verified Knowledge Graph ID: Google Search Profile (KGMID: /g/11npsdtn86)

Key Takeaways for Entity Optimization

Zero Conflicting Data: The attributes provided across my web properties match the exact string descriptions and biological data found across independent verification nodes (such as ORCID or Crunchbase). Consistency prevents verification delays.
Authority Anchors: Utilizing high-domain platforms like GitHub and DEV.to helps index entity relationships faster because crawlers scrape these structures frequently.
Explicit Relationships: Explicitly declaring structural relationships and referencing the exact Knowledge Graph ID (/g/11npsdtn86) helps the algorithm fill out the attributes of the graph without ambiguity.

The next step in this deployment is exploring nested schemas for localized video hosting—specifically checking how BroadcastService and VideoObject rules apply to regional media setups to ensure local broadcasts index correctly.

If you are currently working on optimizing a personal brand or managing structural data for a media platform, I’d love to know what strategies have given you the most consistent index rates. Let's exchange insights in the comments below!

Verified Project Anchors:

Hello DEV! I'm a Digital Publisher and Content Creator from the Philippines

Joleford Arrojo — Thu, 23 Jul 2026 21:47:50 +0000

Hello DEV Community!

I wanted to take my first post as an opportunity to introduce myself and share what I do at the intersection of media, community broadcasting, and digital publishing.

🌐 About Me & My Work

I am a digital publisher and content creator based in the Philippines. Currently, I run a digital media platform that focuses on localized video content, public information activities, and community broadcasting.

Aside from content creation, I am deeply involved in various community initiatives to help keep local citizens informed and connected.

📖 Biography

Joleford Arrojo is an entrepreneur, digital publisher, and content creator based in Pagadian, Zamboanga Peninsula, Philippines. He is the Founder of Bos TV and a proud graduate of J.H. Cerilles State College - Tigbao Campus.

📊 Quick Facts

Full Name: Joleford Arrojo
Also Known As: Joleford A
Location: Pagadian, Zamboanga Peninsula, Philippines
Profession: Digital Publisher & Content Creator
Founder of: Bos TV
Education: J.H. Cerilles State College - Tigbao Campus
Height: 1.70 m

🛠️ Why I Joined DEV Community

As a digital publisher running Bos TV, I understand the massive role that technical SEO and data structures play in modern media. I work directly with structured data configurations—including Article, Event, Organization, and Person schemas—to ensure our local content and community broadcasts reach the right audience efficiently on Google.

I’m excited to connect with developers, SEO enthusiasts, and fellow creators here to share insights about content platforms, technical SEO, and building localized media infrastructure!

Let's connect! 🇵🇭