Back
Scan complete

verifyy.wispbyte.app

1 page · 1.0s · Scanned just now

0/ 100
AI automation score

Mostly human-written

72% confidence

How to read this score
0–35 · Mostly human35–65 · Mixed signals65–100 · Mostly AI

The score is a fingerprint of automation, not a quality judgment. A high score means the page reads as machine-generated. It doesn't mean the page is bad.

What we saw

The page is a functional Discord verification portal with live stats, real UTC timestamps, named contacts ("Wookiee"), and concise imperative copy — none of which resemble LLM output. The 3-step numbered list is the only mild AI-adjacent structural signal, but it's a natural fit for an onboarding flow, not a template artifact. The short word count limits signal depth, but what's there points clearly toward human-authored utility content.

This page opts out of search results

Its robots meta tag includes noindex, which tells Google and every other search engine to leave the page out of results entirely. Nothing else in this report affects ranking until that changes — intentional for private pages, fatal for public ones.

It also sets nofollow, so crawlers ignore every link on the page as well.

Found: noindex,nofollow,noarchive,nosnippet,noimageindex

65/100Caution
AI Governance· financial

1 governance risk detected

1 critical
What we scanned
Page title
AltSieve
Meta description
Canonical URL
Robots directive
noindex,nofollow,noarchive,nosnippet,noimageindex
Language
en
Search & social preview

How the page presents itself in a Google result and as a shared link, rebuilt from the tags we crawled.

Google result
v
verifyy.wispbyte.appverifyy.wispbyte.app

AltSieve

  • Title · 8 characters
  • No meta description — Google will pull an arbitrary snippet instead
Fine-tune this snippet in the SERP simulator
Shared link card
verifyy.wispbyte.app

AltSieve

  • No og:image — shared links render as bare text with no picture
  • No Open Graph title — the share card falls back to the page title
AI Governancefinancial · 6%
65/100
Caution1 risk detected
criticalSite classified as financial content

AI-generated financial content may constitute unlicensed investment advice

Content that discusses investment strategies, specific securities, or financial products and is generated by AI without licensed advisor review can violate SEC and FINRA rules on investment advice. The FTC also scrutinises AI-generated financial claims for deceptive practices.

SEC Rule 206(4)-7FINRA Rule 2010FTC Act §5
Fix
Financial disclaimer template
## Financial Disclaimer

The content on this website is provided for informational and educational
purposes only and does not constitute investment advice, financial advice,
trading advice, or any other type of professional advice.

Nothing on this site should be construed as a recommendation to buy, sell, or
hold any security or financial instrument. Past performance is not indicative
of future results.

> Some content on this site is created or assisted by AI. AI-generated
> financial content may contain errors or outdated information. Always
> consult a licensed financial advisor before making investment decisions.

_Disclaimer last reviewed: [DATE]_
Financial disclaimer component (HTML)Pro
Available on the Pro plan.See pricing →
Top findings
  • Clear signalStructure

    Numbered 3-step 'How it works' section follows a common template pattern

    Evidence
    • Press Verify in DiscordH3
    • Open the official pageH3
    • Receive the roleH3
    Try this

    Rewrite at least one step as a full descriptive sentence rather than a heading-only label to differentiate from boilerplate onboarding templates.

  • Worth notingContent

    Word count of ~300 is too thin to provide strong authorship signal either way

    Evidence
    • The page runs a short browser and network check. It does not ask for account credentials.body
    Try this

    Add a short paragraph explaining what the browser/network check actually inspects, which would add specificity and reduce ambiguity.

What's working

Signals of human authorship the page is doing well.

  • Content

    Real live stats with specific UTC timestamps and a named contact ('ping Wookiee') anchor the page in genuine operational context.

  • Tone

    Terse, security-focused imperative voice ('You never need to enter your Discord password') reads as a real operator warning, not marketing copy.

SEO auditGood
79/100
AI breakdown by category
  • Content20

    Short, functional prose with specific real-world details (timestamps, counts, named user "Wookiee") and no LLM filler phrasing

  • Structure30

    Numbered 3-step "how it works" block is a mild template pattern, but overall layout is minimal and utility-focused, not AI-builder boilerplate

  • Imagery10

    Zero images present on the page — no stock photos, no AI-generated imagery, nothing to flag

  • Tone15

    Terse, imperative security-utility voice with named individual ("ping Wookiee") and direct second-person warnings — distinctly non-AI register

By the numbers
  • Words300
  • Images0
  • Alt coverage100%
  • Internal links4
  • External links0
  • Schema blocks0
  • HTML size14 KB
  • Text-to-HTML13%
