Back
Scan complete

ndfebshapes.com

1 page · 0.6s ·

0/ 100
AI automation score

Mostly AI-generated

70% 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 repeats the same boundary sentence ("This matches the alias ... as a micro block format") and exposes internal planning language such as "Content gaps closed on June 20, 2026" and "a standalone alias route would create duplicate near-identical N52 magnet pages," which reads like a templated programmatic SEO page. The writing is technically specific in places, which tempers the score, and the imagery is too thin to judge.

50/100Caution
AI Governance· ecommerce

3 governance risks detected

2 high1 medium
What we scanned
Page title
N52 Magnet Calculator | 1/16 x 1/16 & 1/16 x 1/32 Micro Guide
Meta description
Use the N52 magnet calculator to convert 1 16x1 16 n52 magnet and 1 16 x 1 32 n52 magnets, estimate weight and RFQ risk, and review sourcing boundaries.
Canonical URL
https://ndfebshapes.com/learn/n52-magnet
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
n
ndfebshapes.comndfebshapes.com/learn/n52-magnet

N52 Magnet Calculator | 1/16 x 1/16 & 1/16 x 1/32 Micro Gui…

Use the N52 magnet calculator to convert 1 16x1 16 n52 magnet and 1 16 x 1 32 n52 magnets, estimate weight and RFQ risk, and review sourcing boundaries.

  • Title · 61 characters — long titles get cut around 60
  • Description · 152 characters
Fine-tune this snippet in the SERP simulator
Shared link card
ndfebshapes.com

N52 Magnet Calculator | 1/16 x 1/16 & 1/16 x 1/32 Micro Guide

Use the N52 magnet calculator to convert 1 16x1 16 n52 magnet and 1 16 x 1 32 n52 magnets, estimate weight and RFQ risk, and review sourcing boundaries.

  • Open Graph image present
AI Governanceecommerce · 71%
50/100
Caution3 risks detected
highE-commerce site with AI score ≥ 60

AI-generated product descriptions risk FTC false advertising action

FTC Act §5 prohibits unfair or deceptive acts regardless of whether they are intentional. AI-generated product descriptions that contain unsupported efficacy claims, fabricated specifications, or misleading comparisons are fully subject to this standard.

FTC Act Section 5FTC Advertising Guidelines
Fix
Product description review checklist
## AI Product Description Review Checklist

Before publishing AI-generated product descriptions, verify:

- [ ] All specification claims (dimensions, weight, materials) match supplier data
- [ ] Performance claims ("best", "fastest", "most durable") are either removed or substantiated
- [ ] Comparison claims against competitors are accurate and current
- [ ] Health or safety benefit claims are reviewed by a qualified person
- [ ] "AI-assisted" label added if required by platform terms

**FTC standard:** Advertising must be truthful, not misleading, and claims
must be substantiated before publishing — not after a complaint.
highE-commerce site with AI score ≥ 70 and no AI disclosure

AI-generated reviews violate FTC's 2024 Review Rule

The FTC's 2024 rule on consumer reviews explicitly bans AI-generated fake reviews, review suppression, and insider reviews without disclosure. Violations can result in civil penalties up to $51,744 per violation.

FTC Rule on Consumer Reviews and Testimonials (2024)
Fix
Review authenticity policy template
## Review Authenticity Policy

All customer reviews published on this site are from verified purchasers.

We do not:
- Publish AI-generated or synthetic reviews
- Suppress negative reviews
- Offer incentives for positive reviews without disclosure

AI may be used to moderate, summarise, or respond to reviews, but all
review content reflects genuine customer experiences.

