domains / families / marketing / seo-page

seo-page

combined

Single-page SEO audit: content quality under Google's E-E-A-T framework and Helpful Content guidelines, on-page factors, search intent, technical signals and readability. Pulls GSC data for the page, crawls the live HTML, checks metadata, schema, internal linking and depth, and produces a scored report with fixes. Use whenever the user wants to analyze a specific page or URL, not the whole site. Trigger on: "analyze this page", "audit this URL", "how is this page doing", "evaluate my blog post", "check this landing page", "page SEO", "content quality check", "is this page good enough", "review this page's SEO", "what's wrong with this page", "how can I improve this page", "page analysis", "single page audit", "content audit for [URL]", or any request naming a specific URL/page for SEO evaluation. If the user provides a specific URL (not just a domain), this is likely the right skill; use /seo-analysis for full-site audits instead. Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Use when user says "analyze this page", "check page SEO", or provides a single URL for review.

When to use

• Use when the user provides a single URL for detailed on-page SEO review.
• Use when auditing one page rather than an entire site.
• Use when checking metadata, content, schema, images, and page-level technical signals together.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies overlap in scope (single-page SEO audit) but each contains material steps the other lacks. The nowork-studio copy is a thin pointer to an external WORKFLOW.md and emphasizes GSC data, search intent, and internal linking depth, but it does not define the audit checklist or output format. The sickn33 copy provides a detailed, self-contained checklist (on-page, content quality, technical, schema, images, Core Web Vitals heuristics), a scored output format, error handling, and optional DataForSEO integration, but it does not mention GSC or search intent. Crowning one would hide a real alternative: the first is a workflow wrapper with GSC/intent focus, the second is a concrete audit procedure. They do not directly conflict on parameters, but they disagree on what the skill is (a pointer vs. a full procedure).