Explore SEOForge

Legal · effective 20 July 2026

Use automation to operate authorized websites—not to manufacture deception or bypass controls.

This policy applies to SEOForge accounts, agents, APIs, CLI, MCP, webhooks and connected providers. It supplements the Terms and does not reduce your responsibility to follow law and third-party terms.

Nothing publishes without approvalPaid product accessNo ranking guarantees

Core rule

Use only systems and data you are authorized to access, for lawful and non-deceptive purposes.

Prohibited conduct

The following uses are not allowed.

Access and security

  • Accessing sites, repositories, accounts or data without authority
  • Circumventing authentication, rate limits, robots rules or provider protections
  • Entering malware, secrets or exploit instructions into production workflows
  • Attempting to obtain another tenant’s data or credentials

Content and manipulation

  • Fabricated reviews, credentials, customer results or citations
  • Impersonation, phishing, fraud or misleading affiliation
  • Mass thin, duplicate, doorway or intentionally deceptive content
  • Copyright, privacy or other rights violations

Platform abuse

  • Disrupting service availability or uncontrolled high-rate requests
  • Using agents to evade human approval or branch/CMS protection
  • Reselling access outside an authorized agreement
  • Reverse engineering where prohibited by law or agreement

High-risk content

Do not use SEOForge as the sole basis for medical, legal, financial, safety-critical or regulated claims. Appropriate qualified review and legal compliance remain required.

Enforcement

Protective action should match the risk.

SEOForge may restrict a workflow, connection or account while investigating suspected abuse; preserve relevant evidence; notify the customer where appropriate; and comply with valid legal obligations. Severe or repeated violations may lead to termination under the Terms.

Paid deployment · human authority

Questions about a planned workflow? Ask before connecting it.

Describe the use case without sending credentials or restricted data.