Every JSON-LD type this site emits

Our honest position on structured data

Structured data is standard search infrastructure: it states the facts about a business in a form machines can parse without guessing. Google's own guidance is explicit that no special AI schema exists — there is no markup that makes an AI engine prefer a site. We emit ordinary, valid Schema.org JSON-LD whose claims match the visible page, and nothing else. What any engine does with it is up to the engine.

Site-wide graph — on every page

The base layout emits one connected @graph on every page. Its nodes:

• Organization · ProfessionalService · LocalBusiness

  One node, three types (@id #org)

  Who we are: name, founder, founding date, contact, coverage, hours. The canonical entity every other node points at.

• WebSite

  @id #website

  The site itself, publisher-linked to #org, with a SearchAction wired to our live scanner (/scan?url=…).

• WebPage

  One per page (canonical URL)

  The page you're on, linked into #website, with a SpeakableSpecification (h1 + first paragraph).

• BreadcrumbList

  Every page

  Position of the page in the site hierarchy (ListItem entries).

• Service · Product

  One node, two types

  The single offer — pixel-faithful rebuild + maintenance — with Brand and a $997 Offer pointing at /pricing.

Page-specific types

• FAQPage (Question / Answer)

  /faq · home · /why-it-matters · /geo-agency · /ai-visibility-standard · blog posts

  Real questions we actually get, answered in full on the page. Note: Google retired FAQ rich results in 2026 — we keep this markup because it makes the answers machine-readable, not because it earns a rich result.

• Article (with ImageObject)

  /blog/ai-visibility-websites · /blog/aeo-geo-llmeo-explained · /blog/get-cited-by-chatgpt

  Standard article markup on long-form posts: headline, dates, author, publisher, image.

• TechArticle

  /ai-visibility-standard

  The AI Visibility Standard documented as a technical article.

• ItemList

  /blog

  The blog index as an ordered list of posts.

• Review · Rating · LocalBusiness

  /case-studies/[slug]

  Each case study marks up the customer's business and the documented outcome. Facts in the markup match the facts on the page.

• Product (with QuantitativeValue)

  /founder-beta

  The founder-beta offer with its limited-quantity counter.

• Organization · ProfessionalService

  /ai

  The AI manifest re-states the canonical org facts for agents and answer engines.

Supporting types (nested inside the above)

Person

Founder (Ricky Parker) and case-study reviewers

Offer

Pricing on the core Service/Product node and page-level offers

Brand

The Website Recycling brand on offer nodes

PostalAddress · Country

US coverage on #org

OpeningHoursSpecification

Availability on #org

ContactPoint

[email protected] on #org

SearchAction

The WebSite node's scanner action

SpeakableSpecification

h1 + first paragraph on WebPage nodes (Speakable is a beta, news-oriented spec — we emit valid markup, we don't sell it as a local-business switch)

ImageObject

Article images on blog posts

ListItem

Entries inside BreadcrumbList and ItemList

QuantitativeValue

Founder-beta quantity counter

Verify it yourself

View the source of any page on this site and read the application/ld+json blocks, or paste a URL into Google's Rich Results Test or the Schema.org validator. The markup and the visible page say the same thing — that's the whole point.