Skip to content
Capra Digitals

Losing visibility to AI search

Nothing on your site is machine-readable

Schema is unglamorous and frequently oversold. It will not rescue thin content. What it does is remove guesswork: instead of inferring that a page describes a service offered by a specific organisation, a machine is told.

Short answer

Which schema markup do we actually need, and does it help with AI search?

At minimum: Organization on the site, WebPage or Article on content pages, Service on service pages, FAQPage where you genuinely answer questions, BreadcrumbList for hierarchy, and Product or Offer if you sell online. Schema is not a ranking factor and it will not make weak content rank, but it removes ambiguity — it states what the page is, who published it and how entities relate, which supports rich results in search and gives AI systems a corroborating signal alongside the text. Implement it as JSON-LD rendered in the server HTML, keep it consistent with what the page visibly says, and validate it.

01

How this shows up

If four or more of these are true, this is your problem.

  • No structured data at all, or only what a theme injected years ago
  • Rich results appearing for competitors but not for you
  • Schema present but invalid, or contradicting the visible page
  • FAQ markup on pages with no real questions on them
  • Structured data injected by JavaScript after page load
  • No consistent Organization identity across the site

02

Why it happens

  • Nobody owns it

    Schema falls between marketing and engineering, so it either never gets implemented or gets implemented once and never maintained.

  • Plugin defaults

    Generic plugin output often marks up the wrong type or contradicts the page. Invalid markup is worse than none.

  • Client-side rendering

    Structured data injected after load may not be seen by every crawler. It belongs in the server-rendered HTML.

  • Markup that oversells

    FAQ schema on a page without visible questions, or review markup without real reviews, risks manual action and provides no benefit.

03

What it costs you

Weeks

1–2

Full schema implementation

Core types

6

Cover most B2B sites

Server-rendered

100%

How we implement it

Fabricated markup

0

Only what the page says

Schema is a small, cheap, durable improvement. It is not the thing that makes you visible in AI answers — structure and specificity do that — but it is the easiest supporting signal to get right and the one most often left undone.

04

How we fix it

  1. 01

    Audit what exists

    Validate current markup, find contradictions with page content, and identify the types missing per page template.

  2. 02

    Define a per-template schema plan

    One decision per page type — service, article, case study, tool, contact — so implementation is consistent rather than page-by-page improvisation.

  3. 03

    Implement as server-rendered JSON-LD

    Markup present in the initial HTML, with a consistent Organization identity referenced across the site.

  4. 04

    Keep it truthful

    FAQ markup only where questions are visible on the page, ratings only where real reviews exist. Everything asserted must be verifiable on the page itself.

  5. 05

    Validate and monitor

    Validation at build plus periodic checks in Search Console, so a template change does not silently break coverage.

05

What changes afterwards

  • Every page template carrying correct, validated structured data
  • A consistent organisation identity machines can resolve
  • Eligibility for rich results where they exist for your page types
  • A corroborating signal supporting the extractable content work

Questions

People ask us this

Is schema markup a ranking factor?

Not directly. It makes pages eligible for rich results and gives machines an unambiguous statement of what the page is, which supports discovery and citation. It does not compensate for weak content.

Does schema help AI assistants cite us?

It is a supporting signal rather than the deciding one. Extractable content and entity corroboration matter more, but schema confirms publisher and page type, and it costs very little to get right.

Can we add FAQ schema to every page?

No. FAQ markup should only appear where the questions and answers are genuinely visible on the page. Marking up questions that are not there risks a manual action and gains nothing.

Losing visibility to AI search

Related challenges

Next step

Tell us what is actually going wrong

Thirty minutes, no pitch deck. We will tell you whether this is a quick fix, a project, or something you can do yourself.