# Website Tech Stack & SEO Snapshot (`parselane/site-snapshot`) Actor Paste URLs, get each site's technology stack (CMS, framework, analytics, CDN, hosting) plus an on-page SEO audit (title, meta, canonical, H1, schema.org, Open Graph, alt text) as clean JSON. Respects robots.txt. You only pay for successful snapshots. - **URL**: https://apify.com/parselane/site-snapshot.md - **Developed by:** [Parselane](https://apify.com/parselane) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.00 / 1,000 url snapshots This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Website Tech Stack & SEO Snapshot Paste a list of URLs. For each one you get the site's **technology stack** and an **on-page SEO audit** as clean JSON, ready for spreadsheets, CRMs or AI agents. - **You only pay for successful snapshots.** URLs that fail (DNS errors, timeouts, blocked by robots.txt) are free. - **Polite by default.** Respects robots.txt, identifies itself, and fetches one page per URL. No login walls, no personal data. - **Fast.** Up to 50 URLs in parallel. ### What you get per URL | Field | Details | |---|---| | `technologies` | CMS (WordPress, Shopify, Webflow, Wix, Framer, Ghost…), frameworks (Next.js, Nuxt, Astro…), analytics (GA4, GTM, Plausible, Hotjar), payments, live chat, CDN and hosting (Cloudflare, Vercel, Netlify, CloudFront, Fastly), web server | | `seo` | title, meta description, canonical, ``, H1s, robots meta, Open Graph, Twitter card, hreflang, schema.org types, internal/external link counts, images missing alt text | | `security` | HSTS, CSP, X-Frame-Options headers | | `issues` | Plain-English list of on-page problems (missing title, several H1s, no canonical, noindex, images without alt…) | | `score` | 0–100 quick health score (100 minus 10 per issue) | | `status`, `responseTimeMs` | HTTP status and response time | ### Example output ```json { "url": "https://www.python.org/", "status": 200, "responseTimeMs": 412, "technologies": [ {"name": "Fastly", "category": "CDN"}, {"name": "Nginx", "category": "Web server"}, {"name": "jQuery", "category": "JS library"} ], "seo": {"title": "Welcome to Python.org", "canonical": null, "h1": ["…"], "schemaTypes": []}, "issues": ["5

tags (expected 1)", "missing canonical link"], "score": 80 } ``` ### Use cases - **Lead qualification:** find which prospects run Shopify, WordPress or a competitor's tool. - **SEO agencies:** bulk on-page checks across client or prospect sites. - **Competitive research:** see what stack competitors use. - **AI agents (MCP):** give an agent a cheap, structured "what is this website?" tool. ### Input ```json { "urls": ["https://example.com", "shopify.com"], "maxUrls": 1000, "concurrency": 10 } ``` Bare domains get `https://` added automatically. ### Pricing Pay per event: **USD 2 per 1,000 successful URLs** (USD 0.002 each), plus a tiny USD 0.00005 start fee per run. Failed URLs cost nothing. Set a maximum charge per run and the Actor stops cleanly when it is reached. ### Limits - Detection reads the HTML and headers of the page you give it. It doesn't run JavaScript, so tools loaded only after client-side rendering may be missed. - Only one page is analysed per URL. Submit several URLs to audit several pages. ### Feedback Missing a technology or found a wrong detection? Open an issue on the **Issues** tab. Fixes usually ship within a few days. # Actor input Schema ## `urls` (type: `array`): Pages to analyse. Bare domains get https:// prepended. ## `maxUrls` (type: `integer`): Safety cap per run. ## `concurrency` (type: `integer`): How many URLs to fetch in parallel. ## Actor input object example ```json { "urls": [ "https://apify.com", "https://vercel.com" ], "maxUrls": 1000, "concurrency": 10 } ``` # Actor output Schema ## `overview` (type: `string`): One row per URL: technologies, SEO score and issues. ## `seo` (type: `string`): Title, meta description, canonical, H1 and schema.org per URL. ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "urls": [ "https://apify.com", "https://vercel.com" ] }; // Run the Actor and wait for it to finish const run = await client.actor("parselane/site-snapshot").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "urls": [ "https://apify.com", "https://vercel.com", ] } # Run the Actor and wait for it to finish run = client.actor("parselane/site-snapshot").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "urls": [ "https://apify.com", "https://vercel.com" ] }' | apify call parselane/site-snapshot --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,parselane/site-snapshot" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/gmns10BNYTIG85acJ/builds/eEIBPkfGLmsRwbwPq/openapi.json