Website as Entity Home Base
Session 4.2 · ~5 min read
Your Website Is Not a Brochure
Most businesses treat their website as a digital brochure. It shows what they do, displays some photos, and provides a contact form. From a human perspective, that might be enough. From Google's perspective, it tells the search engine almost nothing about who you are as an entity.
Your website is the canonical source of truth for your entity. It is the one property you fully control. Every other signal in the MVES (GBP, directories, social profiles) references your website. If your website fails to declare your entity properly, everything built on top of it is weaker.
Your website does not just host content. It declares who you are. If that declaration is incomplete or missing, every other entity signal you build is undermined.
The Entity Declaration Checklist
For your website to function as an entity home base, it needs specific pages with specific information. Not all of this is visible to users in the traditional sense. Some of it is structured data that only search engines read. But all of it must be present.
| Page | Required Information | Entity Signal |
|---|---|---|
| Homepage | Organization schema (JSON-LD), clear business description, logo | Primary entity declaration |
| About Page | Founding year, founder names, company history, industry, mission | Entity attributes and context |
| Contact Page | Full address, phone, email, map embed, business hours | NAP confirmation |
| Service/Product Pages | What you offer, who it serves, with appropriate schema | Entity scope definition |
| Team/People Pages | Key people with bios, credentials, Person schema | Associated entity relationships |
The About Page: Entity Identity Card
Your About page is the most important page for entity declaration after the homepage. It provides the narrative context that structured data alone cannot convey. Google's natural language processing reads your About page to extract entity attributes: what kind of business you are, when you started, who runs it, and what makes you distinct.
A complete About page includes:
- Legal name and any trade names or abbreviations
- Founding date and brief founding story
- Founder and key people by name, with titles
- Industry and niche stated explicitly
- Physical location(s) with full addresses
- Service area if applicable
- Achievements, certifications, or notable clients
Notice that this is factual information, not marketing copy. "We are passionate about delivering excellence" tells Google nothing. "Founded in 2015 in Jakarta, PT Arsindo Perkasa manufactures and distributes industrial pumps across Indonesia" tells Google five entity attributes in one sentence.
Understanding"] AP["About Page"] -->|NLP Extraction| G CP["Contact Page"] -->|NAP Confirmation| G SP["Service Pages"] -->|Scope Definition| G TP["Team Pages"] -->|Person Entities| G G --> KG["Knowledge Graph
Candidate"]
The Contact Page: NAP Anchor
Your Contact page anchors your NAP (Name, Address, Phone) on your own domain. This is the reference point against which Google checks every other mention of your business across the web. If your Contact page shows a different address format than your GBP, that is an inconsistency that weakens reconciliation.
The Contact page should display:
- Full business name (matching your master NAP exactly)
- Complete street address with postal code
- Phone number with country code
- Email address
- Business hours
- Embedded Google Map (this creates a direct link between your site and your GBP listing)
Structured Data on Every Page
Structured data is covered in depth in Module 5. For the MVES, the minimum is Organization schema on your homepage. This is a JSON-LD block in your page's HTML that tells Google: "This website belongs to this organization, with these properties."
The bare minimum Organization schema includes: name, url, logo, description, foundingDate, address, telephone, and sameAs (linking to your social profiles). Session 5.3 covers the full property list. For now, understand that this structured data block is what transforms your website from "a collection of pages" to "the home base of a recognized entity."
A website without Organization schema is like a building without a nameplate. People inside know who they are. Nobody walking past can tell.
Common Failures
The three most common website-as-entity-home-base failures:
| Failure | Consequence | Fix |
|---|---|---|
| No About page (or one-paragraph placeholder) | Google cannot extract entity attributes | Write a factual, detailed About page with all entity information |
| No structured data at all | Google must guess your entity type and properties | Add Organization JSON-LD to homepage |
| NAP on Contact page does not match GBP or directories | Entity reconciliation fails | Standardize NAP from a master document (Session 4.5) |
Further Reading
- Organization Structured Data - Google's official guide to implementing Organization schema on your homepage.
- Organization - Schema.org Type - The full list of Organization properties available in schema.org.
- Local Business Structured Data - Google's guide for businesses with physical locations.
- Organization Schema: A Complete Guide - Aubrey Yung's practical implementation walkthrough with examples.
Assignment
Review your website against the entity declaration checklist above.
- Open your About page. Does it contain: founding year, founder name(s), company description (what you do, for whom), physical address, industry/niche, and a brief history? List everything that is missing.
- Open your Contact page. Is the NAP displayed in full? Does the format match what you would want to use everywhere else?
- View your homepage source code (right-click, View Page Source). Search for
application/ld+json. If you find nothing, your site has zero structured entity data. - Write down the complete entity information your website should contain. You will need this for the structured data implementation in Module 5.