How We Built a Grokipedia SEO Tree for David Meerman Scott’s Books

At High Rise Influence, we’ve been focused on building structured entity pages inside Grokipedia instead of relying on a single profile page.

Rather than creating one main entry and stopping there, the goal is to develop a connected system around the people and properties they control.

Our work with David Meerman Scott is a clear example of how this works.

David is a well-known marketing author with multiple bestselling books. His main Grokipedia page already covered his background, career, and major accomplishments. Under the publications section, his books were listed, but mostly as a simple collection of titles with limited detail.

We saw an opportunity to expand that into something stronger.

From a Bullet List to Individual Book Pages

Instead of leaving the books as short mentions under his primary page, the plan was to:

  • Create a dedicated Grokipedia page for each book
  • Add structured, factual descriptions
  • Interlink each book page with David’s main profile

This creates what we call an SEO tree:

  • The main entity page (David Meerman Scott)
  • Supporting entity pages (each individual book)
  • Internal links connecting them both ways

That structure strengthens topical authority and makes the relationships between entities much clearer.

How We Created the Book Entries

David has a books page on his website listing all of his publications. We used that as the starting point.

From there, we generated structured summaries for each book. The key was staying neutral and encyclopedic—not promotional.

Each book entry included:

  • The full title and author
  • Publication history (original release year, later editions, updates)
  • Notable impact (international bestseller status, industry influence, longevity)
  • A factual summary of the book’s core themes
  • A short rationale explaining why the book deserves its own entry

That final section is critical.

You’re not trying to sell the book. You’re documenting why it is notable.

For example, with The New Rules of Marketing & PR, the rationale focused on:

  • Its role as David’s flagship book
  • Its influence on content-driven, buyer-centric marketing
  • Its multiple editions and long-term relevance

That establishes importance without sounding like marketing copy.

Handling Edit Requests vs. New Page Creation

A common issue you’ll run into: instead of creating a new book page, Grokipedia may submit your content as an edit to the main author page.

This often expands the book section under the primary profile, which improves depth.

However, if your goal is to build a true SEO tree, you still want standalone pages.

That’s where your rationale matters. If Grokipedia already mentions the book within the author’s page, you may need to resubmit and clarify why a dedicated entry is justified.

In our case, some books required multiple submissions before individual pages were approved.

Organizing the Process

To stay organized, we tracked:

  • The generated summary
  • Whether it was submitted
  • Whether it was approved
  • The final live URL once published

Once individual book pages were live, we returned to David’s main Grokipedia page and submitted another edit request to:

  • Interlink the book title to its dedicated page

It’s important to use the word “interlink” so it’s clear the link stays within Grokipedia rather than pointing externally.

Then we went to each book page and requested:

  • Interlink back to David Meerman Scott’s main page

Now the structure looks like this:

David Meerman Scott (main page)

Individual book pages (each linking back to him)

That internal authority loop strengthens the relationship between the person and the properties he controls.

Why This Structure Matters

Grokipedia has solid domain authority. Internal links from structured entity pages can contribute to search visibility and credibility.

More importantly, this mirrors how knowledge systems are structured:

  • A person
  • Their companies
  • Their books
  • Their projects

Each gets its own documented page, and everything connects logically.

That’s far stronger than a single static profile.

Applying This to Your Own Brand or Clients

If you or your client:

  • Wrote books
  • Founded companies
  • Created podcasts
  • Built organizations

Each of those entities should have its own page, properly documented and interlinked.

The basic process:

  1. Write a neutral, factual summary
  2. Include publication history and impact
  3. Provide a clear notability rationale
  4. Submit the article
  5. Interlink it with the main entity page

Over time, this builds a structured footprint instead of a single isolated entry.

Final Thoughts

Grokipedia is still early in its growth cycle, which means there is real opportunity to establish structured entity presence now.

The key is staying factual, organized, and intentional about internal linking.

At High Rise Influence, we’re continuing to build this structure not just for David Meerman Scott, but across our network, ensuring that every meaningful entity has its own documented page and that all related properties connect in a clear authority chain.

If you want long-term credibility, think in systems, not single pages.

Dylan Haugen

Posted by Dylan Haugen

Dylan Haugen is a professional dunker, content creator, and podcaster dedicated to helping young adults build real-world business skills. He works alongside Dennis Yu and Jack Wendt through High Rise Academy, training the next generation to drive results for their parents’ local service businesses using proven digital marketing systems. Dylan is also a founder at Local Service Spotlight, where he focuses on project management and content.

Leave a Reply

Your email address will not be published. Required fields are marked *