Rayon growth teardown: 63/100

Rayon scores 63 out of 100 on our Level 0 Growth Scan of its public footprint. Measurement is the weaker of the two pillars we scored, at 60. The biggest single fix is a DMARC record for rayon.design. The domain has none today, and adding one takes about 30 minutes.

Rayon is a browser-based CAD tool for interior designers and architects. The Next Web describes it as Paris-based. On 29 September 2026, Tech.eu and The Next Web reported a €10M Series A led by Partech.

Method

We scanned rayon.design on 28 October 2026. This is a Level 0 scan: public footprint only, with no account access. It ran four modules with 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, and we ran no AI Visibility prompts. Those pillars show as “Not scanned” and are left out of the Growth Score.

Our raw-HTML tag check missed tags that load through JavaScript, so it reported no analytics. We loaded the homepage in a real browser at 1440 and 390 pixels wide and corrected that check to Pass. We checked DNS records through Cloudflare’s public DNS-over-HTTPS resolver.

The Agent Readiness checks read the raw HTML, because that is what crawlers that skip JavaScript see. The scores below use that reading.

Visibility: 65, Warn

Visibility averages two modules: Agent Readiness at 60 and SEO Technical at 70.

What passes: robots.txt allows all 9 AI crawlers we check, including GPTBot, ClaudeBot and PerplexityBot. The homepage is indexable, the sitemap at /sitemap.xml returns valid XML, and every entry URL lands on one HTTPS host, https://www.rayon.design/. There is one H1, “The effortless CAD”.

What does not: the homepage has no canonical tag, and /llms.txt returns 404. The title is 5 characters and the meta description is 75, both short of our targets. And http://rayon.design/ takes 2 redirects to get there: a 308 to https://rayon.design/, then a 301 to www. Run curl -sI http://rayon.design/ to see the first hop. One 301 straight to the final URL is the fix, about 2 hours.

Our raw-HTML check found no JSON-LD block. In a browser, the page does add WebSite and Organization JSON-LD, but only after JavaScript runs. Crawlers that skip JavaScript will not see it.

Measurement: 60, Warn

Measurement averages Tag Health at 60 and Email Authentication at 60.

Tag Health passes on analytics. In a real browser, the homepage sends GA4 hits to G-ECHYD5J0S3, a Google Ads config hit for account 10790139501, and LinkedIn Insight requests for partner 6863698. The Meta Pixel script also loads with pixel 805856998416989.

Tag Health fails its consent check. From test machines in India and the US on 28 October 2026, we saw no consent banner, and GA4, Google Ads and LinkedIn requests fired on first load. We did not test from an EU address. EU visitors may be treated differently.

Email Authentication passes on MX (5 Google Workspace records) and SPF (~all, 2 lookups). DKIM is a Warn: we found no key on the 8 common selectors we probe, and Rayon may use a custom one. DMARC is a Fail.

Finding 1. Fail: No DMARC record

What we checked. We looked up the TXT record at _dmarc.rayon.design.

Evidence. Query _dmarc.rayon.design for TXT with any DNS tool, for example dig TXT _dmarc.rayon.design. The answer is NXDOMAIN: the name does not exist.

Why it matters. The domain has 5 MX records and an SPF record, so it sends and receives mail. With no DMARC record, receiving servers get no instruction for mail that fails SPF or DKIM. Rayon also gets no reports on who sends mail as its domain.

Fix. Publish v=DMARC1; p=none; rua=mailto:<reporting address>, read the reports for 4 weeks, then move to p=quarantine. Effort: 30 min.

Finding 2. Fail: No canonical tag

What we checked. We looked for <link rel="canonical"> in the raw HTML and in the browser-rendered page.

Evidence. View the source of https://www.rayon.design/ and search for “canonical”. There is no match. The same is true of /pricing. https://www.rayon.design/?utm_source=test also returns the full page with a 200 status and no canonical.

Why it matters. Every tracked link creates another URL for the same page. Without a canonical, search engines and AI crawlers choose which version to index on their own.

Fix. Add a self-referencing absolute canonical to every indexable page. Effort: 30 min.

Finding 3. Warn: A 5-character homepage title

What we checked. We measured the homepage <title> against a 30 to 60 character target.

Evidence. View the source of https://www.rayon.design/. The title is <title>Rayon</title>, 5 characters. The Open Graph title is also “Rayon”.

Why it matters. The title is the blue link in search results and often the label on a shared link. Today it leaves out the category word CAD and the audience. The H1 and meta description already say “The effortless CAD” and “interior designers & architects”, so the words exist on the page.

Fix. Rewrite the title to 30 to 60 characters with the category and audience, for example “Rayon: browser-based CAD for interior designers” (47 characters). Check the other page templates while you are there. Effort: 1 day.

What Rayon does well

The hero says what it is and who it is for. The H1 “The effortless CAD” sits above “AI-powered drawing for interior designers and architects.” That is the category and the audience in 10 words, and both lines show at 1440 and 390 pixels wide.

The CTAs are clear on mobile. “try it for free” is a solid orange button, and “book a demo” is an outlined secondary. On a 390 by 844 viewport, both show without scrolling, with “sign up” in the header.

The product shows up early. Directly under the CTAs, the hero shows a screenshot of the drawing tool with a play button labeled “Discover Rayon”. It plays a product video, app.mp4.

Customer proof is linked. A “Meet our customers” strip links out to 14 customer sites, including Virgin Atlantic and Goldbeck.

The measurement stack is in place. GA4, Google Ads, LinkedIn Insight and the Meta Pixel all load on the homepage, so the base for ad and conversion tracking exists.

If we were fixing this

1. Publish a DMARC record at _dmarc.rayon.design with p=none and a rua address. Effort: 30 min.
2. Add self-referencing canonical tags to every indexable page. Effort: 30 min.
3. Publish /llms.txt with an H1, a one-line summary and links to 10 to 30 key pages. Effort: 30 min.
4. Rewrite the homepage title to 30 to 60 characters with the category and audience. Effort: 1 day.
5. Lengthen the homepage meta description from 75 to 120 to 160 characters. Effort: 1 day.

FAQ

Why is Measurement 60 when the first scan said there was no analytics? Our raw-HTML check only reads the page before JavaScript runs, and Rayon loads its tags with JavaScript. A real browser showed GA4, Google Ads, LinkedIn Insight and the Meta Pixel loading, so we scored the analytics check as Pass. Tag Health moved from 0 to 60.

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

How long would the first five fixes take? About 1.5 hours for the three 30-minute fixes, plus 2 days for the title and description work. None of them needs a redesign.

Run the same Growth Scan on your own site.