https://saaspilot.app·Oct 6, 2026, 04:59 PM UTC·11 technologies·AI

saaspilot.app

Built with Html5, Javascript, Next Js, Node Js, React and 6 more

https://saaspilot.app

Performance

TTFB

126ms

DOM Ready

401ms

Load Complete

401ms

Requests

Total Size

614KB

Domains

Errors

Technologies

Other

Html5

Scripthigh

Javascript

Scripthigh

Next Js

AIhigh

Node Js

AIhigh

React

AIhigh

Sitebeacon

AIhigh

Sonner

AIhigh

Vercel

AImedium

Webpack

AImedium

Inter Font

AIlow

Typescript

AIlow

Company estimate

Company

SaaSPilot

AI-powered website automation and data extraction platform

Estimated annual tech spend

$30K

The page clearly identifies the company as SaaSPilot via the <title> 'SaaSPilot — drive any site' and the meta description describing a service that turns plain-language requests into validated browser-automation recipes published as API endpoints, webhooks, or chat assistants. No HQ, founding year, valuation, or employee-count signals appear anywhere in the page, and SaaSPilot is not a company recognised from prior knowledge, so valuation, headquarters, yearFounded, employeeCountEstimate, and ticker are all null (techSpendUsd is a rough inference from the Next.js/Vercel stack with LLM-backed recipe generation).

SEO recommendations

SEO health score

SaaSPilot's homepage has solid on-page basics — a real title and a well-written meta description — but it is missing structured data, a canonical tag, and OpenGraph/social tags, with no visible sitemap or robots reference and a JS-heavy Next.js shell that leaves crawlable content and internal links unproven, so the biggest technical wins are unclaimed.

Add structured data to your websiteVery High
No JSON-LD or schema.org markup appears anywhere in the head, so search engines get no entity or product context for what SaaSPilot offers.
→ Add JSON-LD WebSite + Organization blocks (via Next.js next/script) and FAQPage markup for the landing sections so rich-result features become eligible.
85%
impact
Improve page speedVery High
Two precedence-ordered stylesheets render-block first paint, multiple Next.js JS chunks load up front, and a third-party sitebeacon script is included, though the font is preloaded with crossorigin and scripts are async.
→ Run PageSpeed Insights on the live URL, inline or defer critical CSS, keep the sitebeacon script fully deferred, and lazy-load any below-fold images or video.
70%
impact
Trailing slashes may cause duplicate contentHigh
No rel=canonical link tag is present in the head, so http/https and trailing-slash variants of the homepage can split ranking signals across duplicate URLs.
→ Add a self-referencing canonical <link rel="canonical" href="https://saaspilot.app/"> and enforce one URL format (non-trailing slash) site-wide.
70%
impact
Optimize your sitemapVery High
No XML sitemap link or robots.txt reference is visible in the HTML, so discoverability of a mostly client-rendered Next.js site is unverified.
→ Generate /sitemap.xml with next-sitemap, reference it in robots.txt, and ensure it lists the canonical homepage URL plus pricing/docs pages.
60%
impact
Improve internal linkingVery High
The visible HTML is mostly an app-shell bootstrap with no crawlable body content shown, so the internal link graph between the homepage, pricing, docs and the recipe/API product is unconfirmed.
→ Add a static footer and header nav with anchor-rich links (Docs, Pricing, API, Get started) and confirm they are present in the served HTML, not only after JS runs.
55%
impact
Content to-do listMedium
The homepage HTML is mostly JS bootstrap, leaving little crawlable semantic content (headings, explainer copy, FAQ) to rank for high-intent queries like site recipe API or webhook generation.
→ Build out crawlable H1/H2 sections covering use cases, how recipes are validated, and an FAQ, plus a few long-form posts such as 'what is a site recipe'.
50%
impact
Avoid internal redirectsHigh
The head gives no evidence of redirect handling, so http→https or www→apex hops on saaspilot.app could be chains that waste crawl budget.
→ Verify https://saaspilot.app resolves with a single 301 (no www or http hops) using server-level rules, and keep redirects out of client-side JS.
45%
impact
Review similar contentHigh
This is a single app-style page with no visible crawlable body copy, so thin or overlapping content between the homepage and landing/feature variants is a real risk.
→ Audit /, /pricing and any feature pages for duplicated or near-duplicate copy and consolidate variants that target the same queries.
40%
impact
Add OpenGraph tagsMedium
No og: or twitter: meta tags appear in the head, so LinkedIn, X, and Slack link previews will fall back to whatever their scrapers happen to extract.
→ Add og:title, og:description, og:url, og:image (the brand mark) and twitter:card via Next.js metadata export so shares render rich previews.
35%
impact
Improve page titlesLow
Title 'SaaSPilot — drive any site' is present and on-brand but short (about 24 chars) and 'drive any site' is vague as a standalone keyword target.
→ Keep the brand and expand the tagline with the core query, e.g. 'SaaSPilot — turn any website into an API, webhook or chat assistant'.
15%
impact
Improve meta descriptionsLow
A roughly 200-character description is present, clearly explains the product (recipes, API endpoint, webhook, chat assistant) and reads persuasively.
→ No change needed now; optionally A/B test a version that leads with the primary search phrase and a call to action.
10%
impact

