AAJMarketing Skills

// execute

Structured Data for AI Search

Use when the user wants to add, fix, or validate structured data (JSON-LD, schema.org) so search engines and AI answer engines read a page correctly: which types belong on which page, which properties Google requires, and whether the markup matches what the page shows. Also use when the user mentions schema markup, JSON-LD, structured data, rich results, SoftwareApplication, Organization schema, FAQPage, HowTo, Article or BreadcrumbList markup, or "is our schema right". Produces a page-by-page type map, a sourced check of each page's JSON-LD, and the exact fixes.

ExecuteengineIntermediate
bash
$npx skills add sarojkjha/aaj-marketing-skills --skill structured-data-for-ai-search
Or run it in Claude or ChatGPT through the AAJ engines connector

Claude Code

/plugin marketplace add sarojkjha/aaj-marketing-skills
/plugin install aaj-marketing-skills@aaj

OpenAI Codex

codex plugin marketplace add sarojkjha/aaj-marketing-skills
codex plugin add aaj-marketing-skills@aaj

Claude or ChatGPT — no install

Add this as a custom connector:

https://aaj-engines-mcp.sarojkjha10.workers.dev/mcp
Recipes: vendor data in, a verdict out

// when to use it

Use when the user wants to add, fix, or validate structured data (JSON-LD, schema.org) so search engines and AI answer engines read a page correctly: which types belong on which page, which properties Google requires, and whether the markup matches what the page shows. Also use when the user mentions schema markup, JSON-LD, structured data, rich results, SoftwareApplication, Organization schema, FAQPage, HowTo, Article or BreadcrumbList markup, or "is our schema right". Produces a page-by-page type map, a sourced check of each page's JSON-LD, and the exact fixes.

// what you give

The site's key page types, and for each page its JSON-LD (or full HTML) plus the visible text

// what you get

A type-per-page map, a per-page check (fix, eligibility, improve, with the source for each), corrected JSON-LD, and a re-validation plan

Engine spec

// decision it supports

Is the JSON-LD on this page valid, true to what the page shows, and complete for its type?

// inputs

The site's key page types, and for each page its JSON-LD (or full HTML) plus the visible text

// output

A type-per-page map, a per-page check (fix, eligibility, improve, with the source for each), corrected JSON-LD, and a re-validation plan

// acts or analyzes

Analyzes only

Makes no network calls, writes no files and changes nothing in your tools.

// where your information goes

How you run itWhere your inputs go
Skill installed in your agent, or the local MCP serverThe engine runs on your machine and AAJ receives nothing. Your AI agent still sends what you give it to its model provider (Anthropic, OpenAI and so on), under your own account's terms.
Hosted MCP serverYour agent's model provider, as above, plus AAJ's server on Cloudflare, which receives the engine inputs over HTTPS, runs them in memory and keeps no copy. Cloudflare keeps error logs (no inputs) for up to 7 days.

No engine needs customer names, emails or other personal data; leave them out.

// limitations

  • It compares markup with what readers see only when you pass html or visibleText. Without them the verdict is "Valid markup, not checked against the page", never "Ready to publish".
  • It checks the markup you paste, not what a crawler receives. JSON-LD added by client-side JavaScript may never reach a crawler.
  • A clean check does not promise a rich result or any effect on AI answers. Google says no special schema is needed for its AI features.
  • Its rules follow Google and schema.org pages opened on 2026-10-10. Google edits those pages; re-check the source each finding cites.

// review before acting

Whoever owns the site confirms every price, rating, question and date in the markup appears on the live page, then re-validates the deployed URL with Google's Rich Results Test and checks the JSON-LD is in the server response.

// setup

install
$npx skills add sarojkjha/aaj-marketing-skills --skill structured-data-for-ai-search
hosted mcp
$https://aaj-engines-mcp.sarojkjha10.workers.dev/mcp

Agents listed: Claude Code, Cursor, OpenAI Codex, Windsurf, Cline. Tested and recorded: Claude Code.

Full spec on GitHub

Structured Data for AI Search

Give every key page JSON-LD that says exactly what the page is and nothing the page does not show, then prove it with a sourced check.

When to use

The user is adding schema to a site, fixing markup a validator complained about, deciding which types a SaaS, AI, EdTech or MedTech site needs, or asking whether schema will help them appear in AI answers. For a whole-page SEO/GEO/AEO score, use seo-geo-aeo-audit; for rewriting content to be cited, use geo-content-optimization. This skill is the markup itself.

Before you start

  1. Read the brand/product context first. Pull the product name, pricing model, and site map from .agents/product-marketing.md. If none exists, ask for the key URLs.
  2. Gather inputs: for each page to check, its HTML (best: JSON-LD and visible text in one) or its JSON-LD plus the page text.
  3. Check what crawlers receive. If the site renders client-side, JSON-LD added by JavaScript may not be in the HTML a crawler fetches. Run the fetch test in seo-geo-aeo-audit first; markup nobody receives fixes nothing.
  4. Set expectations honestly. Google says there is "no special schema.org structured data" needed for AI Overviews or AI Mode, and lists structured data matching the visible text among the fundamentals (Google, AI features and your website). Treat schema as an accurate description of the page, not a lever that wins AI citations. Do not promise an effect on any AI engine.

