Website Insights
Infer initiatives and pain points by analyzing website changes across 6M+ companies - text modifications, page additions, and page removals.
A company's website is the most direct expression of their strategy — what they're building, who they're selling to, and where they're headed. By tracking website changes over time, we surface signals that indicate business priorities, growth initiatives, and potential pain points.
This is one of our highest-volume signals — a single monthly delivery can exceed 12 GB and contain tens of millions of signals across 6 million websites. The breadth makes it powerful for TAM-wide monitoring at scale.
We scan 6 million company websites on a recurring basis, capturing full-page snapshots and comparing them against previous versions. Our pipeline analyzes text modifications, page additions, and page removals — then classifies each change into one of 38 standardized subtypes using a model trained to infer business intent from website content.
A single company can produce multiple signals if we detect meaningful changes across different areas of their site (e.g., both a pricing restructure and a new partnership announcement in the same scan).
See real delivered data → Sample Files
Subtypes represent the specific type of website change detected — from pricing updates to product launches to executive changes. Use them to filter for the go-to-market signals most relevant to your sales motion.
Available Subtypes (38)
| Subtype Enum | Description |
|---|---|
acquisition | M&A activity detected |
brandingChange | Brand, logo, or visual identity updates |
communityEngagement | Community or user engagement initiatives |
complianceUpdate | Compliance, security, or legal page changes |
contactUpdate | Contact information or location changes |
customerWin | Customer logo, case study, or testimonial added |
eventAnnouncement | Event, webinar, or conference announcement |
executiveChange | Leadership or executive team changes |
expansionGeneral | General business expansion signals |
featureLaunch | New feature announcement |
featureUpdate | Existing feature enhancement |
fundingNews | Funding round or investment news |
geographicExpansion | New market or region expansion |
marketData | Market data or industry statistics published |
marketingCampaign | Marketing campaign launch |
marketingChannel | New marketing channel or platform |
marketingContent | New marketing content published |
marketingShift | Messaging or positioning change |
mediaPress | Press release or media coverage |
operationalChange | Operational or process changes |
other | Other website changes |
partnershipAnnouncement | Partnership or integration announced |
pricingChange | Pricing page or tier changes |
pricingPromotion | Promotional pricing or discounts |
productExpansion | Product line expansion |
productHighlight | Product spotlight or featured content |
productLaunch | New product announcement |
productRemoval | Product or feature deprecation |
productUpdate | Product enhancement or update |
programLaunch | New program (partner, referral, etc.) |
projectUpdate | Project milestone or update |
recognitionAward | Award or recognition announcement |
serviceUpdate | Service offering changes |
targetAudienceShift | Target market or audience shift |
teamExpansion | Hiring or team growth signals |
technicalUpdate | Technical or infrastructure changes |
technologyAdoption | New technology adoption |
websiteUpdate | General website updates |
Example Signal
What a single entry looks like in a delivered signal file:
{
"signal_id": "c4d5e6f7-8a9b-0c1d-2e3f-456789abcdef",
"batch_id": "2026-03-10-00-00-00",
"signal_type": "website",
"signal_subtype": "pricingChange",
"detected_at": "2026-03-09T00:00:00Z",
"association": "company",
"company": {
"name": "Lattice",
"domain": "lattice.com", // match on domain
"linkedin_url": "linkedin.com/company/latticehq", // or match on LinkedIn URL
"industries": ["Software Development", "Human Resources"],
"employee_count_low": 501,
"employee_count_high": 1000,
"description": "People management platform for performance..."
},
"contact": [],
"data": {
"summary": "Lattice restructured its pricing page to remove the self-serve tier entirely, replacing it with 'Contact Sales' for all plans — signaling an upmarket shift toward enterprise...",
"evidence": "Removed page: /pricing/starter. Modified page: /pricing — removed '$11/person/month' starter tier, added 'Contact Sales' CTA for all plans, added new 'Enterprise' section with SSO, SCIM, and custom SLA mentions...",
"impact_rationale": "Eliminating self-serve pricing and gating all plans behind sales contact indicates Lattice is shifting upmarket to enterprise. Companies making this transition typically need new sales tooling...",
"source_url": "https://www.lattice.com/pricing",
"relevance": 0.88 // 0.0-1.0; higher = more actionable for outreach
}
}Field Reference
Standard envelope and entity fields are shared across all signals — see Schema and Resolution. The fields below are specific to this signal:
Signal-Specific Fields
The data object contains everything unique to this signal type — the intelligence extracted from the website change.
| Field | Type | Description |
|---|---|---|
summary | string | LLM-generated summary describing what changed on the website and its likely business meaning. Written for a salesperson — explains the change, what it signals strategically, and why it might create an outreach opportunity. Typically 2–3 sentences |
evidence | string | Specific evidence of what changed — the actual content that was added, removed, or modified on the page. Includes page paths, quoted text, and diff-level detail. Useful for fact-checking or displaying to end users as proof of the change |
impact_rationale | string | Business impact explanation connecting the website change to a potential buying signal. Explains why this change matters commercially and what kind of vendor or solution the company might need as a result |
source_url | string (URL) | URL where the change was detected. Links to the specific page that was added, removed, or modified. Useful for manual verification or displaying alongside the signal |
relevance | float (0.0–1.0) | How actionable this website change is for sales outreach. Higher values indicate stronger commercial intent (pricing changes, product launches). Lower values indicate informational changes (blog posts, minor copy edits). Useful for prioritization and filtering |
Timing & Delivery
detected_atis when the website change was detected during our scan cycle. Usesource_urlto verify the current page state.- One signal per subtype per company per scan window. A single company may produce multiple signals across different subtypes in the same delivery, but won't fire the same subtype twice for the same change.
- Each delivery arrives in a timestamped folder. Treat all signals in a new folder as recent — no need to diff against prior deliveries.
Coverage
- Refresh: Monthly
- Coverage: 6,000,000 company websites
- Best for: Competitive intelligence, sales timing, detecting upmarket shifts, identifying active go-to-market changes
Updated 10 days ago
