Structured Data Experiment Log: AEO & Schema Implementation

Introduction: Building an AEO Learning Lab

This page serves as a living log documenting the structured data experiments conducted on nichernandez.com. My goal is to demonstrate practical, hands-on experience in implementing various Schema.org types to enhance discoverability and citation potential in the era of Answer Engine Optimization (AEO) and generative AI search. Each experiment reflects a targeted approach to improving machine readability and E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) signals.

Experiment 1: Site-Wide Person Schema (Completed: 2026-06-28)

What Was Implemented

To establish a consistent authorial identity and expertise across nichernandez.com, a Person schema was implemented site-wide. This schema explicitly identifies “Nic. Hernandez” as a “Technical Content Strategist” and includes relevant sameAs links (e.g., LinkedIn) and knowsAbout fields outlining areas of expertise.

Why It Matters for E-E-A-T and AI

In the context of AI search and AEO, E-E-A-T is paramount. Search engines, and by extension, generative AI models, prioritize information from credible, authoritative sources. By clearly defining the Person behind the content, we provide explicit signals about the author’s credentials, which helps establish expertise and trustworthiness. This is a foundational step in building an authoritative online presence.

Code Changes

This involved modifying src/layouts/Layout.astro to:

1. Add a personSchema object containing your details.
2. Render this personSchema via a <script type="application/ld+json"> block on every page.

Validation

Schema.org Validator: Person schema detected and valid (0 errors, 0 warnings).

Experiment 2: CollectionPage and Article Schema on Portfolio (Completed: 2026-06-28)

The Problem

Initially, all pages on nichernandez.com (including portfolio case studies) were defaulting to a BlogPosting schema from Layout.astro. This was problematic for portfolio pages, as it often resulted in "datePublished":"undefined" errors due to missing pubDatetime values on non-blog content, and inaccurately described the content type.

The Solution: Schema Override and Specific Types

This experiment involved a multi-pronged approach to accurately classify content types and prevent erroneous default schema:

1. Schema Override Prop: An overrideDefaultSchema boolean prop was added to Layout.astro. This allows individual pages to disable the default BlogPosting schema if they are providing their own comprehensive schema.
2. Conditional BlogPosting: The default BlogPosting schema in Layout.astro was updated to only render if pubDatetime is present and overrideDefaultSchema is false.
3. CollectionPage for Portfolio Index: The main portfolio index page (src/pages/portfolio/index.astro) was updated to pass a CollectionPage schema, embedded with an ItemList of all case studies.
4. Article for Individual Case Studies: Each individual case study page (src/pages/portfolio/[slug].astro) was updated to pass a specific Article schema, pulling title, description, pubDatetime, and modDatetime directly from its frontmatter, and correctly generating ogImage.

Why It Matters for AEO

Accurately categorizing content with specific Schema.org types (CollectionPage for a directory, Article for a detailed piece) is fundamental for AEO. It explicitly tells search engines the nature of the content, improving machine understanding and eligibility for relevant rich results. The Article schema, in particular, provides crucial E-E-A-T signals like author and publication dates, enhancing trust and visibility in AI-driven search.

Code Changes

This involved modifications to:

1. src/layouts/Layout.astro (for the override prop and conditional BlogPosting).
2. src/pages/portfolio/index.astro (to pass overrideDefaultSchema={true} and the new CollectionPage schema).
3. src/pages/portfolio/[slug].astro (to pass overrideDefaultSchema={true} and the new Article schema with correct dates and ogImage).

Validation

Portfolio Index — Schema.org Validator: CollectionPage, FAQPage, and Person all detected and valid (0 errors, 0 warnings).

Case Study Slug — Schema.org Validator: Article and Person detected and valid (0 errors, 0 warnings).

Experiment 3: FAQPage Schema on Portfolio Index (Completed: 2026-06-28)

What Was Implemented

To directly address common questions about Nic. Hernandez’s background, services, and location, three Q&A pairs were added as visible HTML content to the portfolio index page (src/pages/portfolio/index.astro). Correspondingly, an FAQPage schema was integrated into the page’s structured data.

Why It Matters for AEO and Rich Results

FAQPage schema is one of the highest-impact structured data types for AEO. It makes content explicitly eligible for FAQ rich results in Google Search, where answers can appear directly on the SERP. More importantly, it provides direct, concise answers in a structured format that generative AI models can easily extract and cite, significantly boosting visibility in AI Overviews and other answer engines.

Code Changes

This involved modifying src/pages/portfolio/index.astro to:

1. Add the visible Q&A content in a new <section>.
2. Construct an FAQPage schema based on these Q&A pairs.
3. Pass an array of schemas (the existing CollectionPage and the new FAQPage) to the <Layout> component’s schema prop.

Validation

Schema.org Validator: FAQPage detected and valid on the portfolio index page (0 errors, 0 warnings). Confirmed alongside CollectionPage and Person in the same validation pass.

Google Rich Results Test context: Google has restricted FAQ rich results primarily to government and health sites since 2023. The FAQPage schema is correctly implemented and validated for AI engines (Perplexity, ChatGPT) to parse, even if Google does not generate a visual rich result from it.

Experiment Log Page — Self-Validation (Completed: 2026-06-28)

Schema.org Validator: BlogPosting and Person detected and valid (0 errors, 0 warnings).

Conclusion & Future Experiments

These initial structured data experiments lay a strong foundation for optimizing nichernandez.com for answer engines. By meticulously applying Schema.org markup and aligning content with AEO principles, the site is better positioned to be understood and cited by AI. Future experiments will explore other high-impact schema types (e.g., HowTo, Courses, JobPosting) and integrate advanced monitoring techniques.