Skip to main content
Skip to main content
Service · Structured data

Schema markup, done properly.One clean entity across every page you own.

The structured data layer of the Cognos program, built properly once and kept correct as the site changes.

  • One connected graph
  • Validated
  • Maintained as you publish
The short answer

Schema markup is a managed service that rebuilds a site's structured data into one connected entity graph instead of scattered, conflicting tags. Perfectus Labs operators design, implement, and validate it so machines can resolve who you are without guessing.

What it is

Schema Markup

The common failure isn't missing schema. It's several disconnected fragments, each declaring the same company slightly differently, so a parser can't tell which one is authoritative.

We rebuild it as one graph. A single organization node with a stable identifier, referenced by every page, with services, articles, authors, breadcrumbs, and FAQs hanging off it correctly.

Then we validate it and wire it into the templates, so new pages inherit it instead of needing a person to remember.

Included in Cognos

Included in your Cognos program.

It's included in every tier, alongside the technical work, schema, content, business profile, and press. They pay off together: press points models at pages the technical work made readable, and schema only helps once there's something worth quoting. What changes between tiers is how much ships each month.

How it runs

Four steps, every month.

01

Audit existing markup

Everything currently emitted, including duplicates and anything asserting something that isn't true.

02

Design the graph

One organization node, stable identifiers, and the relationships between page types.

03

Implement in templates

So the markup is a property of the page type, not something someone pastes in by hand.

04

Validate and monitor

Checked against the validators and included in the continuous scan afterwards.

The difference

How most teams handle this, and how we do.

Markup design

The usual approach

Tags get copied from a template online

Schema Markup

Operators design a graph specific to your business

Consistency

The usual approach

Each page asserts facts slightly differently

Schema Markup

One organization node feeds every page

Implementation

The usual approach

Someone pastes JSON-LD in by hand

Schema Markup

We build it into the templates directly

Validation

The usual approach

Markup ships without being checked

Schema Markup

We validate it before and after launch

Ongoing accuracy

The usual approach

New pages are missed or done inconsistently

Schema Markup

New pages inherit correct markup automatically

What you get

  • A single connected entity graph
  • Service, article, author, FAQ, and breadcrumb markup
  • Template-level implementation
  • Validation and ongoing monitoring

Who it's for

Sites with a real page count, multiple services, or an author-driven blog, where hand-pasted markup has already drifted.

Schema won't rescue a site with nothing worth citing. It's a legibility layer, not a content strategy.

Included in every tier of the Cognos program. Month to month, thirty days notice.

Investment

From $1,500 a month.

  • Tier 1 from $1,500 / month
  • Tier 2 from $2,500 / month
  • Tier 3 from $3,500 / month
  • One-time $1,000 setup, month to month after that
Reporting

A dashboard, updated regularly. A report, every week.

Prompt-level citation movement, everything shipped tied to the branch it targeted, what it changed, and what's next. Including the parts that didn't move and what we're doing differently because of it.

The rest of the system

The rest of the same program.

Each one is included in Cognos, running on the same engine and reporting into the same monthly document.

See everything included in Cognos

Questions

Before you ask us.

Will this get us rich results?

Sometimes, but that's not why we do it. It's about being resolvable as an entity so a model can name you with confidence.

Can our developer implement it?

Yes. We'll hand over the graph design and the exact markup per template if you'd rather your team ship it.

Is the schema work included?

Yes. Schema is built and maintained inside Cognos alongside the content, because legibility only pays off when there's something worth quoting on the page.

Does the markup stay if we stop working together?

When it's implemented in your templates, yes, and that's how we prefer to ship it. If it's served live through the Cognos script, ask for the hand-off before you leave and we'll give your team the graph and the markup per template.

Start with the free audit.

We run your category's questions against the answer engines, scan the technical side, and show you where this work lands inside your Cognos program.