← Back to Blog

Building Your E-E-A-T Profile Network: Google, Wikidata, LinkedIn & More (Part 2 of 5)

Building Your E-E-A-T Profile Network: Google, Wikidata, LinkedIn & More (Part 2 of 5)

This is Part 2 of the E-E-A-T Authority series. In Part 1, I covered what E-E-A-T is and why consistency across platforms is the foundation. Now we build the actual profiles.

The goal of this article is specific: by the end, you will have profiles on seven platforms that Google uses to verify entities. Each profile references the others, creating a closed loop of identity verification that Google's Knowledge Graph can follow.

I built these profiles for the J.A. Watte author entity and the Trap Series book brand. Within six weeks of completing this process, two of our entities appeared in Google's Knowledge Graph with Wikidata QIDs: J.A. Watte (Q139329710) and The Trap Series (Q139329783).

Platform 1: Wikidata — The Knowledge Graph Source

Wikidata is the structured data backbone of Google's Knowledge Graph. It is free, open, and anyone can create entries — but most brands never do.

How to Create a Wikidata Entry

  1. Create an account at wikidata.org/wiki/Special:CreateAccount
  2. Go to wikidata.org/wiki/Special:NewItem
  3. Fill in the Label (your brand name), Description (one sentence), and Aliases

For a person entity, I used:

  • Label: J.A. Watte
  • Description: American author and entrepreneur
  • Aliases: JA Watte, Joshua Watte

Then add statements — these are structured properties:

Property Value Why It Matters
instance of (P31) human (Q5) Tells Google this is a person
occupation (P106) writer (Q36180) Categorizes the entity
country of citizenship (P27) United States (Q30) Geographic signal
official website (P856) https://jwatte.com Links to your site
notable work (P800) The Trap Series References your products

For a book series, I created a separate item:

  • Label: The Trap Series
  • Description: Personal finance and business book series by J.A. Watte
  • Statements: instance of → book series, author → J.A. Watte (linked to the person item)

I then created individual items for each book: The $97 Launch (Q139329727), The $20 Dollar Agency (Q139329733), The Resale Trap (Q139329731), and The $100 Network (Q139329736).

The Wikidata Propagation Timeline

Wikidata changes do not appear in Google immediately. In my experience:

  • 2-4 weeks: Google crawls the Wikidata entry
  • 4-8 weeks: Entity associations begin appearing in Knowledge Graph
  • 8-12 weeks: Knowledge Panel may appear (if sufficient convergent signals exist)

Create the entries now. The clock starts ticking when you save.

Platform 2: Google Business Profile

Even if you are an online-only business, a Google Business Profile (GBP) is one of the strongest entity signals you can send.

  1. Go to business.google.com
  2. Click "Add your business"
  3. Enter your business name exactly as it appears everywhere else
  4. Choose a category — for authors, use "Author" or "Publisher." For a product brand, use the most specific category available
  5. If you have no physical location, select "I deliver goods and services to my customers"
  6. Add your website, phone number, and description
  7. Complete verification (Google may offer email, phone, or postcard verification)

After verification, fill out every field. Upload a profile photo. Add your products or services. Post at least one update. Respond to any reviews. Google rewards complete profiles.

Platform 3: LinkedIn

LinkedIn serves two roles: it is a sameAs signal in your schema markup, and it is a platform Google actively crawls for entity information.

Personal Profile

  • Update your headline to match your exact title across all platforms
  • Under Experience, list your current role with your brand
  • Add your website in the Contact Info section
  • Under Publications, list each book or product with its URL

Company Page (Optional but Valuable)

  • Create a company page for your brand or publishing entity
  • Use the same logo, name, and description as everywhere else
  • Link to your website
  • Post updates linking to your blog content

Platform 4: Amazon Author Central

For authors, Amazon Author Central is the most impactful profile after Wikidata.

  1. Go to author.amazon.com
  2. Sign in with your Amazon account
  3. Claim your author page by searching for your books
  4. Add a biography, author photo, and blog RSS feed
  5. Link to your website and social profiles

