Definition
What is a founder source page?
A founder source page is meant to be understood as a source, not just experienced as a layout. For a founder or operator, it should answer the identity question, the company connection, the current topic cluster, the proof pages behind the method, the external corroboration layer, and the next commercial route.
That is a different job from a portfolio. A portfolio says: look at the work. A source page says: here is the stable version of the facts, here is the topic map, here is the evidence, and here is how the public surfaces connect.
In practice, the difference is structure. Facts need to appear in visible copy, not only in metadata. A credible page links to the writing archive, research archive, company profile, public projects, and distribution surfaces. Visible copy and schema should tell the same story.234101112
Source hierarchy
Why social profiles are not enough
Social profiles are useful corroboration. They are weak as the primary canonical source.
LinkedIn can show role and history, but posts fragment quickly. X can move an idea, but it is not a stable source of record. GitHub and Hugging Face are strong proof surfaces for technical work, but they are not complete editorial context. Company profile pages are important, but they serve the company narrative first.101112
A founder site can coordinate those surfaces. It can say: this is the preferred name, this is the founder role, this is the company, these are the current topics, these are the canonical pages, and these external profiles are the corroborating layer.
That hierarchy matters because AI answers often assemble a picture from multiple surfaces. If those surfaces disagree, the answer layer can pick the wrong role, old positioning, outdated geography, or a shallow summary. A personal site cannot control every model output. It can make the source graph less messy.
Architecture
What does the source-page architecture include?
A useful founder source page has several layers. The point is not to turn every page into an SEO artifact. The point is to make the public source hierarchy easy to inspect.
| Layer | What it answers | Example on this site |
|---|---|---|
| Entity facts | Who is this person and what role do they hold? | The homepage states Gregory Shevchenko as founder and CEO/CTO of Humanswith.ai.1 |
| Topic map | What should this person be associated with? | The writing archive groups AEO/GEO, AI Search visibility, ContentOS, marketing agents, and agentic engineering.2 |
| Methodology | What is the underlying point of view? | The research archive explains AI Search visibility and agentic marketing work as methods.3 |
| Source-backed notes | Which pages answer one durable question? | Notes on AI citation structure, publishing for AI visibility, and measurement.456 |
| Commercial route | Where does the method become an implementation? | Humanswith.ai routes for AI Search visibility, ContentOS, and marketing agents.910 |
| External corroboration | Which public profiles confirm identity and work? | Humanswith.ai profile, GitHub, Hugging Face, LinkedIn, Medium, VC.ru, Habr, and X.101112 |
Drift
Where do founders go wrong?
Founders often treat the profile, the company page, the blog, and social posts as separate projects. That creates drift. One surface says "consultant", another says "agency founder", a third says "AI operator", and the company site uses a different offer.
In answer-layer work, drift becomes a quality problem because AI systems reconcile partial evidence. More content does not fix that by itself. Source order fixes it: decide which page is canonical, make the supporting profiles visible, and route every adaptation back to the durable source.
Publishing order
What I would publish first
If I were building a founder site from zero for AI visibility, I would not start with a big blog calendar. I would start with a small canonical stack.
Volume is not the point. Source order is. Publish the durable source first, then adapt it to LinkedIn, Medium, DEV.to, Habr, VC.ru, Substack, Telegram, or X when those surfaces are useful.5
Maintenance
How to keep it current
A source page needs a light maintenance loop. Check the entity facts when the role, company, location, offer, or public profiles change. Add new source-backed pages when a topic becomes important enough to be cited. Update distribution links after external adaptations go live. Recheck technical surfaces such as sitemap, feed, canonical tags, schema, and llms.txt when pages are added.
AI visibility work comes after that. Track whether target prompts mention, cite, recommend, misdescribe, or ignore the source. If the answer is wrong, fix the smallest layer that explains the failure.67
Usually that means entity facts, canonical page depth, source depth, external corroboration, internal links, or distribution.
Keep the loop boring. A founder site is not a magic citation machine. It is a controlled source that can be improved when the public picture drifts.
Checklist
What checklist should a founder source page pass?
Sources
Sources and related reading
1. Gregory Shevchenko homepage
https://gregshevchenko.com/
2. Writing archive
https://gregshevchenko.com/writing/
3. Research archive
https://gregshevchenko.com/research/
4. How to structure content for AI citation
https://gregshevchenko.com/notes/how-to-structure-content-for-ai-citation/
5. Where to publish for AI visibility
https://gregshevchenko.com/notes/where-to-publish-for-ai-visibility/
6. How to measure AI Search visibility
https://gregshevchenko.com/notes/ai-search-visibility-measurement/
7. AI Search source hierarchy
https://gregshevchenko.com/research/ai-search-source-hierarchy/
8. Source packs are the new briefs
https://gregshevchenko.com/research/source-packs-are-the-new-briefs/
9. What ContentOS is
https://gregshevchenko.com/notes/contentos/
10. Humanswith.ai founder profile
https://humanswith.ai/team/gregory-shevchenko/
11. GitHub profile
https://github.com/g-shevchenko
12. Hugging Face profile
https://huggingface.co/gshevchenko
FAQ
FAQ
Is this just personal SEO?
No. SEO still matters, but the job is broader. The page should help search engines, AI answer systems, buyers, collaborators, and journalists reconcile the same public facts.
Do I need a blog?
Not necessarily. You need a source map. For some founders that can be five strong pages: homepage, profile, methodology, one proof page, and one practical guide.
What belongs on the personal site versus the company site?
A personal site should explain the founder's role, method, public work, and point of view. The company site should carry the commercial offer, product pages, customer proof, and conversion routes.
How often should the page be updated?
Update it when public facts change, when a new canonical page goes live, or when AI visibility checks show a repeated misunderstanding. A monthly review is enough for a stable founder profile.
How do I know whether it is working?
Look for cleaner branded answers, fewer entity mistakes, more consistent citations to first-party pages, and better buyer understanding in conversations. Do not reduce the whole thing to one traffic number.
What should the first source-backed article be?
Start with the question you most want AI systems and buyers to answer correctly. For this site, that means AI Search visibility, ContentOS, marketing agents, source packs, and agentic engineering.
Next reading