Back
Scan complete

lowbacklashgearbox.com

1 page · 0.6s · Scanned just now

0/ 100
AI automation score

Mixed signals

62% 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

This page signals mixed authorship: the tool interface and decision-tree structure are likely AI-assisted or templated (repeating input labels, structured data callouts), but the technical content—ratio bands, efficiency tradeoff tables, supplier references (APEX, Neugart, Harmonic)—appears domain-researched. The prose avoids heavy LLM markers ("leverage," "seamlessly") but also lacks distinctive human voice; it reads like engineering documentation written for clarity over personality. The page is substantial (3620 words) and in-domain, reducing ambiguity, but the signal split between bespoke engineering logic and generic UX copy keeps confidence moderate.

70/100Managed
AI Governance· news

2 governance risks detected

1 high1 medium
What we scanned
Page title
100:1 Gear Reducer Servo Motor Guide | LowBacklashGearbox
Meta description
Run a 100:1 gear reducer servo motor fit checker to validate ratio/inertia limits, compare topology tradeoffs, and launch an RFQ with next engineering steps.
Canonical URL
https://lowbacklashgearbox.com/learn/100-1-gear-reducer-servo-motor
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
l
lowbacklashgearbox.comlowbacklashgearbox.com/learn/100-1-gear-reducer-servo-motor

100:1 Gear Reducer Servo Motor Guide | LowBacklashGearbox

Run a 100:1 gear reducer servo motor fit checker to validate ratio/inertia limits, compare topology tradeoffs, and launch an RFQ with next engineering ste…

  • Title · 57 characters
  • Description · 157 characters — long descriptions get cut around 155
Fine-tune this snippet in the SERP simulator
Shared link card
lowbacklashgearbox.com

100:1 Gear Reducer Servo Motor Guide | LowBacklashGearbox

Run a 100:1 gear reducer servo motor fit checker to validate ratio/inertia limits, compare topology tradeoffs, and launch an RFQ with next engineering steps.

  • Open Graph image present
AI Governancenews · 29%
70/100
Managed2 risks detected
highNews/editorial site with AI score ≥ 40

AI-generated news content creates defamation and accuracy risk

AI models can hallucinate facts, fabricate quotes, and misattribute statements. Publishing AI-generated news content without rigorous editorial review creates liability for defamation, false light, and — in regulated markets — press standards violations.

Common law defamationIPSO Editors' CodeIMPRESS Standards Code
Fix
Editorial AI review checklist
## AI Content Editorial Checklist

Before publishing any AI-assisted article, verify:

- [ ] All named individuals and their attributed statements are verified
- [ ] All statistics and figures are sourced and linked
- [ ] No AI-generated quotes are presented as real without verification
- [ ] Legal/defamation review completed for claims about living persons
- [ ] Byline reflects the actual authorship (AI-assisted vs AI-generated)
- [ ] Publication date and version history recorded

**Disclosure line to add to AI-generated articles:**

> _This article was written with the assistance of AI tools and reviewed
> by [editor name] on [date]. Factual claims have been independently
> verified where possible._
Pro1 more risk hidden

Unlock the full breakdown

Pro shows each risk’s plain-English explanation, regulatory framework, official guidance links, and copy-paste fix snippets — plus the AI-generated governance document for your site.

1 medium
See Pro pricing
Top findings
  • Clear signalStructure

    Repeating input-field structure suggests template or form builder; not clearly AI-generated, but lacks bespoke custom markup

    Evidence
    • Motor continuous torque (Nm) Motor rated speed (rpm) Target ratio (40 to 220) Peak factor Backlash target (arcmin)body
    • Balanced Conservativebody
    • Uniform Moderate High shockbody
    Try this

    If the form inputs are generated from a schema or page-builder template, add custom prose or visual hierarchy to break the pattern and establish authorial ownership of the decision logic.

  • Worth notingContent

    Generic instructional framing ('Run the tool first', 'use the report layers') mixed with specific supplier data references

    Evidence
    • Run the tool first for an immediate 100:1 fit signal, then use the report layers to validate evidencebody
    • APEX PGII public data splits 2-stage ratios at 12-100 and 3-stage ratios at 120-1000body
    • Neugart PSFN and Harmonic CSF-GH public pages show materially different backlash/repeatability classesbody
    Try this

    Cite the specific APEX and Harmonic documents by URL or publication date to anchor credibility and differentiate this guide from generic reduction-ratio content.

What's working

Signals of human authorship the page is doing well.

  • Content

    Named supplier comparisons (APEX PGII, Neugart PSFN, Harmonic CSF-GH) and specific numerical boundaries (12-100, 120-1000, >=94%, >=91%) ground the advice in real engineering data, not generic principles

SEO auditExcellent
100/100
AI breakdown by category
  • Content68

    Mix of technical jargon ("reflected inertia," "backlash class") with some generic SaaS phrasing ("Run the tool first," "understand boundaries")

  • Structure58

    Non-standard layout mixing tool UI, decision report, and engineering documentation—not a typical template, but heavy use of repeating label+explanation pairs

  • Imagery75

    Only 2 images present; both have alt text; no visible stock-photo grid or AI-generated hallmarks, but minimal visual content overall

  • Tone65

    Shifts between technical documentation (stage maps, inertia math) and conversational tool instruction ("Run the checker to get..."); no consistent authorial voice

By the numbers
  • Words3,620
  • Images2
  • Alt coverage100%
  • Internal links48
  • External links20
  • Schema blocks7
  • HTML size271 KB
  • Text-to-HTML8%
LLM-marker phrases0.3 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
  • robust×1
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, 21 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.6s · 271 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
    7 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
    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. H1100:1 Gear Reducer Servo Motor Fit Checker + Decision Report
  2. H2100:1 Servo Gear Reducer Quick Fit Checker
  3. H2100:1 ratio band
  4. H2Stage map
  5. H2Inertia reflection
  6. H2Efficiency tradeoff
  7. H2Backlash classes
  8. H2Key Numbers and Decision Meaning
  9. H2Stage1b Evidence Gap Audit
  10. H2Stage1b Research Delta (2026-05-11)
  11. H2Concept Boundaries and Applicability Conditions
  12. H2Use / Not-Use Boundary Matrix
  13. H2Method Flow
  14. H2100:1 Boundary Logic
  15. H2Mid-Flow Handoff for Engineering Review
  16. H2Alternative Topology Comparison
  17. H2Risk and Mitigation Matrix
  18. H2Public Evidence Gaps and Minimum Executable Path
  19. H2Scenario Demonstrations
  20. H2FAQ by Decision Intent
  21. H2Evidence and Source Notes
  22. H2Next-Step Navigation
  23. H3100:1 is usually a stage-boundary decision, not a single-number purchase
  24. H3Precision expectations can force topology changes before torque becomes the bottleneck
  25. H3Inertia reflection improves rapidly at 100:1, but control tuning risk does not disappear
  26. H3Service-factor logic is duty-dependent and not directly vendor-comparable
  27. H3Worm self-locking behavior is a boundary condition, not a free safety feature
  28. H3Standards scope and revision status are part of engineering risk
  29. H3Commercial parity remains uncertain without normalized RFQ templates
  30. H3Methodology Table
  31. H3Numeric Evidence and Counterexamples
  32. H3100:1 Decision Basics
  33. H3Performance and Reliability
  34. H3Execution and RFQ
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.