Communitygithub.com

controlmodeler/UCE-Website

improve the uce website for basic search visibility without harming clarity. use when writing or revising page titles, meta descriptions, heading hierarchy, semantic page structure, internal links, and keyword placement for homepage or simple product pages.

Was ist UCE-Website?

UCE-Website is a Claude Code agent skill that improve the uce website for basic search visibility without harming clarity. use when writing or revising page titles, meta descriptions, heading hierarchy, semantic page structure, internal links, and keyword placement for homepage or simple product pages.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/controlmodeler/UCE-Website/tree/HEAD/skills/landing-page-seo-lite

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

Overview

Apply lightweight SEO discipline.

Do not turn the site into keyword spam. Preserve readability and credibility first.

Core rules

  • One clear topic per page.
  • Keep title tags specific.
  • Write natural meta descriptions.
  • Use semantic heading hierarchy.
  • Ensure important content is visible in page text.
  • Prefer clarity over keyword stuffing.

MVP SEO priorities

For each page, ensure:

  • a strong title
  • a useful meta description
  • one clear H1
  • logical H2/H3 structure
  • descriptive link text
  • meaningful body copy
  • fast, lightweight page structure

Keyword guidance

Use keywords naturally around themes such as:

  • industrial automation engineering
  • control system engineering
  • structured control definition
  • deterministic validation
  • engineering compiler
  • process control workflows
  • automation system design

Do not force all of them into one page.

Homepage SEO pattern

Title

Keep it concise and specific.

Example direction:

  • Universal Control Engine | Structured Control Engineering Platform

Meta description

Summarize:

  • what UCE is
  • who it helps
  • what it improves

H1

State the page’s central topic clearly.

H2s

Use section headings aligned with real reader intent:

  • the problem
  • the approach
  • key capabilities
  • why it matters

Technical content rule

Search visibility should come from real technical clarity, not vague SEO filler.

Pages should explain:

  • current engineering workflow pain
  • UCE’s structured approach
  • validation and deterministic outputs
  • relevance to EPC and controls teams

Link guidance

Use descriptive links such as:

  • Review the platform architecture
  • Request early access
  • Explore key capabilities

Avoid vague links such as:

  • Click here
  • Learn more everywhere

Output preference

When improving a page, provide:

  • title
  • meta description
  • suggested H1
  • suggested H2 structure
  • concise SEO notes only when needed

Individual skills in this repo

This repo contains 2 individual skills — each has its own dedicated page.

Verwandte Skills