Tsoden
Public audit for vast-neracu.vercel.app

What we found

Dependency graph and impact analysis for your GitHub repo is 7 fixes away from more trial signups.

7 things a visitor needs are missing. The ones costing you the most: Search engines can’t tell what you sell, no easy way to get in touch and AI assistants have nothing to read, plus 4 more below.

Read from 5 live pages · metadata, crawlability, trust, CTA, schema, sitemap, robots, llms.txt

Questions about this audit? Reply to the email or write to us — a human answers same day.

7 fixable leaks

The complete, prioritized plan to fix all 7 leaks above and win more trial signups — written for Dependency graph and impact analysis for your GitHub repo, delivered instantly.

Book a free 30-min call See what's leaking ↓

What buyers and AI/search engines see right now

Pages checked55 read in full
How we read itRead as crawlers doSame view buyers & bots get
Response time16589msWell over the 2.5s target
Checks verified6/137 need fixing

Diagnostics

What we checked, and what we found

41 checks across six areas — search visibility, AI & answer engines, performance, security, conversion and trust — each measured against Dependency graph and impact analysis for your GitHub repo's live site.

25 pass 0 warn 16 fail

Of the 41 checks we ran on your page

Anything we couldn’t read is its own segment — a page that blocks our reader is our limitation, not a mark against you, and it never lowers your score.

Fine as-is — 25Needs fixing — 16Couldn’t read — 0
See the numbers
StateCountShare
On your page2561%
Missing1639%
Couldn’t read00%

Where your page is strong, and where it isn’t

Each area is scored 0–100 against what a customer needs to find before they act.

strong (75+)close (50–74)needs work (under 50)
Can they take the next step 65
Reasons to believe you 60
Can people find you 81
Can AI assistants read it 0
Speed on a phone 44
A safe, trusted connection 100
See the numbers
Part of your pageScoreHow that reads
Can they take the next step65/100close
Reasons to believe you60/100close
Can people find you81/100strong
Can AI assistants read it0/100needs work
Speed on a phone44/100needs work
A safe, trusted connection100/100strong

Priorities

Fix these first

Ranked by revenue impact. Each one is something developers — or an AI answer engine — need to see and currently can't. Fixing the top few moves your score the most.

01

Search engines can’t tell what you sell

Add structured data (LocalBusiness / Organization schema: address, hours, phone, ratings) so search engines show you with rich results.

02

No easy way to get in touch

Simplify the process for developers to connect their GitHub repo and access risk reports.

03

AI assistants have nothing to read

Publish /llms.txt with a concise machine-readable product summary, audience, pricing, and docs links.

04

The page is slow to answer

Speed up the homepage — most developers arrive on a phone, and a slow first load loses them before the page shows.

05

Shared links look broken

Add Open Graph tags so shared links render with a clear title and value proposition.

06

Search engines have no map of your site

Publish /sitemap.xml and submit it to search engines.

07

No robots.txt telling crawlers what to do

Publish /robots.txt with a sitemap reference and no accidental blocking.

What we read on your page

What a customer finds — and doesn’t

6 of the 8 things we could check are already on your page. Your page already has 6 of the 8 things a customer looks for. You don't need a redesign — just the few that are missing.

Below is the breakdown: what's already working (with the exact text quoted from your page as proof), and the highest-impact additions to win more trial signups — in priority order.

Scope: an automated scan of the 5 pages we could read across your site. Every “found” item quotes the exact text on your page so you can verify it. It doesn't judge copy quality or design.

Already on your page

  • A headline that says what you do — found: “Catch risks before release.”
  • An obvious button that starts the thing — found: “Try it free →”
  • Reviews or proof from real customers — we found “Review”, which points at it, but no actual review or rating on the page we read
  • A concrete number, not an adjective — we found “2 minutes”, which points at it, but no actual number on the page we read
  • Something that removes the risk of trying you — found: “no credit card”
  • A price, or at least a from-figure — found: “$0” (on /pricing)

What to add, in order of impact

  • An easy way to get in touch — Give an easy capture path: short form, booking link, or contact route from the first screen.
  • Answers to the questions people ask before buying — Answer the top 3-5 buyer objections in an FAQ to remove hesitation before the CTA.

