AI search

What Are Author and Organization Entities?

Author and organization entities are the named person and the named business a page declares as responsible for it. Google's generative search filing reads trustworthiness from author, domain, and inbound links. A byline, an author page, an identity block, and matching structured data make those inputs resolvable.

Author and organization entities, illustrated
Four layers stacked above a fifth: author entity, organization entity, inbound links, and structured data feeding trustworthiness, which is highlighted
Author, domain, and inbound links are the three inputs the filing names. Structured data restates the first two in machine-readable form.

Which trust inputs does Google's generative search filing name?

Google's generative search filing names three sources of trustworthiness for a document: its author, its domain, and its inbound links.

The filing is US 2024/0289407, still pending. Trustworthiness sits among its query-independent measures, next to selection rate across queries, overall popularity, and freshness. The measure helps select the handful of documents a summary is built from. The filing also weighs verifying documents by trustworthiness when it rates confidence in a summary sentence.

The filing does not say how author or domain trust is computed. The page-side reading is plain: a page names its author, the author resolves to a profile, and the domain resolves to an organization. Anonymous pages have one fewer trust input. The agency builds to that reading and does not sell it as a ranking factor.

Source trust appears in the older query augmentation patent too. The patent scored synthetic queries higher when they came from sources with configuration control, such as established companies, directories, and government repositories. Blogs and community pages scored lower. The patent has lapsed, so the point is design logic, not a guarantee.

What does Google's helpful content guidance say about who, how, and why?

Google's helpful content guidance asks three questions of every page: who created it, how it was created, and why it exists.

Who asks if authorship is self-evident to visitors. Google points to bylines and background information about the author. How asks for background on the process, including how automation or AI generation was used. A product review answers how with the number of products tested, the results, and the test method.

Why is the question Google calls perhaps the most important. Content exists primarily to help people, not to attract search visits. Google adds that E-E-A-T itself is not a specific ranking factor. Its systems use a mix of signals to identify content that shows those qualities, and trust counts most.

Google's rater guidelines ask raters to find who is responsible for a website and who created the content on a page. Rater scores evaluate search results; they do not rank pages directly. The reviews system in Google's ranking guide rewards reviews with expert or enthusiast authorship. Topics that affect health, finances, or safety get more weight on strong E-E-A-T.

What does an author entity need on the page and on the author page?

An author entity needs a linked byline on the page and an author page that states who the person is.

The byline names the person the same way on every page. The link goes to one author page per person, never to a search results page or a social profile. The author page states the name, the role, the credentials, and the specialism. The author page also lists the pages the person wrote or reviewed. A pen name with no profile gives a system nothing to resolve.

The byline sits outside the primary content in DOM order. A byline, a date stamp, or a share bar between the H1 and the first body block lands inside the centerpiece Google extracts. The name then reads as part of the page's opening passage. Centerpiece annotation covers that failure in detail.

Digital Vikingz follows the pattern on its own site. Every article closes with a band naming Usman Ishaq as writer, with his role, his certification, and a review date. The band links to his profile on the team page. The name and the profile link match the Person entry in the page's structured data.

What belongs in an organization identity block?

An organization identity block holds the business name, address, contact details, and category as visible text, reachable in one click from every page.

The block uses one canonical business name. Brand and organization names are strings the lapsed augmentation patent did not transform, so a second spelling is a second string. The address, phone, and category match the site's directory listings token for token. Local businesses carry the same block on the homepage and on each location page.

The block lives in a stable place: the footer, the contact page, or the team page. Every page reaches it in one click. The site name Google shows in results is a separate, documented feature, set with WebSite structured data. The site name, the identity block, and the Organization markup use one string.

The block states facts, not claims. Awards, client logos, and review stars belong elsewhere on the page. A block crowded with badges reads as promotion, and the name and address lose their place as its subject. Each line holds one attribute of the organization: name, address, phone, email, or category.

How do Person and Organization structured data connect a site to its entities?

Person and Organization structured data restate the visible identity in schema.org types, and sameAs links each entity to pages that describe it.

Person markup carries name, url, jobTitle, and worksFor, which points to the Organization. Organization markup carries name, url, logo, address, and contactPoint. Each article's author property points to the Person, and its publisher property points to the Organization. The graph in the markup then matches the graph in the visible text.

Schema.org defines sameAs as the URL of a reference page that identifies the item. A name alone is ambiguous, because many people share a name. The sameAs links connect the name to pages that already describe one specific person or business. Each link narrows the name to one entity.

Markup restates; it does not create. A page with Person markup and no visible byline declares an author the reader never sees. The agency rule is that every property in the markup appears in the visible text of the page or the linked profile. Mismatched names across markup, byline, and listings split one entity into several strings.

Questions about author and organization entities

Does every page need a named author, including service pages?
Yes, under the agency's build rule. Service and product pages name the organization as publisher and a person as author or reviewer. A service page makes commercial claims. A named person behind it answers the who question for buyers and for systems alike.
Can a company publish under its organization name instead of a person?
Schema.org accepts an Organization as an author, and an organization byline answers the who question. A named person adds a second entity with credentials of its own. The agency uses the organization as publisher and a person as author.
Does disclosing AI assistance hurt a page?
Google's guidance lists disclosure of automation or AI use under the how question, as background that helps readers. The guidance frames the purpose of the content as the deciding question, not the tool used. The agency discloses AI assistance where a reader expects to know it.
Which credentials belong on an author page?
Credentials relevant to the topics the person writes about, each with its issuer. A certification names the issuing body, and a licence names the regulator and the licence type. Unverifiable titles such as growth hacker add words, not identity.
Should guest authors get author pages?
Yes. A guest byline without a profile is a name with no entity behind it. The guest author page states the person's own role and organization, and links to their own site through sameAs.
What happens to an author page when the author leaves?
The page stays live, with the role marked as former. Removing it breaks every byline link and orphans the pages the person wrote. Pages that change after the departure carry a current reviewer's name.
Is a Google Business Profile part of the organization identity?
Yes, for a business with a location. The profile's name, address, and category match the site's identity block token for token. The lapsed augmentation patent generated synthetic queries from those same listing fields.
What is a reviewed-by line, and when does a page carry one?
A reviewed-by line names a second person who checked the page, with that person's credential. Pages on health, finance, and legal topics carry one when the writer is not the licensed expert. The reviewer gets an author page and a Person entry in the markup, the same as the writer.
Which profiles belong in sameAs?
Profiles the entity controls and reference entries that describe it. Typical targets are a company registry entry, an industry association listing, a LinkedIn page, and a Wikidata item where one exists. Every target describes the same entity under the same name. A profile for a different person with the same name defeats the purpose.
Does an author's reputation off the site matter?
Google's rater guidelines tell raters to research the reputation of the website and the content creator in independent sources. Raters do not rank pages, but their guidelines show what Google counts as reputation. Mentions of the author on independent pages in the same field are the off-site half of the author entity.
How does a company with several brands mark up its organizations?
Each brand gets its own Organization entity with its own identity block. The schema.org properties parentOrganization and subOrganization connect the brands to the holding company. One shared block for unrelated brands merges entities the site means to keep separate.
Do author pages need their own structured data?
Yes. The author page carries a Person entity with the same name, role, and sameAs links as every byline that points to it. The schema.org type ProfilePage marks the page itself as a profile. Article markup elsewhere references that Person by its URL.
Usman Ishaq, founder and CEO of Digital Vikingz
Written by Usman IshaqFounder and CEO, Digital Vikingz. Koray Tuğberk Gübür Semantic SEO Fundamentals certified. Mechanical engineering background.Reviewed September 2026. Profile
Book a callWhatsApp