Question 1

What is the difference between Guard and KeyPages.ai?

Accepted Answer

Guard is the core technology DataJelly builds — the rendering, snapshot, and check engine that works out what a page is for and verifies it still does its job. KeyPages.ai is the product built on Guard, and it is where you sign up, pay, and protect your pages. If you want to buy page monitoring, you go to KeyPages.ai.

Question 2

What is KeyPages.ai?

Accepted Answer

KeyPages.ai is page-first production protection for the important pages in your live app. You paste a URL and KeyPages opens the live page in a real browser, works out what the page is for, turns on the protections that fit it, and keeps checking as you ship. It catches customer-visible failures a basic uptime check misses — a missing signup form, a disabled buy button, a page that still returns 200 while refusing to sell.

Question 3

What is DataJelly Guard?

Accepted Answer

Guard is the production monitoring technology behind KeyPages.ai. It renders your key pages like a real browser, runs the checks that apply to that page type, and flags the moment something silently breaks — blank pages, missing content, broken CTAs, SEO regressions, or performance drops. Your site returns 200 OK; Guard proves it actually works. You use it by protecting a page on KeyPages.ai.

Question 4

How is Guard different from uptime monitoring?

Accepted Answer

Uptime monitoring checks if a URL returns a response. Guard checks if the page actually works. A page can return HTTP 200 while showing a blank screen, broken form, or wrong metadata. Guard renders the page, captures the output, and detects these silent failures that uptime tools miss.

Question 5

What does Guard actually test?

Accepted Answer

Guard runs 30 tests across 6 categories: Availability (HTTP status, redirects, SSL), Render Integrity (blank page detection, DOM size, visible text), Content Integrity (H1, title, key selectors), SEO Signals (canonical, noindex, meta tags), Performance (Lighthouse scores, Core Web Vitals), and Crawler Safety (robots.txt, sitemap, AI files).

Question 6

Which pages should I monitor?

Accepted Answer

Start with pages that cost you money or visibility when broken: homepage, pricing, signup, checkout, contact, and your highest-traffic landing pages. These are the pages where silent failures have the biggest impact. You can expand from there as you see value.

Question 7

What is Edge and is it still available?

Accepted Answer

DataJelly Edge was our prerendering and dynamic rendering product. Edge is no longer offered to new customers. Modern frameworks like Next.js and builders like Lovable now handle SSR by default. Our active product is KeyPages.ai, which uses our Guard technology to monitor live pages for regressions after deploys. Our educational guides on JavaScript SEO and prerendering remain available.

Question 8

How do I get started?

Accepted Answer

Sign up at KeyPages.ai, verify your email, and paste the URL of a page you care about — no credit card required to start. We recommend your homepage and pricing page. KeyPages works out what the page is for, turns on the protections that fit, and runs your first check shortly after.

Question 9

Do I need to install anything or change my code?

Accepted Answer

No. Guard is external monitoring — add the pages you care about and verify ownership. There is nothing to install, no scripts to add, and no code changes required. Guard handles the scanning from our infrastructure.

Question 10

How do I verify ownership of my site?

Accepted Answer

When you add a domain, we ask you to add a TXT record to your DNS. This proves you control the domain. Once verified, you can add any page on that domain to monitoring. The process takes 2-5 minutes depending on your DNS provider.

Question 11

How long until I see my first results?

Accepted Answer

Once a page is added and enabled, Guard runs it on the next scan cycle — about every 30 minutes on most plans. Your first results appear on the Latest Test Results page shortly after.

Question 12

Can I try KeyPages before paying?

Accepted Answer

Yes. Every account can monitor 2 pages for free with all features enabled — the full test suite, alerts, and AI-generated report cards. This is a real preview of the product, not a limited demo. Paid plans start with a 10-day free trial.

Question 13

What pricing plans do you offer?

Accepted Answer

KeyPages.ai plans: Basic ($49/mo) for 10 pages, Startup ($99/mo) for 40 pages, Growth ($249/mo) for 100 pages, and Enterprise ($599+/mo) for custom needs. All plans include the full check suite, alerts, and AI report cards. Higher plans increase pages, check frequency, data retention, and support level. Current pricing is always on KeyPages.ai.

Question 14

Do you offer a free trial?

Accepted Answer

