Agent skill

Browser4 SEO

Extract and audit SEO metadata from the current browser page.

Apache-2.0Auto-check passedMarketing & SEO

Install Browser4 SEO

skills CLI

$ npx skills add platonai/Browser4 --skill browser4-seo -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 browser4-seo --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/browser4-seo .claude/skills/browser4-seo && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "browser4-seo" agent skill from https://github.com/platonai/Browser4/tree/main/skills/browser4-seo into .claude/skills/browser4-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser4-seo", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/platonai/Browser4/tree/main/skills/browser4-seo

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add platonai/Browser4 --skill browser4-seo -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 browser4-seo --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/browser4-seo .agents/skills/browser4-seo && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "browser4-seo" agent skill from https://github.com/platonai/Browser4/tree/main/skills/browser4-seo into .agents/skills/browser4-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser4-seo", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add platonai/Browser4 --skill browser4-seo -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 browser4-seo --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/browser4-seo .cursor/skills/browser4-seo && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "browser4-seo" agent skill from https://github.com/platonai/Browser4/tree/main/skills/browser4-seo into .cursor/skills/browser4-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser4-seo", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/platonai/Browser4.git --path skills/browser4-seo

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add platonai/Browser4 --skill browser4-seo -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 browser4-seo --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/browser4-seo .gemini/skills/browser4-seo && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "browser4-seo" agent skill from https://github.com/platonai/Browser4/tree/main/skills/browser4-seo into .gemini/skills/browser4-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser4-seo", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install platonai/Browser4 browser4-seo

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add platonai/Browser4 --skill browser4-seo -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/browser4-seo .github/skills/browser4-seo && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "browser4-seo" agent skill from https://github.com/platonai/Browser4/tree/main/skills/browser4-seo into .github/skills/browser4-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser4-seo", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add platonai/Browser4 --skill browser4-seo -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install platonai/Browser4 browser4-seo --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/browser4-seo .opencode/skills/browser4-seo && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "browser4-seo" agent skill from https://github.com/platonai/Browser4/tree/main/skills/browser4-seo into .opencode/skills/browser4-seo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser4-seo", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: browser4-seo
GitHub stars: 1.2k
Token cost: ~1.6k tokens
SKILL.md length: 594 words
Files: 1
Skills in repo: 17
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Extract and audit SEO metadata from the current browser page.

Works in 3 steps: Quick SEO health check → Full metadata extraction → Diagnose poor ranking
The user wants to check a pages SEO health
SKILL.md covers Quick Start, When to Use, How It Works and Patterns, plus 6 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Browser4 SEO is an agent skill from platonai/Browser4. Extract and audit SEO metadata from the current browser page. Use when the user wants to check a page's SEO health, review meta tags, Open Graph, Twitter Cards, canonical links, structured data (JSON-LD), or diagnose why a page ranks poorly.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering SEO audit, Schema markup and On-page SEO. It works with X (Twitter). The repository describes itself as: Browser4 — an AI-native browser engine for autonomous agents, intelligent extraction, and large-scale web automation. The licence is Apache-2.0.

When your agent uses it

The user wants to check a pages SEO health
Review meta tags
Canonical links
Structured data (JSON-LD)

Example prompts

“/browser4-seo”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Quick SEO health check
Full metadata extraction
Diagnose poor ranking

What it can do on your machine

Read from SKILL.md and the folder at commit 0fdba82. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Browser4 SEO loads about 1.6k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 594 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~64
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from platonai/Browser4 at commit 0fdba82, republished under its Apache-2.0 licence (© platonai). 594 words, ~1,570 tokens.

