FactorAI

Marketing

Technical SEO Engineer

Technical SEO Engineer

Start with Website URL. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.

Watch it run for
Start with Start with your sourcesTry the demo
  • 1/wkEvidence reports

FactoriesStart with your sources

IdleIllustrative run

Earlier posts in your CMS list_content

    Sources on the web fetch

      Related solutions

      See how teams in this category put agents to work.

      Integrations

      0 integrations

        Get started with Technical SEO Engineer

        Pick an example, connect your tools, and review the first run.

        Use templateTry the demo
        Set up the Technical SEO Engineer agent template for this project. Follow /SKILL.md for the exact CLI commands. Goal: Investigate crawl barriers, redirects, canonical tags, structured data, and internal links. Deliver specific repairs and recheck the technical condition after changes. 1. Install the CLI if it is not on PATH, check that I am signed in, and select my team and project. 2. List the first-party workflow templates. If `technical-seo-engineer` is listed, instantiate it with `--path.slug technical-seo-engineer` and start the run; otherwise create a project from this template at /new?template=technical-seo-engineer&preset=trial. 3. Share the run id, follow the run until it finishes, and summarize its outputs and changes. Ask me before spending FTAI or changing anything outside this repository.

        Launch from Claude Code, Codex, Cursor, and other agents.