How the UnifAPI SEO Agent uses live SERP, keyword, competitor, backlink, and rendered-page records to produce cited SEO briefs inside Claude or Codex.

In short: The SEO Agent is built for on-demand, cited SEO work inside an assistant. It pulls live SERP, keyword, competitor, backlink, and rendered-page evidence through UnifAPI instead of forcing every check into a seat-based dashboard.

Most SEO tools assume a human analyst is sitting inside a product dashboard. That is still useful for standing projects, but it is not how an assistant works.

An assistant needs records. It needs to ask: What ranks now? Which features appear? Is the target domain visible? Which competitors show up? What pages win? Which backlinks or ranked keywords explain the gap? What did the page actually render as?

The SEO Agent packages that work into a role you can run inside Claude, Codex, or another MCP-capable assistant.

What the SEO Agent reads

The SEO Agent combines several live record families:

Evidence family	What the agent uses it for
Live SERP records	Organic positions, SERP features, target visibility, competitor domains
Keyword records	Ideas, related queries, overview metrics, history, difficulty, intent
Competitor records	Ranked keywords, relevant pages, historical rank, domain comparisons
Backlink records	Referring domains, anchors, backlinks, new/lost links, spam signals
Browser records	Rendered Markdown or HTML for pages that plain fetch cannot read well

The goal is not to replace human SEO judgment. The goal is to give the assistant enough observable evidence to make a useful brief without pretending memory or search snippets are data.

A copyable run prompt

Use this prompt after connecting UnifAPI MCP:

Track these keywords for example.com in the US market: "public data API", "MCP server for marketing agents", and "SEO API for agents". Return organic positions, AI SERP visibility when available, competing domains, rich SERP features, and the pages that win. Then inspect our strongest relevant page with Browser Markdown and recommend the highest-leverage fix plan. Cite every record used and label recommendations separately from observed facts.

The important pieces are the keyword set, target domain, market, evidence standard, and boundary between facts and recommendations.

The output should be a brief, not a dump

A useful SEO Agent answer should fit into a decision memo:

Section	What it should contain
Executive summary	What changed, what matters, and where the opportunity is
Query table	Keyword, rank, target visibility, features, competitors
Competitor pages	Which pages own the query and why they look strong
Page inspection	Rendered headings, content gaps, internal links, schema notes
Fix plan	3-7 prioritized actions with expected impact and confidence
Source log	Operations, timestamps, and records used

If the answer skips the source log, ask the assistant to rerun with citations. If it invents exact traffic impact, ask it to separate observed rank evidence from inferred business impact.

Where Browser fits

The Browser API is not the headline SEO product, but it is critical in a real audit. Many important pages rely on JavaScript, redirects, client-side content, or components that a simple fetch will miss.

The SEO Agent can use Browser Markdown to read what the page actually renders, Browser HTML to inspect technical structure, Browser links to map crawlable paths, and Browser screenshots when visual proof matters.

That means the SEO brief can connect the SERP to the page:

The target page ranks #8 for a query.
Three competitors rank above it.
The rendered target page lacks a visible comparison section.
The winning competitors answer that comparison directly.
The fix plan recommends a specific page section, not a generic "optimize content" note.

Pricing shape

The SEO Agent uses UnifAPI public-data credits. You already pay for the assistant runtime; UnifAPI bills the records it returns.

That works well for bursty SEO work. An agency can run a 20-keyword audit for a new client, a founder can check launch visibility, and a growth team can inspect a competitor's ranking set without opening another monthly seat.

The assistant should still keep cost visible. For larger keyword sets, ask it to plan first:

Run size	Good behavior
5-20 queries	Fetch directly and report
50-200 queries	Estimate cost and batch
Multi-domain backlink research	Ask for scope, depth, and cap
Ongoing monitoring	Propose a repeatable schedule and record budget

What it should not do

The SEO Agent should not claim it changed your site, submitted a sitemap, edited schema, or accessed Search Console. UnifAPI reads public data. Your assistant can draft fixes and you can execute them with your own tools.

It should also avoid treating one SERP pull as a universal truth. Location, language, device, timing, and personalization can all affect results. The right answer is an evidence-backed snapshot with confidence notes, not a permanent ranking decree.

Primary references

This workflow follows Google's public search guidance rather than private ranking folklore. Use the Google SEO Starter Guide for baseline crawlable, useful-page principles; use Google's JavaScript SEO basics when Browser records reveal client-rendered content; and use Google's structured data introduction plus Schema.org Article when checking page metadata and article entities.

What to read next

SEO, GEO, and Browser as one visibility stack - combines classic search, AI answers, and rendered-page evidence.

AI Visibility Agent for GEO - tracks AI answer citations and LLM mentions.

SEO API catalog - shows the live SEO operations behind the Agent.