From fbc8661e6d2f5ebe96cfa6d8f239f37e5fdbcaae Mon Sep 17 00:00:00 2001
From: yinnho <163239465+yinnho@users.noreply.github.com>
Date: Tue, 25 Aug 2026 19:14:58 +0800
Subject: [PATCH] Add curated topic definition for browser-automation

---
 topics/browser-automation/index.md | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 topics/browser-automation/index.md

diff --git a/topics/browser-automation/index.md b/topics/browser-automation/index.md
new file mode 100644
index 00000000000..30e7d4ec3ea
--- /dev/null
+++ b/topics/browser-automation/index.md
@@ -0,0 +1,10 @@
+---
+display_name: Browser Automation
+topic: browser-automation
+aliases: web-automation, browser-testing
+related: headless-browser, web-scraping, puppeteer, playwright, selenium, mcp
+short_description: Browser automation drives a web browser programmatically to test, scrape, and interact with websites.
+---
+Browser automation controls a web browser through code to perform tasks a person would otherwise do by hand: navigating, clicking, filling forms, and reading the resulting pages. It underpins end-to-end testing, web scraping, and agent-driven browsing.
+
+The field spans browser-level protocols such as the Chrome DevTools Protocol and WebDriver, higher-level libraries such as Puppeteer and Playwright, and purpose-built headless engines exposed over HTTP or MCP.