CRCrawlRanker
Back
Scan complete

microbldc.com

1 page · 0.4s ·

0/ 100
AI automation score

Mostly AI-generated

60% 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 category copy is repetitive and template-like, with the same two lines repeated for each article and generic framing such as "Instead of generic theory" and "reusable inputs." Counterweights are concrete specifics (named articles, RFQ fields like OD and voltage, a named operating company), and the crawl shows no imagery evidence, so confidence is moderate.

90/100Clean
AI Governance

1 governance risk detected

1 medium
What we scanned
Page title
Product Engineering Insights | Micro BLDC Blog
Meta description
Micro BLDC motor selection, customization strategy, and integration guidance for compact OEM devices and assemblies.
Final URL
https://microbldc.com/en/blog/category/product
Canonical URL
https://microbldc.com/en/blog/category/product
Robots directive
Not set — search engines default to index, follow
Language
en
Built with
Next.js
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
m
microbldc.commicrobldc.com/en/blog/category/product

Product Engineering Insights | Micro BLDC Blog

Micro BLDC motor selection, customization strategy, and integration guidance for compact OEM devices and assemblies.

  • Title · 46 characters
  • Description · 116 characters
Fine-tune this snippet in the SERP simulator
Shared link card
microbldc.com

Product Engineering Insights | Micro BLDC Blog

Micro BLDC motor selection, customization strategy, and integration guidance for compact OEM devices and assemblies.

  • Open Graph image present
AI Governance
90/100
Clean1 risk detected
mediumAI score ≥ 60 and no disclosure statement detected on page

No AI content disclosure detected

EU AI Act Article 50 requires that AI-generated content presented to EU audiences be labelled as such. The FTC has also signalled enforcement interest in undisclosed AI-generated content. A simple site-wide disclosure policy covers both.

EU AI Act Article 50FTC Act §5
Official guidanceEU AI Act — Article 50 (Transparency for general public)FTC — Using AI: What Businesses Need to Know
Fix
AI content disclosure policy template
## AI Content Policy

Some content on this website is created or assisted by artificial intelligence
(AI) tools. We are transparent about our use of AI and committed to accuracy.

**What we use AI for:** [content drafting / image generation / data summaries]
**Human review:** All AI-generated content is reviewed before publication
**Accuracy:** We verify factual claims, but AI-generated content may contain errors

This disclosure is consistent with EU AI Act Article 50 obligations.

Questions? Contact us at [email].

_Policy version: 1.0 — [DATE]_
Site-wide AI disclosure banner (HTML)
<!-- Place in your site header or footer -->
<div
  class="ai-disclosure-notice"
  role="note"
  aria-label="AI content notice"
>
  Some content on this site is AI-assisted.
  <a href="/ai-policy">Our AI policy</a>
</div>
Top findings
  • Clear signalContent

    Reading-pack rows reuse identical copy in the Primary Use and Next Step columns across all three articles

    Evidence
    • “Buyer-side decision and supplier communication alignment.”×3body
    • “Convert checklist items into your RFQ or sample plan.”×3body
    Try this

    Write distinct primary-use and next-step lines for each article that name its specific decision or checklist.

  • Clear signalContent

    Category intro leans on generic framing rather than specific examples

    Evidence
    • “Instead of generic theory, these posts focus on what buyers can send, measure, and approve in supplier communication.”body
    • “In practical sourcing programs, this category is most useful when its article checklists are copied into internal review templates”body
    Try this

    Replace abstract benefit statements with one concrete example of a real RFQ or sample review drawn from your own projects.

  • Worth notingStructure

    Duplicated 'Product Engineering' headings and a long tagline H2 suggest templated section scaffolding

    Evidence
    • “Sourcing checklists, sizing methods, and OEM execution guides for micro BLDC motor projects.”H2
    Try this

    Give the category heading a distinct label and keep the H2 short so the header hierarchy reads as hand-edited.

What's working

Signals of human authorship the page is doing well.

  • Content

    Concrete RFQ guidance naming motor type, OD, voltage, speed, load and quantity gives real technical specificity.

SEO auditExcellent
93/100
AI breakdown by category
  • Content62

    Identical 'Buyer-side decision' and 'Convert checklist items' lines repeated across rows; 'reusable inputs' and 'Instead of generic theory' phrasing

  • Structure70

    Listing page with templated three-row reading-pack table; duplicated H2 'Product Engineering' and tagline-style H2 suggest CMS/template output

  • Imagery35

    Thin signal: nine images, all with alt text, no filenames or stock-treatment evidence visible in crawl

  • Tone60

    Uniform procurement-guide register with no author voice; concrete company and phone details partly offset it

By the numbers
  • Words484
  • Images9
  • Alt coverage100%
  • Internal links46
  • External links2
  • Schema blocks1
  • HTML size143 KB
  • Text-to-HTML3%
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
    All present
    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
    0.4s · 143 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
    1 schema blocks
    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
    1/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. H1Micro BLDC Engineering Blog
  2. H2Sourcing checklists, sizing methods, and OEM execution guides for micro BLDC motor projects.
  3. H2All
  4. H2Product Engineering
  5. H2Product Engineering
  6. H2Recommended Reading Pack
  7. H3Micro BLDC Motor Sizing Guide for Compact Robotics
  8. H3Coreless Brushless vs Traditional BLDC Motors: An Engineering Comparison
  9. H3How to Select a Micro BLDC Motor for Medical Devices: An Engineering Deep Dive
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.