Sentence rhythmVaried — reads human

Each bar is one sentence of the page, in reading order — taller means longer. Human prose tends to look jagged, mixing short punches with long explanations. Machine drafts tend to flatten into even bars.

Avg words / sentence13.0
Rhythm variation76%
Vocabulary diversity58%
Sentences analysed23

Computed from the body text we crawled, split on punctuation and filtered to prose-length sentences. Rhythm is a heuristic, not a verdict — some human writers are metronomically even, and a good editor smooths a machine draft.

LLM-marker phrases

No common LLM-marker phrases found — none of the stock AI vocabulary we scan for appears in the body text even once.

SEO audit detail
  • Meta tags
    Missing 2 tags
    Why this matters

    Why it matters. Title and description are the two strings Google shows in search results. They decide whether anyone clicks. A canonical tag tells Google which URL is the source of truth when the same content lives at multiple paths.

    Passing looks like. A non-empty title under 60 characters, a meta description under 160, and a self-referencing canonical link.

    Fix. Add the missing tags inside the page head. Treat the title as a headline you'd want to read in a SERP, not a brand slogan.

  • Heading structure
    1 H1, 5 H2
    Why this matters

    Why it matters. Headings are how crawlers and assistive tech understand a page's outline. One H1 names the page. H2s break it into sections. Skipped levels and missing H1s confuse both.

    Passing looks like. Exactly one H1, at least one H2, and no skipped levels (no H1 to H3 jumps).

    Fix. Replace the missing or duplicate H1 with a single, descriptive heading. Promote section titles to H2. Demote sub-points to H3.

  • Mobile readiness
    Responsive
    Why this matters

    Why it matters. Google indexes mobile-first. A page without a responsive viewport renders zoomed-out on phones, fails Core Web Vitals on touch, and loses its mobile ranking.

    Passing looks like. A meta viewport tag with width=device-width and a layout that reflows under 600px.

    Fix. Add a viewport meta tag set to width=device-width and initial-scale=1, then audit your largest blocks at mobile widths.

  • Page speed signals
    1.0s · 14 KB
    Why this matters

    Why it matters. Page weight and response time directly feed Core Web Vitals. Slow LCP and oversized HTML hurt rankings more than people expect.

    Passing looks like. First-byte under 1.5s, HTML payload under 500 KB, fewer than 30 images on the initial render.

    Fix. Trim render-blocking scripts, defer non-critical CSS, and serve compressed images sized to the viewport. Move heavy components below the fold.

  • Schema markup
    No JSON-LD
    Why this matters

    Why it matters. JSON-LD structured data is how you earn rich results: review stars, FAQ accordions, breadcrumbs, article cards. Skip it and Google has nothing structured to pull from when it builds your SERP card.

    Passing looks like. At least one valid JSON-LD block matching schema.org types relevant to the page (Article, Product, FAQPage, Organization).

    Fix. Add an application/ld+json script block describing the page. Validate with Google's Rich Results Test before deploying.

  • Broken links
    0/1 broken in sample
    Why this matters

    Why it matters. Broken internal links waste crawl budget, degrade UX, and signal to Google that the site isn't well-maintained. They also cap how deep crawlers reach.

    Passing looks like. Every internal link in the sample returns 2xx or 3xx. No dead anchors, no stale paths.

    Fix. Use the link list above to spot the broken paths. Either restore the missing pages or update the links to point at live URLs.

  • Image alt text
    No images
    Why this matters

    Why it matters. Alt text is what screen readers read aloud, and what Google reads instead of pixels. Skip it and you lose on both fronts.

    Passing looks like. Every meaningful image has a descriptive alt attribute. Decorative images can use alt="" to be skipped intentionally.

    Fix. Audit images in /assets and CMS uploads. Write alts that describe what's in the image, not what it links to.

Heading outline

Every H1, H2, and H3 we found on the page, in document order.

Show heading outline
  1. H1Discord server verification
  2. H2Before you verify
  3. H2Current status
  4. H2How it works
  5. H2Recent activity
  6. H2Basic rules
  7. H3Press Verify in Discord
  8. H3Open the official page
  9. H3Receive the role
  10. H3Privacy
  11. H3False positives
  12. H3Link safety
Sampled links

We HEAD-check up to five internal links to spot broken paths quickly.

Show sampled links

Was this report useful?

Share this scan

Every CrawlRanker scan gets a public, shareable URL. Send it to a client, post it in a thread, or benchmark a competitor.

Preview scan. SEO checks are live. AI scoring is in beta.