For QA engineers and automation builders
Get ranked, stable selectors for every element on a page
Get every element on the rendered page with ranked selector candidates, from test IDs to roles and names.
The problem
A test written against .btn-3a7f breaks the next time the styles are rebuilt. Writing good locators means opening the developer tools for every element and guessing which attribute will still be there next month.
How domscout handles it
A semantic snapshot lists the page's elements with their role, accessible name, text and form state, and gives each one ranked selector candidates: CSS, XPath, text, ARIA role and name, ID, name, label and test ID. stableKey identifies an element by persistent attributes or its position in the structure rather than its text, so it survives copy changes. Use the snapshot to choose locators, then use them as action targets, where a locator that matches nothing or more than one element fails with its own code.
Where it shows up
- Seeding a new end-to-end suite with locators.
- Choosing selectors for a scraper or an extract request.
- Finding elements that lack a test ID or an accessible name.
The request
POST /scrape. semanticSnapshot starts at Pro, and each page costs 2 credits. Through the MCP server, domscout_inspect_page gives an assistant the same snapshot before it automates a page.
Go further
More in Testing and QA: Responsive layout checks · Visual regression testing · JavaScript error checks · Signup and checkout flow checks · Hover, focus and dark mode screenshots · Localization screenshots · Unlabelled control checks · A screenshot of every step · Embedded widget checks · Screenshots for support tickets · Ad landing page checks · Before and after hydration · Print layout checks · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.