AI-generated SEO assessment · impact = estimated priority for this page

Specification compliance (24 shortcomings)

Specification compliance score

22/28 required and 10/32 recommended practices implemented. 24 shortcomings to address.

22/28

Required

10/32

Recommended

Shortcomings

63%

Overall

The HTML doctypeRequired
Standards-mode <!doctype html> present.
100%
Implemented
The lang attribute on <html>Required
<html> declares a language.
100%
Implemented
<meta charset>Required
Character encoding declared.
100%
Implemented
<meta viewport>Required
Responsive viewport meta present.
100%
Implemented
The <title> elementRequired
Page has a non-empty <title>.
100%
Implemented
<meta name="description">Recommended
Meta description present.
100%
Implemented
Canonical URL (rel="canonical")Recommended
No rel="canonical" — risks duplicate-content dilution.
0%
Not implemented
Favicons and app iconsRecommended
Icon link(s) declared.
100%
Implemented
<meta name="theme-color">Recommended
No theme-color — mobile browser UI will not match your brand.
0%
Not implemented
<meta name="color-scheme">Recommended
No color-scheme — form controls and scrollbars will not adapt to dark mode.
0%
Not implemented
Open Graph protocolRecommended
No Open Graph tags — shared links will render without rich previews.
0%
Not implemented
Feed discovery with rel="alternate"Recommended
No feed discovery link found — only relevant if the site publishes a feed.
—
Needs review
Feed content hygieneRecommended
Feed content quality cannot be assessed from a page scan.
—
Needs review
Popover APIRecommended
No popover attributes — only applies if the page has popovers/menus.
—
Needs review

robots.txtRecommended
No robots.txt found at the site root.
0%
Not implemented
XML sitemapsRecommended
No sitemap.xml found and none referenced in robots.txt.
0%
Not implemented
Sitemap index filesRecommended
No sitemap index — only needed once you exceed 50k URLs / 50MB.
—
Needs review
Image and video sitemap extensionsOptional
No image/video sitemap extensions detected.
—
Needs review
URL structureRecommended
URL path is clean and readable.
100%
Implemented
Redirects (301/302/308)Required
http:// redirects to https with a 3xx status.
100%
Implemented
Soft 404sAvoid
Nonexistent paths return a real 404/410.
100%
Implemented
Meta robots and X-Robots-TagRequired
Indexing is not being blocked by robots meta / X-Robots-Tag.
100%
Implemented
Heading hierarchyRequired
Exactly one <h1> heading.
100%
Implemented
Internal linkingRecommended
12 internal links found.
100%
Implemented
Structured data (JSON-LD)Recommended
No JSON-LD — add schema.org structured data for rich results.
0%
Not implemented
BreadcrumbsRecommended
No breadcrumb structured data or navigation found.
0%
Not implemented
IndexNowOptional
IndexNow integration cannot be detected from a page scan.
—
Needs review

