MyPhotoAI · pSEO case study

Three JSON-LD patterns for pSEO leaves that actually help

JSON-LD structured data on a pSEO leaf is a hygiene signal, not a ranking lever. Most surfaces over-invest in elaborate schemas that rich-results-test happily but produce no measurable lift. This leaf documents the three patterns we ship on every leaf and the four we have stopped shipping because they did not move the needle in our two production surfaces.

By AlkenaCode engineering team

We ship programmatic SEO surfaces, AI-driven receptionists, and case-study sites for Kenyan SMEs and overseas clients. Every claim on this page traces back to shipping work, not speculation. The audit tool on /audit is the same software we use to evaluate prospective engagements.

Authors of the myphotoai.alkenacode.dev pSEO surface itself. Source code is open at github.com/Kiragu-Maina/alkenacode-family. Production deployments include agents.alkenacode.dev and home.alkenacode.dev.

Last updated:

The Article and BreadcrumbList JSON-LD on this leaf is the actual production output of our build. You can view-source on this page to inspect the rendered JSON-LD; it matches the templates described in the body.

Three JSON-LD patterns for pSEO leaves that actually help

Article: the only required pattern

Every leaf gets an Article object with headline, datePublished, dateModified, author, mainEntityOfPage, and image. The dateModified value mirrors the lastUpdated field on the slug; the build pipeline embeds it at compile time. Author is an Organization rather than a Person on this surface because the team is the named entity, not any single contributor. We have observed the Article schema correlate with one to two-position rich-snippet placement gains on Bing; Google does not surface them as visibly but still uses them as freshness signals.

BreadcrumbList: cheap, real lift

BreadcrumbList on every leaf describes the path Home, Case study, Spine piece, Leaf. The schema is forty lines of TypeScript composed at build time from the slug's relatedSpineLinks field. The lift is visible in the rich-results test and shows up as breadcrumb display in mobile search results, which earns measurable click-through-rate at the top of the SERP. This is the highest-leverage schema we ship and the cheapest to maintain. The W3C JSON-LD spec is the source for the syntax; schema.org is the source for the type vocabulary.

FAQPage: only when the leaf actually has a FAQ section

FAQPage schema is the most over-applied. Adding it to a leaf without a real FAQ section is a misuse and earns nothing. We ship FAQPage only on leaves that have a literal question-and-answer section in their body, which is about four leaves on this surface. The four that do ship it get rich-snippet FAQ accordion display on Bing and occasional Google placement. The four we stopped shipping (HowTo, Product, Review, VideoObject) either earned no lift or actively triggered manual reviews when the page did not match the schema's contract.

src/app/p/[slug]/page.tsxtsx
import { SLUGS } from "../../../../content/slugs";

export const dynamicParams = false;

export function generateStaticParams() {
  return SLUGS.map((s) => ({ slug: s.slug }));
}

export default function LeafPage({ params }: { params: { slug: string } }) {
  const leaf = SLUGS.find((s) => s.slug === params.slug);
  if (!leaf) notFound();
  // ... render the leaf
}
The leaf route's generateStaticParams reads the manifest at build time and tells Next.js which slugs to emit as static HTML.

Sources

Every claim on this page traces back to one of the verifiable sources below. Citations are publisher-stable; we avoid blog posts and other URLs that may not survive a year.

  1. schema.org: full type hierarchy (schema.org)
  2. W3C JSON-LD 1.1 specification (W3C)
  3. Google: introduction to structured data markup (Google Search Central)
  4. Google: indexing overview (Google Search Central)
  5. Google: creating helpful, reliable, people-first content (Google Search Central)
  6. Next.js docs: generateMetadata (Next.js)
  7. Google: title link and meta description best practices (Google Search Central)
  8. Google: page experience signals (Google Search Central)
  9. Google Search Quality Rater Guidelines (PDF) (Google Search Central)
  10. web.dev: Lighthouse SEO audits (Chrome for Developers)
Free site auditor

See how the pattern applies to your site

The auditor uses the same evidence bundle described above (robots, sitemap, page samples) and returns a structured opinion. No signup, no email required to see results.