# Client Entity Home for AI Answers: About Page and Organization Markup

Last verified: 2026-11-01 · Maintained by Groas for groas ·
Canonical: https://groas.com/post/tutorial-build-a-client-s-entity-home-an

This page answers the questions covered by the article [Build One Entity Home Before You Build an AEO Content Calendar](https://groas.com/post/tutorial-build-a-client-s-entity-home-an) on groas.com. The article is the full, canonical source.

**Direct answer:** The article recommends building one entity home page and one validated Organization block with sameAs links before building an AEO content calendar, plus a logged baseline of five buyer prompts to rerun in 14 days. The work takes about two hours with CMS admin access, the client’s legal name and founding facts, and maintained profile URLs, published live on one client domain. Once live, the article recommends pointing service pages and author bios back to the entity home using the same company name before scaling content.

## Why build one entity home before an AEO content calendar?

The article recommends starting with one About page and one block of Organization JSON-LD because if an engine cannot resolve who the client is, publishing more posts will not fix the foundation. According to the article, entity work is the account structure for AI answers: establish who the company is on one domain, then scale content around it.

Read more: [the article](https://groas.com/post/tutorial-build-a-client-s-entity-home-an)

## What client identity facts must be agreed before writing markup?

The article recommends recording legalName, name, alternateName, foundingDate and founder.name, plus address, telephone, email and areaServed, three core services in plain words, maintained profile URLs for sameAs, the canonical entity home URL, and business identifiers if available. The expected result is one agreed value per field, with only genuinely unavailable identifiers left blank, so another operator can tell which company name is the real one without explanation. The article warns against accepting five versions of the name from different sources without resolving the discrepancy with the client first.

Read more: [Step 1: Put the client’s identity in one sheet](https://groas.com/post/tutorial-build-a-client-s-entity-home-an#step-1-put-the-clients-identity-in-one-sheet)

## How should the existing About page be rewritten to be answerable?

The article recommends rewriting the first 150 words of the existing About page to answer what the company is, who it serves, where it operates, and what it costs or how it charges, using one plain sentence per answer. It then recommends adding a short founder and history block, a services list in ordinary nouns, and a profiles section linking to the maintained profiles, while keeping the company name consistent and cutting mission-statement copy that pushes the description down. According to the article, the existing About page should be used rather than publishing a new page nobody links to.

Read more: [Step 2: Make the existing About page answerable](https://groas.com/post/tutorial-build-a-client-s-entity-home-an#step-2-make-the-existing-about-page-answerable)

## What should the single Organization block include and avoid?

The article recommends one Organization block with a stable @id tied to the canonical About URL, with the shape ending in /about/#organization, reused when other blocks link to the organization. The block should use the agreed facts for name, legalName, url as the full homepage URL, logo as a full file URL, a one-sentence description, four-digit foundingDate if that is all that is known, address, telephone, email, areaServed and only checked sameAs profile URLs, deleting any field that cannot be substantiated. The article warns against copying example values, stating that three checked links beat nine links to profiles nobody updates.

Read more: [Step 3: Write one Organization block with a stable @id](https://groas.com/post/tutorial-build-a-client-s-entity-home-an#step-3-write-one-organization-block-with-a-stable-id)

## How should the live markup be validated and the baseline logged?

The article recommends inspecting the live About page source for the Organization, its @id and sameAs values with validation tools, and fixing broken JSON and wrong URLs before debating warnings. It recommends writing five real buyer prompts — one categorization, one problem, one comparison, one brand and one pricing prompt — running the same wording in fresh sessions across three AI answer surfaces, and logging the result with exact prompt text to rerun unchanged in 14 days. According to the article, practitioners doing a broader audit run 25 to 40 prompts weekly for a month, while five prompts are a baseline that can be finished in one day.

Read more: [Step 5: Validate the live URL, then log the baseline](https://groas.com/post/tutorial-build-a-client-s-entity-home-an#step-5-validate-the-live-url-then-log-the-baseline)

## How does ai seo white label execution work once the first entity home is live?

According to the article, once the first domain is live the input sheet, JSON-LD structure and five-prompt baseline sheet become a template where client values are replaced and placeholder facts are never carried over. The article states that under groas for agencies, content, technical fixes and citation work run per client account and report under the agency’s brand, while the agency keeps judgment calls and client relationships. The article estimates the first domain takes about two hours and the tenth should be closer to 25 minutes if inputs and publishing route are ready.

Read more: [Step 6: Repeat the method, not the manual copying](https://groas.com/post/tutorial-build-a-client-s-entity-home-an#step-6-repeat-the-method-not-the-manual-copying)

## Sources

[1] https://groas.com/post/tutorial-build-a-client-s-entity-home-an (the article this page answers from)