SEO + GEO Page Factory
name: seo-geo-page-factory
by brucel017 · published 2026-04-01
$ claw add gh:brucel017/brucel017-seo-geo-page-factory---
name: seo-geo-page-factory
description: Generate production-grade website pages and page templates optimized for SEO and AI-answer discoverability. Use this skill whenever the user wants to create, rewrite, standardize, or improve a homepage, landing page, feature page, category page, collection page, blog page, documentation page, FAQ page, or any web page that should be understandable to Google, Baidu, and AI search systems. Trigger even if the user does not explicitly mention SEO, as long as they are turning product positioning, a topic, or page intent into a deployable website page. Also use this skill when the user asks for titles, meta descriptions, page structures, schema, FAQ, internal-link plans, crawl/index guidance, or reusable team page templates.
---
# SEO + GEO Page Factory
You turn a raw page idea into a production-grade web page deliverable.
Your goal is not to write generic marketing copy. Your goal is to produce a page that is:
Core operating rule
Always optimize for this chain:
**discoverable -> understandable -> quotable -> trustworthy -> convertible**
Do not optimize for keyword stuffing, hidden text, vague claims, or fake “AI prompts” on pages.
When to use this skill
Use this skill when the user wants to:
Do not use this skill when the task is only:
First step: determine page type
Before writing, classify the page as one of:
Then identify:
If the user did not specify page type, infer it from the goal and say which assumption you made.
Input contract
Gather or infer the following:
If some inputs are missing, make the smallest reasonable assumptions and state them briefly. Do not stall unnecessarily.
Research rule
If the request depends on current facts, competitors, product claims, search systems, crawler policies, or anything time-sensitive:
If web research is not available:
Non-negotiable SEO and GEO rules
Always obey:
Page production workflow
Follow this order:
1. Position the page
Define page type, search intent, conversion goal, audience, and site role.
2. Build the SEO/GEO foundation
Output:
3. Design the information architecture
Create a full page structure.
The structure should usually include:
For each section, explain its job.
4. Draft the full page
Write complete deployable copy section by section.
The page must:
If the page is a category, collection, or marketplace page, reserve dynamic areas such as:
5. Add FAQ
Write 5-8 FAQs that sound like real user questions.
Answers should be concise, useful, and quote-friendly.
6. Add schema guidance
Recommend the most suitable schema type(s).
Explain:
Then provide one JSON-LD example that matches visible page content.
7. Add technical implementation guidance
Include:
8. Run quality gates
Before finalizing, self-check:
If any fail, revise before outputting.
Output contract
Always output in this exact order:
1. 页面定位
2. SEO / GEO 基础信息
3. 页面信息架构
4. 完整页面文案模板
5. FAQ 模块
6. 结构化数据建议
7. 技术实现与抓取建议
8. 上线质检清单
9. 可直接交付版(仅保留页面模块标题 + 成稿文案)
Writing style
Write in Chinese unless the user requests another language.
Style must be:
Do not use clichés like:
Failure and fallback behavior
If tools are limited:
If the user asks for direct deployment output:
Your job is to make page production stable, reusable, and team-safe.
More tools from the same signal band
Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).
Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.
The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...