Alta growth teardown: 86/100

Alta scores 86 out of 100 on our Level 0 Growth Scan of its public footprint. Measurement is the weaker of the two pillars we scored, at 85. The biggest single fix is the DMARC record for altahq.com. It is set to p=none with no reporting address, and adding one takes about 30 minutes.

Alta builds AI agents for go-to-market teams. Its homepage H1 reads “The AI platform built for go-to-market teams.” SiliconANGLE describes Alta as Israel-based and reported on 8 July 2026 that it raised a $25 million Series A led by IN Venture.

Method

We scanned altahq.com on 28 October 2026. This is a Level 0 scan: public footprint only, with no account access. Four modules returned scored results: Agent Readiness, SEO Technical, Tag Health and Email Authentication. Content and Entity and Tech Stack returned no scored checks.

We did not scan Acquisition, Conversion or Retention. AI Visibility prompts, the Meta and Google ad library checks and the conversion checks launch later. Until then those pillars show as “Not scanned” and are left out of the Growth Score.

Our tag check reads raw HTML, so it misses tags that load through Google Tag Manager. To verify the tags, we loaded the homepage in a headless Chromium browser at 1440 and 390 pixels wide, from a US network address, and recorded every request. We checked DNS through Cloudflare’s public DNS-over-HTTPS resolver.

The homepage runs a client-side test. A script in the page sends about two in three first-time visitors from / to /b or /c with location.replace. Our checks read /, which is the URL in the sitemap and in the canonical tag.

We changed two scanner results after checking by hand. The scanner measured the meta description at 162 characters because it counted the HTML entity ' as six characters. The decoded text is 157 characters, a Pass. The scanner also passed “HTTPS and single host” without counting hops. http://altahq.com/ takes 2 redirects to reach https://www.altahq.com/, and our spec scores a chain of more than 1 hop as Warn. With both changes, Visibility is 86 and the Growth Score is 86.

Visibility: 86, Pass

Visibility averages two modules: Agent Readiness at 87 and SEO Technical at 85.

What passes: robots.txt allows all 9 AI crawlers we check, and names GPTBot, OAI-SearchBot, PerplexityBot and ClaudeBot in their own Allow: / group. /llms.txt returns 200 with an H1 and 5 links. The sitemap returns valid XML with 364 URLs. The homepage has a self-referencing canonical, no noindex, one H1, a 52-character title and a 157-character meta description.

What does not: the JSON-LD is a two-property Organization block with no page type (Finding 3). A request for https://altahq.com/robots.txt returns a 301 to the www host before it serves the file. http://altahq.com/ goes to https://altahq.com/ and then to https://www.altahq.com/, so it takes 2 hops where 1 would do.

Measurement: 85, Pass

Measurement weights Tag Health at 86 (weight 1.0) and Email Authentication at 85 (weight 0.8).

Tag Health passes on analytics. In a browser, the homepage loads Google Tag Manager container GTM-5BCNGQWG, GA4 property G-FSEE0QBWKT, a Google Ads tag for AW-11466588388, the Meta Pixel 1216091939570444, LinkedIn Insight for partner 6326073, Hotjar site 3163169 and HubSpot portal 23399151. The raw HTML holds only the GA4 config and GTM. The rest loads through GTM, which is why our raw-HTML check missed the Meta Pixel and the Google Ads tag. Both of those checks stay info-only until the Ad Footprint scan runs. The consent check is a Warn (Finding 2).

Email Authentication passes on MX (5 Google Workspace records), SPF (-all, 2 lookups) and DKIM (a key at selector s1). DMARC is a Warn (Finding 1).

Finding 1. Warn: DMARC is set to p=none with no reports

What we checked. We looked up the TXT record at _dmarc.altahq.com.

Evidence. Run dig TXT _dmarc.altahq.com, or any DNS lookup tool. The answer is "v=DMARC1; p=none;". There is no rua tag.

Why it matters. The SPF record authorizes HubSpot and Google to send for altahq.com, and the DKIM selector s1 points at SendGrid. That is at least 3 services sending as the domain. With p=none, receiving servers take no action on mail that fails SPF and DKIM. With no rua address, Alta gets no reports on who sends mail as altahq.com, so it has no data to move the policy forward.

Fix. Publish v=DMARC1; p=none; rua=mailto:<reporting address>. Read the reports for 4 weeks, confirm all 3 senders pass, then move to p=quarantine and later p=reject. Effort: 30 min.

Finding 2. Warn: The first Google tag fires before any consent state is set

What we checked. We checked the order of the consent setup and the first Google tag, in the raw HTML and in a browser.