Yes. Every paid plan includes a 10-day free trial. You can also monitor 2 pages for free without entering payment details — a true try-before-you-buy preview with all features enabled.

Question 15

What counts as a monitored page?

Accepted Answer

A monitored page is a URL you add in KeyPages.ai. Protection is page-based, not domain-based, so you choose exactly which URLs matter — homepage, pricing, signup, checkout, key landing pages. You can swap pages in and out anytime from the dashboard.

Question 16

What happens if I exceed my page limit?

Accepted Answer

We alert you before you hit the limit. If you need more pages, upgrade to a higher plan. Existing pages continue to be monitored — we do not stop scanning pages you have already added.

Question 17

Can I upgrade or downgrade anytime?

Accepted Answer

Yes. You can change plans at any time from your dashboard. Upgrades take effect immediately. Downgrades take effect at the end of your current billing period. Billing is prorated accordingly.

Question 18

Do you offer annual billing?

Accepted Answer

Yes. Annual plans include two months free compared to paying monthly. You can switch between monthly and annual anytime from your billing settings.

Question 19

Can I cancel anytime?

Accepted Answer

Yes. Cancel from your dashboard at any time. Your service continues until the end of your billing period, and your data remains accessible for 30 days after cancellation.

Question 20

How often does Guard scan my pages?

Accepted Answer

Scan frequency depends on your plan: Basic scans every 30 minutes, Startup and Growth scan every 15 minutes. Enterprise plans can scan more frequently. Guard also runs a scan when you manually trigger one from the dashboard.

Question 21

Does Guard render pages with a real browser?

Accepted Answer

Yes. Guard renders each page in a headless browser (Chromium) just like a real user or bot would see it. This captures JavaScript-rendered content, hydration state, and runtime behavior — not just the initial HTML response.

Question 22

What is Render Integrity and why does it matter?

Accepted Answer

Render Integrity tests detect when a page returns 200 OK but the rendered output is broken — blank pages, script shells, missing DOM sections, or drastically reduced visible text. These failures are invisible to uptime monitoring and server logs.

Question 23

Does Guard check SEO tags and metadata?

Accepted Answer

Yes. Guard monitors title tags, meta descriptions, canonical URLs, noindex directives, Open Graph tags, and structured data. It alerts you when these change unexpectedly or contain errors that could hurt search visibility.

Question 24

Does Guard include Lighthouse monitoring?

Accepted Answer

Yes. Guard runs Lighthouse on your monitored pages and tracks Performance, Accessibility, Best Practices, and SEO scores over time. You can see trends and get alerted when scores drop significantly.

Question 25

Does Guard monitor sitemaps and robots.txt?

Accepted Answer

Yes. Guard monitors your sitemap.xml, robots.txt, and AI visibility files like llms.txt. It alerts you when these files fail to load, return errors, or contain problematic directives.

Question 26

Can I connect Google Search Console?

Accepted Answer

Yes. Guard integrates with Google Search Console to show impressions, clicks, and indexing status alongside your monitoring data. This helps you correlate page health with search performance.

Question 27

Does Guard help with SEO?

Accepted Answer

Guard prevents SEO regressions. It catches accidental noindex tags, canonical mistakes, missing meta tags, and thin content that would otherwise hurt your search visibility. It does not build backlinks or optimize keywords — it protects the technical foundation.

Question 28

What is JavaScript SEO and why does it matter?

Accepted Answer

JavaScript SEO ensures search engines can see and index content rendered by JavaScript. Many modern sites ship thin HTML and rely on client-side rendering. If crawlers cannot see your content, you cannot rank.

Question 29

Does Google render JavaScript?

Accepted Answer

Google can render JavaScript, but rendering is resource-constrained, delayed, and not guaranteed for every page. Strong raw HTML reduces risk. Guard monitors what crawlers actually receive.

Question 30

What is AI visibility and why should I care?

Accepted Answer

AI crawlers like GPTBot, Claude, and Perplexity extract content differently than Google. They often do not render JavaScript. If your raw HTML is empty, you are invisible to AI search and citation systems.

Question 31

My site is indexed but gets no traffic. Why?

Accepted Answer

Being indexed does not mean you will rank. Common causes: thin HTML that weakens signals, poor internal linking, missing or duplicate metadata, weak content structure, or canonicalizing to the wrong URL. Guard helps catch these technical issues.

Question 32

How do I test what Google actually sees?