Colour contrastRequired
Colour contrast requires rendering analysis — review with an automated contrast checker.
—
Needs review
Image alt textRequired
No <img> elements to caption.
100%
Implemented
Form labelsRequired
No form fields requiring labels.
100%
Implemented
Keyboard navigationRequired
Keyboard operability needs interactive testing.
—
Needs review
Visible focus indicatorsRequired
Focus-indicator visibility needs rendering review.
—
Needs review
Skip linksRecommended
No skip link — keyboard users must tab through the nav on every page.
0%
Not implemented
Semantic HTML and landmarksRequired
Semantic landmark elements in use.
100%
Implemented
ARIA — first rule of ARIARecommended
No obvious ARIA misuse, but full review needs assistive-tech testing.
—
Needs review
Descriptive link textRequired
Link-text quality needs manual review.
—
Needs review
Empty links and buttonsAvoid
No empty links or buttons detected.
100%
Implemented
Accessible form errorsRequired
Form-error accessibility needs interactive testing.
—
Needs review
Document and parts languageRequired
Document language is declared.
100%
Implemented
Reduced motionRequired
prefers-reduced-motion handling detected.
100%
Implemented
Accessibility overlaysAvoid
No accessibility-overlay widget detected.
100%
Implemented
Captions and transcriptsRequired
No audio/video requiring captions.
100%
Implemented
Accessible data tablesRequired
Tables use <th> header cells.
100%
Implemented
Touch target sizeRequired
Touch-target sizing needs rendering measurement.
—
Needs review
Hidden until foundRecommended
Not used — only relevant for collapsible/accordion content.
—
Needs review
Native interactive elementsRecommended
Could not confirm use of native interactive elements.
—
Needs review
CSS state and relational selectorsRecommended
CSS selector strategy needs source review.
—
Needs review

HTTPS and TLSRequired
Page is served over HTTPS.
100%
Implemented
HSTS (Strict-Transport-Security)Required
No Strict-Transport-Security header — browsers will not enforce HTTPS.
0%
Not implemented
Content Security Policy (CSP)Recommended
No CSP header — the page has no defence-in-depth against injected scripts.
0%
Not implemented
/.well-known/security.txtRecommended
No /.well-known/security.txt — researchers have no disclosure contact.
0%
Not implemented
X-Content-Type-Options: nosniffRequired
No X-Content-Type-Options: nosniff — browsers may MIME-sniff responses.
0%
Not implemented
Clickjacking protectionRequired
No frame-ancestors or X-Frame-Options — the page can be framed for clickjacking.
0%
Not implemented
Referrer-PolicyRecommended
No Referrer-Policy — full URLs may leak to third parties.
0%
Not implemented
Permissions-PolicyRecommended
No Permissions-Policy — powerful browser features are not locked down.
0%
Not implemented
Subresource Integrity (SRI)Recommended
0/1 cross-origin scripts use SRI — add integrity hashes to the rest.
1%
Partial
Cookie attributes — Secure, HttpOnly, SameSiteRequired
No cookies set on the document response.
100%
Implemented
DNS CAA recordsRecommended
CAA records are not collected by the scanner — check your DNS provider.
—
Needs review
DNSSECOptional
DNSSEC status is not collected by the scanner.
—
Needs review

Well-known URIsRecommended
No /.well-known/ resources found.
0%
Not implemented
/.well-known/change-passwordOptional
No change-password redirect — recommended if the site has accounts.
—
Needs review
/.well-known/openid-configurationOptional
Not present — only relevant for OIDC identity providers.
—
Needs review
/.well-known/api-catalogRecommended
Not present — recommended if the site exposes public APIs.
—
Needs review
/.well-known/webfingerOptional
Not present — only relevant for federated identity.
—
Needs review
/.well-known/apple-app-site-associationOptional
Not present — only needed for iOS Universal Links.
—
Needs review
/.well-known/assetlinks.jsonOptional
Not present — only needed for Android App Links.
—
Needs review
/.well-known/nodeinfoOptional
Not present — only relevant for Fediverse servers.
—
Needs review
/.well-known/traffic-adviceOptional
Not present — optional prefetch-proxy control file.
—
Needs review