Method

Diagnose what each page is, then design one primary type per page plus the shared types (Organization once, BreadcrumbList on inner pages), and execute by checking every block against two sources: Google Search Central's documentation for the properties Google requires and recommends, and schema.org for the types Google no longer documents. The rule that overrides all others is Google's general guideline: structured data "must be a true representation of the page content" and you should not "mark up content that is not visible to readers of the page". A rating, price, question or step in the markup that the page does not show is the most common and most damaging error, so the check compares markup against the visible text whenever it is supplied.

Which type on which page

PageTypeWhat Google documents (opened 2026-10-10)
Home page, or one About pageOrganizationNo required properties; recommends name, url, logo, sameAs, description and more. Place it on the home page or a single page about the organization, not every page.
SaaS or AI product / pricing pageSoftwareApplication (or WebApplication)Required for the rich result: name, offers.price (0 if free), and one of aggregateRating or review. Recommended: applicationCategory, operatingSystem.
Physical product (e.g. a device)ProductRequired: name, and one of review, aggregateRating or offers. Offer needs price.
Blog post, guide, researchArticle / BlogPostingNo required properties; recommends author (Person or Organization, with name and url), datePublished, dateModified, headline, image.
Visible FAQ sectionFAQPageGoogle stopped showing FAQ rich results on 7 May 2026 and removed the docs on 15 June 2026. Valid schema.org; use only where it mirrors a visible FAQ.
Step-by-step instructionsHowToGoogle removed How-to docs on 14 September 2023; the rich result is not shown on desktop or mobile. Valid schema.org.
Any page below the home pageBreadcrumbListAt least two ListItems; each needs name and position; item (URL) on all but the last. Mirror the visible trail.

Ratings belong only where real ratings are shown on the page. Never add an aggregateRating to qualify for a rich result. Google also notes that reviews an organization controls about itself, on pages using Organization markup, are not eligible for star review snippets.

Workflow

  1. List the page types on the site and assign each a primary type from the table.
  2. Collect each page's HTML (or JSON-LD plus visible text).
  3. Run the checker per page with its pageType.
  4. Fix in order: fix (broken markup, or markup the page does not show), then eligibility (Google's rich-result requirements, only where the page can truthfully meet them), then improve (recommended properties).
  5. Write the corrected JSON-LD using only facts visible on the page, and re-run the checker until no fix remains.
  6. Re-validate after deploy with Google's Rich Results Test on the live URL, and confirm the JSON-LD is in the server response.
  7. Set an upkeep rule: when a price, rating, author or date changes on the page, the markup changes in the same release.

Run the tool

node resources/schema-check.js --demo
node resources/schema-check.js '{"pageType":"software","html":"<!doctype html>..."}'
node resources/schema-check.js --help

Input a page type and a JSON-LD blob, a JSON string, or HTML containing <script type="application/ld+json">. Add html or visibleText to compare markup with what readers see. The engine parses every block and @graph, checks @context and @type, checks every node of a known type (and that the page's own type is present), and returns findings at four levels (fix, eligibility, improve, info), each with the source URL it relies on and a verdict: Fix before publishing, Valid, not rich-result eligible, or Ready to publish.

Reference

Sources opened on 2026-10-10 (re-check them; Google edits these pages):

Present the result

  • Type map: each page, its primary type, and the shared types.
  • Per page: the verdict, then fixes in order (fix, eligibility, improve), each with its source.
  • Corrected JSON-LD for each page, built only from visible facts.
  • What not to expect: no guaranteed rich result, and no promised effect on AI answers.

Guardrails & common mistakes

  • Visible or nothing. Never mark up a price, rating, question or step the page does not show.
  • No invented ratings. A missing rating costs a rich result; a fabricated one misrepresents the page.
  • FAQPage and HowTo are descriptions now, not Google features. Keep them only where they mirror visible content.
  • One Organization, consistent everywhere. The same name, url and logo on every page that references it.
  • Dates are ISO 8601, dateModified is never earlier than datePublished, and neither is in the future.
  • Rendered, not just written. Markup injected by client-side JavaScript may never reach a crawler.
  • Never claim schema wins AI citations. Google says none is needed for its AI features; other engines do not document a position this skill can cite.

Related AAJ resources

Related skills

seo-geo-aeo-audit · geo-content-optimization · agent-readiness-audit · aaj-programmatic-seo · comparison-pages

// faq

// install

$npx skills add sarojkjha/aaj-marketing-skills --skill structured-data-for-ai-search

// worked example

Get the worked example for Structured Data for AI Search

One email. The filled-in config, the output, and how to read it.

No spam. Unsubscribe anytime.

// sprint

AI Visibility Sprint — $3,500, 10 business days

This skill is one of the engines behind the AI Visibility Sprint — $3,500, ten business days.

SEO/GEO/AEO audit, citation tracking, and agent readiness — scored, with the fixes ranked.

See what's included.

// human in the loop

Need a human in the loop?

AAJ builds the strategies, tools, and playbooks these skills are made of — with engagements for growth-stage and enterprise teams.

Explore tools Services