Download SKILL.mdSave it as .claude/skills/browser4-seo/SKILL.md (or your agent's skills folder).

name: browser4-seo
description: Extract and audit SEO metadata from the current browser page. Use when the user wants to check a page's SEO health, review meta tags, Open Graph, Twitter Cards, canonical links, structured data (JSON-LD), or diagnose why a page ranks poorly.
title: Browser4 SEO
tier: procedure

Browser4 SEO

Quick Start

bash

browser4-cli goto "https://example.com"     # load the page to audit
browser4-cli plugin-list                    # confirm browser4-seo is installed AND enabled
# then call seo.extractMeta() — full SEO metadata extraction (see Tools below)

Extract and audit SEO metadata from the current page using the browser4-seo plugin's two tools.

When to Use

Use this skill when the user wants to:

Check a page's SEO health — "audit the SEO of this page", "is this page SEO-friendly?"
Review meta tags — "what's the title/description/canonical of this page?"
Check Open Graph / Twitter Card — "does this page have proper social share tags?"
Review structured data — "does this page have JSON-LD schema markup?"
Diagnose ranking problems — "why isn't this page ranking?" (SEO issues are a common cause)

Do NOT use this skill for:

General content extraction — use the browser4-cli HTML snapshot / X-SQL instead.
Performance auditing (Core Web Vitals) — this plugin only covers SEO metadata, not performance metrics.

How It Works

The browser4-seo plugin exposes two tools that operate on the page currently loaded in the browser session: seo.extractMeta() returns every SEO metadata field (title, description, canonical, Open Graph, Twitter Cards, JSON-LD), and seo.checkIssues() compares the page against SEO best practices and returns a health report.

Patterns

1. Quick SEO health check

text

seo.checkIssues()   # returns a prioritized issue list

2. Full metadata extraction

text

seo.extractMeta()   # all fields: title, description, canonical, OG, Twitter, JSON-LD

3. Diagnose poor ranking

text

seo.checkIssues()   # start with the issue report, then fix the top items

Flags

Neither seo.extractMeta() nor seo.checkIssues() takes arguments — both operate on the page currently loaded in the browser session.

Errors & Recovery

Symptom	Cause	Fix
Tool call fails with "plugin not found"	`browser4-seo` not installed	`browser4-cli plugin-list`; install the plugin
Plugin installed but `seo.*` tools unavailable	Plugin is opt-in (default-disabled)	Enable it: `browser4.plugins.enable=browser4-seo` (or `browser4.plugins.enable-all=true`) and restart
`extractMeta` returns empty fields	No page loaded in the session	`browser4-cli goto <url>` first
`checkIssues` reports everything missing	Page is a JS shell	The plugin reads the loaded DOM — ensure the page finished rendering

Prerequisites

The browser4-seo plugin must be installed AND enabled on the Browser4 server. The plugin is opt-in (defaultEnabled: false): installing the JAR alone does not activate it. Enable it with browser4.plugins.enable=browser4-seo (or browser4.plugins.enable-all=true) and restart. Check with:

bash

browser4-cli plugin-list
# Look for "browser4-seo" in the output

If not installed, see the plugin's README for build and deploy instructions.

Tools

Show full SKILL.md (272 more words)Show less

`seo.extractMeta()`

Extracts all SEO metadata from the current page. No arguments — operates on the page currently loaded in the browser session.

Returns a JSON object with fields:

Field	Type	Description
`url`	String	Final page URL (after redirects)
`title`	String?	`<title>` content
`description`	String?	`<meta name="description">`
`canonical`	String?	`<link rel="canonical">` href
`robots`	String?	`<meta name="robots">` content
`og`	Object	All Open Graph tags (`og:title`, `og:image`, etc.)
`twitter`	Object	All Twitter Card tags
`headings`	Object	Count of h1/h2/h3/h4
`images`	Int	Total `<img>` count
`imagesWithoutAlt`	Int	Images missing `alt` attribute
`wordCount`	Int	Approximate body word count
`jsonLd`	Array	Parsed JSON-LD structured data blocks

`seo.checkIssues()`

Audits the page and returns a categorized list of SEO issues.

Returns a JSON object with:

Field	Type	Description
`issueCount`	Int	Total issues found
`errorCount`	Int	Critical issues (e.g., noindex, no title)
`warningCount`	Int	Important issues (e.g., no canonical, thin content)
`infoCount`	Int	Minor issues (e.g., no Twitter Card)
`issues`	Array	Each issue: `{ severity, field, message, value }`

Severity levels: error (must fix) > warning (should fix) > info (nice to have).

Workflow

Example 1: Quick SEO audit

1. Navigate to the target page (browser4-cli navigate <url>)
2. seo.checkIssues()                      → get the issue list with severity
3. Summarize errors first, then warnings
4. If user wants detail on a specific field → seo.extractMeta()

Example 2: Full metadata review

1. Navigate to the target page
2. seo.extractMeta()                      → full metadata object
3. Present: title, description, canonical, OG, Twitter, JSON-LD
4. Flag any missing or suspicious values

Example 3: Compare before/after a fix

1. seo.checkIssues()                      → baseline (note error/warning counts)
2. (user or agent fixes the page source)
3. Refresh the page
4. seo.checkIssues()                      → compare counts to verify the fix

This last workflow is the browser-first feedback loop: change code → refresh → re-audit → confirm.

Tips

Always run seo.checkIssues() first — it gives a quick summary. Use seo.extractMeta() only when you need the raw values.
The noindex robots directive is an error-level issue — flag it immediately, as it blocks the page from search engines entirely.
imagesWithoutAlt > 0 is common but easy to fix — suggest adding alt text.
JSON-LD count of 0 is only info severity — not all pages need structured data, but e-commerce and article pages benefit from it.

Files

Just SKILL.md in skills/browser4-seo of platonai/Browser4.

Open the folder on GitHubat commit 0fdba82

Compare with similar skills

Browser4 SEO next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Browser4 SEO compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Browser4 SEO this skillplatonai/Browser4	1.2k	—	~1.6k	Automated safety check: Pass	Apache-2.0	yesterday
SEO Optimizerailabs-393/ai-labs-claude-skills	454	1 repos	~3.2k	Automated safety check: Pass	MIT	11 mo ago
Single-Page SEO Auditnowork-studio/notfair-plugin	3.9k	1 repos	~5k	Automated safety check: Pass	MIT	8 days ago
SEO PageAgriciDaniel/codex-seo	791	5 repos	~1.2k	Automated safety check: Pass	MIT	27 days ago
Universal SEO AnalysisAgriciDaniel/claude-seo	18k	—	~4.9k	Automated safety check: Pass	MIT	4 days ago
Single Page SEO AnalysisAgriciDaniel/claude-seo	18k	—	~1.1k	Automated safety check: Pass	MIT	4 days ago

Similar skills

SEO Optimizer
ailabs-393/ai-labs-claude-skills
This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.
454 GitHub starsUsed in 1 repo~3.2k tokens
Marketing & SEOAuto-check passed
Single-Page SEO Audit
nowork-studio/notfair-plugin
Audits one URL for content quality, E-E-A-T, search intent, on-page and technical signals, and produces a scored report with fixes.
3.9k GitHub starsUsed in 1 repo~5k tokens
Marketing & SEOAuto-check passed
SEO Page
AgriciDaniel/codex-seo
Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance.
791 GitHub starsUsed in 5 repos~1.2k tokens
Marketing & SEOAuto-check passed
Universal SEO Analysis
AgriciDaniel/claude-seo
Hub for site-wide SEO work: audits, technical checks, schema, content quality, local, hreflang and AI-search readiness, run through slash commands.
18k GitHub stars~4.9k tokensUpdated 4 days ago
Marketing & SEOAuto-check passed
Single Page SEO Analysis
AgriciDaniel/claude-seo
Reviews one URL for on-page SEO, content quality, technical metadata, schema, images and performance, using concrete length and size thresholds.
18k GitHub stars~1.1k tokensUpdated 4 days ago
Marketing & SEOAuto-check passed
SEO
gridaco/grida
SEO best practices for the Grida project across Next.js pages, blog posts, and documentation.
2.7k GitHub stars~2.1k tokensUpdated yesterday
Marketing & SEOAuto-check passed

Questions about Browser4 SEO

What does Browser4 SEO do?

Extract and audit SEO metadata from the current browser page. Browser4 SEO is an agent skill from platonai/Browser4. Extract and audit SEO metadata from the current browser page.

When should I use Browser4 SEO?

Browser4 SEO fits situations like: the user wants to check a pages SEO health; review meta tags; canonical links; structured data (JSON-LD).

How do I install Browser4 SEO in Claude Code?

Run `npx skills add platonai/Browser4 --skill browser4-seo -a claude-code`. Or copy the skill folder (skills/browser4-seo in platonai/Browser4) into .claude/skills/browser4-seo in your project. Claude Code loads it when a task matches its description.

How do I install Browser4 SEO in Codex?

Run `npx skills add platonai/Browser4 --skill browser4-seo -a codex`. Or copy the skill folder (skills/browser4-seo in platonai/Browser4) into .agents/skills/browser4-seo in your project. Codex loads it when a task matches its description.

Can I use Browser4 SEO in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add platonai/Browser4 --skill browser4-seo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser4-seo, .gemini/skills/browser4-seo, .github/skills/browser4-seo and .opencode/skills/browser4-seo in your project.

What does Browser4 SEO need to run?

SKILL.md names no scripts, command-line tools or credentials: Browser4 SEO is instructions for the agent only.

Does Browser4 SEO access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Browser4 SEO safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Browser4 SEO use?

Browser4 SEO is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Browser4 SEO use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Browser4 SEO?

Skills that share tags, products or a category with Browser4 SEO: SEO Optimizer (ailabs-393/ai-labs-claude-skills, 454 stars), Single-Page SEO Audit (nowork-studio/notfair-plugin, 3.9k stars), SEO Page (AgriciDaniel/codex-seo, 791 stars) and Universal SEO Analysis (AgriciDaniel/claude-seo, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Browser4 SEO?

platonai (a GitHub user) maintains it in platonai/Browser4, which has 1,152 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.

Source: platonai/Browser4 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Browser4 SEO

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Browser4 SEO

Quick Start

When to Use

How It Works

Patterns

1. Quick SEO health check

2. Full metadata extraction

3. Diagnose poor ranking

Flags

Errors & Recovery

Prerequisites

Tools

seo.extractMeta()

seo.checkIssues()

Workflow

Example 1: Quick SEO audit

Example 2: Full metadata review

Example 3: Compare before/after a fix

Tips

Files

Compare with similar skills

Similar skills

More from platonai/Browser4

Related

Questions about Browser4 SEO

`seo.extractMeta()`

`seo.checkIssues()`