stumason.dev
TypeScript
Pull Request Opened
PR #51 opened: Add Schema.org Person structured data for LLM/search visibility
What
Adds Schema.org JSON-LD structured data to the main Blade layout (resources/views/app.blade.php), so it appears on every page of stumason.dev.
Why
LLMs (ChatGPT, Perplexity, Claude) and search engines increasingly rely on structured data to understand who a site belongs to and what they do. This makes Stu's identity, skills, and web presence machine-readable across the whole site — not just one page.
Schema added
Person
name: Stuart Mason /alternateName: Stu MasonjobTitle: Software Engineer / Technical Leaderdescription: Authentic blurb drawn from existing site copyknowsAbout: Laravel, PHP, React, Inertia.js, TypeScript, AI-augmented development, developer tooling, SaaS architecture, etc.sameAs: stuartmason.co.uk, github.com/StuMason, linkedin.com/in/stu-mason, x.com/StuMason
WebSite
potentialAction(SearchAction): points to/articles?q=for search discovery
Notes
- Uses
@graph+@idanchors so the two nodes can cross-reference each other cleanly - No changes to any JS/TS components — pure Blade template
- The services page already has a similar (older) Person block; this global one takes precedence for crawlers
+64
additions
-0
deletions
1
files changed