Skip to content

[codex] Add structured profile data #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Radical-Coder wants to merge 2 commits into from
Closed

[codex] Add structured profile data #8

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3630e4c
Add structured profile data
Radical-Coder Jun 16, 2026
906bf96
Make structured data person first
Radical-Coder Jun 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
82 changes: 82 additions & 0 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,88 @@
<meta name="twitter:card" content="summary_large_image" />
<meta name="theme-color" content="#000000" />
<title>Ryan Gonyon | Make Fragile Software Dependable</title>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Person",
"@id": "https://radical.codes/#ryan-gonyon",
"name": "Ryan Gonyon",
"url": "https://radical.codes/",
"email": "mailto:coderradical@gmail.com",
"jobTitle": "Software engineer",
"brand": {
"@id": "https://radical.codes/#radical-codes"
},
"sameAs": [
"https://github.com/Radical-Coder"
],
"knowsAbout": [
"AI-built MVP stabilization",
"Stripe payment flows",
"Supabase auth and RLS",
"workflow automation",
"internal operations dashboards",
"production readiness"
]
},
{
"@type": "Brand",
"@id": "https://radical.codes/#radical-codes",
"name": "Radical Codes",
"url": "https://radical.codes/"
},
Comment on lines +47 to +51

@coderabbitai coderabbitai Bot Jun 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

For Schema.org JSON-LD, is an unreferenced node in @graph (like OfferCatalog) considered related to Person/Brand/WebSite without an explicit linking property? What is the recommended property (e.g., hasOfferCatalog) to connect a Brand or Person to OfferCatalog?

💡 Result:

In Schema.org JSON-LD, an unreferenced node within a @graph array—meaning no other node points to it via an @id reference or as an inline property value—is considered an orphaned or disconnected node [1][2][3]. While it may be syntactically valid JSON-LD, search engines often fail to associate such nodes with the primary entities (like Person, Organization/Brand, or WebSite) on the page, effectively causing them to be ignored in the context of the Knowledge Graph [2][3]. To connect an OfferCatalog to a Person or Organization (Brand), the recommended property is hasOfferCatalog [4][5][6]. Key points for implementation: 1. Relationship: The property hasOfferCatalog is explicitly designed to link a Person, Organization, or Service to an OfferCatalog [4][7][6]. It is the standard, authoritative way to establish this connection [8]. 2. Graph Connectivity: When using @graph, you should ensure all entities are explicitly linked [1][9]. An OfferCatalog should be nested within the Person or Organization object using the hasOfferCatalog property [4][6], or linked via an @id reference if the nodes are defined separately at the top level of the @graph array [1][9]. 3. Avoiding Orphans: If you define an OfferCatalog as a separate object in the @graph array, ensure another node in that graph references it [2][3]. Without an explicit linking property (like hasOfferCatalog), the nodes remain disconnected, and the relationship will not be inferred by search engines [2][3]. For example, using the recommended approach: { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://example.com/#organization", "name": "Example Brand", "hasOfferCatalog": { "@id": "https://example.com/#catalog" } }, { "@type": "OfferCatalog", "@id": "https://example.com/#catalog", "name": "Our Services", "itemListElement": [...] } ] } This structure explicitly links the Organization to the OfferCatalog, ensuring the graph is fully connected and valid [1][9].

Citations:

🏁 Script executed:

cat -n index.html | sed -n '40,105p'

Repository: Radical-Coder/radical-codes-site

Length of output: 2643

Link the OfferCatalog node to a primary entity instead of leaving it orphaned.

The OfferCatalog defined at line 65 is never referenced by Person, Brand, or WebSite, so search engines will not associate the service lanes with your brand. Add hasOfferCatalog to the Brand node to explicitly connect them.

Suggested fix 
          {
            "`@type`": "Brand",
            "`@id`": "https://radical.codes/#radical-codes",
            "name": "Radical Codes",
-           "url": "https://radical.codes/"
+           "url": "https://radical.codes/",
+           "hasOfferCatalog": {
+             "`@id`": "https://radical.codes/#service-lanes"
+           }
          },
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"@type": "Brand",
"@id": "https://radical.codes/#radical-codes",
"name": "Radical Codes",
"url": "https://radical.codes/"
},
"`@type`": "Brand",
"`@id`": "https://radical.codes/#radical-codes",
"name": "Radical Codes",
"url": "https://radical.codes/",
"hasOfferCatalog": {
"`@id`": "https://radical.codes/#service-lanes"
}
},
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@index.html` around lines 47 - 51, The OfferCatalog node at line 65 is
disconnected from your primary entities and will not be recognized by search
engines. Add a hasOfferCatalog property to the Brand node (the one with `@id`
"https://radical.codes/#radical-codes") that references the OfferCatalog to
establish the relationship and ensure search engines associate the service
offerings with your brand.

{
"@type": "WebSite",
"@id": "https://radical.codes/#website",
"name": "radical.codes",
"url": "https://radical.codes/",
"about": {
"@id": "https://radical.codes/#ryan-gonyon"
},
"publisher": {
"@id": "https://radical.codes/#ryan-gonyon"
}
},
{
"@type": "OfferCatalog",
"@id": "https://radical.codes/#service-lanes",
"name": "Radical Codes service lanes",
"itemListElement": [
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "AI-built MVP stabilization"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Stripe, Supabase, and provider hardening"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Reviewable AI workflow automation"
}
},
{
"@type": "Offer",
"itemOffered": {
"@type": "Service",
"name": "Internal control boards"
}
}
]
}
]
}
</script>

<!-- Google Fonts: Outfit (headings), Inter (body), JetBrains Mono (code) -->
<link rel="preconnect" href="https://fonts.googleapis.com">
Expand Down