CRCrawlRanker
Back
Scan complete

rollerscrewactuators.com

1 page · 0.5s ·

0/ 100
AI automation score

Mostly AI-generated

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

Post titles follow a templated "How to X: Sizing, Specs, and Procurement Guide" pattern, and the intro copy is generic and uniform ("reduce ambiguity in RFQ, validation, and production release decisions"). The page has no named authors or personality, and the heavy keyword-driven taxonomy suggests programmatic content generation.

70/100Managed
AI Governance

3 governance risks detected

3 medium
What we scanned
Page title
Engineering Guides Insights | Roller Screw Actuator Blog
Meta description
Practical design, sizing, failure-analysis, and lifecycle guidance for industrial motion-control engineers and technical buyers.
Final URL
https://rollerscrewactuators.com/blog/category/engineering
Canonical URL
https://rollerscrewactuators.com/blog/category/engineering
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/blog/category/engineering

Engineering Guides Insights | Roller Screw Actuator Blog

Practical design, sizing, failure-analysis, and lifecycle guidance for industrial motion-control engineers and technical buyers.

  • Title · 56 characters
  • Description · 128 characters
Fine-tune this snippet in the SERP simulator
Shared link card
rollerscrewactuators.com

Engineering Guides Insights | Roller Screw Actuator Blog

Practical design, sizing, failure-analysis, and lifecycle guidance for industrial motion-control engineers and technical buyers.

  • 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
Official guidanceUS Copyright Office — AI and Copyright guidanceCopyright Office — Policy Statement on AI-generated works
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.
mediumAI score ≥ 70 with no strong E-E-A-T signals

High AI content score risks Google Helpful Content penalty

Google's Helpful Content system actively demotes content it classifies as written primarily for search engines rather than humans. A predominantly AI-generated site with low E-E-A-T signals is a candidate for site-wide demotion.

Google Search Essentials — Spam Policies
Official guidanceGoogle — AI-generated content and SearchGoogle — Creating helpful, reliable content
Fix
E-E-A-T improvement checklist
## E-E-A-T Improvement Checklist

Google evaluates Experience, Expertise, Authoritativeness, and Trustworthiness
(E-E-A-T). For AI-heavy sites:

- [ ] Add named author bios with credentials to key pages
- [ ] Link to primary sources for all factual claims
- [ ] Add a clear About page explaining who runs the site and their expertise
- [ ] Publish a clear editorial policy describing your AI use
- [ ] Add schema markup: `author`, `Organization`, `dateModified`
- [ ] Ensure contact information is present and functional
- [ ] Solicit and publish genuine user reviews where appropriate
- [ ] Verify key facts and add human-authored expertise on high-traffic pages
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
  • Strong signalContent

    Blog titles follow a formulaic, keyword-stuffed pattern typical of LLM-generated SEO content

    Evidence
    • “How to Write an RFQ for a Roller Screw Actuator: Sizing, Specs, and Procurement Guide”H3
    • “How to Specify Condition Monitoring and Predictive Maintenance (PdM) for Roller Screw Actuators”H3
    Try this

    Rewrite titles around specific real cases or findings, and add named engineer authors.

  • Clear signalTone

    Intro copy is abstract and contrastive in a generic way, with no author voice

    Evidence
    • “Instead of generic theory, these posts focus on what buyers can send, measure, and approve in supplier communication.”body
    Try this

    Add first-person engineering anecdotes, real project numbers, and a named author.

What's working

Signals of human authorship the page is doing well.

  • Content

    Domain-specific terminology (S1 duty, PdM, RFQ, life calculation) suggests some real subject-matter grounding.

SEO auditExcellent
100/100
AI breakdown by category
  • Content80

    Generic category intro: "Instead of generic theory, these posts focus on what buyers can send, measure, and approve"

  • Structure72

    Programmatic SEO-style taxonomy, 8 categories, colon-laden long titles, and 81 internal links

  • Imagery60

    11 images with full alt text but likely uniform blog card thumbnails; no evidence of real photos

  • Tone80

    Uniform corporate B2B register with no author personality or named individuals

By the numbers
  • Words657
  • Images11
  • Alt coverage100%
  • Images without size0
  • Internal links81
  • External links0
  • Schema blocks2
  • HTML size237 KB
  • Text-to-HTML2%
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
    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 title, a meta description and a canonical link are all present, with exactly one description tag, placed where Google reads it. Their lengths are shown in the report's search preview.

    Fix. Add the missing tags inside the page head and delete any second description tag. Keep images and iframes below your meta tags, because Google stops reading the head at the first one. Treat the title as a headline you'd want to read in a SERP, not a brand slogan.

  • Heading structure
    1 H1, 11 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. A missing H1, or several, blurs what the page is about.

    Passing looks like. Exactly one H1, and at least one H2.

    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 the mobile version of a page. Without a responsive viewport, phones render the page zoomed out, which makes it hard to read and use.

    Passing looks like. A viewport meta tag set to width=device-width. The scan reads the HTML and doesn't render the page, so it can't check touch targets or font sizes.

    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 · 237 KB
    Why this matters

    Why it matters. Response time, page weight and images that load without a reserved size all show up in Core Web Vitals. Slow pages, and layouts that jump as images arrive, cost visitors and rankings.

    Passing looks like. The HTML arrives in under 1.5 s and weighs under 500 KB, the page has fewer than 30 images, and no more than two images lack width and height. These are signals from one HTML fetch, not a PageSpeed Insights measurement.

    Fix. Speed up the server response and trim the HTML. Give every image width and height attributes, or a CSS aspect-ratio, so the layout doesn't jump, and serve compressed images sized to the viewport.

  • Schema markup
    2 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 JSON-LD block is present. The check doesn't validate the block or its types, so test it with Google's Rich Results Test too.

    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 loads successfully, after following redirects. Timeouts and network errors count as broken.

    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. Nearly every image has non-empty alt text. An empty alt="" counts as missing here, even on a decorative image.

    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. H1B2B Engineering Blog
  2. H2Technical checklists, life calculation methods, and engineering guides for high-force linear motion projects.
  3. H2All
  4. H2Best Practices
  5. H2Factory Insights
  6. H2Engineering Guides
  7. H2Maintenance Engineering
  8. H2Buyer Guides
  9. H2Procurement
  10. H2Product Engineering
  11. H2Engineering Guides
  12. H2Recommended Reading Pack
  13. H3Specifying Roller Screw Actuators for Continuous Duty (S1) Applications: Thermal Management and Sizing Guide
  14. H3How to Specify Condition Monitoring and Predictive Maintenance (PdM) for Roller Screw Actuators
  15. H3How to Write an RFQ for a Roller Screw Actuator: Sizing, Specs, and Procurement Guide
  16. H3How to Prevent Premature Fatigue Failure in Roller Screw Actuators: An Engineering Guide
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.