DOM Injection Detector for SEO

Compare a page's server HTML with the JavaScript-rendered page, and find content injected on click or hover. For SEO.

See exactly which SEO content on a page depends on JavaScript, and hand developers a ready-made ticket to fix it. Search engines, AI crawlers and link-preview scrapers do not all run JavaScript. Content that only appears after JavaScript runs, or only after a click, can be indexed late, missed entirely, or left out of link previews. DOM Injection Detector shows you what that content is, element by element. RAW VS RENDERED Compare the HTML the server sends (fetched without cookies, scripts not run) with the page after JavaScript runs. Every difference is marked JS-only, Removed by JS, Changed or Match, with the raw and rendered values side by side: • Title, meta description, robots, canonical, lang and viewport • Open Graph and Twitter card tags, and every other meta tag • hreflang, pagination, AMP and other link tags • Structured data: JSON-LD, microdata and RDFa • Headings, body text and word count • Images, video embeds, iframes and links • Noscript fallbacks such as "please enable JavaScript" Cookie-consent banners, tracking pixels and other third-party noise are left out. CLICK AND HOVER INJECTIONS Find content that only appears after an interaction: accordions, tabs, mega-menus, "load more" buttons and links whose JavaScript loads content in place. • Click around yourself, or let Auto-hover & click work through every menu, button, tab, accordion, JavaScript link and link on the page • Each injection is reported with the element that caused it, the injected content and a screenshot • The page is kept from navigating away the whole time: link clicks, script navigation, pop-ups, form submits and downloads are all cancelled BUILT FOR HANDING OVER TO DEVELOPERS • XPath and CSS selector for every finding, one click to copy • "Show on page" scrolls to any finding and highlights it • Developer report: a Jira-style investigation ticket with summary, key findings, every finding with its XPath, steps to reproduce, suggested fix and acceptance criteria • Copy the report as formatted text for Jira Cloud and Confluence, as Jira wiki markup for Jira Server / Data Center, or download it as Markdown • Export the full data as CSV or JSON PRIVATE BY DESIGN Everything runs in your browser. Results are stored locally on your device and are never sent anywhere. The only network request the extension makes is to fetch the page you are analyzing, from that page's own server. Developed by William Harvey.