[codex] Add structured profile data - #8
Conversation
📝 WalkthroughWalkthroughA ChangesSchema.org JSON-LD Structured Data
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with 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.
Inline comments:
In `@index.html`:
- Around line 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.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| "@type": "Brand", | ||
| "@id": "https://radical.codes/#radical-codes", | ||
| "name": "Radical Codes", | ||
| "url": "https://radical.codes/" | ||
| }, |
There was a problem hiding this comment.
🧩 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:
- 1: https://www.thatdevpro.com/blog/schema-org-graph-validates-first-try/
- 2: https://jwatte.com/blog/blog-tool-json-ld-nesting/
- 3: https://jwatte.com/blog/blog-tool-schema-graph-visualizer/
- 4: https://www.schema.org/hasOfferCatalog
- 5: https://schemaorg-coda.dpb.io/term?name=hasOfferCatalog
- 6: https://www.karpi.studio/schema-glossary-terms/has-offer-catalog
- 7: https://validator.schema.org/OfferCatalog
- 8: Offer and OfferCatalog schemaorg/schemaorg#995
- 9: https://squin.org/structured-data/json-ld-tutorial/
🏁 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.
| "@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.
|
Closing as superseded by #14. The structured data work has been adapted into current JSON-LD on both the home page and /ai-app-rescue/ route. Keeping this closed avoids applying schema for the old page model. |
1 participant
What changed
Adds schema.org JSON-LD to describe radical.codes as Ryan's professional hub without implying Radical Codes is a separate agency:
PersonBrandWebSiteOfferCatalogsameAsWhy
The site is becoming the canonical hub for GitHub, Upwork, and public profile links. Structured data helps crawlers understand the entity while staying aligned with the site copy: this is Ryan's personal proof surface, not a separate agency wrapper.
Validation
npm run buildSummary by CodeRabbit