GrackerAI PageLens

A Summarize button on your site. Readers land in ChatGPT, Claude, or Gemini already asking about your page, which puts your pages into the answers your readers get.

It stays yours. PageLens isn't part of your plan, so it keeps working for free, on as many pages as you like, after everything else stops.

PageLens is not part of your plan. It isn't metered, seat-limited, or tied to a subscription. Use it on as many pages and sites as you like, and it keeps running if you cancel or drop to the Free plan. You don't even need an account: the bare tag works on its own.

Your monitoring stops when the plan does. Your AI visibility doesn't have to.

What it does

It does not rank your page or promise a citation. It removes the friction between your page and the answer engine, and puts your framing in the prompt instead of whatever the reader would have typed.

What the reader sees

Six seconds. One click. Your content is the source in an AI conversation.

What it is not

Installation

One tag, before </body>:

<script src="https://cdn.gracker.ai/summarize.min.js" defer></script>

That is the full install. Every option has a sensible default, so the bare tag is complete.

To configure it visually, go to Connectors → GrackerAI PageLens. Position, engines, and appearance are on the left, with a live preview on the right, and Edit tag gives you the finished snippet to paste.

The snippet Gracker generates carries only what you changed:

<script src="https://cdn.gracker.ai/summarize.min.js"
        data-position="top-left"
        data-label="Ask AI"
        defer></script>

Privacy and performance

While a reader is just reading:

The widget renders inside a shadow root, so your site's CSS cannot reach into it and its CSS cannot leak out. Provider logos are inlined as SVG, so it makes no requests of its own. The only request is the script tag itself. A click triggers an ordinary navigation carrying your URL and prompt.

Prompt configuration

The prompt decides what a click is worth. Most people leave it at the default.

Prompts by page type

Supported assistants

Appearance settings

Motion effects

Driving it yourself

Add data-manual to skip auto-mount and control the widget from your own code. The global is SummarizeThisPage:

<script src="https://cdn.gracker.ai/summarize.min.js" data-manual defer></script>
<script>
  const widget = SummarizeThisPage.mount({
    position: 'bottom-left',
    providers: 'chatgpt,claude',
    accent: '#111111'
  });

// later
  widget.destroy();
</script>

Why it matters

Readers already do this

Pasting an article into an assistant is ordinary behaviour. It happens whether or not you enable it. The only question is whose tab it happens from.

The only lever that works on demand

No adoption blockers

Highest-return content

Best practices

Summary

One script tag turns a common reader habit into a distribution channel.

FAQ

Does it slow my site down?

No. The script is deferred, and it makes zero requests of its own. Nothing loads until a reader clicks.

Do I need a cookie banner for it?

It sets no cookies, uses no storage, and sends no requests while a reader is reading, so there is nothing to consent to before a click. Confirm with your own counsel as you would for any third-party script.

How many pages can I use it on?

All of them. One site-wide tag, no limit, and no limit on the number of sites either.

Is it included in my plan?

No, and that is deliberate. It is not plan-gated, metered, or seat-limited, and it keeps working after a GrackerAI plan ends. You do not need an account to use it.

Can I use different prompts per page?

The tag carries one prompt, so emit it from your template with a different data-prompt per page type. Docs, pricing, and comparison pages each deserve their own question.

What if a reader never clicks?

They see a small button. Nothing loads, nothing is tracked, and nothing is sent anywhere.

Why isn't Perplexity showing in my menu?

Perplexity is the one engine that is off by default. Add it explicitly with data-providers, listing every engine you want in the order you want them shown.

Will it clash with my site's CSS?

No. The widget renders inside a shadow root, so your styles cannot reach into it and its styles cannot leak out.