Grounding Page Project
Bookmarklet

Test how AI reads your page — before it’s public

Drag the bookmarklet into your bookmarks bar and run the Grounding Check on the rendered DOM of any page you can see. Made for staging URLs, draft pages and JavaScript apps that crawlers can’t yet reach. For pages that are already public, URL input is faster.

Test before publishing Staging & draft pages No crawling required Reads the browser DOM
Drop here
Grounding Check

Drag this button up into your bookmarks bar — clicking won't install it.

Ready in 3 steps

  1. Show bookmarks bar Ctrl + Shift + B (Windows/Linux) · Cmd + Shift + B (macOS)
  2. Drag button up Drop the blue Grounding Check button into your bookmarks bar.
  3. Click on any page The cleaned content opens in a new tab and analyses automatically.
Add manually as a bookmark

If drag-and-drop doesn't work, right-click the blue button above → Copy link, then create a new bookmark and paste the javascript: URL as the address.

How it works

Four steps from click to analysis — everything happens in your browser, no extension needed.

1

Read DOM

Uses the rendered browser content from <main>, <article> or <body>.

2

Clean content

Removes navigation, scripts and layout-only attributes — only the visible content remains.

3

Send to analysis

The cleaned content is transferred via postMessage — never as a URL parameter.

4

Show results

Entity map and scoring appear instantly. No extra click needed.

When to use the bookmarklet

Once a page is publicly crawlable, URL input is the faster path. The bookmarklet is the right tool for content that crawlers can’t reach yet.

Staging & pre-launch URLs

Pages that already exist but aren’t yet public — staging environments, draft pages, internal review URLs, member previews. Test how AI would read them before you publish.

JavaScript apps

Next.js, Vue, React and other SPAs render client-side. Server-side fetches see an empty shell; the bookmarklet sees the finished result the way a browser does.

Internal & gated pages

Member areas, intranet pages, paywalls. Useful for diagnosing your own content — not for grounding. AI crawlers can’t access these pages anyway, so any rewrite has to wait until the page is public.

One-click testing

One click on any rendered page instead of copy, paste, submit. Useful when you’re iterating quickly between edits and AI checks.

FAQ

Common questions about the Grounding Check Bookmarklet.

Is data sent anywhere?
Only the cleaned visible content of the current page is sent — once, via postMessage, to the Grounding Check tab you just opened. No tracking, no third-party servers in between.
Does it work in every browser?
Any modern desktop browser with a bookmarks bar: Chrome, Edge, Firefox, Safari, Brave, Arc, Vivaldi. Mobile browsers usually don't support bookmarklets.
Why doesn't a new tab open?
A pop-up blocker is intercepting it. Allow pop-ups for the current page, then click the bookmarklet again.
When should I use URL input instead?
As soon as a page is publicly crawlable, URL input is faster — and it produces the same result an AI crawler would see. Use the bookmarklet only while a page isn’t yet reachable for crawlers (staging, drafts, JS-rendered shells).
What about login-protected pages?
The bookmarklet can read them because you are logged in. But AI crawlers can’t. Use the bookmarklet here only to diagnose the content quality — any actual grounding effect kicks in only once the page is publicly accessible.
How much content is analysed?
Up to 50,000 characters of cleaned visible content per page. Below 80 characters the bookmarklet aborts — not enough text to analyse.