yucod

Make AI search know exactly who you are and what you sell

ChatGPT, Gemini and Perplexity build answers from facts machines can read. We describe your business in schema.org (the standard markup for web pages), add a Wikidata entry (an open fact database) and connect it all into a knowledge graph. The goal is fewer mix-ups with other companies and more accurate mentions of yours.

Quote and schedule after your brief

Who it's for

  • Companies whose name AI confuses with another brand or gets wrong
  • Service sites and online stores that want to appear in AI answers
  • Consultants and clinics where name, specialty and reviews matter
  • Brands with several sites, regions or language versions

Problems we solve

I ask AI about my company and it invents or mixes up facts

We define your company as an entity (a distinct object with a name, address, founders and profiles). We add Organization markup and sameAs links that tie your public profiles to that one object.

My site lists products and services, but AI doesn't pick up prices or specs

We add Product, Service, Offer, FAQ and Review markup only where it matches visible page content. We check it in Google's Rich Results Test and the schema.org validator.

There's no Wikipedia page for us, so it seems hopeless

Wikipedia isn't required. If independent sources exist, we prepare a Wikidata entry following its rules. If sources are thin, we say so and list what to earn first.

A plugin added markup years ago and now it's duplicated and contradictory

We audit what's there, remove duplicates and conflicts, and leave one clean graph that survives theme and plugin updates.

What's included

  • Audit of current markup and brand mentions
  • Entity map: company, people, services, products, locations
  • Organization, WebSite and LocalBusiness markup where relevant
  • Service, Product, Offer, Article, FAQ and BreadcrumbList markup
  • Stable @id identifiers so pages point to the same entity
  • SameAs block: social profiles, Google Business Profile, registries, directories
  • Wikidata entry preparation and submission, if notability is supported
  • Validation in Rich Results Test and Schema Markup Validator
  • Short guide so your team doesn't break the markup on updates
  • Before/after test: we ask AI assistants about your brand

Choose the scope

Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.

01

Core markup

A small site that needs its structured data fixed

  • Audit of existing markup
  • Organization and WebSite
  • Markup for up to 10 pages
  • Validator checks
Discuss this scope
02

Entities & sameAs

A company AI confuses or barely mentions

  • Entity map
  • Markup for up to 40 pages
  • Stable @id and sameAs block
  • Duplicate and conflict cleanup
  • Before/after AI test
Discuss this scope
03

Knowledge graph & Wikidata

A brand with several sites, locations or languages

  • Everything in Entities & sameAs
  • Wikidata entry if sources exist
  • Product or service catalog markup
  • Multilingual links between pages
  • Team guide
Discuss this scope

How we work

01

Brief and requirements

You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.

02

Entity map

We list the objects and relations that describe your business. You confirm the facts: names, addresses, owners, profiles.

03

Implementation

We write the markup in JSON-LD (a code block in the page head) and deploy it through templates, not page by page.

04

Wikidata and external profiles

We prepare the Wikidata entry and align names and descriptions on your profiles so they match your site.

05

Testing and handover

We test in validators and in AI assistants, then hand over documentation. Access and files are already yours.

Scope and limits

  • We don't promise AI will name you in answers: markup helps, but the model decides
  • We can't guarantee a Wikidata entry: it can be rejected without independent sources
  • We won't mark up data that isn't on the page: it breaks Google's guidelines and can hurt you

FAQ

How is this different from regular SEO?

SEO works on how pages rank. This describes who you are and what you offer in a form machines understand. It helps classic search and AI answers. You still need SEO for traffic.

Can't I just install a schema plugin?

For simple sites a plugin gives a base. It often creates duplicates and doesn't know how your entities relate. We check the output and complete it by hand where needed.

Do I need a Wikipedia article?

No. Wikidata is easier but has its own requirements: independent sources that confirm the entity exists. We assess your chances before starting and tell you plainly if they're low.

When will I see results?

Validators show changes immediately. Search engines recrawl in days or weeks. AI models update their knowledge unevenly, so we can't name a date. We record answers before and after.

What do you need from me?

Accurate company data: legal and trading names, addresses, contacts and profile links. We also need access to the site or your developer. All files and access stay with you.

Does it work on any platform?

Yes. JSON-LD works on WordPress, Shopify, Webflow and custom code. Only the way it's inserted differs. Some closed site builders limit certain fields, and we flag that in the audit.

Start with your task

Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.

Start a project brief