Amazon Author Central feeds directly into Amazon's search algorithm and also provides data that Google uses for book-related Knowledge Panels.

Platform 5: Crunchbase

Crunchbase has a documented data partnership with Google. Creating a free profile takes 10 minutes.

  1. Go to crunchbase.com
  2. Click "Add Organization" or search for your entity first
  3. Fill in: organization name, description, website, founding date, headquarters, categories
  4. Add key people (link to your personal profile)
  5. Add social links

The free tier is sufficient. The goal is entity presence, not paying for analytics.

Platform 6: ORCID

ORCID is a researcher identifier used globally in academic publishing. Even if you are not an academic, having an ORCID signals that you take your intellectual output seriously.

  1. Register at orcid.org/register
  2. Set visibility to Public
  3. Add your employment/affiliation
  4. Add your publications or works
  5. Add your website URLs

I registered and received ORCID 0009-0004-9811-6147. This ORCID now appears in the sameAs property of every Person schema across all of our sites.

Platform 7: Google Scholar

If you have any published works that cite data sources — books, research papers, white papers — creating a Google Scholar profile adds another convergent signal.

  1. Go to scholar.google.com
  2. Click the profile icon and "Create my profile"
  3. Add your publications
  4. Add your institutional affiliation and website

Connecting the Profiles

Here is the critical step most people miss: each profile must reference the others.

  • Your Wikidata entry should list your official website
  • Your website's schema markup should list all profiles in sameAs
  • Your LinkedIn should link to your website
  • Your Amazon Author Central should link to your website
  • Your Crunchbase should link to your website and social profiles

This creates a closed loop. Google follows the links from your site to Wikidata, from Wikidata to your site, from LinkedIn to your site, from your site to LinkedIn. Each confirmation strengthens the entity signal.

The sameAs Array

In your website's JSON-LD schema, the sameAs property tells Google "this entity is the same as the entity at these URLs." Here is what mine looks like:

{
  "@type": "Person",
  "name": "J.A. Watte",
  "sameAs": [
    "https://www.amazon.com/author/jawatte",
    "https://www.wikidata.org/wiki/Q139329710",
    "https://orcid.org/0009-0004-9811-6147",
    "https://www.linkedin.com/in/jawatte"
  ]
}

The rel="me" Links

In your HTML <head>, add rel="me" links to each profile:

<link rel="me" href="https://www.amazon.com/author/jawatte">
<link rel="me" href="https://www.wikidata.org/wiki/Q139329710">

These tell search engines: "I am verifying that this is my profile on that platform."

Consistency Audit

After creating all profiles, audit them. Open each one and verify:

  • [ ] Name matches exactly across all platforms
  • [ ] Website URL matches exactly (including https:// and trailing slash)
  • [ ] Description is consistent (does not need to be identical, but should not contradict)
  • [ ] Logo or profile photo is the same
  • [ ] Location matches
  • [ ] Each profile links back to your website

Any inconsistency weakens the signal. Fix it before moving on.

Next: Schema Markup and Structured Data

In Part 3, I will show the exact JSON-LD schema markup I use across all sites to make these entity relationships machine-readable. Person schema, Organization schema, Book schema, BookSeries schema, and how they reference each other through @id nodes.

← Back to Blog

Accessibility Options

Text Size
High Contrast
Reduce Motion
Reading Guide
Link Highlighting
Accessibility Statement

J.A. Watte is committed to ensuring digital accessibility for people with disabilities. This site conforms to WCAG 2.1 and 2.2 Level AA guidelines.

Measures Taken

  • Semantic HTML with proper heading hierarchy
  • ARIA labels and roles for interactive components
  • Color contrast ratios meeting WCAG AA (4.5:1)
  • Full keyboard navigation support
  • Skip navigation link
  • Visible focus indicators (3:1 contrast)
  • 44px minimum touch/click targets
  • Dark/light theme with system preference detection
  • Responsive design for all devices
  • Reduced motion support (CSS + toggle)
  • Text size customization (14px–20px)
  • Print stylesheet

Feedback

Contact: jwatte.com/contact

Full Accessibility StatementPrivacy Policy

Last updated: April 2026