_If you believe a review violates this policy, contact [email]._
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
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

    Same boundary sentence repeated across sections, a sign of templated generation rather than authored copy

    Evidence
    • “This matches the alias 1 16x1 16 or 1 16 x 1 32 n52 magnets as a micro block format.”×2body
    • “The alias is answered here because a standalone alias route would create duplicate near-identical N52 magnet pages.”body
    Try this

    Remove duplicated boilerplate sentences and replace internal planning notes with copy written for buyers.

  • Clear signalContent

    Internal process notes leak into public copy, such as a dated 'content gaps closed' heading

    Evidence
    • “Content gaps closed on June 20, 2026”H2
    Try this

    Delete the changelog-style heading and rewrite it as a buyer-facing section title.

  • Clear signalStructure

    Section layout follows a uniform report template with generic H2 labels

    Evidence
    • “Core decision summary”H2
    • “Risk register”H2
    Try this

    Rename generic report sections to specific claims tied to N52 sourcing decisions.

What's working

Signals of human authorship the page is doing well.

  • Content

    Specific technical figures such as 25.4 mm per inch conversion and ±0.05 mm tolerance impact on 0.79 mm thickness.

SEO auditExcellent
100/100
AI breakdown by category
  • Content82

    Repeated boilerplate sentences and internal-process language ("Content gaps closed", "answered here") read as machine-generated SEO copy

  • Structure86

    Tool widget, then uniform H2 sections (Core decision summary, Risk controls, Risk register) in a templated SEO-cluster order

  • Imagery45

    Only 3 images with alt text present; no visible photography or product imagery to judge authorship either way

  • Tone76

    Uniform clinical register with no author voice; same hedged "screening estimate" phrasing repeated across sections

By the numbers
  • Words3,973
  • Images3
  • Alt coverage100%
  • Images without size0
  • Internal links39
  • External links22
  • Schema blocks6
  • HTML size275 KB
  • Text-to-HTML8%
Sentence rhythmUniform — an AI tell

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.

Avg words / sentence55.8
Rhythm variation22%
Vocabulary diversity52%
Sentences analysed8

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.

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 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, 19 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.6s · 275 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
    6 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. H1N52 magnet calculator for 1/16 x 1/16 & 1/16 x 1/32 micro RFQs
  2. H2Convert, screen, and prepare an RFQ-ready N52 magnet spec
  3. H2Content gaps closed on June 20, 2026
  4. H2Core decision summary
  5. H2Alias normalization flow
  6. H2Methodology and calculation boundaries
  7. H2Evidence table
  8. H2Known and unknown boundaries
  9. H2Specification checklist
  10. H2Where N52 helps
  11. H2Procurement tradeoffs after the evidence review
  12. H2Alternatives and sourcing tradeoffs
  13. H2Related specification paths
  14. H2Risk controls
  15. H2Risk register
  16. H2Scenario examples
  17. H2Claims still marked as pending evidence
  18. H2FAQ
  19. H2Source notes and confidence limits
  20. H2Send the canonical N52 magnet RFQ
  21. H3Normalize
  22. H3Screen
  23. H3Bound
  24. H3Validate
  25. H3Highest N52 grade
  26. H3High-coercivity alternative
  27. H3Thicker coating
  28. H3Industrial-only channel
  29. H3Precision tolerances
  30. H3Single low-cost supplier
  31. H3N52 micro block
  32. H3N42/N45 micro block
  33. H3N52 disc magnet
  34. H3Steel cup or keeper assembly
  35. H3Ferrite or bonded magnet
  36. H3Missing dimension in the alias
  37. H3Over-trusting a high grade label
  38. H3Micro-part assembly loss
  39. H3Consumer-accessible magnet hazard
  40. H3Coating thickness stack-up
  41. H3Shipping field accumulation
  42. H3Sensor trigger in molded pocket
  43. H3Tiny closure through paint
  44. H3Consumer-accessible toy or jewelry
  45. H3Bulk industrial assembly
  46. H3Certified pull force for 1/16 x 1/16 x 1/32 in N52 block
  47. H3Flux index for consumer magnet compliance
  48. H3Final coating stack-up
  49. H3Bulk carton air-shipment status
  50. H3Lead time and price stability
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.