Standalone Feature Page Copy
Purpose: Individual page copy for each feature highlighted on the eko.day homepage. Each page is self-contained — suitable for direct linking from ads, email campaigns, SEO, and the homepage feature cards.
Source: Homepage Copy Section 4: Key Features
Routes:
/features/ai-summaries,/features/noise-filtering,/features/inline-diffs,/features/tracking-notes,/features/urgent-alerts,/features/screenshots,/features/zero-config
Pages
| # | Feature | Route | Nav Label |
|---|---|---|---|
| 1 | AI Change Summaries | /features/ai-summaries | AI Summaries |
| 2 | Noise-Free Monitoring | /features/noise-filtering | Noise Filtering |
| 3 | Section-Level Precision (Inline Diffs) | /features/inline-diffs | Inline Diffs |
| 4 | Tracking Notes | /features/tracking-notes | Tracking Notes |
| 5 | Urgent Alerts | /features/urgent-alerts | Urgent Alerts |
| 6 | Screenshot Comparisons | /features/screenshots | Screenshots |
| 7 | Zero-Config Setup | /features/zero-config | Zero Config |
Feature 1: AI Change Summaries
Route: /features/ai-summaries
Nav label: AI Summaries
Hero
Heading: Know what changed — without reading the page
Subheading: Every change comes with a plain-English explanation of what happened, why it matters to you, and a confidence score so you know when to trust the analysis.
CTA: Start Free
The Problem
Heading: "Change detected" tells you nothing
You get an alert. A page changed. Now what?
With most monitoring tools, that's where the help ends. You click through to a screenshot overlay, squint at highlighted pixels, and try to figure out what's different. For a pricing page, maybe you can spot it. For a terms of service? A careers page with 40 listings? A status page with 12 services? You're on your own.
The alert didn't save you time — it just moved the work from "check the page" to "decode the diff."
How Eko Does It Differently
Every time Eko detects a meaningful change, it generates a structured summary with three parts:
What Changed
A factual, 1–2 sentence description of the difference. No jargon, no HTML, no guessing.
"Stripe updated their Pro plan pricing from $29/mo to $39/mo and reduced the annual discount from 20% to 15%."
Why It Matters
Significance framed by your tracking intent. If you told Eko why you're tracking a page, this section speaks directly to your situation.
"You noted you're evaluating Stripe for your SaaS. This 35% price increase affects your Q2 cost projections."
Confidence Score
A 0–100% rating reflecting how clearly Eko could identify the change signal. This is Eko being honest about its own certainty.
| Score | Meaning | What to do |
|---|---|---|
| High (80%+) | Clear, unambiguous change | Trust the summary |
| Medium (50–79%) | Likely accurate, some ambiguity | Review if critical |
| Low (<50%) | Uncertain or complex change | Check the source page |
Examples
Pricing change — 94% confidence
Page: stripe.com/pricing
What changed: "Stripe raised Pro plan pricing from $29/mo to $39/mo. Annual discount reduced from 20% to 15%. Free tier expanded from 5 to 10 users."
Why it matters: "You're evaluating Stripe for your SaaS. This price increase affects your cost projections."
Status page incident — 98% confidence
Page: status.aws.amazon.com
What changed: "AWS API Gateway changed from 'Operational' to 'Investigating' in the EU region. Incident #4521 opened."
Why it matters: "Your production API routes through EU-West-1. Consider activating your US-East fallback."
Terms of service update — 87% confidence
Page: vendor.com/terms
What changed: "New clause in Section 8.3: Vendor now claims a non-exclusive license to data processed through the API. Liability cap in Section 12.1 reduced from $1M to $500K."
Why it matters: "Your compliance team should review the new data rights clause before your Q3 renewal."
Why Confidence Scores Matter
AI isn't perfect — and most tools pretend otherwise. Eko tells you how certain it is about every change, so you can decide how to act:
- High confidence? Trust the summary and act on it.
- Medium confidence? Skim the source page if the change is critical.
- Low confidence? The page was complex or noisy. Check it yourself.
This transparency builds trust over time. You learn when Eko is reliable (most of the time) and when to verify (edge cases with dynamic content or ambiguous layouts).
How It Compares
| Other tools | Eko | |
|---|---|---|
| Alert content | "Change detected" | What changed, why it matters, confidence score |
| Understanding effort | Decode a screenshot diff | Read 2–3 sentences |
| Personalization | None | Framed by your tracking notes |
| Uncertainty handling | Assumes accuracy | Tells you when to verify |
CTA
Heading: See what AI-powered summaries look like for pages you care about
Primary CTA: Start Free
Secondary CTA: See How It Works
Feature 2: Noise-Free Monitoring
Route: /features/noise-filtering
Nav label: Noise Filtering
Hero
Heading: Only the changes that matter
Subheading: Eko automatically filters out timestamp updates, ad rotations, session data, and minor formatting changes. You get fewer alerts — and every one of them is worth reading.
CTA: Start Free
The Problem
Heading: Alert fatigue is why you stopped using your last monitoring tool
You signed up for a page monitoring service. You added a few pages. Then the alerts started:
- "Change detected" — it was a timestamp update. Last updated: Feb 10, 2026.
- "Change detected" — an ad banner rotated.
- "Change detected" — a session cookie changed your name in the header.
- "Change detected" — whitespace changed in the footer.
After a week of false alarms, you trained yourself to ignore the alerts. Then a real change happened — a price increase, a deprecation notice, a terms update — and you missed it. Not because the tool failed to detect it, but because you stopped paying attention.
The tool that alerts you to everything is the tool you learn to ignore.
How Eko Filters Noise
Eko's AI evaluates every detected difference and classifies it as either meaningful or noise before deciding whether to alert you. Only meaningful changes generate a summary and notification.
What gets filtered out
| Noise type | Example | Why it's noise |
|---|---|---|
| Timestamp updates | "Last updated: Feb 10, 2026" | Changes every visit, carries no signal |
| Session-specific content | "Welcome back, Jonathan" or "Cart (3)" | Unique to your browser session |
| Ad rotations | Different banner on each load | Dynamic ad serving, not content change |
| Minor formatting | Whitespace, line breaks, CSS tweaks | Visual-only, no content difference |
| Cache/build artifacts | Version hashes, asset fingerprints | Technical artifacts, not page content |
What gets through
- Price changes with specific old → new values
- New content sections or removed content
- Policy clause additions or modifications
- Status changes (Operational → Investigating)
- New listings, postings, or announcements
- Feature additions, removals, or restructuring
The Result
Fewer alerts. Higher signal. You never learn to ignore Eko.
When you get an Eko notification, it means something actually changed. This changes your relationship with alerts — instead of anxiety ("another false alarm?"), you feel informed ("something I care about just happened").
How It Compares
| Other tools | Eko | |
|---|---|---|
| Timestamp updates | Triggers alert | Filtered out |
| Ad rotations | Triggers alert | Filtered out |
| Session data | Triggers alert | Filtered out |
| Formatting changes | Triggers alert | Filtered out |
| Actual content changes | Triggers alert (buried in noise) | Clear, standalone alert |
| Your attention | Eroded by false alarms | Preserved for real changes |
CTA
Heading: Track pages without drowning in noise
Primary CTA: Start Free
Secondary CTA: See How It Works
Feature 3: Section-Level Precision (Inline Diffs)
Route: /features/inline-diffs
Nav label: Inline Diffs
Hero
Heading: See exactly what changed
Subheading: Not "pricing section updated." Eko shows you the exact values that changed — highlighted, in context, with before-and-after precision.
CTA: Start Free
The Problem
Heading: "Page changed" is not an answer
You're tracking a competitor's pricing page. You get an alert: "Change detected." You visit the page, but it looks the same. Something's different, but you can't find it.
Was it the Pro plan price? The feature list? The enterprise CTA? A footnote about usage limits? You spend five minutes scanning the page, comparing it to your memory of what it looked like last week. Maybe you find the change. Maybe you don't.
Screenshot diff tools are slightly better — they highlight pixels that changed. But a pixel overlay on a pricing table doesn't tell you "Pro plan: $29/mo → $39/mo." It shows you a red-tinted rectangle. You still have to read both versions and figure out the difference yourself.
How Eko Does Inline Diffs
Eko identifies changes at the section level — individual content blocks within a page — and presents them as structured before/after diffs with exact values.
What you see
| Section | Before | After |
|---|---|---|
| Pro plan | $29/mo | $39/mo |
| Annual discount | 20% | 15% |
| Free tier | 5 users | 10 users |
Not what you see
- "Pricing section was updated"
- A red/green pixel overlay
- Raw HTML diff output
- "3 elements changed on this page"
Examples Across Page Types
Pricing page
| Section | Before | After |
|---|---|---|
| Pro plan | $29/mo | $39/mo |
| Annual discount | 20% | 15% |
You know the exact new price without visiting the page.
Status page
| Section | Before | After |
|---|---|---|
| API Gateway (EU) | Operational | Investigating |
| Incident | — | #4521 opened |
You know which service is affected and the incident number.
Product page
| Section | Before | After |
|---|---|---|
| Price | $1,299.99 | $779.99 |
| Stock | In Stock | Only 3 left |
| Badge | — | "Limited Time Deal" |
You know the exact discount and how much stock remains.
Job listing
| Section | Before | After |
|---|---|---|
| Engineering listings | 12 roles | 14 roles |
| New posting | — | Senior Backend Engineer (Remote) |
You know the exact new role without scrolling through the full careers page.
Why Precision Matters
The difference between "pricing changed" and "$29/mo → $39/mo" is the difference between an alert you have to investigate and an alert you can act on immediately. Precision eliminates the detective work.
For time-sensitive changes — flash sales, status page incidents, competitive moves — seconds matter. Inline diffs give you the answer in the notification itself.
How It Compares
| Screenshot diff tools | Text-based tools | Eko | |
|---|---|---|---|
| Output | Pixel overlay | "Change detected" | Before/after values per section |
| Precision | Page-level | None | Section-level |
| Actionability | Low — you interpret | None — you investigate | High — answer in the alert |
| Example | Red-tinted rectangle on pricing table | "Pricing section changed" | "Pro plan: $29/mo → $39/mo" |
CTA
Heading: Get the exact values, not just "something changed"
Primary CTA: Start Free
Secondary CTA: See How It Works
Feature 4: Tracking Notes
Route: /features/tracking-notes
Nav label: Tracking Notes
Hero
Heading: Tell Eko why you're tracking a page. Get answers that actually help.
Subheading: Add a tracking note when you set up a page. Eko uses your intent to frame every explanation around what matters to you — not generic descriptions.
CTA: Start Free
The Problem
Heading: Generic alerts ignore your context
You're tracking a laptop on Best Buy because you want to buy it when it drops below $800. The price changes. A generic tool says:
"Pricing section was updated with new values."
Is it above or below $800? Did it go up or down? You have to visit the page to find out.
The tool detected the change. But it doesn't know why you care — so it can't tell you whether the change matters to you.
How Tracking Notes Work
When you add a page to Eko, you can optionally write a short note explaining your intent:
"Watching for this laptop to drop below $800."
Eko stores this context and uses it to personalize every change summary for that page. The note becomes the lens through which Eko evaluates and explains changes.
Without a tracking note
"Pricing section was updated with new values."
With a tracking note
"The laptop you're watching dropped from $999 to $749 — below your $800 target."
The same change. Completely different usefulness.
Examples by Use Case
Price tracking
Note: "Alert me when this drops below $800."
Eko says: "Price dropped from $999 to $749 — below your $800 target."
Competitor monitoring
Note: "Need to know if they undercut our $49/mo tier."
Eko says: "Competitor dropped Pro plan from $49/mo to $39/mo — $10 below your current pricing."
Job search
Note: "Alert me when they post senior engineering roles with remote options."
Eko says: "New posting: 'Senior Backend Engineer (Remote).' Requires 5+ years Python, mentions distributed systems — matches your criteria."
Vendor terms
Note: "Renewal in Q3 — alert me to any pricing or terms changes."
Eko says: "New clause in Section 8.3 grants vendor a license to API-processed data. Review before your Q3 renewal."
API deprecation
Note: "Alert me to breaking changes or deprecations in the v3 API."
Eko says: "Endpoint /v2/users marked deprecated. Migration deadline: March 1. Replacement: /v3/users with new auth flow."
Tips for Writing Good Tracking Notes
Your tracking note doesn't need to be long. A single sentence is usually enough. Focus on:
- What you're waiting for: "Alert me when the price drops below $800"
- Why you care: "Evaluating this vendor for our Q2 migration"
- What would make you act: "Need to know if they undercut our $49/mo tier"
The more specific your note, the more personalized Eko's explanations become.
How It Compares
| Other tools | Eko without a note | Eko with a note | |
|---|---|---|---|
| Explanation | "Change detected" | "Price changed from $999 to $749" | "Price dropped below your $800 target" |
| Personalization | None | Factual but generic | Framed by your intent |
| Action clarity | You figure it out | You understand the change | You know whether to act |
CTA
Heading: Your pages, your context, your answers
Primary CTA: Start Free
Secondary CTA: See How It Works
Feature 5: Urgent Alerts
Route: /features/urgent-alerts
Nav label: Urgent Alerts
Hero
Heading: Some pages can't wait for your next inbox check
Subheading: Mark any tracked page as Urgent. When a meaningful change is detected, Eko sends you an instant SMS and email — so you never miss what matters most.
CTA: Start Free
The Problem
Heading: Email alerts aren't fast enough for everything
Email notifications work for most pages. You check your inbox a few times a day, scan the Eko alerts, and stay informed. That cadence works fine for competitor pricing pages, job listings, and most content you track.
But some pages are different. When your payment processor's status page changes from "Operational" to "Investigating," you need to know now — not the next time you open your inbox. When a competitor drops their prices the day before your big pitch, three hours of delay is three hours too many.
For these pages, email isn't enough. You need a notification that interrupts you.
How Urgent Alerts Work
Any tracked page can be marked as Urgent — a single toggle in the Eko app.
When Eko detects a meaningful change on an Urgent page, it sends you:
- An SMS to your phone — immediately
- An email — simultaneously
The same AI summary, the same inline diffs, the same confidence score. Just delivered faster, through a channel you can't miss.
What you control
| Setting | Where | Description |
|---|---|---|
| Urgent toggle | Per page | Turn Urgent on or off for any tracked page |
| Phone number | App settings | Set your mobile number for SMS delivery |
| Quiet hours | App settings | Pause Urgent SMS during off-hours (emails still deliver) |
What Eko controls
- Noise filtering still applies. Urgent pages don't get noisier alerts — they get faster alerts when something meaningful changes. Timestamp updates and ad rotations are still filtered out.
- 3x/day monitoring still applies. Urgent doesn't increase check frequency. It changes the notification channel when a change is detected.
When to Use Urgent
Not every page needs Urgent. Reserve it for pages where a few hours of delay could cost you money, opportunity, or uptime.
| Use case | Example page | Why Urgent |
|---|---|---|
| Production dependency | status.aws.amazon.com | Outage detection before customers complain |
| Competitive pricing | competitor.com/pricing | React before your sales team hears it from prospects |
| Vendor terms | vendor.com/terms | Legal review before the change takes effect |
| Time-sensitive deal | bestbuy.com/product/samsung-tv | Flash sales disappear in hours |
| Contract renewal | saas-tool.com/pricing | Catch increases before your renewal date |
| Job listing you applied to | company.com/careers/job-123 | Know if requirements change before your interview |
Quiet Hours
Urgent alerts are designed to interrupt you — but not at 3am. Set quiet hours in your app settings to pause SMS delivery overnight. During quiet hours:
- SMS is paused. No text messages until quiet hours end.
- Email still delivers. You won't miss anything — it's waiting in your inbox.
- SMS resumes automatically. When quiet hours end, any changes detected during that window have already been emailed.
How It Compares
| Email-only tools | Eko (standard) | Eko (Urgent) | |
|---|---|---|---|
| Notification speed | Next inbox check | Next inbox check | Instant SMS + email |
| Interruptibility | Low | Low | High — your phone buzzes |
| Noise filtering | None | ✅ Meaningful changes only | ✅ Meaningful changes only |
| Quiet hours | N/A | N/A | ✅ Configurable |
| Per-page control | N/A | N/A | ✅ Toggle per page |
CTA
Heading: Get a text the moment a critical page changes
Primary CTA: Start Free
Secondary CTA: See How It Works
Feature 6: Screenshot Comparisons
Route: /features/screenshots
Nav label: Screenshots
Hero
Heading: See the change, not just read about it
Subheading: Every change includes before/after screenshots so you can visually verify what happened. Compare using side-by-side, slider, or overlay — your choice.
CTA: Start Free
The Problem
Heading: Text summaries alone don't tell the whole story
AI summaries are powerful. Inline diffs are precise. But sometimes you need to see the change in context — where it appeared on the page, how the layout shifted, what the surrounding content looks like.
A text summary that says "Hero headline changed" doesn't show you whether the new headline is above or below the fold, whether the font size changed, or whether the entire page layout was redesigned. You need eyes on the page.
But visiting the page yourself only shows you the current version. The old version is gone. Without a visual record, you can't compare.
How Screenshot Comparisons Work
Every time Eko detects a meaningful change, it captures a before and after screenshot. These are attached to the change summary and available in three view modes:
Side-by-Side
Before and after screenshots displayed next to each other. Best for quick visual comparison — your eyes can scan between the two versions and spot differences immediately.
Slider
A single view with a draggable handle. Drag left to see before, right to see after. Best for spotting subtle layout changes — the slider makes even small shifts obvious as you drag across the boundary.
Overlay
Toggle between before and after in the same frame. Best for seeing exactly what shifted — elements that moved or resized become obvious as the view switches.
The Full Picture
Eko gives you both text intelligence and visual proof for every change:
| Layer | What it provides |
|---|---|
| AI Summary | What changed and why it matters, in plain English |
| Inline Diffs | Exact before/after values per section |
| Confidence Score | How certain Eko is about the analysis |
| Screenshots | Visual before/after with highlighted change regions |
The text layers tell you what happened. The screenshots show you where it happened on the page. Together, you get the complete picture without visiting the source.
When Screenshots Matter Most
- Competitor homepages — A messaging repositioning isn't just a headline change. Screenshots show the full visual rebrand: new imagery, new layout, new CTA placement.
- Product pages — Pricing table restructures are hard to describe in text. Screenshots show you the old table vs the new table at a glance.
- Status pages — A service moving from green to yellow on a dashboard is instantly visible in a screenshot, even if the AI summary already told you.
- Legal pages — When a terms of service page adds a new section, screenshots show you where in the document it appeared and how long it is.
How It Compares
| Screenshot-only tools | Text-only tools | Eko | |
|---|---|---|---|
| Visual comparison | ✅ Pixel overlay | ❌ None | ✅ Three view modes |
| Text explanation | ❌ None | ✅ Basic alert | ✅ AI summary + inline diffs |
| Change understanding | Low — you interpret pixels | Low — you investigate | High — text + visual together |
| View modes | Usually one (overlay) | N/A | Side-by-side, slider, overlay |
CTA
Heading: AI tells you what changed. Screenshots show you where.
Primary CTA: Start Free
Secondary CTA: See How It Works
Feature 7: Zero-Config Setup
Route: /features/zero-config
Nav label: Zero Config
Hero
Heading: Paste an address. That's the whole setup.
Subheading: No element selectors. No CSS paths. No rules to maintain. Just paste a webpage address and Eko handles everything — from page type detection to noise filtering.
CTA: Start Free
The Problem
Heading: Other tools make you do the hard part
You want to track a pricing page. With most monitoring tools, here's what happens:
- You paste the page address. Good so far.
- "Select the element you want to monitor." You inspect the page, find the right CSS selector, and hope it doesn't change.
- "Configure your monitoring rules." You set thresholds, define what counts as a change, and tweak sensitivity.
- "Choose your notification preferences." More settings. More decisions.
- The page layout changes next month. Your selector breaks. Alerts stop. You don't notice until you manually check — the exact thing you were trying to avoid.
The setup takes 10 minutes. The maintenance never ends. And when it breaks, it breaks silently.
How Eko's Zero-Config Works
Step 1: Paste a webpage address
That's it. You paste an address. Eko takes over.
What happens behind the scenes
| Eko does this automatically | You don't have to |
|---|---|
| Fetches the page using text extraction, with Playwright rendering as fallback | Choose a rendering mode |
| Detects the page type from 24+ categories (Pricing, Status, Careers, API docs, Terms...) | Classify the page yourself |
| Identifies content sections relevant to that page type | Pick CSS selectors |
| Establishes a baseline for future comparison | Configure initial state |
| Applies noise filtering rules for the detected page type | Set sensitivity thresholds |
| Monitors 3x/day automatically | Choose a check frequency |
No maintenance required
When a page changes its layout, Eko adapts. There are no selectors to break, no rules to update, no configuration to maintain. Eko re-analyzes the full page on every check.
Page Type Detection
Eko automatically classifies every page you track into one of 24+ types. This classification drives how Eko analyzes changes — a pricing page is evaluated differently than a status page, which is evaluated differently than a terms of service page.
| Category | Page types |
|---|---|
| Business | Pricing, Product, Careers, Partners, Roadmap |
| Technical | API docs, Changelog, Status, Documentation |
| Legal/Policy | Terms, Privacy, Security, Accessibility |
| E-Commerce | Product detail, Availability, Billing, Shipping, Returns |
| Content | Blog, Events, Entertainment |
You don't choose the type. You don't even see it unless you look. It just works — and it makes every summary smarter because Eko knows what kind of page it's analyzing.
What "Zero Config" Really Means
| Decision | Other tools | Eko |
|---|---|---|
| What to monitor | Select elements with CSS selectors | Entire page, intelligently parsed |
| How to render | Choose text vs screenshot | Automatic (text-first, rendering as fallback) |
| What counts as a change | Set thresholds and rules | AI-driven noise filtering |
| How often to check | Pick a frequency | 3x/day on every page, always on |
| When selectors break | Fix them manually (if you notice) | No selectors to break |
| Page type context | Configure yourself | Automatically detected from 24+ types |
The Real Cost of Configuration
The problem with configuration isn't the initial setup — it's the ongoing maintenance. Every time a monitored page changes its layout, CSS selectors break. Every time a site redesigns, rules need updating. Every broken selector is a page that stops being monitored — silently.
Zero-config isn't a convenience feature. It's a reliability feature. When there's nothing to configure, there's nothing to break.
CTA
Heading: Stop configuring. Start tracking.
Primary CTA: Start Free
Secondary CTA: See How It Works
Implementation Notes
Consistent structure
Every feature page follows the same arc: Hero → Problem → How It Works → Examples/Details → Comparison → CTA. This consistency lets users quickly navigate any feature page and find the information density they need.
Cross-linking
Each feature page should link to related features. Suggested connections:
| Feature page | Links to |
|---|---|
| AI Summaries | Inline Diffs, Tracking Notes, Screenshots |
| Noise Filtering | AI Summaries, Zero Config |
| Inline Diffs | AI Summaries, Screenshots |
| Tracking Notes | AI Summaries, Inline Diffs |
| Urgent Alerts | Noise Filtering (still applies), Zero Config |
| Screenshots | AI Summaries, Inline Diffs |
| Zero Config | Noise Filtering, AI Summaries |
Homepage feature cards → Feature pages
Each feature card on the homepage (Section 4 of public-homepage-copy.md) should link to its corresponding standalone page:
| Homepage card | Route |
|---|---|
| AI Change Summaries | /features/ai-summaries |
| Noise-Free Monitoring | /features/noise-filtering |
| Section-Level Precision | /features/inline-diffs |
| Tracking Notes | /features/tracking-notes |
| Urgent Alerts | /features/urgent-alerts |
| Screenshot Comparisons | /features/screenshots |
| Zero-Config Setup | /features/zero-config |
Shared CTA pattern
Every page ends with the same CTA structure: heading + primary ("Start Free") + secondary ("See How It Works"). The heading varies per feature to reinforce the specific value proposition.
SEO considerations
Each page should have a unique meta description drawn from its hero subheading. Feature page titles should follow the pattern: "Feature Name — Eko" (e.g., "AI Change Summaries — Eko").