Frame the request
Define the user intent and evaluate whether an existing page already satisfies it
Marketing · Specialized agent role
SEO Agent
The SEO Agent turns search questions, site context, and approved business priorities into page briefs and technical review queues without promising rankings.
Best for
- Content teams mapping real audience questions to useful pages and internal-link opportunities
- Website owners reviewing metadata, headings, indexability, duplication, and content gaps at scale
Typical inputs
- Target audience, business topics, query research, existing pages, conversion goals, and brand constraints
- Crawl exports, titles, descriptions, headings, canonicals, internal links, indexability, and performance context
Input quality determines output quality. Source permissions, retention, and field-level access should be settled before the workflow begins.
Core workflow
Each stage has a defined purpose, visible evidence, and a named owner for exceptions.
Gather context
Group related queries by topic, journey stage, evidence needs, and suitable page type
Prepare the work
Prepare a brief or audit finding with recommended structure, metadata, and contextual links
Review and hand off
Send content strategy and technical changes to SEO, editorial, and engineering owners for review
Actions it can perform
- Cluster query themes, map intent to URLs, draft briefs, and inspect common on-page signals
- Identify duplicate intent, thin coverage, weak linking, metadata issues, and potential crawl inconsistencies
Actions should be restricted to the systems, records, and channels required for this role. Broader access is not a substitute for a well-designed workflow.
Outputs
- Intent map, content brief, page recommendation, metadata draft, heading outline, and internal-link plan
- Prioritized audit queue with affected URL, issue, evidence, likely impact, and responsible owner
Every output should make its status clear: prepared, awaiting approval, completed under policy, or escalated with an explanation.
Role-specific configuration details
Use these role-specific terms to make the implementation brief concrete: resolve the relevant definitions, permissions, routes, and exception conditions before the role touches live work.
- turns-search
- search-questions
- questions-site
- business-priorities
- page-briefs
- queues-without
- without-promising
- promising-rankings
- rankings-make
- make-search
- search-planning
- page-quality
- quality-more
- more-systematic
- keeping-strategy
- strategy-expertise
- expertise-content
- content-truth
- technical-changes
- specialist-control
- control-target
- target-audience
- audience-business
- business-topics
- topics-query
- query-research
- research-existing
- existing-pages
- pages-conversion
- conversion-goals
- brand-constraints
- constraints-crawl
- crawl-exports
- exports-titles
- titles-descriptions
- descriptions-headings
- headings-canonicals
- canonicals-internal
- internal-links
- links-indexability
- user-intent
- evaluate-whether
- existing-page
- page-already
- already-satisfies
- group-related
- related-queries
- topic-journey
- journey-stage
- stage-evidence
- evidence-needs
- suitable-page
- page-type
- type-prepare
- audit-finding
- recommended-structure
Human approval and escalation
Approval boundary
SEO and site owners approve indexability, canonical changes, redirects, page creation, content strategy, and any production modification.
Escalation rule
Conflicting intent, migration risk, legal content, unverifiable expertise, unusual crawl behavior, and sitewide changes go to specialists.
What remains under human control
- SEO specialists define research methods, page intent, quality thresholds, indexability policy, and technical priorities
- Editors and engineers verify usefulness, expertise, accuracy, implementation risk, and whether a change should ship
Teams should review permissions and outcomes over time, especially when policies, data sources, responsibilities, or customer expectations change.
Recommended integrations
Connections are workflow building blocks, not proof of automatic availability. Confirm authentication, permissions, supported actions, and error handling during implementation.
Example workflow
A cluster of reporting queries is compared with existing pages; the agent recommends one stronger guide and internal links instead of creating overlapping pages.
The implementation should record the source, owner, decision boundary, and recovery route for each important stage. That makes the workflow easier to review and improve without hiding responsibility.
Related agents
Use related roles only when responsibility and handoff boundaries are genuinely distinct.
Content Writer Agent
See the responsibilities, controls, and handoffs for this related specialist role.
Explore Content Writer AgentCompetitor Research Agent
See the responsibilities, controls, and handoffs for this related specialist role.
Explore Competitor Research AgentMarketing Agent
See the responsibilities, controls, and handoffs for this related specialist role.
Explore Marketing AgentRelated use cases
Explore outcome-led workflows that can combine this role with approved systems and human review.
Create Marketing Content
Understand how this role can contribute to a broader outcome-led workflow.
Explore Create Marketing ContentResearch Competitors
Understand how this role can contribute to a broader outcome-led workflow.
Explore Research CompetitorsQuestions about this role
Does this role guarantee higher search rankings?
No. It supports research and page quality work; search performance depends on many factors outside any agent’s control.
Design a responsible SEO Agent workflow
Define the sources, controls, connected tools, exceptions, and owners before implementation.