Session 10.8: Common Mistakes at the Baseline Level

Course → Module 10: Measurement and Maintenance

Session 8 of 10

After working through nine modules of entity-building fundamentals, it is worth pausing to catalog the mistakes that practitioners most commonly make at the baseline level. These are not exotic edge cases. They are patterns that appear again and again, across industries and entity types. Recognizing them early saves months of wasted effort.

Each mistake below includes a severity rating, the symptoms you will observe, and the specific fix. Severity is rated on a three-point scale: Critical (blocks entity recognition entirely), High (significantly weakens entity signals), and Moderate (reduces effectiveness but does not block recognition).

The Nine Common Mistakes

graph TD A["Common Baseline Mistakes"] --> B["1. Inconsistent NAP"] A --> C["2. Schema as decoration"] A --> D["3. Orphaned profiles"] A --> E["4. GBP neglect"] A --> F["5. Skipping Wikidata"] A --> G["6. Homepage tunnel vision"] A --> H["7. No measurement system"] A --> I["8. Content without entity purpose"] A --> J["9. One-time implementation mindset"] style A fill:#222221,stroke:#c8a882,color:#ede9e3 style B fill:#222221,stroke:#c47a5a,color:#ede9e3 style C fill:#222221,stroke:#c47a5a,color:#ede9e3 style D fill:#222221,stroke:#c8a882,color:#ede9e3 style E fill:#222221,stroke:#c8a882,color:#ede9e3 style F fill:#222221,stroke:#8a8478,color:#ede9e3 style G fill:#222221,stroke:#8a8478,color:#ede9e3 style H fill:#222221,stroke:#c8a882,color:#ede9e3 style I fill:#222221,stroke:#8a8478,color:#ede9e3 style J fill:#222221,stroke:#c47a5a,color:#ede9e3

#	Mistake	Severity	Symptoms	Fix
1	Inconsistent NAP across platforms	Critical	Google shows wrong address or phone. Local pack rankings drop. Knowledge Panel shows conflicting info or does not appear.	Establish canonical NAP. Audit and correct all platforms starting with aggregators (Session 10.6). Set up quarterly checks.
2	Treating schema as decoration	Critical	Schema contains generic or placeholder values. Rich Results Test shows errors. GSC Enhancement reports flag issues. No rich results appear.	Audit all JSON-LD blocks. Every value must match actual, verifiable business information. Remove anything that is not accurate (Session 10.5).
3	Orphaned profiles (no cross-linking)	High	Social profiles do not link to website. Website does not link to profiles. sameAs is missing from schema. Google cannot connect the dots.	Implement bidirectional linking (Module 3). Add sameAs to your Organization schema. Verify all links are live.
4	GBP set-and-forget	High	No posts in 60+ days. Outdated photos. Unanswered reviews. GBP Q&A section filled with spam questions. Hours incorrect.	Post weekly. Respond to every review within 48 hours. Update photos quarterly. Review Q&A monthly (Module 4).
5	Skipping Wikidata entirely	High	No Wikidata item exists. Knowledge Panel has no structured facts. Entity has no presence in the Knowledge Graph's foundational data layer.	Create a Wikidata item with at least 5 verifiable properties and references (Module 5). This is the single highest-leverage baseline action for many entities.
6	Homepage tunnel vision	Moderate	All entity signals concentrated on homepage. About page, service pages, and contact page have no schema, no entity content, no internal linking.	Distribute entity signals across all key pages. Each page should reinforce the entity through schema, content, and internal links (Module 8).
7	No measurement system	High	Cannot answer basic questions: "Is our brand search growing?" "Has our Knowledge Panel changed?" "Are our citations consistent?" No data to inform strategy.	Implement the Entity Presence Scorecard (Session 10.1), weekly KP monitoring (Session 10.2), and monthly GSC reviews (Session 10.3).
8	Content without entity purpose	Moderate	Publishing content that does not reinforce the entity. Blog posts about trending topics unrelated to core expertise. Content dilutes topical authority instead of building it.	Every piece of content should answer: "Does this reinforce what my entity is known for?" If not, either reframe it or do not publish it (Module 9).
9	One-time implementation mindset	Critical	Entity work treated as a project with an end date. Schema deployed once, never checked again. Citations built once, never audited. Brand SERP never monitored.	Shift to a maintenance mindset. Implement the quarterly review cycle (Session 10.7). Entity authority is a practice, not a project.

Severity Distribution

Three of the nine mistakes are rated Critical. These are the ones that can prevent entity recognition entirely. If you are struggling to get a Knowledge Panel or seeing zero improvement in brand search, start your troubleshooting with the Critical items.

Detailed Breakdown

Mistake 1: Inconsistent NAP

This is the most common mistake and the most damaging. It often happens without the business owner's knowledge. A data aggregator has an old address. A former employee set up a Yelp listing with a personal phone number. The website says "LLC" but GBP says "Inc." Each inconsistency is a crack in the foundation. Enough cracks, and the foundation fails.

The fix is tedious but straightforward. Establish a canonical NAP document. Audit every platform. Correct every mismatch. Then audit again quarterly because aggregators will try to overwrite your corrections.

Mistake 2: Treating Schema as Decoration

Some practitioners add structured data to check a box. The Organization schema says "name": "Company" instead of the actual company name. The address is a placeholder. The sameAs array contains URLs that return 404. This is worse than having no schema because it actively sends incorrect signals to Google.

Schema is a sworn declaration to search engines. Every value must be accurate, verifiable, and current. If you would not put it in a legal filing, do not put it in your JSON-LD.

Mistake 9: One-Time Implementation Mindset

This is the mistake that enables all the others. If you treat entity work as a one-time project, every signal you build will eventually degrade. Addresses change. Phone numbers are reassigned. Platforms update their formats. Schema.org releases new versions. Google changes its requirements.

The quarterly review (Session 10.7) exists specifically to combat this mindset. It builds maintenance into the calendar rather than relying on memory or motivation.

Mistakes at the baseline level are rarely about doing the wrong thing. They are about doing the right thing once and then stopping. Entity authority requires repetition, not just execution.

Assignment

Audit your entity for each of the nine common mistakes.

Go through each mistake in the table above. For each one, honestly assess whether it applies to your entity. Rate yourself: "Not applicable," "Partially applies," or "Fully applies."
For any mistake rated "Fully applies," write down the specific evidence that confirms the mistake (for example: "Our Yelp listing shows our old address from 2023").
For the Critical mistakes (1, 2, 9), create an immediate action plan with a deadline within the next 14 days.
For the High-severity mistakes (3, 4, 5, 7), add them to your quarterly action plan with deadlines within the next 90 days.
For the Moderate mistakes (6, 8), note them for the next quarterly review.

Common Mistakes at the Baseline Level