SEOmanual triggermarkdown-export Hardened

Thin Content Expansion Loop

A content quality loop for directory pages that must be useful enough for users and search engines.

Use loop copies the kickoff prompt. Copy Markdown and Download loop include the complete Markdown page with context, source attribution, anchors, and guardrails. Cursor / Claude Code buttons prepare the shorter kickoff prompt only.

Run shape

Supported agents

CursorClaude CodeCodex

Goal

Turn a thin page into a useful page with distinct user value.

Feedback gate

curl -sL $URL | wc -c

Stop condition

The page clearly answers user intent with distinct examples, guidance, and internal links.

Do not weaken, skip, delete, or rewrite the validation command to force success.

Do not claim completion until the stated exit condition is actually satisfied.

If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.

Required context

Give the agent these inputs before it starts the loop. This keeps discovery bounded and prevents vague retries.

Target page.

Search intent.

Available source/loop data.

Required tools

The loop assumes these commands or integrations are available. Missing tools should be reported as blockers, not ignored.

page list

content editor

How to run

Two separate pieces: the kickoff prompt starts the loop, while the downloaded Markdown carries the complete reference page.

1. Copy or download

Use the kickoff for a fast agent run. Download the full Markdown when you need source, context, and attribution in one file.

2. Paste into the agent

Start a fresh agent session in the target repo and provide the requested project context if the loop asks for it.

3. Let it self-pace

The agent should act, check evidence, retry only when the gate fails, and stop at the stated exit condition.

manual triggerSEO Step flow

Manual start

Identify missing value

Add operational details

Add related links and FAQ

Re-read as user

Feedback gate

Goal complete with evidence

not done → return to next actiondone → exit condition met

Action checklist

The diagram shows the order. This checklist keeps only the action, command, and failure handling needed during a real pass.

1. Identify missing value

Compare page content to user intent and similar pages.

2. Add operational details

Add examples, warnings, prerequisites, and failure handling.

3. Add related links and FAQ

Connect the page to loops, categories, and guides.

4. Re-read as user

Check whether the page is actually helpful, not just longer.

Kickoff prompt

This is the text copied by Use loop. It is intentionally shorter than the Markdown export.

Improve a thin page by adding specific examples, operational guidance, source context, FAQs, and related links. Avoid filler and duplicate boilerplate.
Goal: Turn a thin page into a useful page with distinct user value.
Check command: curl -sL $URL | wc -c
Exit condition: The page clearly answers user intent with distinct examples, guidance, and internal links.
Max iterations: 4
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not expand pages with filler text. Add specific, actionable value or remove/noindex the page.

Quality

86/100

Safety

93/100

Expected output

Expanded page outline or implemented content improvements.

Related loops

Browse all

SEOmanual trigger Hardened

AdSense Readiness Audit

Check whether a free content/tool site has enough original value, policy pages, navigation, and ad-safe layout for AdSense review.

CursorClaude CodeCodex

adsensemonetizationpolicy

Kickoff preview

Audit the site for AdSense readiness: content depth, policy pages, navigation, mobile UX, and ad-safe layout. Return blockers and fixes.
Goal: Make the site credible, useful, navigable, and ad-safe before AdSense review.
Check command: curl -I $SITE_URL
Exit condition: Core content, policy pages, navigation, and ad placement are ready for review.
Max iterations: 4
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not place ads next to copy/download/source buttons where users may click accidentally.

View

SEOmanual trigger Hardened

Programmatic SEO Page QA Loop

Review generated SEO pages for thin content, duplicate metadata, broken internal links, and missing structured data.

CursorClaude CodeCodex

programmatic-seoqualitythin-content

Kickoff preview

Audit a sample of generated SEO pages for uniqueness, helpfulness, metadata, internal links, and schema. Fix template/data issues before publishing at scale.
Goal: Ensure template-generated pages provide distinct value and are safe to index.
Check command: curl -sL $URL
Exit condition: Sampled generated pages have unique metadata, useful body content, and valid internal links.
Max iterations: 5
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not create large numbers of thin pages solely to manipulate search ranking.

View

SEOmanual trigger Hardened

Internal Link Builder Loop

Find orphan or weak pages and add relevant internal links from hubs, related pages, and contextual sections.

CursorClaude CodeCodex

internal-linksseosite-architecture

Kickoff preview

Find weak or orphan pages, choose relevant source pages, add natural internal links, and verify the rendered pages expose those links.
Goal: Improve crawlability and user navigation through relevant internal links.
Check command: curl -sL $SITEMAP_URL
Exit condition: Priority pages are linked from relevant hub/detail pages with natural anchors.
Max iterations: 4
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not add irrelevant keyword-stuffed links. User usefulness comes first.

View

CImanual trigger Hardened

Ship PR Until Green

Implement a scoped change, open or update a pull request, inspect CI, and continue until all required PR checks pass.

CursorClaude CodeCodex

pull-requestcigithub-actionsverification

Kickoff preview

Take this branch to a green pull request. Implement the requested change, run local verification, open or update the PR, run `gh pr checks`, inspect failures, fix root causes, and repeat until every required check passes or you hit the iteration cap.
Goal: Open or update a pull request and stop only when all required PR checks are green.
Check command: gh pr checks
Exit condition: All required pull request checks are successful and the PR is ready for review or merge.
Max iterations: 10
Guardrails:
- Do not weaken, skip, delete, or rewrite the validation command to force success.
- Do not claim completion until the stated exit condition is actually satisfied.
- If blocked, report the blocker, evidence, and next safest action instead of gaming the metric.
- Do not disable required checks, edit loops to skip jobs, or remove tests to make CI green.
- Do not merge the PR unless the user explicitly asked for merge authority.

View