Deliverable

The full write-up is ready

We've already done the full work-up for Dependency graph and impact analysis for your GitHub repo — every fix written out, with copy and code ready to paste. Here's what's inside:

Complete fix plan (every issue, step by step)

1. Search engines can’t tell what you sell

Add structured data (LocalBusiness / Organization schema: address, hours, phone, ratings) so search engines show you with rich results.

  1. Add JSON-LD using the schema snippet below, edited with your real details.
  2. Validate it in Google's Rich Results Test before publishing.
  3. Keep it in sync with the on-page facts (name, address, phone, offers).

2. No easy way to get in touch

Simplify the process for developers to connect their GitHub repo and access risk reports.

  1. Add a visible booking link, short form, or tap-to-call number on the first screen.
  2. Keep the form to 3 fields max; every extra field drops completion.
  3. Confirm submissions with a clear success state, not a silent reload.

3. AI assistants have nothing to read

Publish /llms.txt with a concise machine-readable product summary, audience, pricing, and docs links.

  1. Publish /llms.txt with a plain-text product summary, audience, pricing and key links.
  2. Keep it concise — answer engines reward clear, factual structure.
  3. Update it when your offer or pricing changes.

4. The page is slow to answer

Speed up the homepage — most developers arrive on a phone, and a slow first load loses them before the page shows.

  1. Compress and lazy-load images; serve modern formats (WebP/AVIF).
  2. Put the site behind a CDN and enable caching of static assets.
  3. Defer non-critical JavaScript so the first screen paints fast.

5. Shared links look broken

Add Open Graph tags so shared links render with a clear title and value proposition.

  1. Add og:title, og:description, og:image and og:url to <head>.
  2. Use a 1200×630 share image with the value proposition baked in.
  3. Test the preview with the Facebook/LinkedIn debuggers.

6. Search engines have no map of your site

Publish /sitemap.xml and submit it to search engines.

  1. Publish /sitemap.xml listing every indexable URL with <lastmod>.
  2. Reference it from robots.txt and submit it in Google Search Console.
  3. Regenerate it automatically whenever pages change.

7. No robots.txt telling crawlers what to do

Publish /robots.txt with a sitemap reference and no accidental blocking.

  1. Publish /robots.txt that allows crawling and points to your sitemap.
  2. Double-check you are not accidentally Disallow-ing the whole site.
  3. Remove any leftover 'Disallow: /' from staging.

Done-for-you assets — copy & paste

SEO title
Where to paste: Replace the <title> tag inside your page <head>.
Vast — AI Code Architecture Visualization
Meta description
Where to paste: In <head>, set <meta name="description" content="…"> to this (replace the old one).
Transform your codebase into interactive risk maps. Catch issues before release with Vast’s AI-powered insights.
H1 — main page heading
Where to paste: Make this the single <h1> at the top of the homepage (real text, not an image).
Visualize Your Codebase Risks Instantly

— or one of these —
- Identify Code Risks Before Deployment
- Get Instant Insights into Your Code Architecture
Primary CTA button
Where to paste: Use as the main button on the first screen; repeat it after your proof/services section.
Try it Free
JSON-LD structured data (Organization)
Where to paste: Paste this entire block right before </head> (or before </body>).
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Dependency graph and impact analysis for your GitHub repo",
  "url": "https://vast-neracu.vercel.app/",
  "description": "Vast provides AI-driven visualization of microservice architectures for risk assessment.",
  "makesOffer": [
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Interactive dependency mapping"
      }
    },
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Risk scoring per file"
      }
    },
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "GitHub repository integration"
      }
    },
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Real-time change tracking"
      }
    },
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Automated risk reporting"
      }
    }
  ]
}
</script>
robots.txt
Where to paste: Create a plain text file at vast-neracu.vercel.app/robots.txt with this content.
User-agent: *
Allow: /
Sitemap: https://vast-neracu.vercel.app/sitemap.xml
llms.txt (for AI answer engines)
Where to paste: Create a plain text file at vast-neracu.vercel.app/llms.txt with this content.
# Dependency graph and impact analysis for your GitHub repo

