SOP: Phrase Architecture

ID: SOP-002 | Time: 3-5 hours per content piece | Audit pair: Phrase-Based Optimizer

Build content that achieves topical completeness through phrase coverage — the operational application of Anna Patterson's phrase-based indexing patent.

Objective

Ensure every piece of content covers the complete phrase ecosystem for its topic, achieving topical depth that signals genuine expertise to Google's phrase-based indexing system.

Step 1: SERP Research — Build the Phrase Map

For your target topic/query:

1. Search the target query in Google (incognito)
2. Open the top 10 ranking URLs in tabs
3. For each URL, extract the main content body text (paste into a text document, strip formatting)
4. Run through a phrase frequency analyzer OR manually identify recurring 2-4 word phrases

Manual phrase extraction method:

• Read each page and highlight any 2-4 word phrases that seem expert/specific to this topic
• After reading all 10, note which phrases appeared in 5+ pages (primary), 3-4 pages (secondary), 1-2 pages (tertiary)

What you're building: A phrase target map organized by frequency of appearance across top-ranking pages.

Step 2: Audit Your Draft Against the Phrase Map

For each phrase in your map:

1. Search your draft for the phrase (Ctrl+F)
2. Mark: Present / Absent / Partially covered (concept mentioned but phrase not used)
3. Note the location if present: heading, first third, second third, last third

Gap classification:

• Primary phrase gap (appears in 5+ of 10 top pages): HIGH priority — write a section around it
• Secondary phrase gap (appears in 3-4 of 10): MEDIUM priority — add a paragraph or subsection
• Tertiary phrase gap (appears in 1-2 of 10): LOW priority — add where it fits naturally

Step 3: Fill Phrase Gaps by Developing Concepts

For each HIGH priority gap:

• Write a 100-300 word section that genuinely explains the concept behind the phrase
• Use the phrase in the heading (H2 or H3) if it's a central concept
• Use the phrase naturally 1-2 times in the section
• Include the phrase's natural co-occurring words (context anchors)
• Do NOT just insert the phrase into an existing sentence — develop it

For MEDIUM priority gaps:

• Add a 50-150 word paragraph to the most relevant existing section
• Or add a bullet item with explanation to a list section

For LOW priority gaps:

• Add where contextually natural — don't force it
• Can add to an FAQ section at the end of the article

Step 4: Verify Natural Distribution

After adding phrase coverage:

1. Re-read the content as if encountering it for the first time
2. Check: does each phrase appear in a context that makes sense for an expert discussion?
3. Check: does the phrase frequency feel natural, or does any phrase appear too many times?
4. Check: is the content more valuable with the additions, or just longer?

The natural writing test: Would a subject matter expert who wrote this naturally say these things? If you added phrases that no expert would naturally say in this context, remove them and find a more natural way to cover the concept.

Step 5: Check Word Sense Disambiguation

For any potentially ambiguous phrase:

1. Read the sentence containing the phrase
2. Ask: could this phrase be misinterpreted to mean something else?
3. If yes: add a qualifying word or phrase that anchors the meaning

Common disambiguation needs:

• "Python" → "Python programming language"
• "cloud" → "cloud computing" or "cloud storage"
• "organic" → "organic search traffic" or "organic marketing"
• "crawl" → "web crawling" or "Googlebot crawl"

Step 6: Final Phrase Coverage Check

Using your phrase map as a checklist:

• [ ] All PRIMARY phrase gaps filled
• [ ] 60%+ of SECONDARY phrase gaps filled
• [ ] Some TERTIARY phrases included where natural
• [ ] No phrase appears more than 3× in any 500-word section
• [ ] All polysemous phrases disambiguated
• [ ] Content reads as expert writing, not keyword insertion

Output

A content piece that achieves topical depth equivalent to the top-ranking pages, with natural phrase coverage across the full semantic field of the topic — not keyword repetition.