Agent readinessRecommended
No agent-readiness signals (no llms.txt, no structured data).
0%
Not implemented
/llms.txtRecommended
No /llms.txt — agents have no curated map of your key content.
0%
Not implemented
/llms-full.txtOptional
No /llms-full.txt — optional full-content variant.
—
Needs review
Per-page Markdown source endpointsRecommended
No Markdown source endpoint detected — recommended for content/doc sites.
—
Needs review
robots.txt for AI crawlersRecommended
robots.txt has no explicit AI-crawler rules — state your stance on GPTBot/ClaudeBot/etc.
0%
Not implemented
Content Signals in robots.txtOptional
No Content-Signal directives — optional usage-preference signalling.
—
Needs review
Web Bot Auth — verifiable bot identityOptional
Web Bot Auth support cannot be detected from a scan.
—
Needs review
Stable URLsRequired
URL has no obvious session/volatile parameters.
100%
Implemented
Structured data for agentsRecommended
No structured data — agents must scrape prose instead of reading typed facts.
0%
Not implemented
Machine-readable formatsRecommended
No machine-readable alternates detected — recommended for listings/data pages.
—
Needs review
HTTP Link headers for discoveryRecommended
HTTP Link header present for discovery.
100%
Implemented
MCP and tool discoveryOptional
No MCP/tool discovery endpoint — optional.
—
Needs review
A2A agent cardsOptional
No A2A agent card — optional.
—
Needs review
Agent Skills discoveryRecommended
Agent Skills discovery cannot be detected automatically.
—
Needs review
DNS for AI Discovery (DNS-AID)Optional
DNS-AID records are not collected by the scanner.
—
Needs review
NLWeb — conversational interface discoveryOptional
NLWeb support cannot be detected automatically.
—
Needs review
WebMCP — browser-native tools for agentsOptional
WebMCP support cannot be detected automatically.
—
Needs review
Schemamap — discoverable JSON-LD endpointsOptional
Schemamap support cannot be detected automatically.
—
Needs review

Core Web Vitals (LCP, INP, CLS)Required
Lab load completed in 401ms (a proxy). Confirm LCP/INP/CLS with field data.
85%
Partial
Image optimisationRequired
No raster images, or none captured.
100%
Implemented
Lazy loading images, iframes, and videoRecommended
Too few images to need lazy-loading.
100%
Implemented
Preload, prefetch, preconnectRecommended
Resource hints (preload/preconnect/…) present.
100%
Implemented
Cache-Control headersRequired
Cache-Control set on the document (private, no-cache, no-store, max-age=0, must-revalidate).
100%
Implemented
No-Vary-Search response headerRecommended
Not set — optional; helps cache/prefetch URLs that differ only by tracking params.
—
Needs review
Compression (gzip, brotli, zstd)Required
Document response is not compressed — enable Brotli or gzip for text.
0%
Not implemented
Web font loadingRecommended
Font-display/font preload optimisation detected.
100%
Implemented
Critical CSS and render-blocking resourcesRecommended
2 render-blocking stylesheet(s) in <head>.
100%
Implemented
Script loading — defer, async, moduleRecommended
5/6 external scripts use defer/async/module — add defer to the rest.
83%
Partial
HTTP/2 and HTTP/3Recommended
Protocol version not captured — verify HTTP/2/3 is enabled at your edge/CDN.
—
Needs review
Speculation RulesRecommended
No Speculation Rules — optionally prerender/prefetch likely next pages.
—
Needs review
Resource hints overviewRecommended
Resource hints are in use.
100%
Implemented
View TransitionsRecommended
No View Transitions detected — optional polish for navigations.
—
Needs review
Back/forward cache (BFCache)Recommended
BFCache eligibility needs runtime testing.
—
Needs review
Visibility-aware renderingRecommended
No content-visibility detected — optional offscreen-render optimisation.
—
Needs review
CSS containmentOptional
No CSS containment detected — optional.
—
Needs review
Scroll-driven animationsOptional
Not detected — optional.
—
Needs review
Scrollbar gutterRecommended
No scrollbar-gutter — optional; prevents layout shift when scrollbars toggle.
—
Needs review

