Back
Scan complete

rollerscrewactuators.com

1 page · 0.5s · Scanned just now

0/ 100
AI automation score

Mostly AI-generated

68% 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 follows a near-textbook AI page-builder template: short 2-4 word H2s in rigid template order (Best Fit → Review Before Sizing → Solution Highlights → Use Cases → Implementation Focus → Matrix → FAQ), with listicle triples and flat, uniform prose throughout. Phrases like "clean, repeatable, low maintenance" and "Improve precision, repeatability, and control" are generic marketing-speak with no named engineers, real case studies, or specific data points to anchor the copy as human-written. The 783-word count is modest but sufficient to read the pattern clearly.

70/100Managed
AI Governance

3 governance risks detected

3 medium
What we scanned
Page title
Hydraulic Replacement Actuator Solution | Roller Screw Actuators
Meta description
Review heavy machinery axes for hydraulic cylinder replacement with high-force electromechanical actuators. Review fit, engineering risks, validation evidence, and RFQ inputs for OEM actuator programs.
Canonical URL
https://rollerscrewactuators.com/applications/hydraulic-replacement
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
r
rollerscrewactuators.comrollerscrewactuators.com/applications/hydraulic-replacement

Hydraulic Replacement Actuator Solution | Roller Screw Actu…

Review heavy machinery axes for hydraulic cylinder replacement with high-force electromechanical actuators. Review fit, engineering risks, validation evid…

  • Title · 64 characters — long titles get cut around 60
  • Description · 201 characters — long descriptions get cut around 155
Fine-tune this snippet in the SERP simulator
Shared link card
rollerscrewactuators.com

Hydraulic Replacement Actuator Solution | Roller Screw Actuators

Review heavy machinery axes for hydraulic cylinder replacement with high-force electromechanical actuators. Review fit, engineering risks, validation evidence, and RFQ inputs for OEM actuator program…

  • Open Graph image present
AI Governance
70/100
Managed3 risks detected
mediumAI score ≥ 70 (predominantly AI-generated content)

AI-generated content may not be copyrightable

The US Copyright Office has held that AI-generated content without sufficient human authorship cannot be registered and receives no copyright protection. This means competitors can freely copy AI-generated pages and you lose exclusivity over your content.

US Copyright Office — Copyright and Artificial Intelligence (2023)EU Copyright Directive
Fix
AI authorship documentation guide
## Protecting AI-Assisted Content

To maximise copyright protection for AI-assisted content:

1. **Document human contributions** — Keep records of the prompts used,
   the editorial decisions made, and the human modifications applied.

2. **Edit substantially** — Meaningful human selection, arrangement, and
   creative editing of AI output can establish copyrightable authorship.

3. **Register what you can** — Register works with significant human
   authorship via the US Copyright Office, disclosing AI use as required.

4. **Update your Terms of Service** to address AI-generated content:
   > "Content on this site may be created with AI assistance. We retain
   > rights to the selection, arrangement, and editorial expression of
   > all published content."

See the Copyright Office's [AI guidance](https://www.copyright.gov/ai/)
for current registration requirements.
Pro2 more risks 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.

2 medium
See Pro pricing
Top findings
  • Strong signalStructure

    Rigid 13-H2 template order matches AI page-builder output — every section is 2-4 words and follows a formulaic sequence

    Evidence
    • “Best Fit”H2
    • “Solution Highlights”H2
    • “Risk and Mitigation”H2
    Try this

    Rewrite at least 3 H2s as full questions or specific claims relevant to your product, and reorder sections to reflect how your actual buyers evaluate replacements.

  • Strong signalContent

    Listicle triples with parallel verb-noun structure dominate the page, a hallmark of LLM-generated copy

    Evidence
    • “Eliminate hydraulic fluid leaks and contamination”body
    • “Reduce standby energy use where hydraulic power units run continuously”body
    • “Improve precision, repeatability, and control”body
    Try this

    Replace generic benefit bullets with specific measured outcomes — e.g. actual energy savings percentages, named machine types, or customer-reported results.

  • Clear signalTone

    Uniform engineering-marketing register with no authorial voice, named contacts, or internal anecdotes across all 13 sections

    Evidence
    • “clean, repeatable, low maintenance”body
    • “Review heavy machinery axes for hydraulic cylinder replacement with high-force electromechanical actuators.”body
    • “Target Buyer: Plant engineers aiming to modernize facilities and reduce maintenance, leaks, and idle energy use.”body
    Try this

    Add a short first-person note from an engineer on your team — even one sentence citing a real project challenge — to break the uniform register.

What's working

Signals of human authorship the page is doing well.

  • Content

    Technical specificity in the sizing checklist (bore, rod size, pressure, flow, stroke, pin-to-pin envelope) suggests domain knowledge beyond generic LLM output.

SEO auditExcellent
100/100
AI breakdown by category
  • Content70

    Structured listicle pattern throughout — bullet triples, uniform verb-noun headings, and flat informational prose with no named individuals or specific anecdotes

  • Structure78

    Classic AI-page-builder section order: Hero → Best Fit → Solution Highlights → Use Cases → Matrix → FAQ → CTA, all H2s are 2–4 words long

  • Imagery45

    6 images all with alt text present, but no filenames visible to confirm stock or AI origin; cannot confirm custom photography

  • Tone68

    Uniform engineering-marketing register across all sections — "clean, repeatable, low maintenance" — no voice variation, no personality or authorial presence

By the numbers
  • Words783
  • Images6
  • Alt coverage100%
  • Internal links72
  • External links3
  • Schema blocks4
  • HTML size206 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, 13 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.5s · 206 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
    4 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. H1Hydraulic Replacement
  2. H2Best Fit
  3. H2Review Before Sizing
  4. H2Solution Highlights
  5. H2Common Use Cases
  6. H2Implementation Focus
  7. H2Application Evaluation Matrix
  8. H2RFQ Preparation Checklist
  9. H2Risk and Mitigation
  10. H2Factory Validation Evidence
  11. H2Buyer Decision Notes
  12. H2Recommended Products
  13. H2Buyer FAQ
  14. H2Related Resources
  15. H3Can an electric actuator match the force of my hydraulic cylinder?
  16. H3When is hydraulic replacement not a good fit?
  17. H3What should I send for a hydraulic replacement review?
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.