Accepted Answer

Compare raw HTML with rendered output. Check visible text length, internal links, canonical tags, and noindex directives. Use Search Console URL Inspection for Google's view. Guard automates these comparisons on every scan.

Question 33

What data does Guard collect?

Accepted Answer

Guard stores rendered HTML, screenshots, metadata (title, description, Open Graph), timing metrics, console logs, and test results. All data is scoped to publicly accessible pages you explicitly add. We do not collect user sessions, private content, or data behind authentication.

Question 34

Is my data secure?

Accepted Answer

Yes. All data is encrypted in transit (TLS) and at rest. We use secure cloud infrastructure with regular security audits. Your monitoring data is isolated to your account and not shared with other customers.

Question 35

Does Guard scan pages behind login?

Accepted Answer

Guard monitors publicly accessible pages by default. If you need to monitor authenticated pages, contact us to discuss options. We do not store credentials or bypass authentication without explicit configuration.

Question 36

Does Guard check for security issues?

Accepted Answer

Yes. Guard scans for exposed secrets (API keys, tokens), console errors, mixed content warnings, and suspicious JavaScript. These checks help catch accidental leaks before bots or attackers find them.

Question 37

How long do you retain my data?

Accepted Answer

Data retention depends on your plan: Basic retains 30 days, Startup retains 90 days, Growth retains 180 days, Enterprise has custom retention. After cancellation, data remains accessible for 30 days.

Question 38

What alert channels does Guard support?

Accepted Answer

Guard supports email alerts on all plans. Startup and higher plans add Slack integration. Growth and Enterprise plans add custom webhook support for integration with your own systems.

Question 39

Can I connect Guard to Slack?

Accepted Answer

Yes. Startup and higher plans include Slack integration. Connect your Slack workspace and choose which channels receive alerts. You can customize alert types and severity levels.

Question 40

Does Guard integrate with Google Search Console?

Accepted Answer

Yes. Guard connects to Google Search Console to show impressions, clicks, average position, and indexing status alongside your monitoring data. This helps correlate page health with search performance.

Question 41

Can I trigger scans from CI/CD?

Accepted Answer

Yes. Use webhooks to trigger Guard scans after deploy. This ensures every deployment is immediately checked for regressions. Growth and Enterprise plans include webhook support.

Question 42

Do you have an API?

Accepted Answer

Yes. Guard has an API for retrieving test results, triggering scans, and managing monitored pages. API access is available on Growth and Enterprise plans. Contact us for documentation.

Question 43

Why is my page showing as failing?

Accepted Answer

Check the test results for specific failure reasons. Common causes: the page returned an error status, rendered content is significantly different from baseline, SEO tags changed unexpectedly, or the page took too long to load. Click into the test details for diagnosis steps.

Question 44

Guard says my page is blank but it loads fine in Chrome. Why?

Accepted Answer

Guard renders your page like a crawler would — without cookies, sessions, or cached state. If your page depends on JavaScript that fails silently, client-side data that is not available, or cookies that are not set, it may render blank for Guard while appearing fine in your browser.

Question 45

How do I reduce false positives?

Accepted Answer

Guard learns your page baselines over time. If a change is intentional (redesign, content update), the new state becomes the baseline. You can also configure thresholds for specific tests or exclude known-variable elements from comparison.

Question 46

My scores dropped after a deploy. What should I check?

Accepted Answer

Review the test results timeline to see what changed. Check for JavaScript errors, missing resources, changed meta tags, or content differences. Guard shows before/after comparisons to help pinpoint the issue.

Question 47

How do I contact support?

Accepted Answer

Use the Contact page or email support@datajelly.com. Enterprise customers have access to priority support with faster response times. Include your account email and the affected page URL when reporting issues.

Frequently Asked Questions

KeyPages.ai & Guard
Guard is the monitoring technology. KeyPages.ai is the product you buy.

Getting Started
How to set up KeyPages.ai and start monitoring

Pricing & Billing
Plans, pricing, trials, and billing questions

Tests & Monitoring
How Guard tests work and what they detect

SEO & Search
JavaScript SEO, AI visibility, and search indexing

Security & Privacy
Data handling, security, and privacy practices

Integrations
Alerts, webhooks, and third-party integrations

Troubleshooting
Common issues and how to resolve them

Explore More

Still have questions?