From 5af4a42a129a18902e6ad65e7ddd4bfc94f7683c Mon Sep 17 00:00:00 2001 From: Nikola Balic Date: Thu, 30 Jul 2026 14:54:03 +0200 Subject: [PATCH] docs(seo): scope Railway self-hosting page to Steel The page earned 36,672 GSC impressions at 0.05% CTR because Google matched it for Railway-the-platform queries (railway healthcheckpath, railway autoscaling documentation, railway public domain, railway dev, railway web) that Steel can never win. Retarget title and description to self-hosting Steel Browser on Railway, following the intent-phrased convention from #72, and rescope the headings that read as generic Railway platform docs (health check endpoint, public domain access, security considerations). sidebarTitle stays "Railway". --- content/docs/overview/self-hosting/railway.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/content/docs/overview/self-hosting/railway.mdx b/content/docs/overview/self-hosting/railway.mdx index f0bf2918..428999b5 100644 --- a/content/docs/overview/self-hosting/railway.mdx +++ b/content/docs/overview/self-hosting/railway.mdx @@ -1,16 +1,16 @@ --- -title: Railway +title: Self-Host Steel Browser on Railway sidebarTitle: Railway -description: A quick guide on deploying Steel Browser to Railway using our template +description: "Self-host Steel Browser on Railway with our one-click deploy template: launch the container, verify the /v1/health endpoint, and connect over CDP." full: true llm: true --- [Deploy the Template on Railway ↗](https://railway.com/deploy/steelbrowser?referralCode=Jwc4kg&utm_medium=integration&utm_source=template&utm_campaign=generic) ### Overview -Hosting Steel Browser on Railway provides a reliable, scalable environment for running headless Chrome instances. The Steel Browser API handles browser session management, proxy configuration, and CDP passthroughs while Railway provides extremely easy APIs to scale and handles resource allocation automatically. Running Steel Browser on Railway's infrastructure ensures your browser automations run consistently with minimal configuration, while providing automatic scaling and health monitoring for production workloads. +Self-hosting Steel Browser on Railway provides a reliable, scalable environment for running headless Chrome instances. The Steel Browser API handles browser session management, proxy configuration, and CDP passthroughs while Railway provides extremely easy APIs to scale and handles resource allocation automatically. Running Steel Browser on Railway's infrastructure ensures your browser automations run consistently with minimal configuration, while providing automatic scaling and health monitoring for production workloads. -### Common Use Cases +### Common Use Cases for Self-Hosted Steel Browser - **Web Scraping:** Extract data from dynamic websites that require JavaScript rendering - **Browser Automation:** Automate repetitive web tasks and workflows - **End-to-End Testing:** Run automated browser tests for web applications @@ -29,9 +29,9 @@ Hosting Steel Browser on Railway provides a reliable, scalable environment for r ### Implementation Details -**Health Check Endpoint:** +**Steel Browser Health Check Endpoint:** -Verify your instance is running: +Verify your Steel Browser instance is running: ```bash Terminal -wcn curl https://your-domain.railway.app/v1/health @@ -65,16 +65,16 @@ By deploying Steel Browser on Railway, you are one step closer to supporting a c - Simple environment variable management - Seamless integration with other Railway services -### Post-Deployment Notes +### After Deploying Steel Browser After deploying this template, users should: -1. **Access the Instance:** Navigate to the Railway-provided public domain +1. **Access Your Steel Instance:** Navigate to the Railway-provided public domain 2. **Verify Health:** Check the `/v1/health` endpoint returns a successful response 3. **Configure API Access:** Use the public domain URL in their application code 4. **Monitor Usage:** Check Railway's metrics dashboard for resource usage -### Security Considerations: +### Securing Your Steel Browser Instance - Consider adding authentication if exposing publicly - Monitor for unusual traffic patterns - Set up rate limiting if needed for production use