SEO AI Agent Loops
Google SEO, structured data, sitemap, internal linking, and AdSense-readiness loops. Every page is server-rendered, source-aware, and includes a copy-ready Markdown protocol.
All SEO loops
SEO Metadata Audit Loop
Audit title, description, canonical, Open Graph, headings, and indexability for SEO-critical pages.
Kickoff preview
Audit SEO metadata from server-rendered HTML for the target pages. Verify title, description, canonical, H1, Open Graph, and indexability, then fix and re-check. Goal: Ensure SEO-critical pages have unique, server-rendered metadata and indexable content. Check command: curl -sL $URL | head -80 Exit condition: Each target page has unique title, description, canonical, visible H1, and no accidental noindex. 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 rely only on client-rendered metadata for SEO-critical pages. Verify server HTML.
Programmatic SEO Page QA Loop
Review generated SEO pages for thin content, duplicate metadata, broken internal links, and missing structured data.
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.
GSC Indexing Debug Loop
Diagnose why a page is not indexed by checking robots, sitemap, canonical, status code, content quality, and internal links.
Kickoff preview
Debug indexing for the target URL: status, robots, canonical, noindex, sitemap, internal links, and content usefulness. Return exact fixes and uncertainty. Goal: Find technical or content reasons a page may not be indexed. Check command: curl -I $URL Exit condition: The page is technically indexable and remaining indexing uncertainty is clearly documented. 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 promise indexing. Only verify technical readiness and recommend fixes.
AdSense Readiness Audit
Check whether a free content/tool site has enough original value, policy pages, navigation, and ad-safe layout for AdSense review.
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.
Internal Link Builder Loop
Find orphan or weak pages and add relevant internal links from hubs, related pages, and contextual sections.
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.
Sitemap Freshness Check
Verify that important public pages are present in sitemap.xml with canonical URLs and reasonable lastmod values.
Kickoff preview
Fetch sitemap.xml, compare it against expected public URLs, check exclusions, patch the generator, and re-fetch until coverage is correct. Goal: Ensure sitemap.xml includes canonical public pages and excludes private/admin/API routes. Check command: curl -sL $SITE_URL/sitemap.xml Exit condition: Sitemap contains important public URLs and excludes private/API/admin pages. Max iterations: 3 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 include private, admin, API, or duplicate query URLs in sitemap.
FAQ Schema Verification Loop
Ensure FAQ content is visible on the page and structured data matches the rendered questions and answers.
Kickoff preview
Verify visible FAQ content and JSON-LD structured data match exactly. Fix mismatches and avoid marking up hidden content. Goal: Keep FAQ structured data accurate and visible. Check command: curl -sL $URL | rg "application/ld\+json|FAQPage" Exit condition: FAQ JSON-LD matches visible questions and answers on the page. Max iterations: 3 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 mark up hidden, misleading, or unrelated FAQ content.
Thin Content Expansion Loop
Find pages with shallow content and expand them with practical examples, source context, FAQs, and related loops.
Kickoff preview
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.
Why this category matters
SEO loops are useful because AI agents need explicit feedback gates and exit criteria. A plain prompt may produce a first draft; a loop tells the agent how to verify progress, handle failures, and stop with evidence.