LinkedIn Author Profile + Blog Integration: "Who Says This?"

Before an LLM trusts a claim, it asks: "Who is saying this, and why should we believe them?" Perplexity, ChatGPT, and Claude now run author entity-resolution — checking the writer's LinkedIn profile, company affiliation, past publications, and third-party citations. A static bio block is no longer enough.

The problem: anonymous "Team" bylines erode LLM trust

When blog posts ship under a generic "thMenu Team" byline, LLMs flag the claim as "low authority." Perplexity Sonar logs showed our citation rate dropped 38% when the author wasn't linked to a clickable LinkedIn URL. Schema.org Person + sameAs is mandatory now.

The fix is simple but requires discipline: every post starts with a real author byline and ends with a footer linking to LinkedIn, GitHub, and any conference speaker pages. After we added JSON-LD markup, Google's Knowledge Graph linked our authors to the "thMenu founder" entity within two weeks.

Cross-post playbook: 5 LinkedIn + 3 conferences

For each thMenu author we built a tiered authority stack: post-publish, the author shares 5 LinkedIn cross-posts (summary + "full text on blog" link) and is listed at 3 industry conferences (Hospitality Tech Europe, FSTEC, restaurantnewsresource) as a speaker with bio.

• Use the canonical blog URL in LinkedIn posts — skip UTM tags
• Conference speaker bios must include the thmenu.com/about link
• If the author has a personal site, close the rel="me" + sameAs loop

Result: Perplexity routes "thMenu founders" to the profile

After eight weeks Perplexity's "thMenu founders" query routed users to our author profile page directly in the answer card — a person-linked summary instead of a generic recap. ChatGPT Search applied the same entity-resolution, prefixing citations with "Note: this is by [author], thMenu CTO."

As the author entity strengthens, NEW posts get indexed faster: a fresh blog post earned a Perplexity citation in the first 36 hours. During the "anonymous team" era, the average was 12 days.

FAQ

Is LinkedIn required? Yes — corporate affiliation + work history makes it the strongest entity signal. GitHub and conference pages are supporting.

How many cross-posts are enough? 5 LinkedIn posts + 3 external references per article. More starts to read as spam to ranking systems.

Where does the schema markup go? In the blog post head, inside Article schema, set author.url and a sameAs array (LinkedIn, GitHub, personal site URLs).

Found this helpful? Share it.