Dennis Yu

This is the public copy of the agent skill. Live agent skill id: personal-brand-people-directory. Companion author skill: wordpress-author-is-the-person.

Agents share this as Local Service Spotlight. BlitzMetrics.com stays. The agent brand is Local Service Spotlight.

Method article: How we build /people/ pages.

Personal brand people directory

Build a /people/ directory on a personal brand WordPress site — one hub, one child page per person, pretty URLs, no tracking junk on the links. Use this when you have photos, honor posts, or existing entity pages and you need a real page on a real name that Google and language models can cite.

What this is

A tagged photo in Drive is not a page. An honor blog post is a story. The directory card is the entity the other pages can point at.

Working example: https://dennisyu.com/people/ (page 36728). Children live at /people/{slug}/. Templates: Zach Peyton and Jack Wendt.

Inputs

  • The personal brand WordPress site you already control.
  • Photo inventory first — Drive people folders, photos of the site owner WITH the person.
  • Honor posts that already exist.
  • People who already have an entity home or an event page (DealCon or equivalent).
  • A yes before touching a client production domain. Working examples can live on the method site first.

Rules

  • One hub. Never a second /people/.
  • Live first on low-traffic personal brand sites.
  • Do not invent a title.
  • A photo of the site owner WITH them is the honor proof. Their stock headshot is not that.
  • If photos fail to download, ship the card anyway.
  • Client production domains need a yes.
  • No query strings on permalinks or hrefs — no utm_, no fbclid, no page_id=.
  • Author is the person. Use wordpress-author-is-the-person. On dennisyu.com that is Dennis, user id 2.
  • If the name is not unique and there is no documented company, leave the stub thin. Do not invent a company.
  • If a page with the slug exists, update it. Do not create a duplicate.
  • Status is publish. Comments closed. Parent of each card is the hub.

Steps

  1. Find or create the one hub at /people/. If it exists, use that id. Never open a second hub on the same site.
  2. Confirm you are on a low-traffic personal brand site, or that you have a yes for production.
  3. Build the inventory in order: photos of the owner with the person, then honor posts, then existing entity homes and event pages.
  4. For each person, create or update a child page at /people/{slug}/. Pretty URL. Author is the site owner. Comments closed.
  5. Write only what you can prove. Do not invent a title, a company, or a bio.
  6. If you have a photo of the owner WITH them, use it. If the download fails, publish the card without the image.
  7. Link out to the honor post, entity home, and event page when those already exist. Keep every href clean — no query strings.
  8. Leave thin stubs thin when the name is not unique and you have no documented company. Examples on this site: Adam Young, David Park, Michael Jensen.
  9. Ship a batch. The working example added 100+ cards in one day. Fill galleries later.
  10. Report the hub URL, the hub id, and the child URLs. Then run the same skill on the next personal brand site in the fleet — after a yes on production domains.

Source groups (how to pick the first cards)

Derek Moneyberg — next working example

  • He has a who’s-who inventory (podcast + graph).
  • Do not publish onto moneyberg.com or derekmoneyberg.com yet. Funnel and placeholder. Needs a yes.
  • Working example path: https://dennisyu.com/derek/people/
  • Same /name pattern, portable to his domain later.
  • Cards come from documented conversations first, then the podcast inventory. Do not invent a guest list.
  • Then the same skill runs on every other personal brand site in the fleet.

Companion

Use wordpress-author-is-the-person so the published author is the figurehead, not a staff login. On dennisyu.com, author is Dennis, user id 2.

Output

  • One hub URL and id.
  • Child pages at /people/{slug}/, published, comments closed, clean hrefs.
  • A short report of what shipped and what stayed thin on purpose.

Do not

  • Do not clone a repo to do this. REST is enough.
  • Do not print passwords.
  • Do not invent titles, companies, or guest lists.
  • Do not add query strings.
  • Do not publish a second /people/ hub.
  • Do not ship to a client production domain without a yes.

Scroll to Top