browse-seo: SEO Audit for AI Agents
Goal
Run a complete on-page SEO audit for a target URL using the browse CLI. Extract technical
SEO signals, analyze them, and produce a report with findings and recommendations.
Step 0: Consider stealth setup (optional)
If the audit target is behind bot detection (Cloudflare, competitor sites), use camoufox:
browse --runtime camoufox --headed goto <url>
For most public pages, the default Chromium runtime is sufficient. Skip unless you hit blocks.
Step 1: Navigate to the target URL
browse goto <url>
browse wait --network-idle
Verify the page loaded. Note any redirects -- redirect chains matter for SEO. If the page
returns 403 or a challenge, switch to camoufox (Step 0).
Step 2: Extract meta tags
browse meta
Returns title, description, canonical, OG tags, Twitter Card, robots, and viewport. Check:
- Title: present, under 60 chars, contains target keywords
- Description: present, 120-160 chars, compelling and unique
- Canonical: present, correct URL (trailing slashes, www vs non-www)
- Robots: no accidental
noindex or nofollow
- Viewport:
width=device-width, initial-scale=1 for mobile
- OG tags:
og:title, og:description, og:image, og:url all present
- Twitter Card:
twitter:card, twitter:title, twitter:description present
Step 3: Check heading structure
browse headings
Returns H1-H6 hierarchy with counts. Check:
- Exactly one H1: multiple H1s dilute the primary topic signal
- H1 matches topic: should contain the primary keyword
- Logical nesting: H2 under H1, H3 under H2 -- no skipped levels
- Keyword presence: target keywords in H1 and H2 tags
Step 4: Extract structured data
browse schema
Extracts JSON-LD, Microdata, and RDFa from the page. Check:
- Presence: at least one schema type (Article, Product, Organization, etc.)
- Required properties: each type needs required fields per Google's docs
- Valid JSON-LD: no syntax errors or malformed objects
- Correct @type: matches actual page content
- Missing opportunities: FAQ, HowTo, Breadcrumb, Review where content supports it
Step 5: Check performance
browse perf
Returns navigation timing (DNS, TTFB, DOM load, full load). Check:
- TTFB: under 200ms good, over 600ms problem
- DOM Content Loaded: under 1.5s acceptable
- Full load: under 3s for good UX
- DNS: near zero with proper prefetching
Use browse network to inspect render-blocking resources, large assets, and request counts.
Step 6: Analyze link structure
browse links
Returns all anchor elements with text and href. Check:
- Internal links: sufficient linking for crawlability
- Anchor text: descriptive, not "click here" or bare URLs
- External links: appropriate outbound links, nofollow where needed
- Broken links: anything pointing to 404 or error pages
Step 7: Check mobile rendering
browse responsive
Captures screenshots at mobile (375px), tablet (768px), and desktop (1440px). Review for:
- Mobile layout: no horizontal scrolling, readable without zooming
- Tap targets: 48px minimum for touch
- Content parity: mobile has same critical content as desktop
- Font size: 16px minimum base font
Use browse screenshot for a single full-page capture if needed.
Step 8: Custom checks via JavaScript
Run targeted checks the built-in commands do not cover:
# Image alt tags
browse js "const imgs=[...document.querySelectorAll('img')]; const missing=imgs.filter(i=>!i.alt&&!i.getAttribute('role')); JSON.stringify({total:imgs.length,missingAlt:missing.length,examples:missing.slice(0,5).map(i=>i.src.slice(-60))})"
# Duplicate meta tags
browse js "JSON.stringify({titles:document.querySelectorAll('title').length,descriptions:document.querySelectorAll('meta[name=description]').length,canonicals:document.querySelectorAll('link[rel=canonical]').length})"
# Hreflang tags
browse js "JSON.stringify([...document.querySelectorAll('link[rel=alternate][hreflang]')].map(t=>({lang:t.hreflang,href:t.href})))"
# Lazy images without dimensions
browse js "const lazy=[...document.querySelectorAll('img[loading=lazy]')]; const noDims=lazy.filter(i=>!i.width&&!i.height&&!i.getAttribute('width')); JSON.stringify({lazyImages:lazy.length,missingDimensions:noDims.length})"
Check robots.txt and sitemap:
browse goto <origin>/robots.txt
browse text
browse goto <origin>/sitemap.xml
browse text
Step 9: Generate the audit report
After collecting data from Steps 2-8, produce a structured report:
- Summary: one-paragraph overview with pass/fail/warning counts
- Meta Tags: title, description, canonical, robots, OG, Twitter -- each rated
- Heading Structure: H1 count, nesting issues, keyword presence
- Structured Data: schema types found, missing opportunities, validation issues
- Performance: TTFB, load times, blocking resources
- Link Analysis: internal/external ratio, broken links, anchor text quality
- Mobile Friendliness: viewport tag, responsive screenshots, tap target issues
- Images: alt tag coverage, lazy loading, dimension attributes
- Recommendations: prioritized fixes (critical, important, nice-to-have)
Rate each section as PASS, WARNING, or FAIL. Prioritize recommendations by impact.
Important Rules
- The browser persists between commands. Cookies, tabs, and session state carry over.
- After
goto, always wait --network-idle before extracting data.
- The agent interprets all results. Browse extracts raw data; analysis is your job.
- Do not install anything automatically.
- Save screenshots under
.browse/ directories.
- For sites that block bots, use
--runtime camoufox --headed.
1---
2name: browse-seo
3version: 1.0.0
4description: |
5 Run a full on-page technical SEO audit from a LIVE render — real rendered signals, not source
6 guesses — extracting meta tags, heading hierarchy, structured data, navigation timing, link
7 structure, and multi-viewport mobile rendering via the `browse` CLI (meta/headings/schema/perf/
8 links/responsive plus targeted JS checks), then rating each area PASS/WARNING/FAIL with prioritized
9 fixes. The agent interprets the raw signals browse extracts; no scores are invented. Use to audit a
10 page's technical/on-page SEO health.
11allowed-tools:
12 - Bash
13 - Read
14argument-hint: "[URL to audit]"
15arguments:
16 - request
17when_to_use: |
18 Use when the user wants an SEO audit, on-page/technical SEO review, or checks of meta tags, schema,
19 headings, Open Graph/Twitter cards, mobile-friendliness, or Core Web Vitals. Examples: "SEO audit
20 this URL", "check my meta tags and schema". Do NOT use for AI-answer optimization or citation
21 visibility (browse-aeo for one page, browse-geo for cross-engine monitoring), or general browsing
22 and form-filling (browse); this covers classic ranking signals, not AI-answer presence.
23effort: medium
24metadata:
25 source: https://skillmd.com/skills/ulpi-io/browse-seo
26---
27
28# browse-seo: SEO Audit for AI Agents
29
30## Goal
31
32Run a complete on-page SEO audit for a target URL using the `browse` CLI. Extract technical
33SEO signals, analyze them, and produce a report with findings and recommendations.
34
35## Step 0: Consider stealth setup (optional)
36
37If the audit target is behind bot detection (Cloudflare, competitor sites), use camoufox:
38
39```bash
40browse --runtime camoufox --headed goto <url>
41```
42
43For most public pages, the default Chromium runtime is sufficient. Skip unless you hit blocks.
44
45## Step 1: Navigate to the target URL
46
47```bash
48browse goto <url>
49browse wait --network-idle
50```
51
52Verify the page loaded. Note any redirects -- redirect chains matter for SEO. If the page
53returns 403 or a challenge, switch to camoufox (Step 0).
54
55## Step 2: Extract meta tags
56
57```bash
58browse meta
59```
60
61Returns title, description, canonical, OG tags, Twitter Card, robots, and viewport. Check:
62
63- **Title**: present, under 60 chars, contains target keywords
64- **Description**: present, 120-160 chars, compelling and unique
65- **Canonical**: present, correct URL (trailing slashes, www vs non-www)
66- **Robots**: no accidental `noindex` or `nofollow`
67- **Viewport**: `width=device-width, initial-scale=1` for mobile
68- **OG tags**: `og:title`, `og:description`, `og:image`, `og:url` all present
69- **Twitter Card**: `twitter:card`, `twitter:title`, `twitter:description` present
70
71## Step 3: Check heading structure
72
73```bash
74browse headings
75```
76
77Returns H1-H6 hierarchy with counts. Check:
78
79- **Exactly one H1**: multiple H1s dilute the primary topic signal
80- **H1 matches topic**: should contain the primary keyword
81- **Logical nesting**: H2 under H1, H3 under H2 -- no skipped levels
82- **Keyword presence**: target keywords in H1 and H2 tags
83
84## Step 4: Extract structured data
85
86```bash
87browse schema
88```
89
90Extracts JSON-LD, Microdata, and RDFa from the page. Check:
91
92- **Presence**: at least one schema type (Article, Product, Organization, etc.)
93- **Required properties**: each type needs required fields per Google's docs
94- **Valid JSON-LD**: no syntax errors or malformed objects
95- **Correct @type**: matches actual page content
96- **Missing opportunities**: FAQ, HowTo, Breadcrumb, Review where content supports it
97
98## Step 5: Check performance
99
100```bash
101browse perf
102```
103
104Returns navigation timing (DNS, TTFB, DOM load, full load). Check:
105
106- **TTFB**: under 200ms good, over 600ms problem
107- **DOM Content Loaded**: under 1.5s acceptable
108- **Full load**: under 3s for good UX
109- **DNS**: near zero with proper prefetching
110
111Use `browse network` to inspect render-blocking resources, large assets, and request counts.
112
113## Step 6: Analyze link structure
114
115```bash
116browse links
117```
118
119Returns all anchor elements with text and href. Check:
120
121- **Internal links**: sufficient linking for crawlability
122- **Anchor text**: descriptive, not "click here" or bare URLs
123- **External links**: appropriate outbound links, nofollow where needed
124- **Broken links**: anything pointing to 404 or error pages
125
126## Step 7: Check mobile rendering
127
128```bash
129browse responsive
130```
131
132Captures screenshots at mobile (375px), tablet (768px), and desktop (1440px). Review for:
133
134- **Mobile layout**: no horizontal scrolling, readable without zooming
135- **Tap targets**: 48px minimum for touch
136- **Content parity**: mobile has same critical content as desktop
137- **Font size**: 16px minimum base font
138
139Use `browse screenshot` for a single full-page capture if needed.
140
141## Step 8: Custom checks via JavaScript
142
143Run targeted checks the built-in commands do not cover:
144
145```bash
146# Image alt tags
147browse js "const imgs=[...document.querySelectorAll('img')]; const missing=imgs.filter(i=>!i.alt&&!i.getAttribute('role')); JSON.stringify({total:imgs.length,missingAlt:missing.length,examples:missing.slice(0,5).map(i=>i.src.slice(-60))})"
148
149# Duplicate meta tags
150browse js "JSON.stringify({titles:document.querySelectorAll('title').length,descriptions:document.querySelectorAll('meta[name=description]').length,canonicals:document.querySelectorAll('link[rel=canonical]').length})"
151
152# Hreflang tags
153browse js "JSON.stringify([...document.querySelectorAll('link[rel=alternate][hreflang]')].map(t=>({lang:t.hreflang,href:t.href})))"
154
155# Lazy images without dimensions
156browse js "const lazy=[...document.querySelectorAll('img[loading=lazy]')]; const noDims=lazy.filter(i=>!i.width&&!i.height&&!i.getAttribute('width')); JSON.stringify({lazyImages:lazy.length,missingDimensions:noDims.length})"
157```
158
159Check robots.txt and sitemap:
160
161```bash
162browse goto <origin>/robots.txt
163browse text
164browse goto <origin>/sitemap.xml
165browse text
166```
167
168## Step 9: Generate the audit report
169
170After collecting data from Steps 2-8, produce a structured report:
171
1721. **Summary**: one-paragraph overview with pass/fail/warning counts
1732. **Meta Tags**: title, description, canonical, robots, OG, Twitter -- each rated
1743. **Heading Structure**: H1 count, nesting issues, keyword presence
1754. **Structured Data**: schema types found, missing opportunities, validation issues
1765. **Performance**: TTFB, load times, blocking resources
1776. **Link Analysis**: internal/external ratio, broken links, anchor text quality
1787. **Mobile Friendliness**: viewport tag, responsive screenshots, tap target issues
1798. **Images**: alt tag coverage, lazy loading, dimension attributes
1809. **Recommendations**: prioritized fixes (critical, important, nice-to-have)
181
182Rate each section as PASS, WARNING, or FAIL. Prioritize recommendations by impact.
183
184## Important Rules
185
186- The browser persists between commands. Cookies, tabs, and session state carry over.
187- After `goto`, always `wait --network-idle` before extracting data.
188- The agent interprets all results. Browse extracts raw data; analysis is your job.
189- Do not install anything automatically.
190- Save screenshots under `.browse/` directories.
191- For sites that block bots, use `--runtime camoufox --headed`.