| name | semantic-seo-writer |
| description | Comprehensive SEO content writing and optimization skill based on semantic SEO principles. Enforces 71 rules covering featured snippets, entity optimization, sentence structure, content originality, factual writing, truth ranges, and vocabulary richness. Use when writing, editing, reviewing, or optimizing any web content, blog posts, articles, or landing pages for search engine performance and user satisfaction. |
| license | Proprietary |
| metadata | {"author":"Hasnain Ayaz","author_url":"https://hasnainayaz.com/","version":"1.0"} |
Semantic SEO Writer Skill
A complete set of 71 rules for writing SEO-optimized, semantically rich content. These rules are grounded in semantic SEO principles, Google patents research, and proven case studies.
Apply these rules whenever writing, editing, reviewing, or optimizing web content. Rules are organized into three categories. For full details and examples on any rule, load the corresponding reference file.
Category 1: Content Optimization (Rules 1-20)
For full details and examples, read references/content-optimization.md.
Rule 1: 40-Word Featured Snippet
Stick to a 40-word limit per answer where possible to trigger featured snippets. Short, direct answers increase the likelihood of appearing as featured snippets, especially for definitions or quick responses.
Rule 2: Answer Boolean Questions
Boolean questions must start with "Yes" or "No" before elaborating with supporting details.
Rule 3: How to Answer Type/Listing Questions
Answering type or listing questions effectively involves structuring responses to clearly present the required information with proper formatting.
Rule 4: Author Rules
Avoid starting sentences with "if". Minimize the use of the word "also". Present statements before conditions. Avoid nested statements. Measure the vocabulary gap between queries and documents.
Rule 5: Avoid Analogies
Do not use analogies. Replace comparisons with direct, factual statements. Instead of "Coffee is like fuel for your body," write "Coffee provides energy through caffeine."
Rule 6: Avoid Confusing Users and Bots
Do not send the reader or text processors back to previous sections. Restate information directly instead of using "As stated before" or "As explained in section Y."
Rule 7: Avoid Coreference Errors
Ensure every pronoun clearly refers to a specific entity. Unclear pronoun usage confuses both readers and search engines. Always specify the entity instead of relying on ambiguous pronouns.
Rule 8: Avoid Everyday Language
Never use everyday, conversational, or informal language. Avoid slang, colloquialisms, contractions, idioms, informal pronouns, and phrasal verbs. Use formal and professional diction.
Rule 9: Avoid Linking to Citations
Do not link out to external citations or studies. Mention research and sources in text without adding outbound links, to avoid passing link juice.
Rule 10: Avoid Product Promotion in Informational Articles
Do not promote products in informational content. Keep informational pages unbiased, focusing purely on the topic for trustworthiness.
Rule 11: Avoid Uncertain Words / Semantic Triples
Use certain, definite knowledge statements. Structure information using semantic triples: Subject + Special Fact + Main Information. This connects important details directly to the main topic.
Rule 12: Avoid Unnecessary Sentences
Do not create extra sentences without logical reason. Combine related information into single sentences to minimize token usage by search engines.
Rule 13: Be Certain
Use factual, definite statements. Avoid possibility language. "Sun raises every day" (fact) is better than "Sun will rise tomorrow" (possibility).
Rule 14: Be Specific When Describing Things
Do not use vague descriptions. Specify exact counts and categories. Instead of "The symptoms of X disease..." write "There are 6 severe symptoms of X disease, these are..."
Rule 15: Understand Context of Verbs
Use verbs with correct semantic signals. "Increase" signals health metrics. "Improve" signals skill and health outcomes. "Develop" signals gradual skill acquisition.
Rule 16: Cite Authoritative Sources
Always use a source as an authority before giving a statement. Example: "According to the World Health Organization, regular exercise can reduce the risk of chronic diseases." Build stronger entity relationships by mentioning relevant researchers, experts, or authoritative organizations.
Rule 17: Consistent Declarations Across Webpages
Maintain consistent stance on each topic across all pages. If one page says "coffee reduces stress," do not contradict it on another page.
Rule 18: Consistent Style Across Documents
Use a consistent tone and style across all platforms. If the brand tone is friendly and informative, maintain it across all pages, social media, and emails.
Rule 19: Consistent Part of Speech in Listings
Use the same part of speech tag for the first word of every item in a listing. If starting with verbs: "Ensure..., Clear..., Spend..., Absorb..." If starting with nouns: "Coffee provides..., Exercise boosts..., Hydration improves..."
Rule 20: Content Length Rules
Content should be as short as possible but as long as necessary. Tell the same thing with fewer words while including necessary entities and their connections. Long sentences create long dependency trees, diluting meaning between word connections.
Category 2: Semantic SEO & Structure (Rules 21-45)
For full details and examples, read references/semantic-seo.md.
Rule 21: Boolean Questions Format
Boolean questions should start with "Yes" or "No" followed by the detailed answer with supporting evidence and authoritative sources.
Rule 22: Create Proper Context Vector
Create a logical context vector from H1 to the last heading. Start with the main topic in H1 and end with a summary heading that reinforces the same context.
Rule 23: Cut the Fluff
Delete all contextless words and unnecessary filler. Replace verbose passages with concise, entity-rich statements.
Rule 24: Optimize Discourse Integration
Use clear topic sentences, transitional phrases, consistent terminology, and align content with user intent. Maintain logical and contextual connections between sentences and sections.
Rule 25: Adding Perspective Richness
First give a factual answer, then add diverse perspectives. Diversify perspectives based on audience (teacher, parent, professional) while maintaining balance across headings.
Rule 26: Include More Entities and Attribute Values
Include related entities and their attributes as long as they are relevant to the macro context. For a coffee page, mention types (espresso, cappuccino), compounds (caffeine, antioxidants), and attributes (bitterness, acidity).
Rule 27: Focus on Entities, Not Keywords
Focus on association of all relevant entities with detailed information, attributes, and facts within a specific context. Use Named Entity Recognition (NER) principles.
Rule 28: Avoid Entity Stuffing
Entity stuffing is no different from keyword stuffing. Focus on attributes of the main entity using prioritization criteria: Attribute Prominence, Attribute Relatedness, and Attribute Popularity.
Rule 29: Expand Evidence with Variations
Incorporate statistical evidence, anecdotal evidence, scientific studies, and expert opinions to strengthen arguments with multiple types of supporting information.
Rule 30: Factual Sentence Structures
Use objective, verifiable, clear, and direct sentences. Avoid personal bias, subjective interpretation, embellishments, or opinions.
Rule 31: Content Originality is Not Rephrasing
True originality requires actual expert writing with unique contextual terms, answer terms, n-grams, and declarations that are logically unified and semantically sound.
Rule 32: Koray Tugberk Gubur's Semantic SEO Framework
Apply the framework based on 8 years of research on 3,000+ Google patents, proven with 120+ websites and 30+ case studies showing significant traffic improvements.
Rule 33: Give Examples After Plural Nouns
Always follow plural nouns with specific examples. "There are 40 different cryptocurrencies to trade on Coinbase, including Bitcoin and Ethereum."
Rule 34: Sentence Structure — Subject, Predicate, Object
Structure sentences using semantic triples. Place the subject first, then a special fact as a modifier, then the main information. This connects important details directly to the main topic.
Rule 35: Types of Content on a Webpage
Maintain three content types: Main Content (core information, majority of page), Supplementary Content (supporting/complementary information), and Ads Content (contextually aligned advertising).
Rule 36: Key Terms Connect to Title and H1
Key terms must connect to the title, heading 1, and topical map. Ensure key terms appear in both the title and H1 for clear topical focus.
Rule 37: Long-Form Answers Use Definitions and Qualifiers
For long-form answers, use definitions, entity signifiers, and qualifiers. Mention concepts and connections to make content richer and more informative.
Rule 38: Do Not Break Context Across Paragraphs
Keep related details within one paragraph. Stick to one topic per paragraph to avoid confusing the reader or breaking logical flow.
Rule 39: Do Not Break Information Graph with Complicated Transitions
Follow a logical declaration order. Use simple transitions and ensure each point builds on the previous one. Avoid jumping between unrelated ideas.
Rule 40: Match Anchor Text with Target Page Title
Anchor text must match the targeted web page's title and its context between source and target pages.
Rule 41: Match Tenses and Modality Between Questions and Answers
If a question uses present indefinite tense, the answer must also use present indefinite tense. If a question contains a modal verb (can, may, will), the answer must contain the same modal verb.
Rule 42: Mention Studies to Back Facts
Use the format: "A (Year) study at the (Research Organization) found that [State Fact]." to cite research without linking externally.
Rule 43: Give More Information Per Unit
Provide detailed, comprehensive information per webpage, per section, per paragraph, and per sentence. Go beyond surface-level information.
Rule 44: Clarity and Precision
Use simple sentence structures (Subject + Verb + Object/Modifier). Avoid ambiguity, complex terms, filler words, and abstract language. Echo search queries in responses.
Rule 45: Optimize Subordinate Text First Sentence
Match the first sentence under a heading to the heading format. For "How to do X..." headings, start supporting text with "To do X..." not "X is..."
Category 3: Advanced Techniques (Rules 46-71)
For full details and examples, read references/advanced-techniques.md.
Rule 46: Parts of Speech Awareness
Understand and correctly use nouns, verbs, adjectives, and adverbs. Ensure proper grammatical role assignment for each word in a sentence.
Rule 47: Add Perspective Richness for User Satisfaction
For headings searchable by different user types, add multiple perspectives. Structure answers with facts first, then perspectives. Maintain balanced coverage across perspectives.
Rule 48: Put "If" Statements Second
State the action first, then the condition. Write "Take an umbrella, if it rains" instead of "If it rains, take an umbrella."
Rule 49: Prioritize Attributes and Contexts
Use interrogative terms as signals for the answer type. "Where" signals place, "How" signals process. Match answer attributes to the interrogative context.
Rule 50: Give Safe Answers
Provide comprehensive, safe answers by addressing the question directly, then listing factors, conditions, user experiences, manufacturer statements, and observations.
Rule 51: Decrease Contextless Words
Remove unnecessary filler words. Replace "basically, antioxidants in coffee can help reduce inflammation" with "Antioxidants in coffee reduce inflammation."
Rule 52: Relevance Configuration
Adjust sentence structure based on the query context. Different queries about the same entity require different attribute ordering and emphasis.
Rule 53: Include Same N-Grams at Start and End
Use the same key phrases at the start and end of the document to reinforce context and consistency.
Rule 54: Ontology and Taxonomy
Connect entities through shared attributes (ontology) and organize items from general to specific groups (taxonomy).
Rule 55: Short-Form vs Long-Form Questions
Prefer short-form questions in content. Word count does not define short vs long form — the number of concepts does. Use H2 for grouper questions and H3 for connected sub-questions.
Rule 56: Bold the Answer, Not the Search Term
Signal the answer part of a response, not the relevance/query part. Bold the factual answer, not the keyword.
Rule 57: Single Macro Context Per Webpage
Maintain one overarching theme per page. Do not mix unrelated topics on the same page.
Rule 58: Complete a Single Topic Thoroughly
Cover every detail of a topic, including aspects not found in competitor documents or queries. Comprehensive coverage positions the page as an authority.
Rule 59: Table Context
When adding a table, always define with context what is in the table. Explain the table contents and their context before presenting the table.
Rule 60: Do Not Distance Question from Answer
Answer the question immediately, then elaborate. Do not delay the answer with background information. Singularity and plurality matter for micro semantics.
Rule 61: Convert Headings to Questions
Convert headings into question format for better information retrieval and extraction. Question-based headings help search engines learn topics directly from content.
Rule 62: Truth Ranges
When data varies across sources, provide truth ranges (minimum to maximum values) instead of single values. This handles inconsistencies and can boost rankings.
Rule 63: Unique N-Grams
Use unique phrase combinations instead of common, widely-used phrases. "Drinking hot water after dinner" instead of generic "health benefits of hot water."
Rule 64: Abbreviation on First Mention
Always use the full term with abbreviation in parentheses on first mention. "Bitcoin (BTC) is the main cryptocurrency asset."
Rule 65: Diverse Measurement Units
When mentioning measurements, include multiple unit systems. "For each pound (0.45 kg) lost, drink around 16-20 oz (0.5-0.6 liters) of water."
Rule 66: Use Numeric Values
Use specific numbers instead of vague quantifiers. Write "There are 5 main reasons..." not "There are many reasons..."
Rule 67: Use Ordered and Unordered Lists
Use lists for instructional or feature-heavy content. Ordered lists for sequential steps, unordered lists for non-sequential items. Lists improve readability and snippet optimization.
Rule 68: Use Shorter Sentences
Use short sentences to keep dependency trees manageable. Give one piece of information per sentence. Long sentences dilute meaning between word connections.
Rule 69: Sentence Structure and Dependency Trees
Answer one question clearly in a single sentence. Do not answer many questions vaguely in one sentence. Long and complex sentence structures create long dependency trees that hurt readability and content clarity.
Rule 70: Use Research and University Studies
Cite reputable universities and research institutions with specific years, researchers, and findings. Reference real studies to boost credibility and relevance.
Rule 71: Prove Real Expertise with Vocabulary Richness
Use unique, domain-specific words that reflect knowledge-domain terms. Apply headword clusters. Use 3 examples for every plural noun. Use "or" for synonym groups. Build a strong n-gram profile for semantic engines.
How to Apply These Rules
- Before writing: Read the relevant reference file for the content type you are creating.
- During writing: Apply rules from all three categories as you draft each section.
- During review: Use assets/checklist.md for a quick scan of all 71 rules.
- For specific issues: Load the targeted reference file when encountering questions about a particular rule.
Gotchas
- Rules 68 and 69 both address short sentences and dependency trees — they reinforce each other from different angles (practical application vs technical rationale).
- Rule 11 and Rule 34 both cover semantic triples — Rule 11 focuses on avoiding uncertain words via triples, Rule 34 focuses on the Subject-Predicate-Object structure itself.
- Rule 2 and Rule 21 both cover boolean questions — Rule 2 introduces the concept, Rule 21 reinforces the format with source citation requirements.
- Do not apply Rule 9 (avoid linking to citations) if the content platform explicitly requires outbound citation links.
- Rule 47 (perspective richness) should be balanced — adding too many perspectives can break semantic structure per the rule's own warning.
