Red Flags & Anti-Patterns

Common patterns that indicate poor entity SEO health. Use this list during audits to identify quick wins and major gaps.

Red Flags

Thin Service Pages with No Depth

Service pages that list services without supporting context, descriptions, or related content. Google cannot establish what the service entity means from a thin page.

---

No Supporting Topical Content

A site with service pages but no guides, FAQs, or topic pages around those services. Supporting content is how Google understands the topic ecosystem around a core entity.

---

Inconsistent Brand, Service, or Location Facts Across Pages

Different phone numbers, service names, addresses, or descriptions on different pages. Inconsistency breaks entity trust — Google needs facts to be consistent to confidently associate them with an entity.

---

No Internal Links Between Related Topics

Pages that exist in isolation with no links to or from related pages. Internal links are the connective tissue of entity relationships. Orphaned pages contribute nothing to entity clarity.

---

Keyword Pages with No Entity Depth

Pages built to rank for a phrase but containing no entity relationships — no brand references, no links to service or location pages, no schema. These pages rank in isolation and do not build topical authority.

---

Service Pages Isolated from Supporting Topic Pages

A subset of the internal linking problem. Service pages that do not link to or from any supporting topic page signal weak topical authority around that service entity.

---

Schema That Contradicts Page Content

Schema markup that states different facts than what appears on the page — different service names, different locations, different contact information. Schema contradictions actively signal distrust to Google.

---

Scoring Reference

Use these during the Keyword vs Entity Audit:

Anti-Pattern Present	Score Impact
1–2 red flags	Minor — target in next sprint
3–4 red flags	Moderate — prioritize this entity group
5+ red flags	Critical — entity SEO cannot scale until resolved

---

Next: Troubleshooting