Read-only local campaign artifact

koray-semantic-framework.md

direct-seo-wave-40/koray-semantic-framework.md

# Koray semantic SEO master framework -- retained-source kickoff

## Routing decision

This master-framework run defines the source context and routes specific outputs to entity SEO, topical mapping, content briefs, and schema validation. It does not claim a completed ranking model, competitor gap, query-volume set, or ready-to-publish calendar because no fresh research or competitor source packet was supplied.

## Three-principle kickoff

| Principle | Local result | Evidence gate before execution |
|---|---|---|
| Vastness | Initial contextual domains identified from retained service labels. | Confirm actual service scope and obtain source-backed query/competitor evidence. |
| Depth | Content must follow declaration-and-evidence patterns. | Obtain authoritative citations, approved operational facts, and page-specific proof. |
| Momentum | Start with a small coherent cluster, not isolated volume. | Owner approval, editorial capacity, staging access, and measurement baseline. |

## Source context

**Central entity candidate:** Flat Fee House Cleaners Sarasota  
**Central search intent candidate:** Find and understand locally offered house-cleaning services in Sarasota.  
**First contextual domain:** Residential home cleaning and service-scope explanation in Sarasota.

## Core and outer content network

### Core section -- commercial intent

| Node | Entity-attribute focus | Required source before drafting |
|---|---|---|
| Residential cleaning | Business -> residential service -> included tasks | Approved checklist and service area. |
| Deep cleaning | Cleaning service -> scope -> standard versus deep distinction | Approved task list and accurate comparison. |
| Move in/out cleaning | Cleaning service -> move transition -> scope | Approved scope and any cited property requirements. |
| Airbnb cleaning | Cleaning service -> turnover -> workflow | Approved workflow, timing policy, linen/restock policy. |
| Quote method | Business -> flat-rate quote -> inputs | Approved rate card or quote logic; no invented prices. |

### Outer section -- explanatory support

| Node | Contextual purpose | Guardrail |
|---|---|---|
| Cleaning preparation guide | Helps a customer prepare for an approved service. | Use only company-approved policy. |
| Standard vs. deep cleaning guide | Defines scope relationships. | Cite or state only verified task lists. |
| Move cleaning checklist | Explains common checklist categories. | Do not promise deposit outcomes. |
| Cleaning-product policy | Explains supplied products and client preferences. | Reconcile with approved operating policy first. |
| FAQ hub | Groups visible questions by service intent. | Visible page text and FAQ markup must match exactly. |

## Retrieval-cost and information-quality controls

1. One clear service subject per page. Do not combine unrelated service definitions in one page.
2. Keep title, URL, meta description, heading order, internal anchor text, image filename, and alt text aligned to the same macro context.
3. Write direct answers only after each factual value has a source. Flag unresolved values rather than filling gaps with assertions.
4. Link core service pages to their relevant outer explainers, and only add links once the destination exists.
5. Treat the source's service-description mismatch as a content-integrity issue to correct before expansion.

## First reviewable cluster

Start with the residential-cleaning hub plus the standard-versus-deep-cleaning explainer. This is a recommendation for review, not a publishing instruction. It creates one core commercial page and one supporting explanatory node without assuming unverified services, pricing, or rankings.

## Result

**PARTIAL.** The local Koray master-framework procedure produced a constrained semantic network and routed next artifacts. A substantive semantic plan needs current page captures, approved entity/service data, evidence-backed query and competitor research, and editorial approval before implementation.