BASE
Born from crawled page content, not sitemap alone
BASE
AI language on real pages, after discovery — never from the map alone.
Enroll, map URLs, crawl content, then write a Web AI row only when a page clears the quality bar — product claims with substance, not vague AI marketing. Sitemap mapping alone never creates a signal.
- Sitemap / path map never creates signals
- Rows come from page content after crawl + quality check
- Multiplicity is by URL / page kind — which surface spoke
- Vague AI marketing does not ship
Sample signalBASE
Web AI · /product/agents
Discovery · map never writes · sample
Enroll
Map
Crawl
Qualify
/product/agents
Web AI Activity
Cleared quality bar · monitored product page
productchangelogcareersblog
BASE
Role
Discover
Journey
Gated
Quality
At a glance
How this signal shows up in the store
Discover
Discovery pipeline: enroll → map → crawl → qualify
Gated
Proprietary quality bar — keep or discard
URL
One qualifying page can earn its own timeline row
What it is
Evidence that a specific page shows meaningful AI language
A Web AI signal is evidence that a specific company page shows meaningful AI product or ops language — not vague “AI-powered” marketing. Multiplicity is which pages you watch: different URL kinds can each earn their own row.
Discovery always maps the site first. The first successful map is a baseline URL inventory with no signals. Timeline rows appear only after content crawl and a proprietary quality check on first fetch or a real content change.
- Monitored kinds include product, features, changelog, about, and careers
- Blog and news roots discover children; they are not themselves the signal source
- Unchanged content does not rewrite the same signal
Signature story
Discovery pipeline + page kinds
Sitemap never creates signals. Rows come from crawled page content that clears the quality bar — by URL kind.
Enroll → map → crawl → qualify → row
Discovery journey
Enroll
Company enters web pipeline
Sitemap
URL inventory only
Crawl
Content fetch
Prefilter
AI-language soft gate
Qualify
Proprietary quality bar
Write row
Web AI Activity
Page kinds
Monitored
product · features · changelog · about · careers
Re-crawled on a cadence
Discovery roots
blog · news · updates
Find children — not the signal source
One-shot children
blog posts and similar
Usually crawled once after discovery
Quality bar
Substance ships · fluff discards
Vague AI marketing never becomes a row
How we judge it
Discovery pipeline, step by step
Web AI is a discovery journey: mapping comes first; timeline rows come only later from content that clears the bar.
- 1
Enroll the company
Companies with hiring or funding activity are typically enrolled into the web pipeline and may get crawl priority when other signals fire.
- 2
Map the site
Build or refresh monitored and discovered URLs. No signal is written here — the first successful run is baseline inventory only.
- 3
Crawl and prefilter
Crawl prioritized pages. Soft AI-language prefilter stops pages that do not look AI-related. Unchanged content updates timestamps only.
- 4
Qualify and write
On first crawl or content change, proprietary judgment grades the page. Qualifying evidence writes one Web AI row for that URL. Weak marketing writes nothing.
Signal strength
Why the score means something
Web AI uses a proprietary quality bar across pages — keep or discard — so vague AI marketing never floods the timeline.
EvidenceStrengthNote
- Structural product evidenceHighestDedicated product / case-study style substance
- Specific AI claimStrongConcrete claim with measurable substance
- Vague marketing—No row written
- Write-time score0–100Set when the page qualifies
Stock vs flow
Web AI vs “mentions AI on the homepage” lists
Keyword scrapes treat every AI phrase as intent. Web AI waits for mapped URLs, real content changes, and a quality bar before writing a row.
Layer
Traditional
VeilStrat
Discovery
Before any row
Scrape homepage once
No URL inventory discipline
Sitemap baseline first
Map never creates signals alone
Quality
What counts
Any AI buzzword
Marketing fluff looks like product
Proprietary quality bar
Substance ships; fluff discards
Unit
Granularity
One company-level AI flag
Loses which surface fired
Per URL / page kind
Product vs changelog vs post
Change
When it refreshes
Quarterly re-scrape
Misses mid-cycle launches
First crawl or real content change
Unchanged content → no rewrite
Discovery
Before any row
Traditional
Scrape homepage once
No URL inventory discipline
VeilStrat
Sitemap baseline first
Map never creates signals alone
Quality
What counts
Traditional
Any AI buzzword
Marketing fluff looks like product
VeilStrat
Proprietary quality bar
Substance ships; fluff discards
Unit
Granularity
Traditional
One company-level AI flag
Loses which surface fired
VeilStrat
Per URL / page kind
Product vs changelog vs post
Change
When it refreshes
Traditional
Quarterly re-scrape
Misses mid-cycle launches
VeilStrat
First crawl or real content change
Unchanged content → no rewrite
Example snapshots
What a Web AI row looks like
Illustrative page fires — real rows attach URL, page kind, and strength without dumping the grading recipe.
- Product surface
Web AI · /product/agents
Structural product evidence on a dedicated page after crawl and quality check.
Kind: product · Highest strength
- Concrete claim
Web AI · /changelog
Specific AI claim with measurable substance clears the bar on a monitored page.
Kind: changelog · Strong
- No ship
Sitemap baseline only
URL inventory refreshed — still no timeline row until content qualifies.
Map step · No Web AI row written
GTM moments
Public product language before the shortlist
Use Web AI when published site language is the earliest buying signal you can trust.
Timing
Catch launches before RFPs
Product and changelog pages often fire months before a vendor shortlist forms.
Context
Know which surface spoke
Page kind and URL in the snapshot give reps a concrete citation for outreach.
Enrich
Refresh slices when pages fire
Web AI can soft-refresh notebooks and trigger a targeted hiring pull for the company.
Filter
Ignore vague AI marketing
The quality bar keeps fluff off the timeline so lists stay usable.
Discovery journey
Sitemap never creates signals
The first successful map is a baseline of URLs. Signals come from page content — first fetch or a real content change — after an AI-language prefilter and a proprietary quality check. Different URLs can each earn their own Web AI row for the same company.
Related signals
How this connects on the timeline
Public product language before the shortlist — explore the signals that feed or follow this type.
FAQ
Web AI activity, answered
What Web AI means for discovery, quality, and GTM timing.
It is a BASE timeline row showing that a specific company page cleared an AI-language prefilter and a proprietary quality bar after content crawl — not after sitemap mapping alone.
Read what companiespublish about AI.
Web AI signals attach to real URLs — after discovery and crawl — so you act on product language, not sitemap noise.
© 2026 VeilStrat. All rights reserved.All systems operational