CRCrawlRanker
Back
Scan complete

espboards.dev

1 page · 0.1s · 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 shows strong signals of human authorship despite some marketing language. Blog post titles and summaries reference specific hardware (Elecrow CrowPanel, Guan Sen controller, CYD variants), real technical details (GPIO maps, LibreTiny quirks, LVGL widgets), real dates, and hand-curated product reviews with concrete specs. All 12 images have alt text and no AI-generation indicators. The navigation and section structure are functional but not templated in the AI-builder sense (no rigid icon grids, no "leverage" language, no hollow feature lists). Marketing copy is present but anchored to real offerings.

65/100Caution
AI Governance· legal

1 governance risk detected

1 critical
What we scanned
Page title
ESPBoards – The Hub for ESP32 Boards, Troubleshooting, Tools & Tutorials
Meta description
Welcome to the ESPBoards! Your one-stop destination for ESP32 boards, sensors, troubleshooting, expert guides, and essential tools.
Final URL
https://www.espboards.dev/(after redirect from https://espboards.dev/)
Canonical URL
—
Robots directive
Not set — search engines default to index, follow
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
e
espboards.devwww.espboards.dev

ESPBoards – The Hub for ESP32 Boards, Troubleshooting, Tool…

Welcome to the ESPBoards! Your one-stop destination for ESP32 boards, sensors, troubleshooting, expert guides, and essential tools.

  • Title · 72 characters — long titles get cut around 60
  • Description · 131 characters
Fine-tune this snippet in the SERP simulator
Shared link card
espboards.dev

ESPBoards – The Hub for ESP32 Boards, Troubleshooting, Tools & Tutorials

Welcome to the ESPBoards! Your one-stop destination for ESP32 boards, sensors, troubleshooting, expert guides, and essential tools.

  • Open Graph image present
AI Governancelegal · 29%
65/100
Caution1 risk detected
criticalSite classified as legal content

AI-generated legal content may signal unauthorised practice of law

Content that appears to give legal advice — even general guidance — when generated by AI and not reviewed by a licensed attorney can violate unauthorised practice of law (UPL) statutes in most jurisdictions. Penalties range from civil injunctions to criminal charges.

Unauthorised Practice of Law statutes (jurisdiction-specific)ABA Model Rules of Professional Conduct
Official guidanceABA — Unauthorised Practice of LawABA — AI and Lawyer Competence (Formal Opinion 512)
Fix
Legal disclaimer template
## Legal Disclaimer

The information provided on this website is for general informational purposes
only and does not constitute legal advice. Reading this content does not create
an attorney-client relationship.

Laws vary by jurisdiction and change frequently. You should not act or refrain
from acting on the basis of any content on this site without seeking independent
legal advice from a licensed attorney in your jurisdiction.

> Some content on this site is created or assisted by AI and reviewed by legal
> professionals. However, AI-generated content may contain errors. Do not rely
> on it for specific legal decisions.

_Disclaimer last reviewed: [DATE]_
Legal disclaimer footer (HTML)Pro
Available on the Pro plan.See pricing →
Top findings
  • Worth notingContent

    Marketing-speak phrases soften otherwise technical tone, but are not pervasive.

    Evidence
    • “Your one-stop destination for ESP32 boards, sensors, troubleshooting, expert guides, and essential tools”body
    • “Everything you need for your ESP32 journey”body
    Try this

    Replace generic 'destination' and 'journey' phrases with concrete benefit statements: 'Find ESP32 board specs, sensor pinouts, and troubleshooting workflows' reads more authentic to your technical audience.

  • Clear signalTone

    Inconsistent voice between hero section and blog summaries suggests multiple authors or editorial drift.

    Evidence
    • “Your one-stop destination for ESP32 boards, sensors, troubleshooting, expert guides, and essential tools”body
    • “How I reflashed the Guan Sen 2-pump WiFi irrigation kit (Tuya CB3S / BK7231N) with ESPHome via LibreTiny - including the GPIO map, the LibreTiny interrupt quirk, and an auto-off safety timer that actu”body
    Try this

    Harmonize the hero section and blog teasers: adopt the second-person case-study voice (How to, hands-on) across navigation copy to match your strongest section.

What's working

Signals of human authorship the page is doing well.

  • Content

    Blog post titles and summaries reference specific hardware, real dates, and technical details (GPIO maps, LibreTiny quirks, ILI9341 panel specs) that only come from hands-on experience.

  • Imagery

    All 12 images carry alt text and no stock-photo or AI-generation markers; contextual product screenshots and diagrams suggest custom assembly rather than bulk licensing.

SEO auditGood
86/100
AI breakdown by category
  • Content35

    Mix of marketing-speak ("expert guides", "step-by-step") and concrete specifics (Elecrow ESP32 Miner, LibreTiny, GPIO maps, real dates)

  • Structure25

    Regular sectioning (Featured → Resources grid → Blog posts) but no rigid template; custom navigation, real product links, and irregular heading depths suggest hand-built site

  • Imagery22

    12 images all with alt text present; no visible stock-photo grid or AI-generated image paths; product screenshots and diagrams appear contextual and custom

  • Tone45

    Shifts between friendly marketing tone in hero ("Your one-stop destination") and technical detail in blog summaries (GPIO map, LibreTiny interrupt quirk), suggesting multiple human voices

By the numbers
  • Words676
  • Images12
  • Alt coverage100%
  • Internal links66
  • External links12
  • Schema blocks0
  • HTML size82 KB
  • Text-to-HTML6%
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 / sentence17.6
Rhythm variation85%
Vocabulary diversity60%
Sentences analysed17

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 phrases1.5 per 1,000 words · Low density

Common AI writing tells we counted in the body text. A few hits is normal. A dense cluster is the signal.

Show counted phrases1 match across 1 phrase
  • “comprehensive”×1
SEO audit detail
  • Meta tags
    Missing canonical
    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, 14 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
    0.1s · 82 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/5 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
    All have alt
    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. H1ESPBoards – The Hub for ESP32 Boards, Troubleshooting, Tools & Tutorials
  2. H2ESPBoards Learn
  3. H2Explore Our Resources
  4. H2Get Started
  5. H2Blog
  6. H2Boards
  7. H2Sensors
  8. H2Troubleshooting
  9. H2Tools
  10. H2Latest Blog Posts
  11. H2Why Choose ESP32?
  12. H2Subscribe to the ESPBoards Newsletter
  13. H2Resources
  14. H2Company
  15. H2Legal
  16. H3Elecrow ESP32 Miner Review - A CYD with USB-C and a Case
  17. H3Reflashing the Guan Sen WiFi Irrigation Controller with ESPHome
  18. H3Elecrow CrowPanel E-Paper with ESPHome & LVGL (4.2" and 5.79")
  19. H3How to Use a Multimeter - A Practical Guide for ESP32 & Electronics Makers
  20. H3Types of Multimeters - Which One Do You Actually Need?
  21. H3CrowPanel 2.1" ESP32 Rotary Display Review – The Smart Home Knob I Actually Enjoy Using
  22. H3High Performance
  23. H3Versatile Connectivity
  24. H3Vibrant Community
  25. H3Endless Possibilities
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.

Scan another site

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