Entity links: Organization, founder and official profiles

Paste into any coding agent: Claude Code, Cursor, Codex, Copilot, Windsurf or Cline.

# Entity links: Organization, founder and official profiles

Search engines and AI assistants build a picture of a company from its site and the profiles that point back to it. When those disagree or are not linked, assistants mix the company up with others or leave it out. Make the production site, the company and its founder, the founder (ask me for the name), one clear set of entities, linked to the official profiles: the official profiles linked from the site (ask me to confirm the list).

Site: not given. Find the production URL in the project config, or ask me.

## Ground rules

1. Read before you write. Explore the parts of the codebase this job touches and tell me what is already in place.
2. Plan, then stop. Give me a numbered plan: what you will change, in which files, and why. Wait for my approval before editing anything.
3. Fix things at their source (the shared layout, the config, the generator), not with one-off patches page by page.
4. Keep the project's conventions: its framework APIs, file layout, naming and code style. Add no new dependency without asking.
5. Where something is already done well, say so and leave it alone.

## You will not

- Edit `.env` files, secrets or API keys, or print their values.
- Deploy, push, merge or publish anything.
- Delete data, or run migrations or scripts against a production database.
- Add tracking, third-party scripts or links to any site I did not ask for.
- Change copy, design or behaviour that this job does not need.
- Add profiles to sameAs that I have not confirmed are official.

## Your stack

- Framework: Work out the framework, router and build output from the project files (package.json, lockfiles, framework config) before planning, and say which you found.
- Host: Work out where the site is hosted from the config files (vercel.json, netlify.toml, wrangler config, Dockerfile, fly.toml) and say which you found.

## Steps

### 1. Collect the facts once

Gather the company name exactly as it should appear, a one-sentence description, the logo URL, the founding year, the founder's name and role, and the official profile URLs. Put them in one config or constants file that the about page, the footer and the structured data all read.

### 2. Organization and Person markup

In the root JSON-LD `@graph`: an `Organization` with name, url, logo, description, `foundingDate` if known, `sameAs` with the official profiles only, and `founder` referencing a `Person` (name, `jobTitle`, `sameAs` with the founder's own profiles, and an image if there is one). Give both stable `@id`s.

### 3. An about page that states the facts

Make sure there is an about page with the same name, description, founder and links in visible text, and link it from the footer. If it exists, align its wording with the shared facts; show me any copy change.

### 4. Make the profiles agree

Write me a short checklist of each external profile (X, LinkedIn, GitHub, Crunchbase, app stores, directories where the product is listed) with the name, one-line description and URL to use, so they all match the site. I will update those myself.

## Done means

- [ ] One shared source holds the company name, description, logo, founder and profiles.
- [ ] Organization and Person JSON-LD with stable @ids and sameAs are on the site.
- [ ] The about page states the same facts in visible text and is linked from the footer.
- [ ] I have a checklist to make every external profile match.

## Report back

When you finish, give me:

- what you changed, file by file;
- anything you skipped, and why;
- anything I must do by hand (DNS records, dashboards, accounts, deploys);
- how to check each change on the live site.