Evidence. View the source of https://www.altahq.com/ and search for gtag('config. The head contains gtag('config', 'G-FSEE0QBWKT');gtag('config', 'UA-240320255-1', {'anonymize_ip': false});. There is no gtag('consent', 'default' call before it. Now search the same source for “cookieyes”. There is no match, because the CookieYes banner loads later through GTM-5BCNGQWG. In DevTools, filter the Network tab by “collect”. In both of our runs, the first GA4 request carried gcd=13l3l3l3l1l1. In that parameter, each l marks a consent signal with no value set. Requests after the CookieYes update carry gcd=13u3u3u3u5l1.

Why it matters. Google’s Consent Mode expects a default state before any tag fires. Here the first GA4 request leaves before any state exists, so early and late hits from the same visit are recorded under different consent settings. The same snippet configures UA-240320255-1, a Universal Analytics property. Google’s help center says standard Universal Analytics properties stopped processing hits on July 1, 2023. The browser still requests gtag/js?id=UA-240320255-1 on every load.

We tested from a US address and saw the CookieYes banner. Visitors in other regions may see different behavior.

Fix. Delete the UA config line (30 min). Then set Consent Mode defaults for ad_storage, ad_user_data, ad_personalization and analytics_storage before the first tag. Either add a gtag('consent', 'default', ...) call above the snippet, or move the GA4 config into GTM behind the CookieYes default. Effort: 1 day.

Finding 3. Warn: The Organization JSON-LD has two properties

What we checked. We read every JSON-LD block on the homepage.

Evidence. View the source of https://www.altahq.com/ and search for ld+json. There is one block:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Alta",
  "url": "https://www.altahq.com/"
}

There is no logo, no sameAs and no WebSite or WebPage block.

Why it matters. The homepage links 4 company profiles: LinkedIn, X, YouTube and G2. The G2 link uses the slug graphiti-alta. sameAs is the field that tells search and AI engines those profiles belong to the same company. Today the markup gives a name and a URL and connects them to nothing else.

Fix. Add logo, a one-line description and sameAs with the 4 profile URLs to the Organization block. Add a WebSite block with name and url. Effort: 2 hours.

What Alta does well

AI crawlers are welcome. robots.txt allows every crawler we check and names GPTBot, OAI-SearchBot, PerplexityBot and ClaudeBot under Allow: /. A second group allows ChatGPT-User and Perplexity-User. /llms.txt is 2,638 bytes of plain text with an H1, a summary and 5 links.

The homepage test keeps index signals clean. The test pages /b and /c both carry <meta content="noindex" name="robots"/> and a canonical to https://www.altahq.com. The root page has no noindex. Both test pages tell search engines to index the root instead of themselves.

The hero says what and for whom, in the raw HTML. The H1 “The AI platform built for go-to-market teams” sits above “Agents that find prospects, qualify leads, and book meetings, so your team can focus on closing.” Both lines are in the HTML before JavaScript runs. At 1440 and 390 pixels wide, they show above the fold with one dark “Book a demo” button.

The site runs its own product. A chat panel titled “Alta assistant” loads from widgets.altahq.com and opens with “Hi, I’m Alex. I book meetings with your leads in seconds.” A visitor meets the agent before booking the demo.

If we were fixing this

1. Add a rua address to the DMARC record, then move from p=none to p=quarantine once reports are clean. Effort: 30 min.
2. Delete the gtag config line for UA-240320255-1. Effort: 30 min.
3. Set Consent Mode defaults for all four v2 signals before the first Google tag fires. Effort: 1 day.
4. Add logo, sameAs and a WebSite block to the homepage JSON-LD. Effort: 2 hours.
5. Send http://altahq.com/ to https://www.altahq.com/ in one 301 instead of two. Effort: 2 hours.

FAQ

Why does the homepage sometimes load as /b or /c? A script on / assigns each new visitor to one of three versions and stores the choice in the browser under the key ab_home. About two in three first visits move to /b or /c. Both carry noindex and point their canonical at /, so we scored /.

Why is the score 86 when the scanner said 88? We checked two results by hand. The meta description is 157 characters, not 162, which turns a Warn into a Pass. The http redirect takes 2 hops, which turns a Pass into a Warn under our spec. The second change is larger, so Visibility moved from 91 to 86.

Does this mean Alta runs paid ads? We did not scan the Meta or Google ad libraries, so we make no claim about live ads. The Google Ads, Meta Pixel and LinkedIn Insight tags show the site is set up to measure ad traffic. Acquisition shows as “Not scanned”.

Run the same Growth Scan on your own site.