RPA Static Selectors

Stable rpa-id selectors for RPA and automated tests. Choose domains, keep a local registry, and export or import JSON.

RPA Static Selectors adds short rpa-id attributes to page elements on domains you choose. Use these attributes in CSS or XPath selectors for RPA robots and automated tests. For an element with rpa-id="a1", use CSS [rpa-id="a1"] or XPath //*[@rpa-id="a1"]. Features: • An explicit domain allowlist. With an empty list, tagging is disabled. Add subdomains separately. • A local element-to-ID registry retained across browser restarts. • The same live DOM node retains its ID as the interface changes. On later visits, the extension attempts to restore matches using element descriptors. • An rpa-kind category: semantic uses a unique attribute; contextual uses descriptors and the parent; session identifies the same live DOM node. • JSON registry export and import for backups and transfer to a robot computer. Import requires confirmation, replaces the registry and keeps one local snapshot of the previous state. • Accessible frames and open Shadow DOM. Each frame domain must be allowed separately. Getting started: 1. Open the extension popup and add a domain. 2. Inspect an element in browser developer tools to find its rpa-id. 3. Add the attribute to your automation selector and verify the match. 4. When moving to another computer, import the JSON and separately configure the allowed domains. Stability depends on the website. Semantic matches are usually more resilient; contextual matches depend on structure; session matches do not guarantee recovery after a node is recreated. Major UI changes and indistinguishable elements can prevent an old ID from being restored. Selectors are not guaranteed to remain unchanged through every website update. Data handling: the extension locally processes page origins and initial paths, selected DOM attributes, short text labels and element relationships. These descriptors can contain sensitive information from the page. The registry and domain list stay in the browser profile. The extension has no servers, analytics or automatic cloud synchronization. JSON exports are created only at your request and may contain page addresses and element labels. Exports exclude the domain allowlist and the local previous-registry snapshot. Permissions: storage saves the registry and settings locally. Content scripts are declared for HTTP/HTTPS pages to support user-selected sites and dynamic pages. Chrome therefore grants broad website access; the in-extension allowlist controls tagging but does not narrow the Chrome permission. On disallowed domains, the extension does not scan DOM elements to build its registry. Designed for automation tools that support custom DOM attributes. Verify selectors in your own Primo Studio or other automation project. This is an independent product with no claimed Primo certification or verified Yandex Browser compatibility.