Boundaries
What HubSEO deliberately does not do. The limits are the product's integrity.
These boundaries are architectural decisions, not missing features. Each one exists because the alternative would require fabricating or trusting data HubSEO cannot verify.
No internet-scale crawler
HubSEO does not scrape billions of URLs across the web the way backlink-index platforms do. It measures, deeply and precisely:
- Your verified Search Console properties.
- Up to 5 competitor domains you explicitly select.
That is the whole measured surface. Anything wider would mean reselling third-party datasets HubSEO cannot audit.
The 8 paused legacy tools
Tools that previously relied on unverified scraping or mock vanity numbers are paused until production evidence criteria are satisfied:
Needs a verified domain-level data provider. Paused rather than reselling unverifiable third-party metrics.
Needs a real backlink index. Paused: HubSEO will not resell or simulate link data it cannot verify.
Local AI readiness is active; external observation requires a configured provider with real samples.
Needs grounded content data, not generated filler dressed as research.
Targeted competitor monitoring is active; internet-wide gap scraping is paused.
Paused pending live connected evidence rather than heuristic scores.
Paused tools return transparent status cards explaining what evidence they need. They do not render placeholder numbers.
Strict lab versus field separation
Lighthouse lab runs never masquerade as real Interaction to Next Paint measurements. INP is reported exclusively from CrUX real-user p75 field data. A URL with no public field sample reports no INP, plainly.
No autonomous deployment for protected changes
Protected interventions: 301 redirects, canonical tags, robots.txt, URL
migrations. These strictly require explicit human verification and cannot be
auto-deployed by AI under any configuration. Safeguarding uptime outranks
automation coverage. See Autonomous mode.
Scores are diagnostics, not prophecies
No HubSEO score predicts traffic, rankings, revenue, or real-engine visibility. See Claims we refuse to make and How scores are computed.
The roadmap note
Some of these boundaries move as verifiable integrations land: additional CMS connectors (Webflow, Squarespace, Wix), GA4 funnel ingestion, native AI-answer observation across more providers, and edge-injection through Cloudflare Workers. Each lands only when the evidence standard can be met.