Copy, localization & SEO · Improve

Improve SEO GEO

Correct the selected public content or crawl/metadata defect using its maintained source. Preserve product truth, locale ownership and the site’s actual rendering/deployment model.

MCP library 1.6.1 · Instruction library 1.6.1 · English technical instructions

← Back to search

Use this workflow

Connect Vibe Coding Library to a coding agent that supports MCP over Streamable HTTP. Choose Other / MCP agent for a neutral prompt, or a ready-made Codex or Claude Code invocation. Add your task details below.

Scope

Correct the selected public content or crawl/metadata defect using its maintained source. Preserve product truth, locale ownership and the site’s actual rendering/deployment model.

Procedure

  1. Establish the affected route, user purpose and expected public output. Select changes supported by the observed defect or requested content goal.
  2. Align visible copy, titles/descriptions, canonical/language alternatives, internal links and sitemap with actual published pages.
  3. Add or repair structured data only for represented entities and supported features; keep it consistent with visible content.
  4. Make important content available through the framework’s suitable server/static path where needed. Do not introduce hidden keywords, doorway pages, fake ratings or unsupported product claims.
  5. Update directly affected generators, translations and verification. Avoid a visual redesign, analytics setup or platform migration unless required by the request.

Verification

Build and inspect the affected output: status, content, head metadata, links, locale alternatives and applicable schema. Check the deployed artifact when deployment is authorized. Report measured results and unverified indexing/citation or real-user performance separately. Use current Google AI-search guidance; special files or phrasing do not guarantee visibility.

Re-fetch the same affected route and its relevant redirect/locale peers after the maintained-source correction. Reconcile visible claims, structured metadata and canonical/sitemap targets against that output. A failed route or mismatch returns to its generator/rendering owner, followed by the same check and Patch Checking for the change. Do not tune copy or add hidden markup merely to obtain an unsupported visibility claim.

Workflow ID: seo-geo-polish · View the versioned source · Shared workflow and authority rules