Privacy policyRequired
No privacy policy link found — link one from every page (usually the footer).
0%
Not implemented
Cookie consentRequired
No consent manager detected (and no document cookies) — required if you set non-essential cookies.
—
Needs review
Global Privacy Control (GPC)Recommended
GPC handling is server-side and cannot be confirmed from a scan.
—
Needs review
Third-party scripts and privacyRecommended
1 third-party script origin(s) — audit each for data collection.
70%
Partial
Privacy-respecting analyticsRecommended
No analytics detected, or an unrecognised provider.
—
Needs review
Data minimisationRecommended
Data-minimisation practices need a manual review of forms and backend.
—
Needs review

Custom error pages (404, 500)Required
Missing pages return 404 with a substantial (likely custom) error page.
100%
Implemented
Maintenance pages and 503Recommended
Maintenance behaviour can only be observed during downtime.
—
Needs review
Offline support and service workersOptional
No service worker detected — optional offline/PWA support.
—
Needs review
Web app manifestRecommended
No <link rel="manifest"> — add a web app manifest for installability.
0%
Not implemented
Monitoring and uptimeRecommended
Monitoring is operational and cannot be detected from the page.
—
Needs review

Deterministic audit against the website specification checklist. “Needs review” items can't be confirmed from a headless scan and are excluded from the score.

DNS & Infrastructure

DNSFluxwall

EmailWorkflowEmail

HostingHetzner

IP Addresses

65.109.31.16

Hetzner Online GmbH

🇫🇮Helsinki, Finland

Nameservers

ns1.fluxwall.eu

ns2.fluxwall.eu

Mail Servers (MX)

10mail.workflowemail.com

AI Analysis Notes

·SPF uses workflowemail.com include (_spf.workflowemail.com), consistent with the MX record
·MX points to mail.workflowemail.com (WorkflowEmail email service)
·Single A record hosted at Hetzner Online GmbH (AS24940), Finland
·No DMARC record found; SPF softfail policy (~all)
·No secondary MX record, single mail server

Email & Deliverability

Email health score

WorkflowEmail

saaspilot.app receives mail via WorkflowEmail and has SPF plus DMARC in place, but all three authentication layers are only at the baseline: DMARC is p=none (monitor-only), SPF ends in ~all, and no DKIM key is published, leaving the domain spoofable and hurting deliverability to Gmail/Yahoo. The remaining gaps are hardening items (MTA-STS, TLS-RPT).

Mail configuration

Mail servers (MX)mail.workflowemail.com
1 MX record — the domain can receive mail.
SPFv=spf1 a:mail.workflowemail.com include:_spf.workflowemail.com ~all
SPF present but uses a soft fail (~all) — consider tightening to -all once you confirm all senders.
DMARC policyv=DMARC1; p=none; rua=mailto:dmarc@saaspilot.app
DMARC policy is p=none — monitoring only, it does not block spoofed mail. Move to quarantine/reject.
DKIM
No DKIM key found on common selectors. DKIM may use a custom selector, or it may not be set up.
MTA-STS
No MTA-STS policy — optional, but it enforces encryption for mail delivery.
SMTP server220 256ed653854b ESMTP
Primary mail server responded.

Recommended improvements

Publish a DKIM key (or confirm WorkflowEmail signing)Very High
No DKIM selector was found, so signed mail likely fails DKIM verification; since 2024 Gmail/Yahoo require DKIM (or SPF-only fallback is heavily down-ranked) for bulk senders.
→ Enable DKIM signing in WorkflowEmail and publish the returned public key as <selector>._domainkey.saaspilot.app TXT v=DKIM1; k=rsa; p=<key>.
90%
impact
Enforce DMARC with p=rejectHigh
p=none only collects reports and explicitly tells receivers to keep delivering unauthenticated mail, so spoofed saaspilot.app mail still lands in inboxes.
→ After confirming DKIM/SPF alignment over a couple of weeks, step the policy to p=quarantine and then to p=reject, e.g. v=DMARC1; p=reject; rua=mailto:dmarc@saaspilot.app; ruf=mailto:dmarc@saaspilot.app; adkim=s; aspf=s.
85%
impact
Tighten SPF to -allHigh
The ~all soft fail tells receivers to accept the mail even if SPF fails, leaving a spoofing vector that also weakens DMARC alignment enforcement.
→ Once all legitimate senders are confirmed, change the record to v=spf1 a:mail.workflowemail.com include:_spf.workflowemail.com -all.
60%
impact
Add an MTA-STS policyLow
No MTA-STS policy exists, so supporting providers can fall back to plaintext SMTP during inbound delivery; a policy forces TLS.
→ Publish TXT _mta-sts.saaspilot.app "v=STSv1; id=<date>; mx: mail.workflowemail.com" and serve v=STSv1 policy JSON at https://mta-sts.saaspilot.app/.well-known/mta-sts.txt.
30%
impact
Publish a TLS-RPT recordLow
Without TLS-RPT you get no visibility into STARTTLS/MTA-STS failures at receiving servers, so enforcement gaps go unnoticed.
→ Add TXT _smtp._tls.saaspilot.app "v=TLSRPTv1; rua=mailto:dmarc@saaspilot.app" to receive TLS failure reports.
20%
impact

