Write an About Page That AI Engines Trust
Generate an About page packed with the entity signals AI answer engines use to decide whether to cite you — founder names with credentials, founding year, location, expertise areas, press mentions, and same-as references — plus matching Organization + Person JSON-LD. Returns a clear, scannable page humans love and crawlers can parse.
Pro tip
Your About page is the #1 source AI engines use to decide whether your business is real and citable. The pattern: name your founders with full names + credentials + LinkedIn/Wikipedia URLs, name your founding year and HQ city, and make every claim verifiable. Vague "we're passionate about…" copy gets your page skipped entirely. Specific, dated, named claims get you cited.
How to use this prompt
- Pick your AI model. Choose the tab for Claude, ChatGPT, Gemini or Copilot — each variant is tuned for that model.
- Copy the full prompt. Click Copy Full Prompt to copy the text to your clipboard.
- Paste into your AI tool. Open your chosen model and paste the prompt into a new chat.
- Replace the
[placeholders]. Swap any bracketed fields for your company name, audience, product or tone. - Run and refine. Review the output. If anything is off, ask the AI to tighten tone, length or format.
Prompt Variants by Model
Claude
Claude 4.x
FRESH APR 2026
You are an entity-SEO specialist. Write my About page so AI answer engines (ChatGPT Search, Perplexity, Google AI Overviews, Claude) recognize my business as a real, citable entity — and produce the...You are an entity-SEO specialist. Write my About page so AI answer engines (ChatGPT Search, Perplexity, Google AI Overviews, Claude) recognize my business as a real, citable entity — and produce the matching Organization + Person JSON-LD.
<entity_facts>
Legal business name: [LEGAL NAME]
Brand / trading name (if different): [BRAND NAME]
Founded year: [YYYY]
Founded where (city, country): [CITY, COUNTRY]
Current HQ city, state, country: [CITY, STATE, COUNTRY]
What we do (one sentence, customer-language): [DESCRIPTION]
Who we serve (specific): [e.g. "small dental practices in the US Southwest"]
Founder #1: name, title, credentials (degree / certification / years experience), LinkedIn URL, optional Wikipedia URL: [NAME, TITLE, CREDENTIALS, LINKEDIN, WIKI]
Founder #2 (if applicable): [SAME FIELDS]
Key team members worth naming (optional): [LIST]
Areas of expertise (3–5 specific topics, not "marketing"): [LIST e.g. "13-week cash flow forecasting", "Texas dental compliance", "abandoned cart recovery for Shopify"]
Press / podcast / publication mentions (full URLs): [LIST or NONE]
Industry awards or certifications (with year): [LIST or NONE]
Years in business: [N]
Number of customers served (if comfortable sharing): [NUMBER or BLANK]
Any specific outcome or stat you can stand behind: [e.g. "98% retention", "saved clients $4.3M in 2025"]
Brand voice: [warm-expert / no-nonsense / playful / premium-restrained / technical-precise / friendly-everyday]
</entity_facts>
<reference_examples>
Two patterns to choose from:
A. **Founder-led services business** — leads with the founder''s story + credentials, then the business, then the team. Best when one or two named humans are the trust signal.
B. **Team / methodology business** — leads with the methodology + dated track record, then the founders. Best when expertise + process is the trust signal more than personality.
Pick A or B based on whether the founder''s personal credentials or the business''s methodology carry more weight.
</reference_examples>
Output exactly four parts:
**PART 1 — Pattern Choice**
A or B + one-sentence rationale.
**PART 2 — The About Page (markdown)**
Sections in this order:
1. **H1**: One line that names what the business does + for whom (≤12 words). Not "About Us".
2. **Answer-first paragraph** (≤60 words): What we do, where we are, what year we started. First sentence is extractable.
3. **Founders section**: Each founder gets a paragraph — full name, title, year joined, credentials, one specific accomplishment, link to LinkedIn (and Wikipedia if applicable).
4. **What we''re known for**: 3–5 specific expertise areas with one supporting sentence each.
5. **Track record**: dated, specific stats (years in business, customers served, outcomes).
6. **Press / mentions**: bulleted list with publication name + linked URL.
7. **How to reach us**: physical address, phone, email — same NAP that appears in your Organization schema. Match exactly.
Style rules: every claim is dated, named, or numbered. No "passionate about", no "trusted partner", no "world-class". Match the brand voice.
**PART 3 — Organization + Person JSON-LD (paste-ready)**
A single <script type="application/ld+json"> block using @graph with:
- Organization (name, alternateName, url, logo, foundingDate, founder array, address, contactPoint, sameAs, knowsAbout array of expertise)
- One Person entity per founder (name, jobTitle, worksFor, sameAs, alumniOf if relevant)
- Cross-references via @id between Organization.founder and the Person entities
JSON-valid. Omit fields rather than null.
**PART 4 — Verification & Gaps**
- Rich Results Test URL: https://search.google.com/test/rich-results?url=[ABOUT-URL]
- Wikipedia/Wikidata strategy: which entities (founders, business, location) are worth getting on Wikidata as part of long-term entity-SEO work
- Any field where I gave you incomplete info that weakens the entity signal (e.g. "no LinkedIn URL given for Founder #2 — strongly recommended")
Notes: Claude is the strongest variant for the @graph + @id cross-references between Organization and Person. Schema cleanliness matters here — validate before publishing.
ChatGPT
GPT-5
FRESH APR 2026
Act as an entity-SEO specialist. Write my About page so AI answer engines recognize my business as a real, citable entity. Produce matching Organization + Person JSON-LD.
Entity facts:
- Legal name:...Act as an entity-SEO specialist. Write my About page so AI answer engines recognize my business as a real, citable entity. Produce matching Organization + Person JSON-LD.
Entity facts:
- Legal name: [LEGAL NAME]
- Brand name: [BRAND or SAME]
- Founded year: [YYYY]
- Founded where: [CITY, COUNTRY]
- Current HQ: [CITY, STATE, COUNTRY]
- What we do (customer-language sentence): [DESCRIPTION]
- Who we serve (specific): [DESCRIPTION]
- Founder #1: name, title, credentials, LinkedIn URL, optional Wikipedia URL: [DETAILS]
- Founder #2 (if applicable): [SAME FIELDS]
- Key team to name: [LIST]
- Areas of expertise (3–5 specific): [LIST]
- Press / podcast / publication mentions (full URLs): [LIST or NONE]
- Awards / certifications with year: [LIST or NONE]
- Years in business: [N]
- Customers served: [NUMBER or BLANK]
- Specific outcome / stat: [PROOF]
- Brand voice: [warm-expert / no-nonsense / playful / premium / technical / friendly-everyday]
Two reference patterns to choose from:
A. Founder-led services business — leads with founder story + credentials. Best when 1–2 named humans are the trust signal.
B. Team / methodology business — leads with methodology + dated track record. Best when process is the trust signal more than personality.
Pick A or B based on which carries more weight.
Output:
1. Pattern choice (A or B + one-sentence rationale).
2. About page in markdown:
- H1: what business does + for whom (≤12 words). Not "About Us".
- Answer-first paragraph (≤60 words): what / where / when. First sentence extractable.
- Founders section — full name, title, year joined, credentials, one specific accomplishment, LinkedIn (+ Wikipedia).
- What we''re known for: 3–5 specific expertise areas with supporting sentences.
- Track record: dated, specific stats.
- Press / mentions: bulleted with publication + linked URL.
- How to reach us: NAP matching Organization schema.
Style: every claim dated/named/numbered. No "passionate about", "trusted partner", "world-class". Match brand voice.
3. Single <script type="application/ld+json"> @graph block: Organization (name, alternateName, url, logo, foundingDate, founder array, address, contactPoint, sameAs, knowsAbout) + Person per founder (name, jobTitle, worksFor, sameAs, alumniOf). Cross-reference via @id. JSON-valid. Omit instead of null.
4. Verification: Rich Results Test URL, Wikidata strategy (which entities to push to Wikidata for long-term entity SEO), and flag any incomplete fields that weaken the signal.
Notes: GPT-5 occasionally invents accomplishments — keep it grounded with a "do not invent facts" reminder if needed.
Gemini
Gemini 2.5 Pro
FRESH APR 2026
You are an entity-SEO specialist. Write my About page so AI answer engines recognize my business as a real, citable entity. Produce matching Organization + Person JSON-LD.
ENTITY FACTS:
• Legal...You are an entity-SEO specialist. Write my About page so AI answer engines recognize my business as a real, citable entity. Produce matching Organization + Person JSON-LD.
ENTITY FACTS:
• Legal name: [LEGAL NAME]
• Brand name: [BRAND or SAME]
• Founded year: [YYYY]
• Founded where: [CITY, COUNTRY]
• Current HQ: [CITY, STATE, COUNTRY]
• What we do (customer-language): [DESCRIPTION]
• Who we serve (specific): [DESCRIPTION]
• Founder #1: name, title, credentials, LinkedIn URL, optional Wikipedia URL: [DETAILS]
• Founder #2 (if applicable): [SAME FIELDS]
• Key team to name: [LIST]
• Areas of expertise (3–5 specific topics): [LIST]
• Press / podcast / publication mentions (full URLs): [LIST or NONE]
• Awards / certifications with year: [LIST or NONE]
• Years in business: [N]
• Customers served: [NUMBER or BLANK]
• Specific outcome / stat: [PROOF]
• Brand voice: [warm-expert / no-nonsense / playful / premium / technical / friendly-everyday]
REFERENCE PATTERNS:
A. Founder-led services — leads with founder story + credentials. Best when named humans are the trust signal.
B. Team / methodology business — leads with methodology + dated track record. Best when process is the trust signal.
Choose A or B.
OUTPUT:
1. Pattern choice (A or B) + one-sentence rationale.
2. About page in markdown — sections in this order:
- H1: what business does + for whom (≤12 words). Not "About Us".
- Answer-first paragraph (≤60 words): what / where / when. First sentence extractable.
- Founders section — full name, title, year joined, credentials, one specific accomplishment, LinkedIn (+ Wikipedia).
- What we''re known for: 3–5 specific expertise areas with supporting sentences.
- Track record: dated, specific stats.
- Press / mentions: bulleted with publication + linked URL.
- How to reach us: NAP matching Organization schema.
Every claim dated/named/numbered. No "passionate about", "trusted partner", "world-class".
3. Single <script type="application/ld+json"> @graph block: Organization (name, alternateName, url, logo, foundingDate, founder array, address, contactPoint, sameAs, knowsAbout) + Person per founder (name, jobTitle, worksFor, sameAs, alumniOf). Cross-ref via @id. JSON-valid. Omit instead of null.
4. Verification: Rich Results Test URL, Wikidata strategy, flag incomplete fields weakening the signal.
Notes: Gemini 2.5 Pro is strongest for the Wikidata strategy section — it tends to suggest the right entities to seed.
Copilot
Copilot (GPT-5)
FRESH APR 2026
Write my About page so AI answer engines recognize my business as a real, citable entity. Produce matching Organization + Person JSON-LD.
Entity facts:
• Legal name: [LEGAL NAME]
• Brand name:...Write my About page so AI answer engines recognize my business as a real, citable entity. Produce matching Organization + Person JSON-LD.
Entity facts:
• Legal name: [LEGAL NAME]
• Brand name: [BRAND or SAME]
• Founded year: [YYYY]
• Founded where: [CITY, COUNTRY]
• Current HQ: [CITY, STATE, COUNTRY]
• What we do: [DESCRIPTION]
• Who we serve: [DESCRIPTION]
• Founder #1: name, title, credentials, LinkedIn, optional Wikipedia: [DETAILS]
• Founder #2: [SAME FIELDS or N/A]
• Key team to name: [LIST]
• Areas of expertise (3–5 specific): [LIST]
• Press / mentions (full URLs): [LIST or NONE]
• Awards / certs (with year): [LIST or NONE]
• Years in business: [N]
• Customers served: [NUMBER or BLANK]
• Specific outcome / stat: [PROOF]
• Brand voice: [warm-expert / no-nonsense / playful / premium / technical / friendly-everyday]
Reference patterns:
A. Founder-led services — founder story + credentials lead. Best when humans are the trust signal.
B. Team / methodology — methodology + track record lead. Best when process is the trust signal.
Pick A or B.
Output:
1. Pattern choice + one-sentence rationale.
2. About page in markdown:
- H1: what + for whom (≤12 words). Not "About Us".
- Answer-first paragraph (≤60 words): what / where / when.
- Founders section: name, title, year joined, credentials, one accomplishment, LinkedIn (+ Wikipedia).
- What we''re known for: 3–5 specific expertise areas.
- Track record: dated, specific stats.
- Press / mentions: bulleted.
- How to reach us: NAP matching Organization schema.
Every claim dated/named/numbered. No vague "passionate", "trusted partner", "world-class".
3. <script type="application/ld+json"> @graph block: Organization + Person per founder, cross-referenced via @id. JSON-valid. Omit instead of null.
4. Verification: Rich Results Test URL, Wikidata strategy, flag incomplete fields.
Notes: Copilot is reliable for the structural rules. Best for businesses on Microsoft-stack (LinkedIn-rich entity signals).
Frequently Asked Questions
What does the Write an About Page That AI Engines Trust prompt do?
Generate an About page packed with the entity signals AI answer engines use to decide whether to cite you — founder names with credentials, founding year, location, expertise areas, press mentions, and same-as references — plus matching Organization + Person JSON-LD. Returns a clear, scannable page humans love and crawlers can parse.
Which AI models is this prompt tested on?
This prompt is field-tested on Claude, ChatGPT, Gemini and Copilot. Each model has its own optimized variant above.
Do I need a paid AI account to use this prompt?
No. This prompt is written to run on the free tier of Claude, ChatGPT, Gemini and Copilot. Paid tiers simply give you longer context windows and faster responses.
Can I customize this prompt for my business?
Yes. Any text inside square brackets is a placeholder you replace with your own business details, such as company name, audience, product or tone. You can also ask the AI to adjust format, length or style after the first output.
When was this prompt last verified?
Each model variant above shows its own freshness stamp. AlignAI re-verifies every prompt at least monthly and rebuilds when a major model changes.
Don’t see what you need? tailored to your use case.