← Back to all Flat Fee outputs

Read-only local campaign artifact

entity-seo-source-bound-dossier.md

direct-content-wave-7/entity-seo-source-bound-dossier.md

# Entity SEO: Source-Bound Dossier

**Status:** PARTIAL  
**Input:** retained Flat Fee House Cleaners Sarasota homepage text only

## Canonical entity proposal

| Field | Proposal | Evidence status |
|---|---|---|
| Name | Flat Fee House Cleaners Sarasota | Present in retained text; final canonical approval required. |
| Entity type | LocalBusiness, pending the actual legal/business structure. | Proposed for schema planning only. |
| Definition | `Flat Fee House Cleaners Sarasota is a Sarasota, Florida cleaning business whose retained homepage lists residential, commercial, Airbnb, deep, window, pressure-washing, emergency, green, move-in/out, office, and medical-facility cleaning.` | Directly limited to the retained text; availability still needs approval. |
| URL | `https://flatfeehousecleanerssarasota.com/` | Supplied target; current canonical URL not checked. |
| Address/phone | Capture contains a Sarasota address and `(941) 207-9556`. | Do not syndicate until NAP is verified. |

## Entity risks

1. The capture also calls the business `Sarasota House Cleaning`; this is an entity-resolution conflict.
2. The capture mixes cleaning with repair/installation language, weakening topical co-occurrence.
3. No verified owner, founding year, social profiles, Wikidata item, Google Knowledge Panel, or profile identifiers were supplied.
4. No entity-extractor run or competitor baseline was performed, so this dossier has no salience scores or competitive delta.

## Semantic triples for an approved rewrite

These are draft shapes, not publishable facts until the placeholders are approved:

| Subject | Predicate | Object | Required proof |
|---|---|---|---|
| Flat Fee House Cleaners Sarasota | provides | `[approved cleaning services]` for `[approved service area]` | Service catalog and area policy. |
| `[named reviewer]` | reviews | Flat Fee House Cleaners Sarasota service content | Real role and credential evidence. |
| Flat Fee House Cleaners Sarasota | uses | `[approved supplies/process]` | Product/process policy. |
| Flat Fee House Cleaners Sarasota | publishes | `[verified contact and policy pages]` | Current site audit. |

## Home-node copy specification

Place this as the opening of an About page after facts are approved:

> **Flat Fee House Cleaners Sarasota is a [verified business type] serving [verified service area] with [verified cleaning services].** This page is reviewed by [real name and role] and links to the company’s current contact, scheduling, and policy information.

The bracketed fields intentionally remain unfilled. Filling them from the retained capture alone would turn unverified marketing language into a fact claim.

## Schema planning matrix

| Property | Draft source | Do not populate yet |
|---|---|---|
| `name`, `url`, `description` | Approved canonical definition. | Alternate brand name, broad claims, or unrelated services. |
| `address`, `telephone`, `openingHours` | Verified business record. | Retained contact data alone. |
| `areaServed` | Approved service-area policy. | Florida-wide inference from marketing copy. |
| `sameAs` | Verified profile inventory only. | Guessed social/directory URLs. |
| `foundingDate`, `employee`, `review`, `aggregateRating`, `award`, `hasCredential` | Documentary evidence. | Any values shown only in unverified homepage prose. |

## External entity path, not executed

1. Verify the one canonical display name and business record.
2. Run a local text extraction plus permitted external entity baseline and competitor comparison.
3. Build compliant organization/local-business markup whose visible page text matches exactly.
4. Inventory existing verified profiles before adding `sameAs`.
5. Consider Wikidata only if independently sourced notability and policy requirements are met. Do not create a Wikipedia page for the business.
6. Measure entity resolution through authorized quarterly searches and retained dated evidence.

## Completion gate

**Why PARTIAL:** the entity definition, identity-risk analysis, semantic triples, and schema field plan were generated locally. A complete entity run needs approved canonical facts, current page/schema, verified profiles, permitted external extraction, and no-conflict evidence.