Auto-rated from DNS & SMTP records · improvements suggested by AI

Loaded Resources (21 requests · sorted by load time)

Resource	Size	Time	Status
Ssaaspilot.app/_next/static/chunks/app/global-error-e768571ab5467196.js	10.4KB	182ms	200
Ssaaspilot.app/_next/static/chunks/app/not-found-bf350f05be4fefcc.js	9.6KB	154ms	200
Ssaaspilot.app/_next/static/chunks/2619-04bc32f026a0d946.js	8.4KB	148ms	200
Ssaaspilot.app/_next/static/chunks/app/page-6f2a87b0f879582f.js	7.8KB	145ms	200
Ssaaspilot.app/_next/static/chunks/306-b07a8a04ef03ebb2.js	34.5KB	142ms	200
Ssaaspilot.app/_next/static/chunks/app/layout-75145a681bdf8796.js	17.9KB	142ms	200
Ssaaspilot.app/_next/static/chunks/8720-c9ee040177c11cae.js	33.2KB	138ms	200
Ssaaspilot.app/_next/static/chunks/4909-5833c0da806d22ce.js	19.7KB	130ms	200
Ssaaspilot.app/_next/static/css/4e6324d35ca12018.css	79.4KB	111ms	200
Ssaaspilot.app/_next/static/css/a6fc798b75e96a95.css	2.0KB	103ms	200
Ssaaspilot.app/_next/static/chunks/4bd1b696-100b9d70ed4e49c1.js	169.0KB	88ms	200
Ssaaspilot.app/_next/static/chunks/1255-623a1bc706ecd6cc.js	170.1KB	88ms	200
Ssaaspilot.app/_next/static/chunks/main-app-234525b5e3ddebfb.js	525B	88ms	200
Ssaaspilot.app/_next/static/chunks/webpack-dac35c858906ab6b.js	3.5KB	74ms	200
Ssitebeacon.eu/a.js	—	74ms	200
Ssaaspilot.app/_next/static/media/e4af272ccee01ff0-s.p.woff2	47.3KB	73ms	200
Ssitebeacon.eu/api/event	—	52ms	202
Ssaaspilot.app/api/analytics/track	16B	51ms	200
Ssaaspilot.app/signup?_rsc=1p-R_iEY6bj0jY31	132B	29ms	200
Ssaaspilot.app/login?_rsc=1p-R_iEY6bj0jY31	130B	28ms	200
Ssaaspilot.app/api/auth/session	2B	22ms	200

Scan History (1 scans)

Page load time

401ms

TTFB

126ms

Date	TTFB	DOM	Load	Requests	Size	Errors	Scripts
Oct 6, 04:59 PM UTC	126ms	401ms	401ms	21	614KB	0	18AI

Embed a badge

Pick what to show — your detected tech stack, the social-trend valuation, or both.

Badge style

Brand · detected technologies.

Preview

HTML embed

<a href="https://madewith.tech/s/saaspilot.app"><img src="https://madewith.tech/s/saaspilot.app/badge.svg" alt="saaspilot.app on MadeWithTech" /></a>

Markdown

[![saaspilot.app on MadeWithTech](https://madewith.tech/s/saaspilot.app/badge.svg)](https://madewith.tech/s/saaspilot.app)

Share link

https://madewith.tech/s/saaspilot.app