evmotormagnets.com
1 page · 0.6s · Scanned just now
Mostly human-written
72% confidence
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.
This page is primarily human-authored technical content written for a specialized B2B audience (EV motor sourcing teams). The vocabulary is domain-specific (hotspot uncertainty, demagnetization margin, SH/UH grades, magnetic loading) with no generic LLM markers like "leverage" or "in today's fast-paced world." The structure follows a deliberate buyer-decision workflow (TL;DR → triggers → conditions → case study) rather than boilerplate hero-features-testimonial-CTA. However, the overall page structure does fit an identifiable B2B template, and the imagery signal is unclear from the excerpt, lowering confidence slightly.
No governance risks detected
- Page title
- SH vs UH NdFeB Grades for EV Traction Motors: A B2B Decision Guide | EVMotorMagnets
- Meta description
- How sourcing and engineering teams should evaluate SH versus UH grade choices for EV traction motors under thermal, cost, and lead-time constraints.
- Canonical URL
- https://evmotormagnets.com/blog/sh-vs-uh-magnet-grades-for-traction-motors
- Robots directive
- Not set — search engines default to index, follow
- Language
- en
- Built with
- Next.js
How the page presents itself in a Google result and as a shared link, rebuilt from the tags we crawled.
SH vs UH NdFeB Grades for EV Traction Motors: A B2B Decisio…
How sourcing and engineering teams should evaluate SH versus UH grade choices for EV traction motors under thermal, cost, and lead-time constraints.
- Title · 83 characters — long titles get cut around 60
- Description · 148 characters

SH vs UH NdFeB Grades for EV Traction Motors: A B2B Decision Guide | EVMotorMagnets
How sourcing and engineering teams should evaluate SH versus UH grade choices for EV traction motors under thermal, cost, and lead-time constraints.
- Open Graph image present
- Worth notingStructure
Standard B2B blog template with TL;DR, decision matrix, and case study sections may suggest AI-assisted layout scaffolding
Evidence- “Buyer TL;DR”H2
- “Decision matrix buyers can apply in one meeting”H2
- “Anonymous case: SH baseline with UH fallback avoided launch slip”H2
Try thisVerify this structure reflects human editorial choice for buyer workflow, not an AI page-builder template—the content quality suggests human authorship, so the template choice likely is too.
- Worth notingImagery
100% alt-text compliance on 4 images is atypical for stock-photo sites but not a human signal on its own
Evidence- “Images: 4 (missing alt: 0)”page
Try thisSpot-check the four images for custom content (product photos, custom charts) vs. stock—this will clarify whether imagery is in-house or licensed.
Signals of human authorship the page is doing well.
- Content
Specialized vocabulary (hotspot uncertainty, demagnetization margin, magnetic loading) and decision-trigger language specific to EV motor sourcing—unlikely AI-generated phrasing
- Tone
Professional voice addressing sourcing and engineering teams with concrete workflows (trigger-based decisions, grade lock pre-PO checklist) and no motivational marketing language
- Content25
Technical domain language (hotspot uncertainty, demagnetization margin, magnetic loading) with specific product context; minimal generic LLM phrasing
- Structure35
Logical decision-tree structure with buyer triggers and workflows, but follows recognizable B2B template (TL;DR → decision matrix → case study → download CTA)
- Imagery65
4 images present with 100% alt-text coverage; decision tables and visual maps mentioned but actual visual content not detailed in body excerpt
- Tone22
Distinct professional voice addressing sourcing/engineering teams with domain specificity (thermal confidence, grade lock, SOPTrigger language); no marketing platitudes
- Words1,176
- Images4
- Alt coverage100%
- Internal links28
- External links5
- Schema blocks7
- HTML size132 KB
- Text-to-HTML6%
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.
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.
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
- “robust”×1
- Meta tagsAll presentWhy 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 structure1 H1, 17 H2Why 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 readinessResponsiveWhy 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 signals0.6s · 132 KBWhy 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 markup7 schema blocksWhy 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 links1/5 broken in sampleWhy 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 textAll have altWhy 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.
Every H1, H2, and H3 we found on the page, in document order.
Show heading outline
- H1SH vs UH NdFeB Grades for EV Traction Motors: A B2B Decision Guide
- H2Buyer TL;DR
- H2The real question is not SH or UH
- H2Decision matrix buyers can apply in one meeting
- H2When SH is typically sufficient
- H2When UH deserves serious consideration
- H2Supplier data package to request for SH and UH in parallel
- H2Commercial and execution implications
- H2Typical impact ranges to budget for
- H2Recommended buyer workflow
- H2Pre-PO checklist for grade lock
- H2Anonymous case: SH baseline with UH fallback avoided launch slip
- H2Download grade decision templates (CSV + XLSX)
- H2Decision Tables
- H2Visual Decision Maps
- H2Buyer FAQ
- H2References and Evidence
- H2Need OEM support?
- H3SH vs UH Decision Table
- H3SH-UH Grade Decision Tree
We HEAD-check up to five internal links to spot broken paths quickly.
Show sampled links
- 404 · Brokenhttps://evmotormagnets.com/cdn-cgi/l/email-protection
- 200 · OKhttps://evmotormagnets.com/downloads/sh-uh-grade-decision-matrix-template.xlsx
- 200 · OKhttps://evmotormagnets.com/blog
- 200 · OKhttps://evmotormagnets.com/terms
- 200 · OKhttps://evmotormagnets.com/downloads/sh-uh-grade-decision-matrix-template.csv
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.