> Transform your codebase into interactive risk maps. Catch issues before release with Vast’s AI-powered insights.

## Services
- Interactive dependency mapping
- Risk scoring per file
- GitHub repository integration
- Real-time change tracking
- Automated risk reporting

## Links
- https://vast-neracu.vercel.app/

Page-by-page findings

PageWhat to fix
/looks healthy
/pricingno H1 heading
/termslooks healthy
/aboutlooks healthy
/contactlooks healthy

Action order

48-Hour Fix Plan

  • Add structured data (LocalBusiness / Organization schema: address, hours, phone, ratings) so search engines show you with rich results.
  • Simplify the process for developers to connect their GitHub repo and access risk reports.
  • Publish /llms.txt with a concise machine-readable product summary, audience, pricing, and docs links.
  • Speed up the homepage — most developers arrive on a phone, and a slow first load loses them before the page shows.
  • Add Open Graph tags so shared links render with a clear title and value proposition.

Why it matters

The fastest developers do not read every page. They scan the first screen, trust signals, pricing cues and how easy it is to start a free trial. Missing signals make the offer harder to understand and easier to ignore.

Packages

Turn this into more trial signups

You've seen the leaks. Most owners start with the €49 full report — the same fixes we'd implement for €199, written out so you can do them yourself. Want it hands-off? Step up a tier.

Do it yourselfFree

The complete evidence report and the prioritized, step-by-step plan for Dependency graph and impact analysis for your GitHub repo — every fix written out with copy & code ready to paste. It is on this page. Nothing to buy, nothing to unlock.

Read the full plan ↑
Done-for-you — 48h€199

We implement the highest-impact fixes for Dependency graph and impact analysis for your GitHub repo — metadata, schema, CTA, llms.txt, trust signals — in 48 hours. You keep every bit of the lift, no lock-in.

Have us do it — €199
Ongoing monitor€499/mo

Weekly re-checks of Dependency graph and impact analysis for your GitHub repo + drift alerts so the fixes compound and never silently slip back.

Start monitoring

Not sure which fits? Book a free 30-min call and we'll tell you straight. · 48-hour turnaround · no lock-in · every claim verified.

Verification

The exact wording we found

Every signal below was read from your live site — nothing is estimated. We checked 5 pages; “couldn’t verify” means a signal needs JavaScript to read and we won’t guess.

What we read

TitleVast — AI-powered code architecture visualization
Meta description121 chars
H1 heading Found 4/5
Structured data Missing

Crawl & AI files

robots.txt Missing
sitemap.xml Missing
llms.txt (AI) Missing
Response time16589ms

Pages we checked

/
Vast — AI-powered code architecture visualization
Read
/pricing
Pricing | Vast
Read
/terms
Terms of Service | Vast
Read
/about
About | Vast
Read
/contact
Contact | Vast
Read

Questions about anything in here? Reply to the email, or reach us directly — we answer the same day.

Email

Who we are

Tsoden — a full-service web studio

We don't just audit — we build and rank websites end-to-end. Web development & design, plus SEO & AEO, so your business shows up in Google and in AI answers like ChatGPT, Perplexity and Gemini. This report is where we start; we can implement every fix below and grow your visibility on a full-service basis.

Web development & redesign — fast, conversion-first sites
SEO — rank in Google for what your buyers actually search
AEO — get found & cited by AI answer engines (ChatGPT, Perplexity, Gemini)
Ongoing monitoring & growth — we keep it improving
Work with Tsoden →or email support@tsoden.ai

Curious how a competitor scores?

Run the same free check on any site — the same buying signals, the same evidence quoted from the page itself. About a minute, no email needed to see the result.

Disclaimer

This service is a marketing and informational tool based on public website signals. It is not legal, financial, tax, investment, security, or professional advice. Scores and recommendations are estimates, not guarantees of revenue, rankings, AI visibility, deliverability, or business outcomes. You remain responsible for reviewing, approving, and implementing any changes and for complying with laws that apply to your business.

Full disclaimer · Terms · Privacy

This audit is from 28 Aug 2026 — we re-run it fresh when you order Dependency graph and impact analysis for your GitHub repo · Grade D · 49/100
Done-for-you — €199 Book a free 30-min call