---
title: "Entity SEO audit | SEO Skill"
description: "Check whether schema, authorship and brand details clearly connect the people, organisation and content across your site and find conflicting signals."
canonical: "https://seoskill.dev/docs/reports/entity-readiness"
language: "en"
---

# Entity SEO audit

Review the names, authors, dates, schema and sameAs links found across the crawl. The audit can spot missing or conflicting evidence, but it cannot prove that a search engine recognised an entity.

## Install and run the audit

Install the CLI once, then run `seo start` to connect your site and Google data. After setup you can run this audit yourself or ask your agent to run it.

Install the SEO CLI globally.

```
npm i -g seo
```

Run setup after installation.

```
seo start
```

Review naming, authorship, schema, and sameAs evidence.

```
seo entity-readiness --project example
```

## What you get from this audit

Check whether schema, authorship and brand details clearly connect the people, organisation and content across your site and find conflicting signals.

Best for

An organisation, person, or publisher needs a consistency review.

Needs

Saved or fresh crawl extraction

You get

Check whether schema, authorship and brand details clearly connect the people, organisation and content across your site and find conflicting signals.

Use next

Check AI search technical readiness

Every report follows the same rules for missing data and outside estimates.[See how report data works](https://seoskill.dev/docs/reports#how-report-data-works).

## What you need before you run it

The report uses the information below. Optional sources are only used when you ask for them.

### Saved or fresh crawl extraction

Provides page names, authors, publication dates, social links, and structured-data entities.

### Structured data and sameAs evidence

Provides observed organisation, person, article, profile, and external identity references.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### You need the broader crawl, index, snippet, page-structure, and optional resource checks used for AI search readiness.

Run AI readiness. It adds technical access and page-level readiness evidence beyond the identity and publisher signals reviewed here.

AI search readiness audit

](https://seoskill.dev/docs/reports/ai-readiness)

### You need proof that Google or an AI product has recognised a particular person, organisation, brand, or topic entity.

No automated report in this package can observe a search engine's internal entity understanding. Review visible search results, knowledge features, primary profiles, authoritative references, and structured-data validation. This report can still show which names, authors, schema types, and sameAs links are present or inconsistent.

Needs more evidence

## Use the audit with an agent or in code

The command above is enough for most work. These options let an agent, script or application run the same audit with explicit input and structured output.

### CLI

Use the report catalog when an agent, script or CI job needs predictable JSON instead of the normal terminal output. Check the current input first, then run the audit with the validated parameters.

Check the current input before the agent or script runs the audit.

```
seo reports describe entity-readiness --json
```

Once the input is valid, run the audit through the report catalog.

```
seo reports run entity-readiness --params '{"reportId":"crawl_example_20260710"}' --json
```

### MCP

An MCP agent follows the same two-step flow. It inspects the current schema, fills the required fields and only then runs the audit.

Ask the MCP server for the current audit input.

```
{
  "id": "entity-readiness"
}
```

Run the audit after the agent has checked and filled the input.

```
{
  "id": "entity-readiness",
  "params": {
    "reportId": "crawl_example_20260710"
  }
}
```

### TypeScript

Install the package in a Node 22 project when your application needs to run the audit directly. The result includes the same evidence, warnings and limits returned through the CLI and MCP server.

Add the SEO package to your project.

```
npm install seo
```

Run the audit from your TypeScript application.

```
import { executeReport } from 'seo/mcp'

const result = await executeReport(
  'entity-readiness',
  {
  "reportId": "crawl_example_20260710"
},
)

console.log(result)
```

## What to do next

Correct conflicting names, authors, dates and invalid markup before adding optional fields. Recrawl the affected pages and check that the visible content and structured data now describe the same real entity.

1.  01Correct inconsistent source facts and rerun the crawl.
2.  02Use AI readiness for the broader technical access review.

## Related reports

[

Check whether crawlers can access and use important pages in AI search. Find technical blockers without inventing a visibility or citation score.

AI search readiness audit

](https://seoskill.dev/docs/reports/ai-readiness)[

Audit one URL for technical SEO, metadata, canonicals, schema, links and Search Console queries. See the live evidence before changing the page.

SEO page audit

](https://seoskill.dev/docs/reports/audit-page)[

Check sitemap URL status, redirects and access first. Run the full technical SEO crawl only when you need page content, links, metadata and affected URLs.

Sitemap health check and technical site crawl

](https://seoskill.dev/docs/reports/site-crawl)

## Sources used by this audit

These primary sources define the provider data or search controls used by the result.

-   [Google structured data guidance](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data)