A: Great questions! Let me address each one for your SEO use case.

Q1: Deep Crawling - Entire Domain/Sitemap.xml?
⚠️ Partial support - with limitations.
What BrowserAct CAN do:
✅ Extract URLs from sitemap.xml
✅ Use Loop List to crawl multiple pages
✅ Follow internal links within a site
What it CANNOT do automatically:
❌ Recursive domain-wide crawling (like Screaming Frog)
❌ Directly ingest sitemap.xml and auto-crawl all pages
Current approach:
1. Navigate to sitemap.xml
2. Extract all URLs
3. Loop List through URLs
4. Scrape each page
Or use API + external scheduler for large-scale crawling.
For true recursive crawling - traditional crawlers (Screaming Frog, Sitebulb) may be better suited.

Q2: Pre-built SEO Audit Template?
⏳ Not currently available, but can be built.
Check our templates: https://www.browseract.com/template
Currently available SEO-related capabilities:

Extract page titles
Extract meta descriptions
Extract H1, H2, H3 tags
Export to JSON

You would need to build a custom workflow to extract:

Title tags
Meta descriptions/keywords
H-tags (H1-H6)
Canonical URLs
Open Graph tags

We can help you build this - join Discord and we'll create an SEO audit template with you.

Q3: View Source Code & Extract JSON-LD Schema?
⚠️ Limited support.
What BrowserAct is designed for:
✅ Extract visible rendered content (text, data displayed on page)
✅ Extract metadata visible in HTML (titles, meta tags)
What BrowserAct is NOT designed for:
❌ Extract raw HTML source code
❌ Read script tags or JSON-LD schema directly
❌ Parse HTML structure programmatically
Why: BrowserAct mimics human browsing - extracts what users see, not page source.
For raw HTML and schema extraction:

Traditional HTTP requests (Python requests, curl)
Specialized SEO tools (Screaming Frog, Sitebulb)

Honest Assessment for Your SEO Use Case:
BrowserAct strengths:
✅ Extract visible on-page content (titles, headings, text)
✅ Good for competitor content analysis
✅ Can extract metadata (titles, meta descriptions)
✅ Handles JavaScript-rendered pages
BrowserAct limitations for SEO:
❌ No recursive site crawling
❌ Cannot extract raw HTML source
❌ Cannot parse JSON-LD schema directly
❌ Not designed for technical SEO audits

Will BrowserAct Replace Your Custom SEO Scrapers?
Probably not entirely - for these reasons:

Deep crawling: BrowserAct requires URL lists, not automatic discovery
Source code analysis: BrowserAct extracts rendered content, not raw HTML
Schema markup: Cannot directly parse JSON-LD

Where BrowserAct CAN help:
✅ Competitor content analysis (visible content, titles, headings)
✅ Manual URL-based audits (with URL lists)
✅ On-page SEO elements (titles, meta, headings)
For comprehensive technical SEO crawling - keep your custom scrapers or use specialized tools.

Alternative Approach:
Hybrid solution:
Traditional crawler (get all URLs + HTML)
↓
BrowserAct (extract rendered content for specific pages)
↓
Your analysis tools
Use BrowserAct for specific competitor analysis tasks, not full-site technical audits.

Summary:

Deep crawling: Limited - no automatic recursive crawling
SEO template: Not pre-built (can be custom-built)
Source code/Schema: Not supported - extracts rendered content only

BrowserAct is NOT a replacement for technical SEO crawlers like Screaming Frog.
Good for: Competitor content analysis, visible SEO elements
Not ideal for: Full-site technical SEO audits, schema extraction, recursive crawling

Want to Discuss Your Specific Needs?
💬 Discord: https://discord.com/invite/UpnCKd7GaU
We can help determine if BrowserAct fits your workflow or suggest better alternatives.
Claire & the BrowserAct Team