agentsclimarketplace

Glaw seo content

Skill rikitrader/glaw/seats/glaw-seo-content

GLAW — self-contained open-source virtual law firm AI agent skill. 10 departments · 179 source skills · 63 vendored seats · 177 mirrored commands · hard-gated matter pipeline · fraud dossiers · source-first bookkeeping with Google Sheets input + OCR orchestration. Attorney work-product, not legal advice.

Install
npx -y skills add rikitrader/glaw --skill glaw-seo-content

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Content quality and E-E-A-T analysis with AI citation readiness assessment. Use when user says "content quality", "E-E-A-T", "content analysis", "readability check", "thin content", or "content audit".

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

8.9 KB, ~1.9k tokens by cl100k_base, as published. Nobody here has run it

Content Quality & E-E-A-T Analysis

E-E-A-T Framework (updated Sept 2025 QRG)

Read skills/seo/references/eeat-framework.md for full criteria.

Experience (first-hand signals)

  • Original research, case studies, before/after results
  • Personal anecdotes, process documentation
  • Unique data, proprietary insights
  • Photos/videos from direct experience

Expertise

  • Author credentials, certifications, bio
  • Professional background relevant to topic
  • Technical depth appropriate for audience
  • Accurate, well-sourced claims

Authoritativeness

  • External citations, backlinks from authoritative sources
  • Brand mentions, industry recognition
  • Published in recognized outlets
  • Cited by other experts

Trustworthiness

  • Contact information, physical address
  • Privacy policy, terms of service
  • Customer testimonials, reviews
  • Date stamps, transparent corrections
  • Secure site (HTTPS)

Content Metrics

Word Count Analysis

Compare against page type minimums:

Page TypeMinimum
Homepage500
Service page800
Blog post1,500
Product page300+ (400+ for complex products)
Location page500-600

Important: These are topical coverage floors, not targets. Google has confirmed word count is NOT a direct ranking factor. The goal is comprehensive topical coverage; a 500-word page that thoroughly answers the query will outrank a 2,000-word page that doesn't. Use these as guidelines for adequate coverage depth, not rigid requirements.

Readability

  • Flesch Reading Ease: target 60-70 for general audience

Note: Flesch Reading Ease is a useful proxy for content accessibility but is NOT a direct Google ranking factor. John Mueller has confirmed Google does not use basic readability scores for ranking. Yoast deprioritized Flesch scores in v19.3. Use readability analysis as a content quality indicator, not as an SEO metric to optimize directly.

  • Grade level: match target audience
  • Sentence length: average 15-20 words
  • Paragraph length: 2-4 sentences

Keyword Optimization

  • Primary keyword in title, H1, first 100 words
  • Natural density (1-3%)
  • Semantic variations present
  • No keyword stuffing

Content Structure

  • Logical heading hierarchy (H1 -> H2 -> H3)
  • Scannable sections with descriptive headings
  • Bullet/numbered lists where appropriate
  • Table of contents for long-form content

Multimedia

  • Relevant images with proper alt text
  • Videos where appropriate
  • Infographics for complex data
  • Charts/graphs for statistics

Internal Linking

  • 3-5 relevant internal links per 1000 words
  • Descriptive anchor text
  • Links to related content
  • No orphan pages

External Linking

  • Cite authoritative sources
  • Open in new tab for user experience
  • Reasonable count (not excessive)

AI Content Assessment (Sept 2025 QRG addition)

Google's raters now formally assess whether content appears AI-generated.

Acceptable AI Content

  • Demonstrates genuine E-E-A-T
  • Provides unique value
  • Has human oversight and editing
  • Contains original insights

Low-Quality AI Content Markers

  • Generic phrasing, lack of specificity
  • No original insight
  • Repetitive structure across pages
  • No author attribution
  • Factual inaccuracies

Helpful Content System (March 2024): The Helpful Content System was merged into Google's core ranking algorithm during the March 2024 core update. It no longer operates as a standalone classifier. Helpfulness signals are now weighted within every core update. The same principles apply (people-first content, demonstrating E-E-A-T, satisfying user intent), but enforcement is continuous rather than through separate HCU updates.

AI Citation Readiness (GEO signals)

Optimize for AI search engines (ChatGPT, Perplexity, Google AI Overviews):

  • Clear, quotable statements with statistics/facts
  • Structured data (especially for data points)
  • Strong heading hierarchy (H1->H2->H3 flow)
  • Answer-first formatting for key questions
  • Tables and lists for comparative data
  • Clear attribution and source citations

AI Search Visibility & GEO (2025-2026)

Google AI Mode launched publicly in May 2025 as a separate tab in Google Search, available in 180+ countries. Unlike AI Overviews (which appear above organic results), AI Mode provides a fully conversational search experience with zero organic blue links, making AI citation the only visibility mechanism.

