Intermediate

Entity Clarity Rewrite for Service and About Pages

Tighten entity references on a key page so AI engines can reliably identify what the brand is, who it serves, and how it fits in its category.

When to use this prompt

When a service page, homepage, or about page describes the brand in vague language that an AI engine cannot reliably summarize. Common symptoms: descriptions that could apply to ten other companies, missing audience specificity, no named category, and use of internal jargon without translation.

Entity clarity is the foundation of GEO. If an AI engine cannot reliably answer “what is this company” after reading your page, it cannot recommend you for any specific buyer query. Run this rewrite on the three or four pages that an LLM is most likely to use to summarize the brand: homepage, services index, primary service page, about page.

The prompt

<role>Editor specializing in entity clarity for AI retrieval.</role>

<task>Rewrite the page below so an AI engine reading it can answer five entity questions clearly. Preserve voice and length. Verify the rewrite at the end.</task>

<inputs>
<brand>[BRAND]</brand>
<category>[CATEGORY]</category>
<audience>[AUDIENCE]</audience>
<top_competitors>[NAMED COMPETITORS]</top_competitors>
<original_page>
[PASTE PAGE TEXT]
</original_page>
</inputs>

<instructions>
1. After reading the original, the rewrite must enable a model to answer all five entity questions in one sentence each:
   1. What is this brand or product?
   2. What category does it operate in?
   3. Who is it for, named precisely?
   4. What problem does it solve?
   5. What makes it different from the named competitors?
2. Preserve the existing tone and voice. Do not flatten into generic marketing copy.
3. Use specific named entities: products, audiences, integrations, competitors, geographies. Replace vague qualifiers ("various", "many", "a wide range of") with named ones.
4. Where internal jargon is intentional, define it once on first use. Otherwise replace it with category-standard language.
5. Total length stays within ±10% of the original.
6. Do not invent facts that are not in the original or in the inputs above.
7. After the rewrite, answer the five entity questions using only sentences that appear in the rewrite. If you cannot answer a question from the rewrite, mark it [GAP] and explain what content is still missing.
</instructions>

<output_format>
Rewritten page:
[the rewrite]

Five entity answers (using only the rewrite):
1. What: [one sentence]
2. Category: [one sentence]
3. Who: [one sentence]
4. Problem: [one sentence]
5. Differentiator: [one sentence]

Gaps (if any):
- [GAP] [question number]: [what content is still missing]
</output_format>

How it works

The five entity questions are the implicit retrieval questions a system asks every time it tries to summarize your brand. If your page does not answer them clearly, the retrieval system will guess, and the guess will usually be a category-generic summary that does not differentiate you.

The verification step at the end (answer the questions using only the rewrite) is the forcing function. Without it, the model often makes cosmetic edits and reports success. With it, gaps surface as [GAP] markers you can act on.

Tone preservation is in the instructions because brand voice and entity clarity are often treated as opposites. They are not. The strongest brand pages sound like a specific person while still answering the entity questions clearly.

Example output

Five entity answers from the rewrite:

  1. Acme Analytics is product analytics software.
  2. Acme Analytics operates in the data infrastructure category, specifically the product analytics segment.
  3. Acme Analytics is built for product and growth teams of 25 to 200 at mid-market SaaS companies.
  4. Acme Analytics solves the lack of visibility into how users actually use the product and why they churn.
  5. Compared to Mixpanel and Amplitude, Acme Analytics is positioned for mid-market specifically, with a faster implementation and a flat-fee pricing model.

Variations

  • Diagnostic-only mode: Skip the rewrite and only return the five entity answers from the existing page. Useful for spotting which page is the entity-clarity weak link without committing to edits yet.
  • Multi-page comparison: Run on the brand’s homepage, services page, and about page in sequence. Compare the five entity answers across pages. Inconsistencies between them are a major retrieval problem.
  • Competitor comparison: Run on a competitor’s page first to see what their entity model looks like, then rewrite your own page to differentiate.