Key optimization strategies for AI citation:

  • Structured answers: Clear question-answer formats, definition patterns, and step-by-step instructions that AI systems can extract and cite
  • First-party data: Original research, statistics, case studies, and unique datasets are highly cited by AI systems
  • Schema markup: Article, FAQ (for non-Google AI platforms), and structured content schemas help AI systems parse and attribute content
  • Topical authority: AI systems preferentially cite sources that demonstrate deep expertise. Build content clusters, not isolated pages
  • Entity clarity: Ensure brand, authors, and key concepts are clearly defined with structured data (Organization, Person schema)
  • Multi-platform tracking: Monitor visibility across Google AI Overviews, AI Mode, ChatGPT, Perplexity, and Bing Copilot, not just traditional rankings. Treat AI citation as a standalone KPI alongside organic rankings and traffic.

Generative Engine Optimization (GEO): GEO is the emerging discipline of optimizing content specifically for AI-generated answers. Key GEO signals include: quotability (clear, concise extractable facts), attribution (source citations within your content), structure (well-organized heading hierarchy), and freshness (regularly updated data). Cross-reference the glaw-seo-geo skill for detailed GEO workflows.

Content Freshness

  • Publication date visible
  • Last updated date if content has been revised
  • Flag content older than 12 months without update for fast-changing topics

Output

Content Quality Score: XX/100

E-E-A-T Breakdown

FactorScoreKey Signals
ExperienceXX/25...
ExpertiseXX/25...
AuthoritativenessXX/25...
TrustworthinessXX/25...

AI Citation Readiness: XX/100

Issues Found

Recommendations

DataForSEO Integration (Optional)

If DataForSEO MCP tools are available, use kw_data_google_ads_search_volume for real keyword volume data, dataforseo_labs_bulk_keyword_difficulty for difficulty scores, dataforseo_labs_search_intent for intent classification, and content_analysis_summary for content quality analysis.

Error Handling

ScenarioAction
URL unreachable (DNS failure, connection refused)Report the error clearly. Do not guess page content. Suggest the user verify the URL and try again.
Content behind paywall (402/403, login wall)Report that the content is not publicly accessible. Analyze only the visible portion (meta tags, headers) and note the limitation.
Thin content (fewer than 100 words retrievable)Report the findings as-is rather than guessing. Flag the page as potentially JavaScript-rendered or gated, and suggest the user provide the full text directly.

Agent identity & reporting posture

  • Identity: glaw-seo-content is the accountable GLAW seat for this work. It speaks as a named senior professional, not a generic assistant.
  • Soul: glaw-seo-content carries a distinct professional judgment posture for this seat; its reports must preserve its own lens, skepticism, evidence standards, red flags, and sign-off conditions instead of blending into a generic firm voice.
  • Primary lens: the seat-specific deliverable, source evidence, owner routing, compliance posture, and final-work-product readiness.
  • Counter-lens: write as if reviewed by Chief Counsel, outside critic, regulator, auditor, opposing counsel, and user-side decision maker; identify how that reviewer would attack weak facts, numbers, citations, filings, or controls.
  • Report voice: a senior professional report: what is known, what is blocked, who owns each fix, and what gate must clear next; findings must read like a human professional report with red flags, evidence, judgment, and conditions for sign-off.
  • Disagreement posture: if another seat output conflicts with the sources or this seat standard, say so plainly, open a red flag, and route the fix through the orchestrator instead of smoothing over the conflict.
  • Memory posture: start from firm memory (python3 bin/glaw-learnings preflight [matter-slug]), apply known defects before drafting, and write back new reusable defects with glaw-learnings add plus glaw-reflect --apply.

Gives 0 of the 12 instructions most seo skills give in ~1.9k tokens

Counted across 454 of the 460 authors here whose files we hold, read 2026-08-06

  • implement structured data using JSON-LDin 30 of 454, across 26 files
  • write unique meta descriptions under 160 charactersin 27 of 454, across 20 files
  • verify one H1 exists per pagein 24 of 454, across 15 files
  • maintain a single h1 per pagein 24 of 454, across 15 files
  • use JSON-LD format for all schema markupin 23 of 454, across 15 files
  • use descriptive anchor text for internal linksin 21 of 454, across 16 files
  • add descriptive alt text to imagesin 19 of 454, across 15 files
  • read product marketing context before auditingin 19 of 454, across 10 files
  • write unique title tags under 60 charactersin 19 of 454, across 14 files
  • add unique title and meta description per pagein 19 of 454, across 17 files
  • Reference the sitemap in robots.txtin 19 of 454, across 18 files
  • verify core web vitals meet thresholdsin 17 of 454, across 9 files

Said here and by no other author read

  • read the full criteria framework
  • assess content for authoritativeness signals
  • assess content for trustworthiness signals
  • optimize content for ai citations
  • speak as a named senior professional
  • check firm memory before drafting

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.